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.

CC2640R2F: creating production BIM+STACK+APP image

Part Number: CC2640R2F
Other Parts Discussed in Thread: CC2642R

Hello,

we are using BLE 5.0 Stack SDK 1_40_00_45 and hand have created 3 hex images for BIM, Stack, APP. When we flash these usingSmart RF Flash programmer 2, everything is working and we are able to OAD update the app subsequently using BTool. All ok and working. 

Now we would like to generate 1 single master "production" hex image containing all 3 images. We have read "Generate production Off-Chip Image using IAR" in ti/simplelink_cc2640r2_sdk_1_40_00_45/docs/ble5stack/ble_user_guide/html/oad/oad_appendix.html#generate-production-off-chip-image-using-iar

but are not sure we understand this completely. In the doc, the command line post build action is given as follows:

$TOOLS_BLE_DIR$\oad\oad_image_tool.exe $PROJ_DIR$\FlashROM_OAD_Offchip\Exe\$TARGET_BNAME$.hex -t offchip -i app --imgVer 0 -ob $PROJ_DIR$\FlashROM_OAD_Offchip\Exe\$TARGET_BNAME$.bin -m 0x0000 --r 0x0000

But we don't fully understand the given command line arguments. specifically, we dont see a reference to the BIM or stack images this comandline. Can you explain in more detail how we could generate a master production image that contains all 3 images?

Thank you

  • Hi Pixel,

    We have updated the docs since then to help give more clarity to this topic. Can you read through the new OAD docs and let us know if you still have questions?

    dev.ti.com/.../index-ble3-cc2640.html
  • Thanks Evan, we downloaded the SDK version 2.20.00.49 and the documentation on OAD is more clear, thanks. However, I am wondering why the BLE5 stack examples do not include any OAD? If I compare the BLE 4.2 vs. BLE 5 examples directories there are a lot more in the BLE 4.2 examples. Is that intentional or a work in progress? If I wanted to use the BLE 5 simple_peripheral, I would have to manually add OAD?

    As a small note, the link one this page: dev.ti.com/.../add-ble-oad-to-proj.html does NOT pint to the Simple Link academy page as one would expect from the text.
  • Hey Pixel,

    Thanks for pointing that out. Part of the reason why that link doesn't point there is because that lab is currently not live. It will be live within the next week, you just managed to find that link faster than most people :) It will work and are working on releasing the new version of SLA soon.

    As far as BLE5 examples on CC2640R2F, there are no BLE5 OAD examples available for CC2640R2F because of flash constraints on that device. It's hard to find, but this limitation is mentioned here under step three: dev.ti.com/.../get-started.html

    We are working on incorporating more examples for future SDKs.
  • Thanks Evan! Ok, so if we will go with the simple_peripheral_off_chip_oad BLE 4.2 example from 2.20.00.49, but want to use the SLA OAD module as a guide, it seems like there is some difference to keep in mind since the SLA OAD module is written for CC2642R, while we are using the SDK for CC2640R2. Can you elaborate on what the "Persistent.hex" is as mentioned here: e2e.ti.com/.../711956

    Thanks!
  • Correct, the module that is currently public is only for CC26x2 but both CC26x2 and CC2640R2 use "Enhanced OAD". The SLA module for Enhanced OAD on CC2640R2 will be available soon.

    I believe that the persistent app that Sean is pointing out is actually the Boot Image Manager. The BIM image "persists" in flash and cannot be updated via OAD. The BIM is intended to reside permanently on the chip and cannot be updated via the OAD process.

    dev.ti.com/.../bim.html

  • Evan,

    Sean is giving the following comandline:

    <SREC_LOC>/srec_cat.exe BIM.hex -intel PERSISTENT.hex -intel STACK.hex -intel app_oad.bin -bin -o SUPER.hex -intel

    This looks like BIM and PERSISTENT are 2 different hex files!?

    I can make sensor of BIM+STACK+APP, I understand their functions, just dont know what PERSISTENT is. It is a term I haven't heard in 3 years working with BLE Stack from TI :)
  • Hey Pixel,

    Looks like the persistent image was what is referred to Image A.

    Sean updated that thread and it looks like he was using his own terminology a bit maybe :)
    "The persistent app is what used to be referred to as Image A in the legacy OAD system."
    e2e.ti.com/.../2640183