XJTAG 4.3 Change Log
This document lists the main changes in each minor release of XJTAG. Please see the Release Notes for a list of breaking changes and other issues for this release.
Changes are often grouped by application. Note that changes grouped under XJRunner and XJAnalyser typically apply to XJDeveloper and XJInvestigator too.
4.3.0
Released 29th June 2026
Main features
- Add support for FTDI JTAG controllers.
- Allow licences to be served from the internet for evaluations.
- Add support for XJLink-PF20 and XJLink-PF40 in Chain Debugger, XJAnalyser and the Manually Create Board wizard in XJDeveloper.
Smaller enhancements and bug fixes
- XJDeveloper:
- Boards Screen: Fix an issue where it was possible for the manually created board wizard to select the wrong netlist on completion.
- JTAG Chain Screen: Allow any number of JTAG chains to be defined without a supporting pin mapping yet defined.
- Don’t automatically open the Add Board dialog when creating a new project or opening a project without any boards defined.
- Prompt to create a different pin mapping type when creating a new project with hardware attached that does not match the default pin mapping type selected in the application options.
- Add an application option to set the default pin mapping type to create for all new projects.
- Fix an issue where selector dialogs were not parented correctly to the Explorer window and closing the Explorer window would leave the main application unusable.
- Improve the amount of diagnostic information in the XJDeveloper actions log file.
- XJAnalyser:
- Remove the ability to import pre-v3.0 projects.
- Do not copy BSDL files from the library if the user opts not to copy them.
- Remember previous device settings when editing the JTAG chain.
- Fix a crash attempting to run with an XJLink type that is not supported by the project.
- Fix a potential crash after editing JTAG chain with constant pins defined.
- Layout Viewer: Ensure the Export, Print and Print Preview dialogs are parented correctly.
- XJLink Manager: Improve saving of application layout settings.
- XJIntegration:
- Change the XJLink.SerialNumber property to be a string rather than a uint, so increment the assembly version to 3.0.0.0 due to the breaking change.
- Ensure that the Runner.OutputFromLastTestRun property is always reset when running multiple functions.
- Fix potential unnecessary memory usage when opening projects and running code in a tight loop.
- Fix an memory management issue in the Single Test Run VI.
- XJPack: Modernise the command-line switches, replacing various switches with a single dash with two dashes, but keeping the old ones for compatibility.
- XJRun: Modernise the command-line switches, replacing various switches with a single dash with two dashes, but keeping the old ones for compatibility.
- XJEase:
- Allow CALL statements with non-constant values for the device reference and function name.
- Allow CALL statements inside test device files.
- Add FUNCTION_EXISTS function to determine if a test function exists for a specific test device.
- Fix GET_DEVICE_TYPE function to return a more consistent value when a device has multiple categorisations.
- Add a method to allow external APIs to print formatted text.
- Add a method to allow external APIs to open files from inside XJPack files.
- Ensure that when constant integer expressions are evaluated by the compiler, the width of the resulting value is consistent with what happens wen evaluating the same expression using non-constant values at runtime.
- Improve error messages for invalid device references.
- Projects: Write all devices onto separate lines in board files, to help viewing diffs and handling merges in source control systems.
- Ensure that the correct build date is displayed in any error log that is generated.
- Installer: Remove standalone Layout Viewer application.
Older versions
4.2 | 4.1 | 4.0 | 3.13 | 3.12 | 3.11 | 3.10 | 3.9 | 3.8 | 3.7 | 3.6 | 3.5 | 3.4 | 3.3 | 3.2 | 3.1 | 3.0
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.
