• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 81 subscribers
  • Views 981 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/TMS320F28377S: Working with CLA example projects

Eric ***
Prodigy 130 points
Part Number: TMS320F28377S

Tool/software: Code Composer Studio

I have been attempting several CLA example projects without much success.  Currently, I've been attempting to run the  v210 "cla_fir32" example project from Control Suite in Code Composer version 6.2.0.

While debugging, I have been able to connect to the CLA, load the .cla file symbols, and run the program until I hit the first "_mdebugstop()" line and step through the first task.  After this, I cannot get the task to run again.

Furthermore, when I disconnect from the CLA I would expect the main cpu program to run normally and report pass/fail cases; however, the main routine just sits at " Cla1ForceTask1andWait();"

Has anyone worked with these newer example projects?  Any suggestions?

Thanks,

Eric

  • 0
    TI__Mastermind 20850 points

    The issue might be related to this: 

    Eric *** said:
    Furthermore, when I disconnect from the CLA I would expect the main cpu program to run normally and report pass/fail cases; however, the main routine just sits at " Cla1ForceTask1andWait();"

    There is a section in the device TRM on CLA debugging. I pulled this snippet from there 

    5. If desired, disable CLA breakpoints
In Code Composer Studio you can disable the CLA breakpoints by disconnecting the CLA core in the
debug perspective. Make sure to first issue a run or reset; otherwise, the CLA will be halted and no
other tasks will start.

    It would be better to issue the reset, as a run will likely get stuck at the MSTOP for the task.

  • 0 in reply to Vishal_Coelho
    Prodigy 130 points
    The other thread's answer did resolve the problem. It behaves as expected now. Thank you!