XJTAG 3.12 expanded the capability of the Signal Integrity Analysis in XJTAG tools, adding the ability to suggest certain causes of error. This post continues from the previous post on this subject, and describes further errors that XJTAG tries to identify. […]
XJTAG 3.12 has extended the functionality of the Find and Replace dialog that is accessible when viewing XJEase or BSDL code files. […]
In XJTAG 3.12 we have expanded the capabilities of our Signal Integrity testing. Rather than simply reporting any errors found in the attempted scans, it will now inspect those errors and suggest possible causes. […]
Some devices need more than a standard Test Reset sequence to enter the state when they behave as described in their BSDL file and boundary scan can run. Infineon’s Aurix TriCore TC3xx microcontroller family is one such group. […]
With XJTAG 3.11 we’ve made some improvements for working with projects that use the Dynamic Chains feature. Previously, the Analyser, Debug Connection Test, and the Chain Debugger feature would always use the default profile for your project. Using a different profile for these features would require you to manually change the default profile in XJDeveloper. Now, in XJDeveloper, the required profile may be selected independently on each screen, via a drop-down selection menu. […]
XJTAG 3.10 adds a control that allows the default values of XJEase global variables to be overridden. In XJDeveloper, clicking on ‘Options’ at the bottom of the test list on the Run Tests screen now includes a Set Global Variables tab: […]
For many years, the XJEase language has had the READABLE and WRITEABLE built-in functions. Their purpose is to try to work out whether it’s possible to read or write a pin before trying to do so. […]
Version 3.8.3 of XJTAG comes with some usability updates for the new XJEase Waveform Viewer. Tool tip information, event labels, and a context menu for pin navigation and source tracking has been added. […]
From XJTAG version 3.8, the XJEase debugger in XJDeveloper now comes with a Waveform View providing more information about the XJEase code being executed. The XJEase Waveform View is designed to show you what your tests actually did in a style similar to that of a logic analyser, however instead of the bottom axis representing time, it shows the number of scans since the start of the capture. […]
The blog article ‘Debugging Connection Test – part 1 (Updated)’ discusses how to use ‘Debug Connection Test’ to identify a missing disable value. However, if a disable value is set to the wrong value, i.e. low rather than high, then it could prevent the Debug Connection Test from running at all. In this case, XJDeveloper’s Analyser screen can be used to help locate the issue. […]