The embedded tools company

Search FAQs

PDF document ( 27KB / 16-Oct-2019 )

Connect a Nexus Probe to a PowerTrace Unit

Ref: 0197
How do I correctly connect a Nexus Probe to a PowerTrace unit?

A Nexus probe has one, two or three ribbon cables for the connection to the PowerTrace unit.
The PowerTrace has three connectors which are marked with A, B and C. (C is close to the black heatsink)
Nexus probe connectors of newer probes are also marked with A, B and C. Place the appropriate cable into the corresponding connector.
For older probes note the following:

  • Probes with a single cable: connect the ribbon cable to connector C.
  • Probes with two cables: connect the upper cable to connecter C, the second cable underneath to B.
  • Probes with three cables: connect the upper cable to connecter C, the second cable underneath to B and the third cable below to connector A.

An additional JTAG dongle is not required!

Incorrect Nexus-POD CPLD Revision

Ref: 0179
What is the reason for "Incorrect Nexus-POD CPLD revision" message?

There are several reasons for the following message:

Incorrect Nexus-POD CPLD revision - Please call technical support (refer to AREA)

  • A wrong t32xxx.exe has been executed (e.g. Super10.exe for a Copperhead probe). Just use the right SW.
  • The current SW contains a new image for the CPLD on the probe. This reason is very seldom, but it may happen. You have to consider, that it is just a warning and normally you can continue using the debugger. However only for the case, the AREA window shows a similar "expected CPLD revision number". It is recommended to contact the Lauterbach technical support.
  • The probe is defective. This reason can be recognized if the expected CPLD revision number is totally different from the current CPLD revision number, or even 0x00000 or 0xFFFFF. It is a serious reason and requires to send the probe back for repair. Please contact your local support office first.

Missing Address Information on Top of the Trace

Ref: 0263
Is there any reason why symbol addresses and names are not displayed from the beginning of the trace?

The Nexus protocol defines that a full address is transferred only occasionally, just in a Branch-Trace-Sync-Message and Data-Trace-Sync-Message. Most of the time only the significant portion of the current address is generated in the device and transferred in a Nexus message. Therefore the address can only be reconstructed and displayed after occurrence of a Sync-Message in the trace memory. A Sync messages is generated automatically after 255 messages latest.
A single Nexus message without knowing what had happened before is useless!
Look at the Trace.List /NEXUS , then one will see the location of the DTSM . After that location the address information is visible.
A Sync message could be missing on top of the trace in the following cases:
  • Any time Program is running before trace is in ARM state! Normally if analyzer is armed manually!
  • In FIFO mode if trace memory overflows.
  • Selective trace using Watchpoints
  • Selective trace using CTU
  • Some other cases.

Nexus Connector Pinout on Target

Ref: 0311
I don't know exactly which signals from MCU must be connected to which signal on the AUX-port connector. Must certain signals be crossed ?

Not at all. The pin out one can find in the manual and at our home page, fits the description of Nexus standard from the target point of view.
With other words, you have to connect the signals from the device to the appropriate signals with the same name on the connector. You
must not take care about signal crossing.

Copyright © 2019 Lauterbach GmbH, Altlaufstr.40, 85635 Höhenkirchen-Siegertsbrunn, Germany   Impressum     Privacy Policy
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: 16-Oct-2019