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.

MSP-FET430UIF firmware update required with version CCS 6.1.2.00014 and CCS UniFlash version 3.4.0.00002

Other Parts Discussed in Thread: UNIFLASH, MSPDS, ENERGIA, MSP430F5253

I recently upgraded my computer with the above versions of Code Composer Studio and CCS UniFlash. I use UniFlash to load my code and CCS to debug it. With these latest updates, I now get a message indicating I need to upgrade the firmware on my MSP-FET430UIF when I switch between these 2 applications. Can something be done to prevent this?

  • Hi Edward,

    It is likely that each program has a preferred MSPDS debug stack version, and the difference between the two causes each program to request an update before attempting communication: http://www.ti.com/tool/mspds

    The same problem occurs with other programming tools like FET-Pro430, Energia, and IAR. Each can have their own preferred DLL version. You can try to update either program so that the MSPDS versions are the same or try to ignore the request to update the firmware in either.

    Regards,
    Ryan
  • Hi Ryan,

    Thanks for the reply. I tried ignoring the request to update the firmware when launching CCS Uniflash, and I get strange behavior. Our application runs on a MSP430F5253 processor, and we utilize the info pages for some small pieces of code; thus I need to perform a mass erase before loading the code. The mass erase runs fine, but Uniflash hangs when I subsequently try to program the image. If I update the firmware when requested by Uniflash and Code Composer Studio, I do not see this behavior.
  • Hello Edward,

    This is unfortunate and means that the constant firmware changes are necessary. There could be updates to either program in the future that re-syncs the MSPDS but until then it might be necessary to deal with the inconvenience as it stands.

    Regards,
    Ryan

**Attention** This is a public forum