• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 53 subscribers
  • Views 207 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/TMS320F28069: TMS320F28069

Mike Wood
Prodigy 190 points

Part Number: TMS320F28069

Tool/software: Code Composer Studio

I tried to post earlier but it seems to have gotten lost in the ether so here goes again. When building using CCS  Version: 9.3.0.00012 our code behaves as expected when our debugger, XDS100v2, is connected. However, when the probe is removed the code misbehaves. We are running a motor so stopping the motor at the proper time is most important. The code to stop the motor does some floating point math, soft float lib used, and performs correctly with the debug probe connected yet when the probe is disconnected this math no longer works. We have tried to roll back to CCS7 to see if this would have any effect but no joy there. The compiler in CCS9 is TI 18.12.4.LTS. Any guidance at all would be welcome.

  • 0
    TI__Guru**** 476501 points

    Hi Mike,

    Mike Wood said:
    When building using CCS  Version: 9.3.0.00012 our code behaves as expected when our debugger, XDS100v2, is connected. However, when the probe is removed the code misbehaves.

    Can you clarify what you mean by "probe is removed"? Are you referring to running the code independently from CCS (booting up the device and having the device run code from flash with no CCS involvement)? Or are you referring to more where everything works when running from the CCS debugger but while it is running and you disconnect CCS from the target, it stops running correctly? Also, are you referring to if the XDS100 debug probe is physically connected to the target (regardless of if CCS is running or not)?

    Thanks

    ki