Welcome to the XJTAG blog
This is your go-to space for tips, insights, and updates straight from the XJTAG development and support team. We’re here to help you get the most out of your XJTAG system by sharing our knowledge, experience, and best practices. You’ll find posts highlighting particular features of the different software packages that make up the XJTAG development system or aspects of the XJEase language.
Have a topic you’d like us to cover or a question you want answered? Let us know!
For product updates check out the Updates Hub.
Categories for selectors in XJDeveloper – part 1
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.
Archiving XJDeveloper Projects
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 [...]
Highlights of the 2.3 Release
This post outlines what is new in the 2.3 release. Some aspects will be explored in more detail in future entries. […]
Debugging Connection Test – part 3
Solving common Connection Test problems There are several types of error found by Connection Test which regularly (and unsurprisingly) confuse users. This article tries to help out… […]
Netlist Formats
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. […]
Debugging Connection Test – part 2
Understanding the connection test output When Connection Test finds an error on a board it tries to ascertain what the problem is. This may involve carrying out additional checks, to try to eliminate noise on a floating net or cross-talk as a cause of the behaviour. If the fault appears to be genuine then the Connection Test reports the error. [...]