• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 52 subscribers
  • Views 630 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Compiler/CC2650: IAR Compiler

vidushi jain
Expert 1175 points
Part Number: CC2650
Other Parts Discussed in Thread: CC2640,

Tool/software: TI C/C++ Compiler

Hi All,

We are facing issue in OAD Image B from TI BLE SDK Version - ble_sdk_2_02_01_18 according to the steps given in document (BLE-Stack™ Version: 2.2.1) 
- We are able to build the Image B Code with OAD support but getting error OAD IMAGE Rejected in BLE Device Monitor attached are the logs on BLE device Monitor-:

19:05:57.142 > Get Device Information

19:05:57.207 > WriteRsp[2902]: st=0 n=0

19:05:57.210 > WriteRsp[2902]: st=0 n=0

19:05:57.214 > WriteRsp[2902]: st=0 n=0

19:06:00.788 > Binary snapshot: C:/ti/simplelink/ble_examples-master/examples/cc2650lp/simple_peripheral_observer/iar/app/FlashROM/Exe/cc2650lp_app_BAK.bin

19:06:02.272 > GAP Link Param Update: 0 0 800 0 1000

19:06:02.273 > Connection parameters updated

19:06:19.189 > WriteChar.[FFC1,16]: 01 00 00 28 42 42 42 42 00 00 00 00 00 00 00 00

19:06:19.190 > OAD started

19:06:20.233 > WriteRsp[FFC1]: st=0 n=0

19:06:20.236 > Notif.[FFC1]: st=0 n=8 00 00 80 16 41 41 41 41

19:06:20.242 > OAD image rejected

Data in HDR File made from BLE Device Monitor is :  f6 92 ff ff 01 00 00 28 42 42 42 42 00 24 ff ff

We follow all the steps from OAD User Guide for Building Image B. Please do needful in this context.

  • 0
    TI__Mastermind 25035 points
    Hi,

    Are you doing on-chip OAD? Does your application fulfill all these requirements:

    /* Requirements to begin OAD:
    * 1) LSB of image version cannot be the same, this would imply a code overlap
    * between currently running image and new image.
    * 2) Total blocks of new image must not exceed maximum blocks supported, else
    * the new image cannot fit.
    * 3) Block total must be greater than 0.
    */

    Best wishes
  • 0 in reply to Zahid Haq
    Expert 1175 points

    Hi,

    Thanks for your prompt response.

    Yes we are doing on-chip oad. How can i check all requirements you have mentioned above?

  • 0 in reply to vidushi jain
    TI__Expert 5250 points

    Hello Vidushi,

    These has been discussed in CC2640 BLE OAD User's Guide in document folder of your stack. Please refer the same specifically for Image version no and On-Chip OAD (Chapter 7).

    Regards,

    Vikas Chola

  • 0
    Expert 1175 points

    Part Number: CC2650

    Tool/software: TI C/C++ Compiler

    Hi All,

    We have 2 boards one is CC2650 LP & second Smart RF-Kit.

    In Launch_pad we have burn Host target APP & stack however in RF kit we have burn OAD TARGET APP as IMAGE A for continuous advertising.Now we make an oad image B from sample code SimpleBLEPeripheralObserver. Now we have done OAD from IMAGE A to IMAGE B using BLE Device Monitor OAD Completed successfully and IMAGE A disconnected but IMAGE B is not working(i.e. neither ADVERTISING NOR SCANNING).

    Now my query is will OAD Target sample code as image A will support BLE peripharal_observer as an application?