Overview¶
This section explains the major concepts involved in the OAD process from a high level. The concepts here will be expanded upon further in the following sections. Some concepts, such as the Boot Image Manager (BIM), may vary in their implementation details. Wherever possible, the concepts will be covered in this chapter with their implementation details covered in the following chapters.
OAD Types¶
There are two methods of implementing a firmware update using over the air download process. The key difference between the two methods is the location of the downloaded image.
On-chip: | During On-Chip OAD, the downloaded image is written to internal flash, allowing for a single chip OAD solution. |
---|---|
Off-chip: | Off-Chip OAD stores the downloaded image in an external flash part, requiring a two chip OAD solution. The below figure shows a comparison of different OAD methods. Each type of OAD has associated trade offs and benefits which will be discussed in their respective sections. |
Despite their differences, both OAD methods share the same firmware image header format.
OAD Type | Advantages | Limitations |
---|---|---|
On-chip |
|
|
Off-chip |
|
|
Boot Image Manager (BIM)¶
The boot image manager (BIM) is a bootloader that runs after reset and copies a new application image either from internal or external flash to the destionation location. The BIM is a very simple application. It only checks whether a new image has been copied to the system. It is the application’s responsibility to receive the new image and to store it using the OAD service.
BIM’s implementation varies slightly for On-chip and Off-chip OAD solutions, thus there is a separate BIM example project for each.
bim_oad_onchip
See BIM for On-chip OADbim_oad_offchip
See BIM for Off-chip OAD