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.

CODECOMPOSER: Running Code composer in Mac

Part Number: CODECOMPOSER
Other Parts Discussed in Thread: UNIFLASH, LAUNCHXL-F28379D

Hi,

I recently shifted to a macOS system from a windows system and am experiencing some trouble with installation on both CCS part and C2000 Matlab blockset support for macOS. I am considering using parallels with a windows VM for running CCS. Did anyone have experience with this kind of a setup and if CCS is significantly smoother in parallels?

 

Thanks

  • Hello,

    I can only speak for CCS. CCS is supported on macOS. What version of CCS and macOS is being used and what is the installation issue?

    I am considering using parallels with a windows VM for running CCS. Did anyone have experience with this kind of a setup and if CCS is significantly smoother in parallels?

    While not officially supported, this should technically work. People have used this environment successfully in the past. I've also successfully used it a long time ago, though it was with an old version of macOS and CCS.

    Thanks

    ki

  • Hi Ki, 


    Thank you for your response. This is for an Apple silicon (M4) and macOS Tahoe. My objective is to try and see if the C2000 microcontroller blockset from Mathworks works on the parallels based windows VM. I assumed it would be the same TI drivers so to improve workflow I was trying to run CCS on the VM itself instead of the macOS. I am working with Mathworks to get more clarity on this.

    But for CCS -I was able to install CCS (v20.4) but i kept getting "Code 28" error for the XDS100 drivers so was able to build code but not debug/flash a 28379 LaunchXL using CCS or uniFlash. 

    Is that a know limitation of apple silicon where I wont be able to run drivers for the XDS100 or XDS110 from arm based Windows needed for the VM?

    Thank you,

    Aditya

  • Tahoe is supported by CCS 20.4. I was able to install it without issue on my macBook Air M1 running Tahoe. I was able to successfully debug an example F28379D project on my LAUNCHXL-F28379D via the onboard XDS100v2.

    Can you run the xds100serial executable in <CCS INSTALL DIR>/ccs/ccs_base/common/uscif and see if the XDS100v2 of your launchpad is detected by the system?

    Is that a know limitation of apple silicon where I wont be able to run drivers for the XDS100 or XDS110 from arm based Windows needed for the VM?

    There is no known limitation. However, just to clarify that this is not an officially supported (and tested) environment so we cannot guarantee that it will work. 

  • Hi Ki, 
    Thanks for confirming the install run on the macbook. In my case I was able to get the CCS working on the macOS itself, but I was having a lot of driver errors and code 28 type errors in the windows parallels desktop. I am guessing that has something to do with improper path or not the correct drivers. Just to confirm are you mentioning about install on parallels desktop or in macOS itself?

    I tried running the xd100serial exe that you suggested, initially I ran into an error with the FTD driver. I installed the arm64 driver for that but then it just said that it was not able to run properly and there was a window to close the program. 

  • but I was having a lot of driver errors and code 28 type errors in the windows parallels desktop

    ah ok. The issue is the drivers in CCS is natively x86_64 and won't run on ARM64 (Apple Mx silicon). On macOS, this is addressed by Rosetta. But on Windows via Parallels, this won't work. You would need drivers for ARM64 and there is a file for XDS110, none exists for XDS100.

  • Thank you for the clarification and the help with understanding the driver settings.