• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 52 subscribers
  • Views 1728 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Difficulty using labels with F2812

Ryan Mikle
Prodigy 40 points

We are using Code Composer Studio v3.3 for project using the 2407A and the F2812 processors.  We are having trouble using labels in the program for the F2812.  I have attached screenshots that identify the differences. 


Using a debugger (customized, not Code Composer), we are not able to stop the code at the labels with the F2812 code, however we are able to stop the code at the labels using the 2407A code.  Both sets of source code are written in the C language.

It appears that the compiler is not assigning an address to the labels for the code being written for the F2812, while it is for the code written for the 2407A.

I have included an attachement with screenshots of the problem.

Thanks for your help

 

Code generated from the 2407A code.doc
  • 0
    TI__Guru**** 173310 points

    Ryan,

    I tried duplicating the issue, but was able to successfully set a breakpoint at label ROM_Reset. I used the test project you had sent in to TI support.

    In the Labels tab of the Symbol Browser, the label ROM_Reset does not show up, however a equivalent debug label does, in your case, DW$L$_ROM_Checksum$3$E at address 0x3D8EA6 (from your screenshot). The addresses in my test case are a bit different but I am able to set a breakpoint at the ROM_Reset label.

    Are you saying that you are unable to set a breakpoint at that label/address in CCS? What is the error generated by CCS?

     

  • 0 in reply to AartiG
    Prodigy 40 points

    Aarti,

     

    We have figured out the problem.  CCS is performing as expected.  There was a problem with the custom debugger that we were using.  It was not interperting the labels correctly.  This has since been corrected. 

     

    Thanks for your help.

    Ryan

  • 0 in reply to Ryan Mikle
    TI__Guru**** 173310 points

    Ryan,

    Thanks for the update. Glad to hear the issue is resolved.