This error covers a wide range of problems with Lauterbach Trace32 debugger communication
with the Nios® II On-Chip Instrumentation (OCI) core.
A Lauterbach debug script provides additional diagnostic information to narrow the list of possible causes of the problem, allowing further analysis of this failure. The debug script, called lauterbach_system_up_debug_script.cmm, generates data in two files: debug.log and debug.lst.
To launch this script, copy the file to your Lauterbach Trace32 installation directory (C:\T32). From the File pull-down menu, select Run Batchfile, then double-click on the lauterbach_system_up_debug_script.cmm script.
The debug.log file will contain the results of each command executed in the debug script.
The debug.lst file is produced by the trace portion of the debug script. The debug.lst should contain raw data and an up-counting timestamp, if the system is functioning properly.
The debug script and example logs can be downloaded as a zip file: lauterbach_system_up_debug_script.zip
The failed_debug_log.txt is an example debug.log generated by the debug script on a failing Lauterbach connection to a custom board.
The good_debug_log.txt and good_debug_lst.txt files are examples of a successful invocation of the debug script on a Cyclone® III Nios II Embedded Evaluation Kit (NEEK) board with mictor daughter card.
For additional assistance with interpreting the test results in the debug.log and debug.lst, please contact Lauterbach Technical Support. Contact information is available at www.Lauterbach.com