The DFT Analysis screen in XJTAG version 2.4 has been completely redesigned to allow you to assess the test coverage of your circuit design more easily and in a more efficient way. This post highlights the most important new features. […]
We asked one of the guys in-house who works with XJDeveloper most of the time to give some tips from his experience of setting up projects, and here is what he came up with: […]
A frequent question from customers is, “Why is my new XJEase test function not listed when I create an XJRunner test?” XJEase Functions For a function to be eligible to be made available to XJRunner it must be in the main project (.xje) file or a device file, or in a code file specified either in the main project (in the Circuit Code Files Screen) or from within a test device file (in the Test Device Files Screen). […]
Part 1 of this series explained how to add or edit the categories for the selectors in XJDeveloper. This entry will focus on using BOM (Bill of Materials) information in the selectors, using the demonstration board that comes with the XJTAG development system as an example. […]
This post discusses the selectors in XJDeveloper and how you can customise them. Selectors are used whenever you have to select either a Net or a Device. Entries in a selector are grouped into categories that can be customised.
There are two ways to export projects from XJDeveloper either exporting to an XJPack or a zip file. Both options are found on the File -> Export menu in XJDeveloper. XJPack files are used by XJRunner in production. When you have finished creating your project in XJDeveloper, “pack” it and then this file can be used in production. Zipping a project will create a single zip file that contains all the files used by the project. This can be useful if you are sending a project to another department, or for creating regular backups of your project. […]
In versions of XJTAG prior to 2.0, the system supported just four netlist formats: RINF, EDIF 2, PADS PCB and Protel. The parsers for these netlists were written carefully against specifications for the formats where possible, and so should reliably parse all valid netlists in those formats. […]