What is Lauterbach TRACE32?

©1989-2021 Lauterbach GmbH. On-chip Debug Interface. The TRACE32 debugger allows you to test your embedded hardware and software by using the on-chip debug interface. The most common on-chip debug interface is JTAG. A single on-chip debug interface can be used to debug all cores of a multi-core chip.

What is TRACE32 tool?

TRACE32 is a software tool that can assist you with real-time debugging of your Arm based system. TRACE32 can debug any Cortex-based designs and uses Arm CoreSight to help with real-time debugging. TRACE32 is compiler and operating system agnostic, allowing the best fit component, assured of compatibility.

How do I start TRACE32?

To start T32Start, do one of the following: Click the Windows Start button, and then select T32Start. Navigate to the TRACE32 system directory (by default C:\T32\), sub-folders bin\windows or bin\windows64, and then double-click the t32start.exe.

What is JTAG and why is it used?

By providing a mechanism to control and monitor all the enabled signals on a device from a four-pin TAP, JTAG significantly reduces the physical access required to test a board. There are two main ways that this boundary scan capability can be used to test a board.

What is ARM debugger?

Arm Debugger helps you get to the root of software bugs throughout your development process. From device bring-up to application debug, it can be used to develop code on virtual platforms and hardware to help you get your products to market ahead of the competition.

How do I install Lauterbach?

Installing the Lauterbach Trace32 In-Circuit Debugger software

1. For the Product Type, select the ICD In-Circuit Debugger, and then click Next.
2. For the In-Circuit Debugger interface type, select the interface type ICD with PODBUS ETHERNET INTERFACE, and then click Next.

How install TRACE32 on Linux?

In the TRACE32/PowerView GUI (abbreviated ‘TRACE32’ in this manual), you can set the device name in a dialog box that you open via the Misc menu > Interface Config (or via the TRACE32 command line using the IFCONFIG. state command). Once you have set a device name, the option NODE= in config.

Where is JTAG used?

JTAG has been in widespread use ever since it was included in the Intel 80486 processor in 1990 and codified as IEEE 1491 that same year. Today JTAG is used for debugging, programming and testing on virtually ALL embedded devices. With the invention of integrated circuits came the need to test physical interconnects.

Why do we use JTAG?

How do you use a JTAG connector?

To use JTAG, a host is connected to the target’s JTAG signals (TMS, TCK, TDI, TDO, etc.) through some kind of JTAG adapter, which may need to handle issues like level shifting and galvanic isolation. The adapter connects to the host using some interface such as USB, PCI, Ethernet, and so forth.

Is there a way to set a data breakpoint in TRACE32?

In general you can set breakpoints only on local variables (before entering its declaring function), if the local variables have been declared static. (This is not a limitation by TRACE32. No debugger can set a breakpoint on a non-static variable before entering the declaring function.)

What kind of hardware does Lauterbach TRACE32 support?

Our product line TRACE32 ® supports technologies like JTAG, SWD, NEXUS or ETM with embedded debuggers and software and hardware trace. This support is provided for almost 100 cores deployed in over 5000 chip families like ARC, Arm ® Cortex ® -A/-R/-M, Neoverse and Armv9, RISC-V ®, Power Architecture ®, TriCore ™, RH850, Xtensa ® etc.

When does the debugger set the read / write breakpoint?

When the CPU stops at this breakpoint, the debugger sets the read/write breakpoint to the variable. The third command ensures that the read/write breakpoint gets deleted when exiting the function. (Otherwise the read/write breakpoint might trigger on a complete different variable in a complete different function)

How to start TriCore debugger and trace-Lauterbach?

† Start the TRACE32 software to load the debugger firmware. † Connect the debug cable to the target. † Switch the target power ON. † Configure your debugger e.g. via a start-up script. Power down: † Switch off the target power. † Disconnect the debug cable from the target. † Close the TRACE32 software.