Welcome to the XJTAG support 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.
XJTAG version 3.1
A new major version of XJTAG – version 3.1 – is now available from our website for users who are in maintenance. […]
XJTAG Time and Unix Time
This article is a summary of our answers to various customers who have asked us how to convert between XJTAG, Windows and Unix timestamps, so that they can correctly pass data between test systems. […]
XJTAG version 3.0
A new major version of XJTAG – version 3.0 – is now available from our website for users who are in maintenance. […]
XJTAG 2.7: Improved code editors
We are always listening to customers about where they feel the tools could be improved. For XJTAG 2.7 we took this feedback on board and improved the user interface of the code editors in XJDeveloper. These are on the Test Device Files screen and the Circuit Code Files screen. […]
Don’t use EDIF netlists
One of the many netlist formats that XJTAG supports is EDIF 2, an open data exchange format that is widely supported. EDIF stores both netlist and schematic data, but XJTAG only uses the netlist data. It often seems like the obvious choice of format to export from your CAD tool to use in XJTAG. However, there are a number of [...]
COM based XJRunner Integration deprecated
In XJTAG 2.6 we released a new .NET based XJRunner Integration API, replacing the old COM based API that was previously available. Version 2.6 and 2.7 continue to support the COM API, but do not install it by default. We recommend that any new development be done against the new .NET API. […]