• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 52 subscribers
  • Views 384 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/TMS320F28033: Code not working when migrating from CCSv6.0.2 to CCSv9

Eric S
Expert 5660 points

Part Number: TMS320F28033

Tool/software: Code Composer Studio

Customer has concern on his recently migrated machines, that is working on CCS6 but has issue with CCSV9 for a TMS320F28033 processor.  He is attempting to run the same working code that he did not have issues with in v6.0.2, so the code does not appear to be the issue. The issue is somewhere between a build and an upload / debugger issue.
His old machine was an HP Z440 running 64 bit windows 7. His new machine is running windows 10 also 64bit OS.

  • 0
    TI__Guru**** 173310 points

    Eric S said:
    The issue is somewhere between a build and an upload / debugger issue.

    You did not describe what the actual issue is when running the CCSv9 code, but here are a few things they can do to narrow down the issue.

    1) Identify the version of compiler tools used to build the working project in CCSv6. Then set CCSv9 to use the same version of compiler tools. The procedure to do this is described in this page: http://software-dl.ti.com/ccs/esd/documents/ccs_compiler-installation-selection.html. Then build the project and verify its operation. If it works like before, then the change in behavior is likely coming from the newer compiler tools that come with CCSv9. The next step would be to figure out what and where the differences are and their impact.

    2) Take the .out file generated from the CCSv6 build and load it using CCSv9 (without actually rebuilding the project). This can be done by invoking a manual debug session, process described here: http://software-dl.ti.com/ccs/esd/documents/users_guide/ccs_debug-main.html#manual-launch. If running the code shows the "issue" then the change in behavior is likely coming from the debugger. 

  • 0 in reply to AartiG
    TI__Guru**** 173310 points
    Eric,

    I hope the above information was helpful for the customer to understand and make progress on the CCS migration. I will close this thread for now, but please feel free to reply back if they still have specific issues or errors that they need further help with.