• State TI Thinks Resolved
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 85 views
  • Users 0 members are here
Support feedback
Options
Options
Related

C2000-CGT: Code Composer Studio 12 doesn't see the installed compilers

Tenko Yavashev
Prodigy 30 points
Part Number: C2000-CGT
Other Parts Discussed in Thread: SEGGER

  1. The new way to ask questions here is buggy - for example, I selected the C2000-CGT for "TI Part number" and the only available option for "Forum" was "Arm-based microcontrollers forum."
  2. I have installed the CCS v.12.8.1 (initially it was 12.50, therefore the folder c:\ti\ccs1250). Everything was fine until some updates. After them, the CCS doesn't see the installed compilers; Therefore, I added the exact path to the list of "Product discovery path" and clicked the 'Refresh' button. This usually helped uScreenshot 2026-01-08 100105.pngntil today - see attached screenshot. 
  • 0
    TI__Guru**** 474421 points

    Hello,

    The list of compilers is not under "Products" but instead under "Build -> Compilers":

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 30 points

      

    Yeah, my bad.

    I realized it later, after a clean new installation. 

    Nevertheless, my observation remains valid that after some updates, the CCS loses the ability to find the installed compilers at the originally added Tool discovery path c:/ti/ccsXXXX. The workaround is to add a deeper one c:/ti/ccsXXX/tools/compiler. So far, I noticed this happens after the updates of the Segger J-Tag plug-in.

    Regards

  • 0 in reply to Tenko Yavashev
    TI__Guru**** 474421 points
    Tenko Yavashev said:
    Nevertheless, my observation remains valid that after some updates, the CCS loses the ability to find the installed compilers at the originally added Tool discovery path c:/ti/ccsXXXX. The workaround is to add a deeper one c:/ti/ccsXXX/tools/compiler

    This is odd. CCS should always find the ones in ./tools/compiler. It knows about that directory and new compilers installed there are typically auto-detected.

    Tenko Yavashev said:
    So far, I noticed this happens after the updates of the Segger J-Tag plug-in.

    This is interesting. I've updated the J-Link plug-in in the past and never seen this issue. Perhaps it is a recent issue.