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.

MSP430 OTA FW Updates

Other Parts Discussed in Thread: MSPBSL

Hi Team,

I have a customer using an MSP430 controller. It is connected (UART) to a wireless module that can send firmware packages to the MSP430. The expected operation is as follows:

1. Wireless module sends Firmware binary “.bin” file via UART to MSP430
2. MSP430 stores this file in a reserved section of flash
3. Upon download completion, MSP430 starts the BSL to move new firmware image to main memory
4. Done

Would this be possible with our MSP430 parts, and if so, is there documentation on how to implement this? The presumption is that at the very least some modification to the BSL is required to make this happen.

Regards,
Steve

  • Hi Steve,

    This application is definitely possible, the user needs to make sure that they are using a UART BSL compatible MSP device and that the communication protocol sent by the wireless module follows what is outlined in the MSP430 Programming With the Bootloader (BSL) User's Guide (SLAU319): www.ti.com/.../slau319l.pdf

    The BSL version/type varies between devices, does the customer know which MSP430 derivative they would like to use? Several resources are provided on the MSPBSL tool page. The only issue I see is that the customer wants to use a dual-image mode, where there is a download and main memory space partitioned in the MSP430 memory and the main memory is not updated until the download is complete and verified. This application is not supported on the native BSL which will require the customer to reference the MSPBoot application report for a main-memory bootloader solution. Further BSL OAD resources, extending from the MSPBoot application report, are planned to be released in the near future and could be of great benefit to the customer.

    Regards,
    Ryan
  • Hi Ryan,

    Thanks for the response here. Customer is using F5528 so i think we're good to go on that front. I've forwarded this info to them and will let you know if they run into any hurdles referencing the MSPBoot app report for a solution.

    Regards,
    Steve

**Attention** This is a public forum