56303 | 563xx | 5680 | 56805 | 5680x | 56F80 | 56F800DEMO | 56F805 | 56f807 | 56F830 | ADC | Bootloader | Codec | CodeWarrior | CW5 | CW6 | Debugger | DSP56303 | DSP56303EVM | DSP563xx | DSP5680 | DSP56800 | DSP56807 | DSP56858 | DSP56858EVM | DSP56F803 | DSP56F805 | DSP56F807 | DSP56F80x | DSP56F826 | DSP56F827 | DSP56F8xx | EVM | FFT | Flash_over_jtag | GPIO | Interrupt | Interrupts | JTAG | LCD | Linker | MCF5307 | Metrowerks | Modulus | MSCAN | PCMaster | PWM | Quad | Rif | RTOS | SDK | SPI

One of the great features of the DSP 568xx is that its JTAG has FIFO dump of the last 5 jumps (jsr, braches, etc), so it is easier in case of error to debug the sequence that lead to this error. However this can be done only when the debugger (CodeWarrior) is connected. Does anyone know how to get it without debugger? I would like, just before a critical error occurs, to be able to analyze the stack in order to get the functions/memory locations that did the jumps that lead to this error and save those jump in the flash, so I will be able to analyze them offline, after the error occurred (and the system probably reset itself) Does anyone know how to analyze the stack trace to know the jump/branches that exist in the stack, or know how to read the JTAG FIFO dump of the last jumps internally without the debugger? Thanks Tomer

(You need to be a member of motoroladsp -- send a blank email to motoroladsp-subscribe@yahoogroups.com )

Tomer- > One of the great features of the DSP 568xx is that its JTAG has FIFO > dump of the last 5 jumps (jsr, braches, etc), so it is easier in case > of error to debug the sequence that lead to this error. > > However this can be done only when the debugger (CodeWarrior) is > connected. > > Does anyone know how to get it without debugger? I would like, just > before a critical error occurs, to be able to analyze the stack in > order to get the functions/memory locations that did the jumps that > lead to this error and save those jump in the flash, so I will be > able to analyze them offline, after the error occurred (and the > system probably reset itself) > > Does anyone know how to analyze the stack trace to know the > jump/branches that exist in the stack, or know how to read the JTAG > FIFO dump of the last jumps internally without the debugger? If you can't find info in the documentation about a register or memory-mapped FIFO address that you can read directly from DSP code, then it may be something available only through JTAG commands; i.e. using JTAG lines. Of course, it might be available from DSP code but left undocumented... -Jeff

(You need to be a member of motoroladsp -- send a blank email to motoroladsp-subscribe@yahoogroups.com )