• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 79 subscribers
  • Views 565 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

MSP430FR2433: Custom FRAM Partitioning

Rejath Paul Varkey
Intellectual 420 points

Part Number: MSP430FR2433

I need two binaries to be flashed in my MSP FRAM.

  1. Primary image : It contains the basic use-cases that should always be executed by MSP, if secondary image gets corrupted during upgrade. This image is never upgraded once it is flashed in FRAM.
  2. Secondary image : It contains all the use-cases that are executed by MSP. Upgrade always happens in this image.

Is there any way to implement it ?

Please suggest if a better solution exists. My requirement is that, if firmware hang occurs during code execution or firmware corruption occurs during upgrade, then MSP should not brick. It should execute the basic use cases that are contained by primary image.

If I have to design a custom bootloader for this, then please suggest useful documents and sections in it that I should refer.

  • 0
    TI__Genius 17960 points

    Hello Rejath,

    this is a quite complex topic, and difficult to cover thoroughly by a post. But to give you some hints, please find here some suggestions on hand on collateral and web locations to look at for related topics.

    This is an application report on "MSP430 FRAM Technology - How To and Best Practices"

    A web link to our main landing page on Boot Loader topics and collaterals is Here you can find tools, application reports, code examples related to different Boot Loader implementations.

    Finally to give you a top level recommendation and answer to your question, the MSP430 FRAM Value Line family, means MSP430FR2xx and MSP430FR4xx do not have the MPU (Memory Protection Unit) which supports features addressing aspects, as you are trying to implement. The MPU is only integrated in the MSP430FR58xx, FR59xx and FR6xxx Portfolio. Thus I see only two options for the FRAM Value Line.

    1. Create your own customized Boot Loader (See information on main Boot Loader Homepage)

    2. As even a customized Boot Loader with the limited protection features of the MSP430 FRAM Value Line might not give you the desired protection level of your Primary Image, I'd suggest to use the integrated BSL, available in each MSP430 FRAM device, in combination with the HW invoke of it. The advantages of this approach are the following: The BSL is based in ROM. Thus it cannot be damaged, or erased in any way, and always is able to recover the device even if the FW update failed completely. It offers a tested FW update mechanism.

    Best regards

    Peter

  • 0 in reply to Peter Spevak
    Intellectual 420 points

    Hi Peter,

    Thanks for your support. I shall proceed based on your suggestion and contact you during further development.

  • 0 in reply to Rejath Paul Varkey
    TI__Genius 17960 points

    Hi Rejath,

    I assume for now we can close this thread. In case you have further questions, you can either start a new one, or if it should be in the next days, you can reopen this one.

    Best regards

    Peter

**Attention** This is a public forum