XJTAG 2.0 Release Notes
New features and enhancements
Please see the Change Log for a list of new features and enhancements in XJTAG 2.0.
XJDeveloper
XJDeveloper is a a new graphical application that enables you to quickly generate the XJEase description of the circuit you want to test.
Simple Drag-and-Drop Interface to set up the JTAG chain and categorise all of the non-JTAG devices in a circuit
Built-in Netlist Explorer – provides a simple interface for you to view the connectivity between devices.
Support for 25 new netlist formats in addition to RINF, EDIF, PADS PCB and PROTEL. New formats include:
- Cadence Allegro
- P-CAD
- Genrad
- BoardStation (Mentor)
- Zuken
- Protel V2
XJEase
Net names are now case sensitive
Consequences: Existing projects with net names which do not match the case of the net names in the netlist file will no longer pass a syntax check.
Connection Test
- Default behaviour is now to test ALL nets for indirect
shorts. Use the connection test option INDIRECT := CONNECTION; if
you wish to only test CONNECTION LIST nets for this. - The Connection Test now handles devices with asymmetric
open-collector and/or open-emitter INOUT pins (pins which drive in
one direction only.)
Deprecated language features
The TEST_RESET section is no longer supported. This section was replaced by the SEQUENCES section as of XJTAG version 1.2.2
Side-by-side installations
The facility to have multiple versions of XJTAG installed on a single PC was added in version 1.3.1. The earliest version of XJTAG that can be installed alongside version 1.3.1, or later, is version 1.2.
It is only possible to have one instance of each major release of XJTAG installed. It is possible, for example to install any variant of version 1.3.x.x along side any variant of version 1.4.x.x; however it is not possible to install two variants of version 1.3.x.x, 1.4.x.x, etc.
In order to allow users of the XJRunner COM interface to upgrade XJTAG without having to recompile their applications, the GUID for this component of XJTAG does not change with each major version of XJTAG.
Consequences: To use the XJIntegration COM object in side by side installations regsvr32 will need to be run when switching between versions in order to make sure the correct version of the other components of XJTAG are used during testing. If one of the versions of XJTAG is removed regsvr32 will again be required to re-register the remaining OCX.
Previous versions
We welcome any suggestions for improving our products. Please contact us with any comments you may have and we will look into incorporating your ideas into a future version.