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 1.4 Release Notes

    New features and enhancements

    XJRunner COM Interface

    A new property has been added to retrieve the XJLink serial number being used.

    Consequences: The minor-version of the COM object has incremented – If you have developed your own LabView applications you will need to re-reference all instances of the OCX.

    A new extended and improved LabView example has been added.

    The XJRunner COM Interface has been improved to support multiple instances running in a single process

    XJIO

    There is a new section in the help files that details to configuration and use of the XJIO board. This also includes a worked example.

    New Warnings

    As XJTAG is improved and new features added, certain features may become deprecated or replaced with better or more flexible features. XJTAG will start to issue warnings about older code making use of such features once a major release has passed. This version of XJTAG may therefore generate warnings on existing code that were not generated on previous versions.

    Examples of new warnings that might be generated:

    Warning 025: <file.xje>: Cannot write to bit <x> (pin <number>) of pin/bus <bus> on device <device>
    Warning 026: <file.xje>: Cannot read bit <x> (pin <number>) of pin/bus <bus> on device <device>
    XJTAG now checks more thoroughly that pins you use in your device file or in the DISABLE DEVICE section are actually accessible.
    Warning 050: <file.xje>: Use of READ, WRITE and BIDIR in the TEST COVERAGE section is deprecated.
    Since version 1.3.1, there is a new syntax for describing test coverage. Please see the TEST COVERAGE section in the help file for more information.
    Warning 050: <file.xje>: ‘USE <file.pdd> FOR <component>’ in the ‘CONNECTION LIST’ section is deprecated. Use ‘<component> := <file.pdd>’ instead.
    This syntax has been phased out in favour of a simpler and more consistent syntax.
    Warning 084: The BSDL file for component <component> specifies that some pins are internally pulled high or low. Specify INTERNAL_PULLS := TRUE on the device to test the se during connection test (or FALSE not to see this warning).
    The XJTAG Connection Test can now automatically test pins that are internally pulled inside JTAG devices.

    Installation locations

    The install locations of various files have changed to make running XJTAG as an unprivileged user easier. Any files or directories that need to be written by the user have been moved from under <Program Files>\XJTAG 1.3.1 to <Documents and Settings>\All Users\Documents\XJTAG 1.4.

    There is a shortcut installed in the XJTAG Start Menu folder to this new location.

    XJRunner COM Interface

    An ActiveX/COM control called XJIntegration is now included that exposes the functionality of XJRunner, allowing third party applications to include the ability select and run tests.

    Connection Test

    The system will now test internal pull resistors as specified in a device’s BSDL file.

    The Connection Test error reporting is also improved:

    • The debug output is improved to show more clearly which tests found a fault.
    • The Connection Test will attempt to identify the pin that is at fault when there is an open detected.

    XJEase

    • PADS PCB 2005 netlists now supported.
    • General XJEase execution performance has been improved.
    • XJEase code can be put into additional code files, so functions can be shared between device files and the device file preamble can be completely separated from the XJEase code if desired.
    • Boards can be defined in a separate file if required, which means board definitions can be easily shared between projects or duplication eliminated if a multiple instances of a board are used in a design.
    • Functions with a single return parameter can be used directly in an expression.
    • Function parameters can now have an explicit WIDTH specified.
    • Addition of the BREAK keyword to exit loops early.
    • Addition of GETFREQ and SETFREQ keywords to contol the TCK frequency in raw JTAG blocks.
    • Addition of READABLE and WRITEABLE functions to check for read or write access to a bus at runtime.
    • Add an optional exit code to the EXIT keyword and an optional exit code to the CircuitTest function. This value will be returned from XJDebug as an exit code.
    • The system now checks that TCK and TMS are correctly routed to all JTAG devices and will emit a warning if not.
    • The system now checks at compile time whether pins used in a SET statement are accessible and emits a warning if they’re not.

    XJAnalyser

    Devices can now be put into many other instruction modes apart from EXTEST or BYPASS, e.g. SAMPLE, INTEST, HIGHZ, CLAMP.

    XJDebug

    An option has been added to display at runtime which JTAG pins are being used to read/write non-JTAG pins.

    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.0.0.

    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.

    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.