
PowerTrace Serial User´s Guide
38
©1989-2018 Lauterbach GmbH
3. Check
Double-check that the trace connector is properly connected to your target and that the orientation is correct.
For trace port sizes with more than 6 lanes, Serial Port 1 must be used.
4. Check
Did your debugger remain in control over the target at all times when attempting to capture a trace? Error
messages such as “
emulation debug port fail
” indicate that the debugger lost control over the target. In
case your debugger lost control over the target:
•
Is there a separate JTAG connector on your target?
If available, connect the debug cable directly to this connector. Ensure that the JTAG signals are
routed to only one connector, either trace connector or debug connector. Y-routing of signals will
decrease signal integrity by reflections.
•
Are all supply voltage levels stable when the trace port is active?
Double check your targets supply voltage.
•
A debug port fail can also happen in case of trace decoder errors based on inconsistent or
damaged trace data. Clear the trace buffer and try to single step instructions. Do you see them
displayed in the trace list window correctly?
5. Check
Some CPU types do not have dedicated trace port pins. Instead trace signals are multiplexed with other
signals (e.g. SATA and Aurora). A special port pin setup may be required to get trace functionality. Check
your CPU manual for the correct port pin configuration.
6. Check
In case of shared trace pins, additional buffers (e.g. PCIE switches) may be used on the target hardware.
Make sure that these buffers are enabled and configured correctly.
Advanced target applications might use more than one initialization procedure
or the setup might change during run time again. Make sure that the trace port
is actually enabled when attempting to trace.