• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 41 subscribers
  • Views 109 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.

CC3551E: Options for Non-OTA SW updates

Luke
Expert 4305 points

Part Number: CC3551E

Hi team,

We're looking into OTA software update methods other than the documented ARM A/B process that are more suitable for smaller flash sizes. Our main question is:

1. Is there any kind of official support for a single-slot self-update mechanism?

Barring that, if we were required to implement our own, additional questions we have are:

2. Is it possible for us to develop a custom bootloader for the TI bootloader sector?

3. Is the update system used by the XDS developer boards accessible over UART?

4. Is it possible to have two applications in a non-A/B layout:

a. Both in different offsets of a single code region

b. One in the code region and one in the vendor specific region

c. Have one invoke/chain-load into the other

Best,

Luke

  • 0
    TI__Expert 5815 points

    Hi Luke,

    Let's start with your first question. One of the key features of dual-slot is the ability to rollback the update in case there is a failure with the new vendor image. How do you plan on avoiding this with only a single-slot?