• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 31 subscribers
  • Views 486 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.

TM4C123BH6ZRB: Fail Safe Approach For Application Image durinng update through I2C

Viswanathan M
Prodigy 20 points
Part Number: TM4C123BH6ZRB

Hi,

We are using TM4C123BH6ZRB MCU for one of our requirement. Presently we have bootloader and application image for our proj.

The bootloader and application image are copied from FLASH and executing from SRAM.

During the application update, we are updating the application image from the bootloader through GPIO pin check update.

We want to include fail safe approach for the application image update during the update operation.

Could you please provide your suggestions for providing fail safe approach during the application image update operation through I2C??

Regards

Viswanathan M

  • 0
    TI__Guru*** 135355 points
    Hello Viswanathan,

    When it comes to using a bootloader for Flash like this, the only thing I can think of as far as a fail safe would be to have an approach that uses two images (which would reduce your Flash space by half). You could do something like having a version number for each update of your firmware, and have the bootloader try and check for the latest if the firmware clears a check like a CRC check to validate that the firmware is downloaded correctly. If the firmware fails the check, then just revert back to the older firmware?

    Maybe the community can provide other ideas that are more robust though, as that one is not exactly attractive.
  • 0 in reply to Ralph Jacobi
    Guru 117855 points

    How does one (even) begin to define, "Fail Safe?"

    What may be attractive for a small, private, fresh water aquarium - may not prove acceptable to Chicago's "Shedd Aquarium" - w/over 5 million gallons of total tank capacity. (some of which is monitored, logged/alarmed, via our firm's products...)

    Devil - as always - lurks in such detail.      (only) rumor that cb1 (quickly) aborted this tank's sensor updating - upon Shark's arrival...   (rather effective, "fail-safe")