• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 204 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/TMS320F2812: CCS upgrade from windows XP to Windows 10 Environment

kaleswararao kandula
Prodigy 50 points
Part Number: TMS320F2812

Tool/software: Code Composer Studio

Hello,

Greetings for the day..!

We have a question on Code Composer studio and the details are below

Currently we are using TMS320F2812 device with windows XP environment with following IDE and Compilers.

Compiler : Code Composer v3.3

IDE Code Composer Studio : v3.3.38

Emulator : Spectrum Digital Emulator/JTAG (XDS510 USB)

We want to upgrade the windows environment to Windows 10,Requesting you to suggest the Code Composer compiler and IDE to use in Windows 10 environment and also suggest the Emulator to use for the same requirement.

  • 0
    TI__Guru**** 171104 points

    Hi,

    Device:

    The TMS320F2812 is still fully supported by the latest releases of CCS.

    Code:

    Does your code use DSP/BIOS? If so, this imposes a very thorough migration path, since this support is not officially tested since CCSv5.x. I can generate code with the latest releases of CCS, but its debugging capabilities are not present anymore (the Printf logs, the Real-time Analysis tools, etc.). 

    If your code does not use DSP/BIOS, there is a very high probability that your code can be migrated to the newer versions with only path adjustments to source and library files.

    Obviously that any change to the foundational tools (compiler or RTOS) requires a very thorough functional verification. 

    Debug Probe:

    The XDS510USB Debug Probe works well up to CCSv8.3.1, which is fully supported in Windows 10. Given the jump from CCSv3.3 to CCSv8.3.1 is significantly higher than CCSv8.3.1 to the latest CCSv9.3.0, this allows you to perform the migration in steps: first code, then Debug Probe.  

    Hope this helps,

    Rafael