You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Optional split of jump address from start address (ARMmbed#104)
On targets like the NRF52, where the application's entry point is
not at the beginning of the firmware it is necessary to distinguish
between the two.
This commit adds an optional jump address to handle this corner
case. When the jump address is not defined the start address
becomes the default jump address.
Copy file name to clipboardExpand all lines: README.md
+4-1Lines changed: 4 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -25,10 +25,13 @@ NOTE: All these configurations must be set the same in the mbed cloud client whe
25
25
### Active Application and Header
26
26
27
27
1.`update-client.application-details`, Address at which the metadata header of the active firmware is written. **Must align to flash erase boundary**
28
-
1.`application-start-address`, Address at which The application starts **Must align to vector table size boundary and flash write page boundary**. It is assumed the region between `update-client.application-details` and `application-start-address` contains only the header. MUST be the same as "target.mbed_app_start" in the application.
28
+
1.`application-start-address`, Address at which the application starts **Must align to vector table size boundary and flash write page boundary**.
29
+
1.`application-jump-address`, Optional address for the application's entry point (vector table) if this is different from `application-start-address`.
29
30
30
31
If the `application-start-address` is set less than one erase sector after the `update-client.application-details`, the two regions will be erased together. Otherwise the two regions will be erased separately in which case `application-start-address` must also align to **flash erase boundary**.
31
32
33
+
If `application-jump-address` is not set, the `application-start-address` will be used as the application's entry point. The entry point MUST be the same as "target.mbed_app_start" in the application.
34
+
32
35
### Firmware Candidate Storage
33
36
34
37
1.`MBED_CLOUD_CLIENT_UPDATE_STORAGE`, This need to be set in the "macros" section of `mbed_app.json`. Choices are ARM_UCP_FLASHIAP_BLOCKDEVICE and ARM_UCP_FLASHIAP. This determines whether the firmware is stored on a blockdevice or internal flash. If blockdevice is used `ARM_UC_USE_PAL_BLOCKDEVICE=1` must also be set.
0 commit comments