A new major version of XJTAG – version 3.5 – is now available from our website for users who are in maintenance.
Improvements to XJRunner test control
The XJRunner Setup screen, and in particular the list of tests, has received a major re-work. Although the list looks similar, XJRunner testing is now much more flexible, with the ability to add conditions (based on previous tests or the values of variables) to specify whether a particular test (or group of tests) should run.
Selection of tests can now be made from a wider range of functions – functions with input parameters are now eligible to be called as XJRunner tests provided that they are explicitly defined as GLOBAL. The input parameters can again be taken from variables in the running test system if required.
Control of driving/reading pins when accessing busses on Test device is now both easier to control and more fine-grained with the addition of Bus Access controls on a per-test basis.
Connection Test full data output/export
The full data from the automated Connection Test is now available to view from within XJDeveloper/XJInvestigator/XJRunner or from log files. The data can also be exported to .csv format if required. This allows you to see how the automatic fault diagnosis came to its conclusions and also allows you to prove more easily that a particular net took part in the test.
64-bit XJTAG installation
Although XJTAG has supported 64-bit versions of Windows since version 2.3 (in 2009), from version 3.5 XJTAG is now available in both 32-bit and 64-bit full releases. This means that XJRunner integration with 64-bit test executives is now possible, and XJTAG is able to access more of the PC’s memory if required. Make sure you install the correct version of XJTAG to match the architecture of any system you are integrating with.
Side-by-side installations of 32-bit and 64-bit versions of XJTAG with the same major release number (eg 3.5.x) are not possible, though different major releases can have different architecture (ie 32-bit v3.4.x with 64-bit 3.5.x is fine).
Non-TAP XJLink2 pins now used in XJEase
Spare XJLink2 pins which are defined as PIO and with a defined connection to the circuit have been used by Connection Test since version 3.3. This version will now use them in XJEase testing too. They will be used automatically if needed, or the new Bus Access controls on the XJRunner test list allow you to specify times when you wish them to be used explicitly.
do we have some examples or more information on the “Non-TAP XJLink2 pins now used in XJEase” and ” Bus Access controls on a per-test basis” please
Andrew, stay tuned – we’re planning a series of blog posts on all the new 3.5 features over the next couple of weeks.