XJTAG logo
Shopping cart button Open search box button

XJTAG Support
▶ Getting started with XJTAG
▶ Downloads
Release Notes
Change Logs
Download Archive
▶ XJEase
▶ Application Notes
▶ Discontinued Products

XJTAG 3.11 Release Notes

New features and enhancements

Please see the Change Log for a list of new features and enhancements in XJTAG 3.11.

Board file format changes

Previously, not all information about a board was stored in the board file; various bits of data, including notes about devices, the BOM filename and the schematic filenames were stored in the main .xjd project file. Now it is possible to include all the information about a board in the board file. This new format is not used by default, however, to retain backwards compatibility. The new format will be used at the point that the project becomes incompatible with older versions for some other reason.

Idcodes Command Line Utility

The idcodes command line utility has been removed in XJTAG 3.11. All of its functionality is provided by the JTAG Chain Debugger.

XJLink pin behaviour in XJRunner XJIntegration

XJRunner Integration has changed how it handles the XJLink before and after running tests:

  1. When a Runner object is created the pins of the chosen XJLink are placed into a high-impedance state. The pin mapping is only applied when the first test or function call begins. This brings it more in line with how XJRunner configures the XJLink.
  2. When disposing a Runner object the pins of the XJLink will be placed back into a high-impedance state. While the XJLink is in this state, it is still available for use by the host application, but won’t be available to any other process. The XJLink will remain in this state until it is either used again within the application, the XJLink object is disposed, or XjtagSystem.Close() is called. Previously the XJLink pins would have been left unconfigured and floating, meaning that it could place a load on the board under test and cause issues with other test equipment.

Supported Platforms

XJTAG is supported on both the 32 and 64 bit variants of the following operating systems: Windows 7® Service Pack 1, Windows 8.1®, Windows 10® 1607 (Anniversary Update) and later, and Windows 11®.

This version does not support Windows XP or Windows Vista, Windows 8 or Windows 10 1507 or 1511 (November Update).

XJTAG recommends a screen resolution of at least 1024×768.

XJTAG requires a processor that supports the SSE2 instruction set. This includes every Intel processor since the Pentium 4 and every AMD processor produced since the end of 2003. See this blog post for more details. This requirement was introduced in version 3.1.

Target Hardware

In order for XJTAG to interact with a circuit, the JTAG chain must be set up properly. To help with this, we have a produced a set of DFT guidelines. There is also a troubleshooting section in the help files.

Side-by-side installations

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 3.4.x along side any variant of version 3.5.y; however it is not possible to install two variants of version 3.4, e.g. 3.4.3 and 3.4.4.

Changing Project File Associations

By default, double-clicking on an XJTAG project file of any kind will open it in the most recently installed version of XJTAG. The Version Check utility (XJVersion) can be used to control these file associations. It is recommended to do this using the copy installed with the latest version of XJTAG that you have installed.

Previous versions

3.10 | 3.9 | 3.8 | 3.7 | 3.6 | 3.5 | 3.4 | 3.3 | 3.2 | 3.1 | 3.0 | 2.7 | 2.6 | 2.5 | 2.4 | 2.3 | 2.2 | 2.1 | 2.0 | 1.4

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.