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.

MSP430FR5969: Legacy CCS 6 Project (v4.x.x compiler) Won't Build & Run Correctly with New Tools

Part Number: MSP430FR5969

This may be more of a CCS question than a 430FR5969 issue, but am not sure of the cause yet.

So, we have a circa 2014 legacy 430FR5969 based product with firmware originally written using CCS 6.1 (PC) with the TI v4.4.3 compiler:

I've tried loading this old CCS project (import) into the latest CCS 12 (Mac) with the TI v21.6.1LTS compiler. There is a problem with the firmware though when we load newly built firmware files. The devices seem to go into a constant reboot cycle of 1.2s or so. We have an old Windows VM that I can run on my Mac (Parallels) which still has the old environment and I can build firmware files there that work and don't have that reboot problem. Literally the same code on the local machine (shared filesystem with VM).

We want to bring the codebase forward into current tools/libraries and I am trying to figure out what the problem could be.

I did initial work on updating the codebase for the latest MSP Driver Library, thought that might address it but it didn't. Even after updating the driver library and usage in the codebase, new firmware builds still go into the 1.2s reboot loop. Now, I WAS able to initiate a debug session and got got to execute past that 1.2s reboot loop due to code stepping. But when I free-run a unit (no debugger attached) it still goes into the 1.2s reboot loop.

Same hardware and code, the only different is building the firmware from within the VM with the old CCS or building the firmware from my primary desktop with the latest CCS.

Is there some obvious configuration tweaks we should apply due to the compiler or IDE version changes from this era? Particularly I'm thinking about the switch from the older tech TI v4.4.3 compiler to the current tech TI v21.6.1LTS version.

Any help or hints appreciated!

  • Hi Jonathan Maier

    I think your question is "The devices seem to go into a constant reboot cycle of 1.2s or so" using the new version CCS 12 and TI v21.6.1LTS compiler on MAC.

    Could you please try-run this CCS and the compiler (windows version) on the windows environment? VM is the option.

    Thanks

  • I don't want to switch to Windows. I want to bring the project forward into my Mac OS system using CCS 12 (Mac).

    The original project was in an old windows 7 virtual machine with old CCS (that I am able to run on my Mac using Parallels). We want to get rid of the old windows virtual machine and old CCS. I currently use Mac version of CCS for other project so want this old project to be updated to be the same.

    The issue is that using the same project files and code, the old CCS in the old windows virtual machine can generate working firmware files, but when I use the same project files and code with the latest CCS 12 (on Mac), the generated firmware files have a reboot bug.

    Please, I would like someone to respond with something besides "just switch to PC and try it" because that path is not viable and shouldn't even be an issue. If it is, please provide details.

  • As a follow-up, I did install CCS Theia 1.4.0.12 onto a Windows 10 PC. I imported the project, built and loaded firmware. It uses the TI v21.6.1.LTS compiler. It has the same bug.... it's stuck in a ~1.2s reboot loop.

    To me, this seems to be an old vs new compiler and possibly project settings issue. Need help here.

  • Hi Jonathan Maier

    I think you can try-run the code example www.ti.com/.../SLAC536 on CCS 12 (Mac) to check if the stuck in a ~1.2s reboot loop issue will happen

    if there is no issue, This code example should be the base (empty project) for this version CCS and compilar.

    Then, you can consider copying your c code from the old project to the new one

    Thanks

**Attention** This is a public forum