• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 16 subscribers
  • Views 224 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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-Q1: Implement 2.4GHz Proprietary based OAD on CC2640R2F-Q1

Barbara Wu
Intellectual 1900 points
Part Number: CC2640R2F-Q1

Need to implement internal flash OAD function on 2.4GHz proprietary. Since there is no existing example, current idea is that refer to rfWsnNodeIntFlashOadClient and rfWsnConcentratorOadServer in CC13x0 SDK 1.60.00.21, implement application level code, and directly using bim_onchip under C:\ti\simplelink_cc2640r2_sdk_2_20_00_49\examples\rtos\CC2640R2_LAUNCHXL\blestack\simple_peripheral_oad_onchip\tirtos\iar\bim_onchip for BIM part.

Is it on the right direction? Is there any modification needed for BIM?

  • 0
    TI__Mastermind 33460 points
    Hi Barbara,

    In general this is the right idea (re-use a BIM project and integrate that with the protocol stack application code)

    However there are some slight differences between CC13x0 and CC2640R2 when it comes to OAD.
    Namely this is related to features in CCFG (such as being able to configure the boot jump address on the R2 device) and changes related to the TI-RTOS ROM (in pg 1).

    So when migrating any CC13x0 project you will need to account for that in terms of its TI-RTOS config and its linker file.
    With the new CCFG feature, it is only required to reserve pg 31 for BIM (13x0/26x0 devices used to reserve pg 0 and pg 31)
    Keep this in mind when porting. It would be best to try and use the BLE versions of these linker files and adapt them for your needs instead of manually porting the CC13x0 linker file. Note that there are some BLE specific things in there which can be removed, but anything related to image headers and BIM should stay.

    Regarding the OAD image header, so long as the application has the header embedded in the image and filled out by the oad_image_tool (refer to SBP OAD examples from BLE for this) then the BIM should function. However, for completeness the image header fields related to wireless tech type should be changed from BLE (the BIM will not check these so this isn't required, but it should done).

    There are also changes required in the TI-RTOS .cfg file, namely to the resetVectorAddress, again I recommend referring to the BLE files.

    This might be a complicated task, but you are on the right track. Good luck!