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

Problems loading OMAP3530 64x+ core with XDS-100 v2 using the released version of CCS 5.1

Bob Davenport
Intellectual 670 points


I recently installed the released version of CCS 5.1 and noticed that the method of launching a JTAG debug session has changed from even CCS 5 beta.   CCS 4.x and CCS 5 beta allowed the user to open the target configuration, connect the Cortex A-8 and run a GEL script to take the DSP out of reset.  When I try loading/debugging my application with the CCS 5.1 released version, the debugger tries to load the C64x+ directly without bringing up the Cortex A-8 (although, I see the Cortex A-8 and the C64x+ in the Debug Configurations window).  The result is an error message that says the "Device functional clock appears to be off."  Is this because the C64x+ is still in reset or due to some other issue?  How do I launch and load a C64x+ application via the JTAG with the released version of CCS 5.1? 

As mentioned in my subject line, I'm using an XDS-100v2 JTAG emulator.

I re-tested the target  hardware with CCS 4.2 and it loads and executes properly.

 

  • 0
    TI__Guru**** 173310 points

    Bob Davenport said:
    How do I launch and load a C64x+ application via the JTAG with the released version of CCS 5.1? 

    Yes, the behavior is a bit different in CCS 5.1. I assume your target configuration file (.ccxml) is linked (or copied) to your project folder and you are starting it up by right clicking and choosing Debug As->Code Composer Studio Debug Session.

    Instead open the target configurations view, select the .ccxml from there, right click on it and choose "Launch Selected Configuration". That should give you the behavior you are looking for.

  • 0
    TI__Guru**** 468651 points

    Bob Davenport said:
    CCS 4.x and CCS 5 beta allowed the user to open the target configuration, connect the Cortex A-8 and run a GEL script to take the DSP out of reset. 

    This behavior is still supported in the v5.1 release.

    Bob Davenport said:
    When I try loading/debugging my application with the CCS 5.1 released version, the debugger tries to load the C64x+ directly without bringing up the Cortex A-8 (although, I see the Cortex A-8 and the C64x+ in the Debug Configurations window). 

    How did you launch your debug session? Did you launch it from the target configurations view? And do you see the A8 in the debug view at least?

  • 0 in reply to AartiG
    Intellectual 670 points

    Thanks Aarti, that solved the problem.  There were a few other things I had to figure out: The Load Program procedure has changed and (2) the procedure for adding/linking files has changed.  it was necessary to add a linker command file to the Hello World example to successfully load the program and it seemed like that CCS 4.x  example didn't require an external memory map command file, but I may be wrong.

    Thanks for your help!