MCUBoot Based Over-the-Air Download (OAD)

The following sections aim to describe the lower layers of OAD software that are common across all protocol stack implementations. This includes the OAD image header, the flash layout, Secure Bootloader, and the oad image tool.

Note

Currently, the MCUBoot based Proprietary RF OAD solution only supports on-chip OAD

Warning

The Proprietary RF OAD Profile does not implement or perform any security or authentication mechanisms as part of the firmware update process. System developers should take measures to adequately authenticate peer devices and only accept and/or apply firmware images transferred from trusted sources via the OAD Profile.

• Introduction
  • OAD Topology Overview
• MCUboot Overview
• MCUBoot OAD Image Header
  • MCUBoot OAD Image Header
• Flash Layout for On-Chip OAD
  • Constraints and Requirements for On-chip OAD
  • Internal Flash Memory Layout
    • Internal Flash Memory Layout for CC13x2x7 and CC26x2x7
    • Internal Flash Memory Layout for CC13x4 and CC26x4
• Execution flow of MCUBoot Based Proprietary RF OAD

The following sections aim to describe the specific application and profile layer of the OAD solution. The OAD application section will describe the process from a high level in terms of events and states, and the profile section will cover the actual structures that are sent over the air.

• OAD Process
  • Proprietary RF OAD software architecture
  • OAD Client
    • OAD Client Protocol Functions and Callbacks
  • OAD Server
    • OAD Server Protocol Functions and Callbacks
  • OAD Storage