• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 838 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.

CCS with vayu EVM

Shawn Yang
Intellectual 1285 points

I'm working with the Vayu EVM, and When I debug the u-boot, the u-boot is from GLSDK, I found there are some issue.

1.   As you can see on the following snapshot, my code is running at PC 0xDEFAE3E0, from the memory browser, I can see the data in 0xDEFAE3E0 with physical address mode.

but in the disassembly  window, I can only see "mempry map prevented reading...", In the right side of the snapshot, you can see the memory map list.

the memory address is surely can be read by arm A15 core because  I can use the u-boot command md 0xDEFAE3E0 to read it.

What's maybe the point why I can't disassembly the u-boot code?

2. what's the schedule to support the ARM A15 hypervisor

  • 0
    TI__Guru**** 463041 points

    Hi Shawn,

    What exact version of CCS are you using?

    Thanks

    ki

  • 0 in reply to Ki
    TI__Intellectual 1285 points

    CCS5.5 and CCS6

  • 0
    TI__Guru**** 463041 points

    Shawn Yang said:

    but in the disassembly  window, I can only see "mempry map prevented reading...", In the right side of the snapshot, you can see the memory map list.

    the memory address is surely can be read by arm A15 core because  I can use the u-boot command md 0xDEFAE3E0 to read it.

    The debugger memory map is configured by the startup gel file. This memory map defines just to the debugger what memory is available. It will block access to the debugger what it thinks is accessible memory. Again, it only applies to the debugger. That is why the disassembly view is blocked but not the actual program or anything else outside the debugger (like u-boot command md)


    Now the question I have for you is are you sure you want to be using a GEL file at all? GEL files usually do some target initialization and such which can wipe out any initialization done by the boot-loader (u-boot) and put the target in a bad state.

    See this wiki article for more information on using GEL files:

    http://processors.wiki.ti.com/index.php/U-boot_Debug_in_CCSv5#U-boot_debug_setup_and_procedure

    Thanks

    ki