• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 54 subscribers
  • Views 371 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.

DSP cannot access any memory

jc-ti
Mastermind 27585 points

Other Parts Discussed in Thread: OMAP-L138

I'm using CCS5.1.0.06000 with OMAP-L138 target configuration. On all boards I have tried, I can connect to the ARM and run everything fine. However when I connect to the DSP, I cannot load any code or view any memory locations. The disassembly shows up as "Driver did not attempt to read memory at ...." and the Memory Browser shows "XXXXXXXX" for all locations. See attached picture.

Any idea on what could be going on? I'm using the XDS510 USB emulator.

Jeff

  • 0
    TI__Guru**** 171729 points

    Jeff,

    I suppose the MMU is disabled in the ARM, is that so? If not, I imagine the device will prevent the emulator from having access to specific memory locations - especially the 0x80000000 shown in the screenshot, which resides in internal shared memory.

    That said, I am not sure why the DSP ROM memory can't be read (address 0x00700000), but are you sure you are using the proper GEL file for this core as well? It sets the memory map for this device and that could be causing some issues.

    Also, can you try to see if you get the same results if you try to access the DSP exclusive RAM memory at 0x00800000?

    An additional idea is to try to reduce the JTAG clock speed (to 10.368MHz) of the emulator and thus allow a more reliable operation between the emulator and the device - I usually experience issues in OMAPL devices if I use the default automatic with maximum speed (35MHz) setting (especially in the ARM9 core, but could be applied to the DSP as well).

    In any case I strongly recommend updating your CCS to the release version. Several bug fixes were done throughout the beta program that should help you.

    Hope this helps,

    Rafael

     

  • 0 in reply to desouza
    TI__Mastermind 27585 points

    I upgraded to the release version and still see the same issue. No memory locations can be read, and they all look like the screenshot including 0x00800000. I have both GEL files for ARM and DSP that came with the EVM. CCS3.3 is working fine on both cores.

    The TCK is running at 10 MHz already and I see the issue. I've tried other peoples' boards that work and same thing. Does this seem like a software bug?

    Jeff

  • 0 in reply to jc-ti
    TI__Guru**** 171729 points

    Jeff,

    Interesting; since this issue seems heavily tied to your PC, at this point I am more suspicious of corrupt debug cache files or even your current workspace. Can you try to follow the steps listed in the sections Debugger or General IDE of the CCS troubleshooting page?

    As you said that CCSv3.3 works in your PC, I am not aware of any conflicts between these two versions but I will have to verify further.

    Regards,

    Rafael

  • 0 in reply to desouza
    TI__Mastermind 27585 points

    Thanks for the link. I created a new workspace and the issue is resolved!

    Jeff