 Most Recently Viewed Articles |
 |
A304 - Why can't I hit breakpoints in my Kernel, Uboot or program?
Breakpoints are not immediately set when you put a "bi" command in the BDI or a "break" in GDB. They are set as soon as you hit "go" and are cleared as soon as you stop. This way they do not influence debugging. You will never see the breakpoints in the DBCR0 or DBCR1 registers. For debugging Linux kernels, set the initial breakpoint after Uboot has booted up and before the kernel is loaded. This way Uboot will not clear the kernel breakpoint during its startup. ... |
|
|
P207 - JTAG Exits Check Failed, JTAG Bypass Check Failed
If you get a JTAG Exits check failed message after a JTAG Bypass check message then it means the JTAG Chain is disabled for some reason. The BDI tries to read the bypass register but can't. The message will appear in this sequence In the BDI Telnet prompt.... |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
P202 - Error: JTAG instruction stuff overrun
When in debug mode the PPC4xx fetches normal PPC instructions from the JTAG port. The error "# PPC: JTAG instruction stuff overrun" is raised when the processor stops fetching from the JTAG port, possibly because the processor hangs at an un-terminated memory transfer. ... |
|
Categories
