• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 1550 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Reading internal SRAM with openocd

Gerard Green
Prodigy 30 points


Hi,

I am connecting to an am335x sk board with openocd and GDB

I can examine internal SRAM at  0x4030 0000.   

(gdb) mon mdb 0x40300000 4

0x40300000: 40 00 00 00

When I try to examine SRAM at 0x402f 0400 I get an error

(gdb) mon mdb 0x402f0400 4
JTAG-DP STICKY ERROR
MEM_AP_CSW 0x2800060, MEM_AP_TAR 0x402f0400
Block read error address 0x402f0400, count 0x4
in procedure 'mdb'

Can anyone suggest what the problem might be ?

thanks in advance

Gerard Green

  • 0
    TI__Mastermind 44306 points

    Gerard,

    make sure your MMU has that memory range configured. 0x402f is another 1MB block than 0x4030.

    Are you really running Starterware inly? I assume gdb requires Linux.

    Regards,

  • 0 in reply to Frank Walzer
    Prodigy 30 points

    Frank,

    Thanks for responding. I am using Starterware only although this problem is evident before Starterware is even loaded.

    This problem happens immediately after I ask openocd to reset the processor.

    According to the output from openocd, the MMU and both caches are disabled.

    regards

    Gerard Green

  • 0 in reply to Gerard Green
    TI__Mastermind 44306 points

    Gerard,

    so maybe I misunderstood... you run gdb/openocd as JTAG emulation tool on your host? The connected target software is Starterware?

    But if you have an emulation issue the target software shouldn't matter as usually JTAG has direct access. But I am not an emulation expert and no experience with openocd as we use the TI CCS debuggers only. Maybe you need to modify any openocd config file for the target so it knows about that memory region and how to access it. Apparently 0x4030 block is configured but that is L3 SRAM. 0x402F is inside the ARM core block.

    I assume you should ask for help in the AM3xx forum...

    Regards.

  • 0 in reply to Frank Walzer
    Prodigy 30 points

    Frank,

    You are correct, I am probably on the wrong forum. Further testing tells me that you may be correct and this may in fact be an openocd config error or operator error (or less likely bug).

    So I'll pop over to an openocd forum and see what I can find.

    thanks for your help

    Gerard Green