• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 55 subscribers
  • Views 586 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 Debug for C54x

Delared Delared
Expert 1945 points

Hi all,

I’m using code composer studio 5.4 for DSP C54x.

I have an algebraic asm code, and I want to interface it with a C code.

So I added a main.c file in which I made a call of asm routines. With these changes, I call build the project without error, but I have a problem, as follows the difference before/after my changes:

-          Before: I have no main.c, at CCS debug, I must click on play so the code will be running

-          After: I have a main.c that call asm routines, when I pass on CCS Debug, the code is running directly (without click on play!!!). 

as result i can't control the init of the running of my code.

there are some required modifs that i should add when interfacing C and asm ????

  • 0
    TI__Mastermind 43955 points

    HI Delared,

    As your query is about CCS, moving it to CCS forum as you may get faster response there.

     

    Regards,

    Shankari

     

  • 0
    TI__Guru**** 171729 points

    Hi,

    By default the CCS debugger will automatically run to your main() function after the code is loaded, therefore if anything in the initialization routine is preventing the device to reach it or maybe it is even resetting the device, the debugger will appear as "running forever".

    If you want to disable the autorun to main, go to the menu Run --> Debug Configurations, select your configuration and select the tab Target. Then, scroll down until you find Auto Run Options (in newer versions you have to select Auto Run and Load Options) in the tree. Remove the main and de-select the checkboxes. Next time you load the code, it will be in the entry point _c_int00 and halted.

    This will help to see where your code is losing control, and therefore you can start debugging from the very beginning of its execution.

    Hope this helps,

    Rafael