Specifications

80 System Software Diagnostics Guide — September 2006
Dlgsnapshot Reference
When boards are downloaded and you run Dlgsnapshot manually, a question is posed about
running diagnostic firmware. You must confirm that you want Dlgsnapshot to stop the running
board and download diagnostic firmware.
Each core dump file is named according to the type of fault detected and the date/time the fault
occurred. The naming convention of the core dump files is
faulttype_MM_DD_YY HH_NNxx_MS
where:
• faulttype denotes the type of fault (CPDump, SPDump, Counter [Windows only], or Driver
State)
• MM is a two-digit number indicating the month
• DD is a two-digit number indicating the day
• YY is a two-digit number indicating the year
• HH is a two-digit number indicating the hour
• NN is a two-digit number indicating the minute
• xx indicates whether the fault occurred din the AM or PM
• MS is a number indicating the milliseconds
Note: If multiple DSPs on the same board generate a fault, the core dump file will only contain
information about the DSP that generated the initial fault.
Following are some examples of file names:
• CounterDump_11_03_2003 03_13PM_35
• StateDump_11_03_2003 03_13PM_35
All the dump files have a *.txt extension except the SRAM dump in Windows, which has a *.bin
extension.
15.3 Options
This section contains the following information:
• Enabling Autodump
• Running Dlgsnapshot on Demand
• Command Line Options
15.3.1 Enabling Autodump
If you want to enable autodump, open the dlgproductagent.cfg file located in the cfg directory and
uncomment out the following line:
DIAGNOSTIC_AGENT = libdlgdm3diagagent
The default looks like this (the line you must change is in bold):