Table of Contents
Advertisement
Troubleshooting Tips
At some point, you'll run into something strange. We're the first to admit that JTAG-
based run-control and trace are not always deterministic. JTAG is a 30-year hardware
protocol, and when something goes astray at a very low level, SourcePoint tries to (but
sometimes doesn't) recover gracefully. There will be times that the board will power
cycle on its own. Or the firmware thinks that a thread is running but gets out of sync with
the SourcePoint software, which thinks it's halted. Or the DbCStatus.exe ball stays red
instead of turning green, while you swear you have a good DbC connection. Sometimes
you have no choice but to quit SourcePoint and power cycle the target. That usually
clears up the one-of's. But if the issue is repeatable, we ask that you collect as much
information as you can, and open a ticket with us at
https://www.asset-
We'll respond as soon as possible.
intertech.com/support/
.
In the meantime, here are a few errata that we've noticed on the UP Xtreme i11, and
the steps needed to mitigate.
Firmware gets out of sync with software
On the host PC using DCI, functionality is roughly partitioned between software
(SourcePoint application with its GUI) and firmware (lower-level run-control primitives).
Broad-brushing it, SourcePoint software on the host communicates with the firmware,
that encapsulates JTAG traffic into packets which are sent to the PCH, which in turn
performs the JTAG mastering function.
Somewhere along the line, the firmware may get out of sync with the software. You may
see symptoms like:
In the Viewpoint window, the threads are shown as Running, whereas the Status Bar at
the bottom right shows Stopped.
P0 in the Viewpoint window is Running, with one or more threads below it are in the
Stopped state.
If this happens, you'll likely have to quit SourcePoint, kill the AssetDCI process (see
below), power-cycle the target, then start over. Sorry. Then please enter aalog =
20987 in the Command window, and try to reproduce. We're extremely interested in
these cases, so capture the verbose logs in the Log window and send to us.
Trace buffer overflows
DCI traffic processing has its limitations. When you try to collect too much trace data,
the trace buffer overflows, causing aberrant behavior.
©2023 ASSET InterTech, Inc.
32
SourcePoint Getting Started Guide – UP Xtreme i11
Advertisement
Table of Contents
