This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

ARM RBL tries to jump to 0x1309c, but target crashes.



Trying to perform NAND boot on ARM Core 0. Set DEVSTAT = 0x106E7. Reset CPU. Step through RBL code.

1) Branches and eventually reads DEVSTAT at 0x120f0

2) Loops through logic to determine boot mode

3) Eventually branches to 0x660

4) Does some comparisons and ends up at 0x6AC "bl #0x1309c"

5) I can disassemble 0x1309c. It shows:

0001309c:   E59FC038            ldr        r12, [pc, #0x38]
000130a0:   E59C0000            ldr        r0, [r12]
000130a4:   E200C007            and        r12, r0, #7
000130a8:   E1A002A0            lsr        r0, r0, #5
000130ac:   E2001001            and        r1, r0, #1

6) When I set a breakpoint at 0x1309c, console issues error message (in red):

"arm_A15_0: Trouble Setting Breakpoint with the Action "Remain Halted" at 0x1309c: (Error -1065 @ 0x3D5A) Unable to access device memory. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 6.0.228.0)"

7) Eventually ends up at 0x6B8, "bxne ". Single step causes console to issue this error:

"arm_A15_0: Trouble Setting Breakpoint with the Action "Continue or Finish Stepping" at 0x6bc: (Error -1065 @ 0x3D5A) Unable to access device memory. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 6.0.228.0)"

8) Ends up branching to these addresses in sequence: 0x0068, 0x075c, 0x0004, then 0x0128. The last address is a "b #0x128" which is a continuous loop