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

accessing peripherals on the OMAP4460

Errett Hogrefe
Prodigy 220 points
Other Parts Discussed in Thread: CCSTUDIO

I am getting started debugging the OMAP4460 on the Pandaboard ES.  I have followed the instructions below to start the debug session, and have used the GEL files for the OMAP4460 that are distributed with the CCS 5 tools. 

http://processors.wiki.ti.com/index.php/GSG:Connecting_to_slave_cores_in_SoC_devices

I can run the GEL script for the master cpu (omap4460_cortexA9_cpu0_startup.gel), but after it completes, I still cannot access any of the peripherals through the memory window.  For example, viewing GPIO2 at 0x48055000 gives ?? for each location (processor was not able to access that location).

I do not have an SD card plugged in, so there is only ROM code, but no X-Loader.  Do I need the X-Loader AND the GEL files?  More generally, how do I figure out what I am doing wrong? 

Thanks,

Errett

 

  • 0
    TI__Genius 10545 points

    I have next questions in order to narrow down the issue.

    1. Are you using CCS version 5.2 or 5.1? there was an issue with v5.2 where some files where not installed properly, I am not sure if there is a fix for this already or didn't check if there is a new version since then.

    2. Are you using XDS100v2 or v3?

    Next post talks about XDS100v2

    http://e2e.ti.com/support/omap/f/849/p/195600/698628.aspx#698628

    from next link XDS100v2 features from v2 supports A9 debugging.

    http://processors.wiki.ti.com/index.php/Xds100v2

  • 0 in reply to Manuel Contreras
    Prodigy 220 points

    I am using CCS 5.2.1 and XDS100v2.  I am pretty sure the debugger is working ok, since I can probe memory regions in the OMAP4460.  The issue is that I cannot access the peripheral regions.  Another symptom is that when I probe the L4 region directly adjacent to the peripheral space (for example, 0x48056000 instead of 0x48055000 for the GPIO), I get a pattern that repeats every 0x80 addresses.  The first  word at 0x48056000 (and 0x48056080, 0x48056100, 0x48056180, etc.) is 0x00206435. 

    It seems like some configurations are not being done on the chip, but perhaps there is something wrong in my setup that prevents the GEL files from working correctly.  Any help is appreciated. 

    Errett

  • 0 in reply to Errett Hogrefe
    TI__Genius 10545 points

    By checking shared information I can do next suggestions;

    1. In CCSv5.2.0 there was an issue with some chip identifiers that where not correctly installed, I am checking if this was corrected for CCSv5.2.1, but one thing to do is to install CCSv5.1.1 and see if it is correctly identified, please read full post last point could be the one that fixes the issue. why not in #1 probably because it requires to update the device and there are notes about not updating if you are not having certain issues.

    from next link not sure if it was SDSCM00044338 or SDSCM00044152.

    http://software-dl.ti.com/dsps/dsps_public_sw/sdo_ccstudio/CCSv5/CCS_5_2_1/exports/ReleaseNote.htm

    2.It could be needed to check license that was used to install CCS, check next post

    http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/85224.aspx

    it is for CCSv4 but the same applies to CCSv5

    3.In next link they mention that some input and output definitions were incorrect

    'Fixed definitions of certain signals from "inout" to "output" (EMUs and TMS). T_SRST remains "inout".'

    http://processors.wiki.ti.com/index.php/XDS100#Q:_How_can_I_update_the_CPLD_on_my_XDS100v2.3F

    this link contains all the information related on how to update the device.

    and some links about Troubleshooting and Debug issues.

    http://processors.wiki.ti.com/index.php/Debugging_JTAG_Connectivity_Problems

    http://processors.wiki.ti.com/index.php/Troubleshooting_CCS