XJTAG 2.0 Change Log
This document lists the main changes in each minor release of XJTAG. Please see the Release Notes for a list of major changes that came with version 2.0.
Version 2.0.11
Released 14th April 2008
- Connection test: under certain circumstances it was possible while identifying possible shorts for the connection test to write to nets that the user had specified as constant nets.
Version 2.0.10
Released 8th April 2008
- XJEase: fix running of XJEase functions from a test reset sequence.
Version 2.0.9
Released 25th March 2008
- Installer:
- Fix installation of the driver after a previous version of XJTAG has been uninstalled.
- Fix help file installation for XJAPI installation.
- Better at removing files when uninstalling.
- XJEase examples: Improved flash tests.
Version 2.0.8
Released 19th March 2008
- XJDeveloper
- Net names in functional tests were being incorrectly quoted.
- Fix crash when exploring a bus that contains the same pin twice.
- Fix use of non-core netlist files, e.g. GenCAD.
- Fix crash on JTAG chain screen when invalid TDI specified.
- Fix crash when trying to save a device file that is opened in another application.
- XJEase: Don’t drive any pins on the XJLink connector until code is actually run.
- XJAnalyser: Fix loading of projects that contain items in the watch.
- XJEase examples: New flash tests.
- LabView integration example: Modify to be re-entrant and allow multiple instances.
Version 2.0.6
Released 13th February 2008
- Connection Test:
- Fix the incorrect driving of constant pins in some circumstances.
- Fix potential false positives in some circumstances with BIDIR pins with common controls.
- XJEase: fix problems calling XJRunner test functions from other test functions.
Version 2.0.5
Released 1st February 2008
- Fix crash in the Connection Test in some circumstances when diagnosing potential shorts.
Version 2.0.4
Released 28th January 2008
- XJEase: minimise time spent in SAMPLE on first JTAG access, since SAMPLE gives JTAG devices control of the pins.
- XJEase: write all data out to the JTAG chain immediately at the end of a TRST sequence to prevent timing problems.
- PADS PCB: Add v2007 support.
Version 2.0.3
Released 4th January 2008
- XJDeveloper:
- Fix crash when an intra-board connection is put in the inter-board connection list and then the netlist is modified and reloaded.
- Fix crash when removing a board whose name differs only in case from another board.
- XJPack: fix problems packing additional code files that are not in the same directory as the circuit file.
- Connection Test: fix incorrect errors being reported in some cases with constant pins and common controls.
- Add support for Orcad “Wire List” netlist format.
- Add support for PADS 2000 netlist format.
- XJEase: fix crash with two EDIF netlists in a single project.
Version 2.0.2
Released 30th November 2007
- XJDeveloper:
- Ability to rename and reorder XJRunner Tests and Functional Tests.
- DFT: Fixes to printing and exporting where untested and functionally tested pins were swapped and case where nothing was printed out when selecting boards.
- XJAnalyser: Fix crash on failure to parse a BSDL file.
- Installer: Stop the installer launching and not being able to find xjtag.cab in XJAnalyser wizard.
Version 2.0.1
Released 12th November 2007
- XJDeveloper:
- When creating a new project, the system now creates an empty CircuitTest function in its own additional code file rather than in the main circuit file.
- Fix problem with PDD files with forward slashes in their filenames.
- Improved capture of comments when importing projects.
- Several pinmapping/TRST sequence fixes.
- Now open netlist files readonly, so that they can still be opened when held open in another application.
- Fix crash when doing JTAG chain auto discovery on a brand new project with just a netlist added.
- XJEase: It is no longer an error to connect a power net to a pull net, or to pull two power nets – generate a warning instead.
- DFT: fix DFT statistics when using -c command line switch.
- Installer: install TextPad syntax files on demand for each user on a machine.
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.
