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.

CC1354R10: BIM for CC1354R10 (SDK F2 8.30.01.01)

Part Number: CC1354R10
Other Parts Discussed in Thread: CC1354P10, SYSCONFIG

Tool/software:

I am running the Basic BLE OAD Off Chip example - it doesn't appear to use MCUBoot but rather the standard OAD BIM.

Where is the Off Chip BIM project located as I can only find the MCUBoot project nortos example?

For the CC1352R1 I find this: simplelink_cc13xx_cc26xx_sdk_8_30_01_01\examples\nortos\CC1352R1_LAUNCHXL\bim\bim_offchip

For the CC1354R10 (assuming same as CC1354P10) I can only find simplelink_cc13xx_cc26xx_sdk_8_30_01_01\examples\nortos\LP_EM_CC1354P10_1\mcuboot\

  • Sorry. I see it is actually using MCUBoot. It is just not enabling the MCUboot in the basic_ble_oad_offchip.syscfg file.

    Is there a reason this is not enabled?

  • Hello Scot,

    As you mentioned, the device examples use MCUBoot as the boot-loader. The MCUboot SysConfig configuration is only used to modify the actual MCUBoot project, not the application one (basic_ble_oad_offchip in this case). So there is no need to enable any MCUBoot instance. If you want to get the mcuboot hex file out of the box, please use the one that is included inside the SDK: \examples\rtos\LP_EM_CC1354P10_1\ble5stack\hexfiles -> mcuboot_offchip_LP_EM_CC1354P10_1_nortos_ticlang. In case you need to modify the MCUBoot example, import it from: \examples\nortos\LP_EM_CC1354P10_1\mcuboot\mcuboot, then you will see it actually includes the MCUBoot instance in SysConfig which you can modify to fit your type of OAD (off-chip, on-chip) and the slot primary/secondary addresses and sizes.

    Hope this helps.

    David.