FAQs for Debugger Hardware
|How can I use multiple USB devices with several TRACE32 instances?|
If you need to debug with more than one PowerDebug module connected to the PC or workstation via USB, you can address these using their device name in the configuration file (e.g. config.t32). The option NODE=<device_name> in the configuration file tells TRACE32 to connect with the specific ‘named USB device’ that you want.
PBI= USB NODE=my-dev-001The device name can be set in TRACE32 PowerView using the menu Misc > Interface Config or by calling the command IFCONFIG.state from the TRACE32 command line.
Please refer to the TRACE32 Installation Guide for more information
|How to force a connection to a PowerDebug which is already in use?|
If you see a dialog box with the message "TRACE32 device already in use" then one of the following has happened:
1. You've started TRACE32, while another TRACE32 GUI is still exclusively connected to the same PowerDebug box.
2. TRACE32 PowerView was previously not properly closed (e.g. killed or crashed).
3. You have started a second TRACE32 for an AMP multicore scenario, but the second GUI wasn't configured with CORE=2 or the first GUI wasn't configure for CORE=1.
In case of issue 1 & 3 you should click NO. If you click YES, you will crash the already running TRACE32 GUI.
In case of issue 2 you could safely click YES.
If you want TRACE32 to automatically "click" NO , to immediately close the new TRACE32 session, use the statement CONNECTIONMODE=AUTOABORT in the PBI= section of your TRACE32 configuration file (usually "config.t32").
If you want TRACE32 to automatically "click" YES , to force connection to the PowerDebug box by resetting it, use the statement CONNECTIONMODE=AUTOCONNECT in the PBI= section of your TRACE32 configuration file.
Please refer to the "TRACE32 Installation Guide" for mode information.
|Is it possible to debug with two debug boxes and two debug cables two processors over one single JTAG connector?|
Yes this is possible using a Y-Adapter. Please refer to "Configuration 3: Two (or more) PowerDebug Modules" in "ICD Debugger User's Guide". However, this setup is quite error prone and electrically sensitive. An approach with two licenses in one single debug cable is thus recommended.
Essential things to check:
The JTAG "bus" is used as shared resource using a TriState technique. This is why the JTAG lines must have proper pullup/pulldown.
|Is it possible to use both uTrace connectors, A and B to debug two targets?|
Only connector A of the uTrace can be used together with a whisker cable for debugging.
Debugging two targets using two whisker cables is only possible with the CombiProbe. The standard configuration of the uTrace is with a MIPI20T whisker cable plugged to connector A. The extended configuration is to add a TRACE32 Analog Probe plugged to connector B via a Converter uTrace to PI-Analog Probe. The TRACE32 Analog Probe enables an energy profiling of your application.
|Should I use one or two power supplies, USB/Ethernet cables when two Lauterbach debug modules are connected together via PodBus?|
Debug boxes connected via PODBUS SYNC synchronize their clocks and can trigger each other. However each box needs its own power supply and sepaerate USB cable or Ethernet connection to the PC. In t32start each debugger is configured as a separate PodBus Device Chain.
Debug boxes connected via PODBUS IN build one chained debug system, where the first box is the master. All boxes use the same clock, triggers, power. Only the first box should be connected to the PC. In t32start all debuggers are added to the same PodBus Device Chain.
|What is the operational temperature range of TRACE32 hardware tools?|
The TRACE32 tools are designed for a temperature range of about +10°C to +40°C. Tools may work below or above that range, but we can not guarantee proper operation.
|What kind of power supply should I use with my PowerDebug/PowerTrace module?|
When your TRACE32 hardware is delivered, you will receive one of the following power supplies:
|Why do I get the error message "Plugged debug cable is not suitable for CPU"?|
In general you get the error message "Plugged debug cable is not suitable for CPU", when the started TRACE32 application is not supported by the debug cable plugged to your PowerDebug.
E.g. The "PowerPC-4xx Debug Cable" is not suitable for "TRACE32 for ARM" (t32marm.exe)
Please start the correct TRACE32 application or connect the correct debug cable to your PowerDebug.
As a special case, you also get the error message "Plugged debug cable is not suitable for CPU" if you use TRACE32 R.2018.02 or older and you use a new debug cable that is not yet supported by that version:
Copyright © 2020 Lauterbach GmbH, Altlaufstr.40, 85635 Höhenkirchen-Siegertsbrunn, Germany
The information presented is intended to give overview information only.
Changes and technical enhancements or modifications can be made without notice. Report Errors
Last generated/modified: 10-Jan-2020