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.

MSP430F5328: How to make MSPBoot work

Expert 3560 points
Part Number: MSP430F5328
Other Parts Discussed in Thread: MSP430F5529

Hi Champs,

My customer want to implement the MSPBoot on F5328. However, since the example project was built for MSP430F5529, they will need to do some porting.

Do we have any guidelines for this?

Regards,

Kien Nguyen

  • Hello Kien,

    There are no guidelines on this. The customer needs to do the exercise of looking at the differences between the part and adjusting as needed.  If you compare the data sheets, you will see the main difference is memory size and an LDO block instead of USB. 

    That being said, the customer doesn't necessarily need MSPBoot here, as MSP430F5xxx devices have their BSL code stored in Flash, so it can be directly replaced with a custom BSL. Please see the Custom BSL app note on www.ti.com/tool/mspbsl 

  • Hi Jace,

    Thanks for your reply. My customer is considering both BSL and MSPBoot.

    May I know what are the main differences between them? And when to use which one?

    Regards,

    Kien Nguyen

  • Kien,

    MSPBoot is an application space BSL (Takes up application flash memory) that was created mainly for devices where you can't update the BSL as it is in ROM. 

    Custom BSL solution, is the source code for the TI provided BSL that you can modify to fit your needs. Most common use case is changing the peripheral interface (UART/I2C/SPI, etc) or adding some kind of security check. This option is only available on MSP430F5xxx/6xxx devices as their BSL is tored in a special Flash region, and thus can be modified. The BSL Flash region is only 2kB though, so your custom solution must fit into that. 

  • Jace,

    Understood. Thanks a lot for your supports.

    Regards,

    Kien Nguyen 

**Attention** This is a public forum