FAQs for Debugger Hardware
|How can I use multiple USB devices with several TRACE32 instances?|
More than one Lauterbach USB device can be used at the same time from the same host.
For each USB device, a TRACE32 instance needs to be started.
To use multiple USB devices with one PC or workstation, you need
|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.
|Ist 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 debugger_user.pdf. 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.
|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.
|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:
|Why does my TRACE32 software version not work with PowerDebug PRO or PowerTrace PX?|
If you get an error message like
"Fatal error: This software is too old to use this Lauterbach Hardware. Use more recent software!"
"FATAL ERROR from PODBUS-driver: TRACE32 USB device not connected".
Please check whether the used TRACE32 software fulfills the requirements below.
PowerDebug PRO is the successor of PowerDebug-II.
This kind of new hardware module requires at least TRACE32 software revision 58927 from 11/2014.
PowerTrace PX is the successor of PowerTrace.
This kind of new hardware module requires at least TRACE32 software revision 59808 from 11/2014.
The TRACE32 USB driver must be updated too.
Copyright © 2019 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: 05-Dec-2019