• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 83 subscribers
  • Views 218 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.

TMS320F280041C: I can`t start debug session with CCS 20

Pavlin Stoyanoff
Expert 1725 points

Part Number: TMS320F280041C

Greetings! I have F280041C and XDS110v3 probe and my project uses MotorControl_SDK_v5_04 as base. When I am using CCS 12 everything works just fine, but when I migrate to CCS 20.4 i can`t start debug my project. The UI never sets the pointer to my main(). When i start debug session my C28xx_CPU1 startus is disconnected, I manually connect it and I have a red dot right after C28xx_CPU1 and the status is halted. If i press continoue or step forward it just  returns to the same state. The breakpoints in the mains are automaticly disable and i can`t reanable them. Can you tell me how to fix this?

  • 0
    TI__Guru**** 483701 points

    Hello,

    Pavlin Stoyanoff said:
    The UI never sets the pointer to my main()

    It sounds like auto-run to main fails meaning that the program is unable to reach main from the entry point. Is the target just running freely, never reaching main? If so, if you manually halt the target, where is the program counter?

    Pavlin Stoyanoff said:
    When i start debug session my C28xx_CPU1 startus is disconnected, I manually connect it and I have a red dot right after C28xx_CPU1 and the status is halted

    This sounds like you tried a project-less debug session and manually connected. Did you then try loading your program after this? 

    From a debug standpoint, if it worked in CCS 12, then it should work with CCS 20. 

    The best thing to try is to start a project-less debug session, manually connect, and the load the *.out from CCS 12.x (which works) directly to CCS 20 and see if it can auto-run to main. Do not rebuild the project in CCS 20.x and use the program from there. See if this works first.

    Thanks

    ki

  • 0 in reply to Ki
    Expert 1725 points

    Ok! It seems the CCS 20.5 or 4 has a problem with probe selectrion and access to C directory. So i moved all TI files to another drive. So after that i was able to import example projects and executed them on my controler. But ContorControl SDK has another glitch. Those projects don`t have specific MCU set and they have no probe selected because ot that. So when I selected my F280041C in the  project properties and my probe, everything works fine. It seems, no matter there is *.ccxml file, CCS 20 demands in the project properties the exect MCU and probe to be set...

    Thanks!

  • 0 in reply to Pavlin Stoyanoff
    TI__Guru**** 483701 points
    Pavlin Stoyanoff said:
    a problem with probe selectrion and access to C directory. So i moved all TI files to another drive.

    I'm curious what happened here. Where there specific folders in your C directory that you did not have permissions to which caused this failure?

    Pavlin Stoyanoff said:
    It seems, no matter there is *.ccxml file, CCS 20 demands in the project properties the exect MCU and probe to be set...

    If there is a valid ccxml file in the project folder, then it should use that. The option to manage the project's target config is optional. Did some error get generated that no valid target configuration was found?

  • 0 in reply to Ki
    Expert 1725 points

    Pavlin Stoyanoff said:
    a problem with probe selectrion and access to C directory. So i moved all TI files to another drive.

    I'm curious what happened here. Where there specific folders in your C directory that you did not have permissions to which caused this failure?

    I don`t know. All my TI files were in C:/TI/...

    If there is a valid ccxml file in the project folder, then it should use that. The option to manage the project's target config is optional. Did some error get generated that no valid target configuration was found?

    i think i`ve noticed such warning, but it wasn`t an error i think. So i right clicked on the .ccxml file and selected "Set as default". Later I`ve noticed on regular project, when the .ccxml file is active there is a blue label "Active" next to it. 

    I have some exeprience with visual studio code, but every company has it own approach. For now i think i am fine...

  • 0 in reply to Pavlin Stoyanoff
    TI__Guru**** 483701 points

    Ok, I'm glad things are working for you now. Please let us know if you run into further problems.

    Thanks

    ki