Configuration variables in XJTAG allow settings to be configured for a device. For example the address of an IIC device may need to be defined. Configuration variables are associated with a test device file, and in previous versions of XJTAG were only available in device files from the XJEase library. From XJTAG 3.9 configuration variables [...]
Version 3.8.3 of XJTAG comes with some usability updates for the new XJEase Waveform Viewer. Tool tip information, event labels, and a context menu for pin navigation and source tracking has been added. […]
From XJTAG version 3.8, the XJEase debugger in XJDeveloper now comes with a Waveform View providing more information about the XJEase code being executed. The XJEase Waveform View is designed to show you what your tests actually did in a style similar to that of a logic analyser, however instead of the bottom axis representing [...]
From XJDeveloper 3.6 a new BOM data type is available in the BOM Import dialog, the “Unfitted” device field. Any devices with an entry in a column assigned to this are suggested under the “Suggested Unfitted Devices” category on the Categorise Devices screen. […]
There are new global functions in XJTAG 3.6 which are always available to use (like the built-in Connection Test). The functions RUNSTAPL and RUNSVF allow users to run programming files without having to write any further XJEase to enable this. […]
From XJTAG 3.6 onwards the suggested device categories on the Categorise Devices Screen have been renamed and expanded, with separate categories for different types of resistor packs. In addition, the “Suggested Resistors – Other” category now displays the reason for any resistor’s inclusion using a separate “Reason” column, to make the inclusion of a device into this category easier to understand. [...]
From XJTAG version 3.6.0, you can store multiple variables of the same type in an array structure. Arrays are supported for the types INT, STRING and FILE. […]
From XJTAG version 3.6, the XJEase debugger in XJDeveloper now comes with a Call Stack window providing more information about the XJEase code being executed. […]
Until now, XJRunner tests have been limited to functions which have no input arguments and a single return argument (which returns the result). XJTAG v3.5 relaxes that restriction, allowing input in XJRunner tests, though there is still a requirement to have a single return argument for the result. […]
Alongside other improvements to the XJRunner test setup, XJTAG v3.5 has a new interface to specify bus access from the test system using the XJRunner Setup screen. When you edit a test there is now a Bus Access tab on the dialog, which allows full control of which pins are used to read and/or write [...]