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.

MSP430F5438: Question on Migration to 5438A

Part Number: MSP430F5438
Other Parts Discussed in Thread: , MSP-TS430PZ5X100

Team,

My customer has been using the MSP430F5438 and are wondering what exactly will happen if they do not rebuild the code using the 438A version’s header and linker files.

They’re reading the migration guide, but it is going to take them a few weeks to move a new code rev through their code validation system so they’re are wondering if they absolutely have to update the code to use this “A” version part.

 Also, in terms of a dev kit, do you recommend I just provide them the MSP-EXP430F5438 & a few samples of the MSP430F5438A? They want to try the original code on the new part.

Thank you.

  • Hello,

    My customer has been using the MSP430F5438 and are wondering what exactly will happen if they do not rebuild the code using the 438A version’s header and linker files.

    They’re reading the migration guide, but it is going to take them a few weeks to move a new code rev through their code validation system so they’re are wondering if they absolutely have to update the code to use this “A” version part.

    My guidance would be to use the correct compiler settings that match the specific part number and revision. My main concern is that there are errata fixes implemented by the compiler that may not be necessary on the non-A version of the device. I'm not sure if that would cause any issues or not. This is not something that we would recommend, so it's not something we would test. The first change that I would make is to change the part number to the A version in the project settings, build the code and see how everything works.

     Also, in terms of a dev kit, do you recommend I just provide them the MSP-EXP430F5438 & a few samples of the MSP430F5438A? They want to try the original code on the new part.

    That's a good approach. The Experimenter Board features an onboard socket that would allow them to easily replace the device without soldering it to the board. Make sure the sample packages match what the board's socket supports, since some devices are offered in multiple types of packages (e.g. QFN, TSSOP, etc.).

    The MSP-TS430PZ5X100 target board is a viable alternative to the Experimenter Board too.