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.

Devices stop advertising after doing OAD on cc2650 Sensortag

Other Parts Discussed in Thread: CC2541, CC2650, CC2640

I am Doing OAD to simpleBLEPeripheral sample Code Provided by TI.
I followed the Process given in the OAD Guide to Produce a super HEX file which include BIM_ExtFlash+Stack+Application.
Then i used Flash Programer 2 to Load the Code into sensor Tag.
TH

>Initiate access to target: XDS-00000000.
>Reading file: C:/Users/SenseGiz 1/peripheral1/SimpleBLEPeripheral/FlashOnly_ST_OAD_ExtFlash/OAD_IMAGE_FULL.hex.
>Start flash erase ...
>Erase finished successfully.
>Start flash programming ...
>Programming finished successfully.
>Start flash verify ...
>Skip verification of unassigned page: 0.
>Skip verification of unassigned page: 10.
>Skip verification of unassigned page: 11.
>Skip verification of unassigned page: 12.
>Skip verification of unassigned page: 13.
>Page: 1 verified OK.
>Page: 2 verified OK.
>Page: 3 verified OK.
>Page: 4 verified OK.
>Page: 5 verified OK.
>Page: 6 verified OK.
>Page: 7 verified OK.
>Page: 8 verified OK.
>Page: 9 verified OK.
>Page: 14 verified OK.
>Page: 15 verified OK.
>Page: 16 verified OK.
>Page: 17 verified OK.
>Page: 18 verified OK.
>Page: 19 verified OK.
>Page: 20 verified OK.
>Page: 21 verified OK.
>Page: 22 verified OK.
>Page: 23 verified OK.
>Page: 24 verified OK.
>Page: 25 verified OK.
>Page: 26 verified OK.
>Page: 27 verified OK.
>Page: 28 verified OK.
>Page: 29 verified OK.
>Page: 30 verified OK.
>Page: 31 verified OK.
>Verification finished successfully.
>Reset target ...
>Reset of target successfull.

I got this response on Uploading the Code into the Sensor tag.
I thing this means that code has been Successfully loaded.
The Problem i am facing is that The device is not Advertising. Can Someone please help me out in getting this Problem resolved.?

  • Hi,

    Have you also tried just downloading each project separately from the IDE? Which script did you use?

    Best wishes
  • Hey Zahid,

    Yes i tried Dubugging all the three files sepratly also but the result was same for that.
    i am using this script for making Super_hex_file

    C:/Python27/Scripts/hexmerge.py  -o "${PROJECT_LOC}/FlashOnly_ST_OAD_ExtFlash/OAD_IMAGE_FULL.hex" -r "000:1FFFF" --overlap=error "${PROJECT_LOC}/FlashOnly_ST_OAD_ExtFlash/${ProjName}.hex":0000:1EFFF "${PROJECT_LOC}/../${ProjName}Stack/FlashROM/${ProjName}Stack.hex" "C:/Users/SenseGiz 1/peripheral1/BIM_ExtFlash/FlashOnly/BIM_ExtFlash.hex":1F000:1FFFF
    

    Please let me know if m going wrong somewhere.

  • Hey Zahid,

    Any Suggestion for the Above Issue??
  • I tried some other approch by using that device start advertising after Getting Debugged.

    When I try to erase "Pages in Image" while programing that Device is advesrting after getting COde uploaded.

    But when i use "All Unprotected Pages" while erasing then Devices doesn't Advertise.

    So is it ok to use the "Pages in Image" Method???

    Thanks

  • Hi Pradeep,

    BIM also takes up the first page. Based on your script, it is only taking up the last page. Please use similar script used in the BLE OAD User's Guide section 8.3:

    "C:\Python27\python" "C:/Python27/Scripts/hexmerge.py" -o "${PROJECT_LOC}/FlashOnly_ST_OAD_ExtFlash/SUPER_IMAGE_FULL.hex" -r "0000:1FFFF" --overlap=error "${PROJECT_LOC}/FlashOnly_ST_OAD_ExtFlash/${ProjName}.hex":1000:1EFFF "${PROJECT_LOC}/../SimpleBLEPeripheralStack/FlashROM/SimpleBLEPeripheralStack.hex":1000:1EFFF "${PROJECT_LOC}/../../../../util/BIM_extflash/CC26xx/CCS/FlashOnly/BIM_ExtFlash.hex":0000:1FFFF

    Best wishes

  • Hey Zahid,

    Thanks for the Guidance. This Code worked for me very fine.

    Now i was trying to do OAD with TI SENSORTAG APP in which i was using bin file which inculude app and Stack.

    These are the error which i am facing. can u guide me here also??

    How to get a Different image??

    In cc2541 we use to get two images i.e Image_A and Image_B, Can this be done in cc2650 also??

  • Hey Zahid,

    any Solution for the Image Problem??
    Thnaks
  • Hi Pradeep,

    Can you try reflashing the SensorTag image on the SensorTag? Are you using the SensorTag project from the latest BLE 2.1.1 release?

    Thanks
  • Hey Zahid,

    Yes i had tried Re flashing the image on the Sensortag and yup i'm using the Latest BLE STACK.
  • Hey Zahid,

    I saw some post on the Fourm which suggest that its not Possible to Do OAD for CC2650 for SImpleBLEPEripheral using the TI SensorTag APP.
    Is it true?
    is only way to Do OAD for CC2650 as if now is to use BLE Device Monitor which is a "Safe" mode??
    or any other way by which i can test OAD?

    Fourms i saw:
    1.e2e.ti.com/.../495201
    2.e2e.ti.com/.../496349


    Thanks
  • Hi Pradeep,

    We plan to support OAD with SimpleBLEPeripheral with our SDK 4.2 release. We recommend to use Device Monitor for now.

    Best wishes
  • Thanks for all the help.
  • Hey Zahid,
    Now i am using Ble Device Monitor.
    Its not accepting ".Bin" file so tried it wiht Super_Hex file on doing so its showing two error.

    When I try using "FAST Mode" Its having Overflow Error and when i don't select "fast Mode" its show Time out.
    So can u please guide me in this thing also.

    Thanks
  • Hi Pradeep,

    Please decrease Blk/conn rate to see if timeout does not occur. This is also described in the sectino 7.6.1 Using BLE Device Monitor in the BLE OAD User’s Guide found in the SDK.

    Also try loading just the application only hex file.
     
    Best wishes

  • I am building an off-chip OAD for simple_peripheral project from BLE SDK 2_02_00_31 on 2650.I built the bim,,ble stack and the application image ,as explained in the CC2640 BLE OAD User's Guide. I am getting the following error while  performing oad using ble device monitor.The device disconnects at 0%. 
    13:32:51.977 > Scan request ...
    13:32:52.544 > GAP Device Information: status=0 type=0x00 [len=11]
    13:32:52.544 > MAC address (ind. adv): 98:7B:F3:2E:E3:86
    13:32:52.544 > Scan resp: ad=0x01 len=2
    13:32:52.544 > Scan resp: ad=0x02 len=7
    13:32:52.544 > GAP Device Information: status=0 type=0x04 [len=18]
    13:32:52.544 > Device found: SenseGiz-FIND
    13:32:52.544 > Scan resp: ad=0x0a len=2
    13:32:52.544 > MAC address (scan. resp): 98:7B:F3:2E:E3:86
    13:32:52.986 > Scan cancel request ...
    13:32:53.006 > Scan finished [1.29 sec]
    13:32:53.006 > GAP Device Discovery: 0 device(s), status=0x30
    13:33:08.765 > Scan request ...
    13:33:09.336 > GAP Device Information: status=0 type=0x00 [len=11]
    13:33:09.336 > MAC address (ind. adv): 98:7B:F3:2E:E3:86
    13:33:09.336 > Scan resp: ad=0x01 len=2
    13:33:09.336 > Scan resp: ad=0x02 len=7
    13:33:09.336 > GAP Device Information: status=0 type=0x04 [len=18]
    13:33:09.336 > Device found: SenseGiz-FIND
    13:33:09.336 > Scan resp: ad=0x0a len=2
    13:33:09.336 > MAC address (scan. resp): 98:7B:F3:2E:E3:86
    13:33:10.304 > GAP Device Information: status=0 type=0x00 [len=11]
    13:33:10.305 > MAC address (ind. adv): B0:B4:48:EA:1E:06
    13:33:10.305 > Scan resp: ad=0x01 len=2
    13:33:10.306 > Scan resp: ad=0x02 len=7
    13:33:10.320 > GAP Device Information: status=0 type=0x04 [len=15]
    13:33:10.321 > Device found: SenseGiz-FIND
    13:33:10.322 > MAC address (scan. resp): B0:B4:48:EA:1E:06
    13:33:11.549 > GAP Device Information: status=0 type=0x00 [len=11]
    13:33:11.549 > MAC address (ind. adv): B0:B4:48:EA:17:04
    13:33:11.549 > Scan resp: ad=0x01 len=2
    13:33:11.549 > Scan resp: ad=0x02 len=7
    13:33:11.559 > GAP Device Information: status=0 type=0x04 [len=15]
    13:33:11.559 > Device found: SenseGiz-FIND
    13:33:11.559 > MAC address (scan. resp): B0:B4:48:EA:17:04
    13:33:18.896 > Scan cancel request ...
    13:33:18.926 > Scan finished [10.162 sec]
    13:33:18.926 > GAP Device Discovery: 0 device(s), status=0x30
    13:33:22.159 > Scan request ...
    13:33:22.200 > GAP Device Information: status=0 type=0x00 [len=11]
    13:33:22.200 > MAC address (ind. adv): 98:7B:F3:2E:E3:86
    13:33:22.200 > Scan resp: ad=0x01 len=2
    13:33:22.200 > Scan resp: ad=0x02 len=7
    13:33:22.462 > GAP Device Information: status=0 type=0x00 [len=13]
    13:33:22.462 > MAC address (ind. adv): 20:CD:39:AA:05:36
    13:33:22.463 > Scan resp: ad=0x01 len=2
    13:33:22.463 > Scan resp: ad=0x02 len=7
    13:33:22.464 > Scan resp: ad=0x18 len=20
    13:33:23.078 > GAP Device Information: status=0 type=0x00 [len=11]
    13:33:23.078 > MAC address (ind. adv): B0:B4:48:EA:17:04
    13:33:23.078 > Scan resp: ad=0x01 len=2
    13:33:23.078 > Scan resp: ad=0x02 len=7
    13:33:23.162 > GAP Device Information: status=0 type=0x00 [len=11]
    13:33:23.163 > MAC address (ind. adv): B0:B4:48:EA:1E:06
    13:33:23.163 > Scan resp: ad=0x01 len=2
    13:33:23.164 > Scan resp: ad=0x02 len=7
    13:33:23.182 > GAP Device Information: status=0 type=0x04 [len=15]
    13:33:23.183 > Device found: SenseGiz-FIND
    13:33:23.185 > MAC address (scan. resp): B0:B4:48:EA:1E:06
    13:33:32.296 > Scan cancel request ...
    13:33:32.326 > Scan finished [10.167 sec]
    13:33:32.326 > GAP Device Discovery: 0 device(s), status=0x30
    13:33:43.531 > Scan request ...
    13:33:43.606 > GAP Device Information: status=0 type=0x00 [len=9]
    13:33:43.606 > MAC address (ind. adv): B0:B4:48:EA:1A:06
    13:33:43.606 > Scan resp: ad=0x01 len=2
    13:33:43.606 > Scan resp: ad=0x02 len=5
    13:33:43.619 > GAP Device Information: status=0 type=0x04 [len=30]
    13:33:43.619 > Device found: SimpleBLEPeripheral
    13:33:43.619 > Scan resp: ad=0x12 len=5
    13:33:43.620 > Scan resp: ad=0x0a len=2
    13:33:43.620 > MAC address (scan. resp): B0:B4:48:EA:1A:06
    13:33:45.427 > GAP Device Information: status=0 type=0x00 [len=11]
    13:33:45.427 > MAC address (ind. adv): 98:7B:F3:2E:E3:86
    13:33:45.427 > Scan resp: ad=0x01 len=2
    13:33:45.427 > Scan resp: ad=0x02 len=7
    13:33:45.437 > GAP Device Information: status=0 type=0x04 [len=18]
    13:33:45.438 > Device found: SenseGiz-FIND
    13:33:45.438 > Scan resp: ad=0x0a len=2
    13:33:45.438 > MAC address (scan. resp): 98:7B:F3:2E:E3:86
    13:33:48.878 > GAP Device Information: status=0 type=0x00 [len=11]
    13:33:48.878 > MAC address (ind. adv): B0:B4:48:EA:1E:06
    13:33:48.878 > Scan resp: ad=0x01 len=2
    13:33:48.878 > Scan resp: ad=0x02 len=7
    13:33:48.878 > GAP Device Information: status=0 type=0x04 [len=15]
    13:33:48.878 > Device found: SenseGiz-FIND
    13:33:48.878 > MAC address (scan. resp): B0:B4:48:EA:1E:06
    13:33:53.671 > Scan cancel request ...
    13:33:53.691 > Scan finished [10.160 sec]
    13:33:53.691 > GAP Device Discovery: 0 device(s), status=0x30
    13:33:54.498 > Connect request
    13:33:54.608 > Gap Link Established: h=0 CI=1544 SL=0 TO=59392
    13:33:54.608 > SimpleBLEPeripheral connected
    13:33:54.658 > Service discovery started
    13:33:54.688 > ReadByGrpTypeRsp: st=0 n=19
    13:33:54.718 > ReadByGrpTypeRsp: st=0 n=7
    13:33:54.748 > ReadByGrpTypeRsp: st=0 n=21
    13:33:54.748 > ReadByGrpTypeRsp: st=26 n=0
    13:33:54.748 > Primary Service Discovery done [0.90 sec]
    13:33:54.748 > Characteristic description discovery started
    13:33:54.818 > FindInfoRsp: st=0 n=21 fmt=1
    13:33:54.818 > FindInfoRsp: st=0 n=21 fmt=1
    13:33:54.818 > FindInfoRsp: st=0 n=21 fmt=1
    13:33:54.828 > FindInfoRsp: st=0 n=21 fmt=1
    13:33:54.848 > FindInfoRsp: st=0 n=21 fmt=1
    13:33:54.878 > FindInfoRsp: st=0 n=21 fmt=1
    13:33:54.888 > FindInfoRsp: st=0 n=21 fmt=1
    13:33:54.918 > FindInfoRsp: st=0 n=21 fmt=1
    13:33:54.948 > FindInfoRsp: st=0 n=21 fmt=1
    13:33:54.978 > FindInfoRsp: st=0 n=5 fmt=1
    13:33:54.988 > FindInfoRsp: st=0 n=19 fmt=2
    13:33:55.008 > FindInfoRsp: st=0 n=13 fmt=1
    13:33:55.018 > FindInfoRsp: st=0 n=19 fmt=2
    13:33:55.038 > FindInfoRsp: st=0 n=13 fmt=1
    13:33:55.048 > FindInfoRsp: st=0 n=19 fmt=2
    13:33:55.068 > FindInfoRsp: st=0 n=9 fmt=1
    13:33:55.108 > FindInfoRsp: st=0 n=19 fmt=2
    13:33:55.128 > FindInfoRsp: st=0 n=9 fmt=1
    13:33:55.138 > FindInfoRsp: st=26 n=0 fmt=1
    13:33:55.138 > Characteristic Description Discovery done [0.390] sec
    13:33:55.141 > Characteristic discovery started
    13:33:55.168 > ReadyByTypeResp: st=0 n=22
    13:33:55.208 > ReadyByTypeResp: st=0 n=22
    13:33:55.218 > ReadyByTypeResp: st=0 n=22
    13:33:55.248 > ReadyByTypeResp: st=0 n=22
    13:33:55.268 > ReadyByTypeResp: st=0 n=22
    13:33:55.278 > ReadyByTypeResp: st=0 n=15
    13:33:55.308 > ReadyByTypeResp: st=0 n=22
    13:33:55.318 > ReadyByTypeResp: st=0 n=22
    13:33:55.358 > ReadyByTypeResp: st=0 n=22
    13:33:55.378 > ReadyByTypeResp: st=0 n=22
    13:33:55.428 > ReadyByTypeResp: st=26 n=0
    13:33:55.428 > Characteristic Discovery done [0.287] sec
    13:33:55.428 > OAD support detected
    13:33:55.448 > WriteChar.[2902]: v=0000 
    13:33:55.648 > WriteChar.[2902]: v=0000 
    13:33:55.848 > WriteChar.[2902]: v=0001 
    13:33:56.048 > WriteChar.[2902]: v=0000 
    13:33:56.248 > WriteChar.[2902]: v=0000 
    13:33:56.448 > WriteChar.[2902]: v=0001 
    13:33:56.668 > Get Device Information
    13:33:56.668 > ReadChar[2A26]
    13:33:56.718 > WriteRsp[2A26]: st=0 n=0
    13:33:56.718 > WriteRsp[2A26]: st=0 n=0
    13:33:56.718 > WriteRsp[2A26]: st=0 n=0
    13:33:56.728 > WriteRsp[2A26]: st=0 n=0
    13:33:56.728 > WriteRsp[2A26]: st=0 n=0
    13:33:56.728 > WriteRsp[2A26]: st=0 n=0
    13:33:56.728 > ReadResp[2A26]: st=0 n=17, 46 69 72 6D 77 61 72 65 20 52 65 76 69 73 69 6F 6E
    13:33:56.728 > Firmware: Firmware Revision
    13:34:07.178 > Binary snapshot: C:/Users/Parnav/Downloads/merged (1)_BAK.bin
    13:34:09.125 > WriteChar.[FFC1,16]: BB C2 FF FF 00 00 00 78 45 45 45 45 00 04 01 FF
    13:34:09.125 > OAD started
    13:34:09.144 > WrNoRsp[FFC2,18]: 00 00 BB C2 FF FF 00 00 00 78 45 45 45 45 00 04 01 FF
    13:34:09.144 > WrNoRsp[FFC2,18]: 01 00 68 41 00 20 D1 75 00 00 F9 98 00 00 F9 98 00 00
    13:34:09.147 > WrNoRsp[FFC2,18]: 02 00 F9 98 00 00 F9 98 00 00 F9 98 00 00 F9 98 00 00
    13:34:09.147 > WrNoRsp[FFC2,18]: 03 00 F9 98 00 00 F9 98 00 00 F9 98 00 00 F9 98 00 00
    13:34:09.176 > WrNoRsp[FFC2,18]: 04 00 F9 98 00 00 F9 98 00 00 AF 9E 00 00 D7 4A 2D E9
    13:34:09.176 > WrNoRsp[FFC2,18]: 05 00 F0 4F 01 26 AD F1 14 0D 02 F1 41 01 04 90 D1 48
    13:34:09.178 > WrNoRsp[FFC2,18]: 06 00 C1 F8 CF 6F 07 68 00 2F FC D0 D1 48 C0 23 44 38
    13:34:09.178 > WrNoRsp[FFC2,18]: 07 00 03 60 CD 4B 02 90 03 F1 08 00 00 68 80 08 04 D2
    13:34:09.206 > WrNoRsp[FFC2,18]: 08 00 58 68 00 0C 40 F0 F0 00 00 E0 72 20 D9 4F DA 4C
    13:34:09.206 > WrNoRsp[FFC2,18]: 09 00 01 93 00 25 87 F8 4C 02 A4 F1 D0 08 18 46 C1 F8
    13:34:09.208 > WrNoRsp[FFC2,18]: 0A 00 FF 5F D0 F8 0C A0 58 F8 04 0C C0 F3 04 60 09 F0
    13:34:09.208 > WrNoRsp[FFC2,18]: 0B 00 8F FB 00 EB 2A 70 40 1C 16 28 05 DA 10 F1 0A 0F
    13:34:09.241 > WrNoRsp[FFC2,18]: 0C 00 B8 BF 6F F0 09 00 00 E0 15 20 00 F0 1F 00 40 F4
    13:34:09.241 > WrNoRsp[FFC2,18]: 0D 00 F8 50 A7 F8 64 02 10 68 80 08 28 BF 4A F0 40 6A
    13:34:09.244 > WrNoRsp[FFC2,18]: 0E 00 C6 49 4F EA DA 60 4F EA 9A 65 80 F0 01 00 00 F0
    13:34:09.244 > WrNoRsp[FFC2,18]: 0F 00 01 00 08 60 85 F0 01 00 00 F0 01 00 88 60 50 46
    13:34:09.270 > WrNoRsp[FFC2,18]: 10 00 04 F0 EA FD 00 22 04 46 15 46 09 F0 FF FB 00 B9
    13:34:09.270 > WrNoRsp[FFC2,18]: 11 00 35 46 2A 46 BA 4D 2B 68 00 2B FC D0 BF 48 00 F1
    13:34:09.274 > WrNoRsp[FFC2,18]: 12 00 08 09 C9 F8 10 40 2E 60 0A B1 09 F0 F5 FB 08 F0
    13:34:09.274 > WrNoRsp[FFC2,18]: 13 00 2B FF B4 4C 40 F2 FF 32 00 23 80 B2 2C 21 00 90
    13:34:09.277 > Command Status: 16 FDB6 [len=0]
    13:34:09.277 > OAD host overflow
    13:34:14.302 > Command Status: 16 FDB6 [len=0]
    13:34:14.369 > Command Status: 16 FDB6 [len=0]
    13:34:14.369 > Command Status: 16 FDB6 [len=0]
    13:34:19.138 > WriteRsp[FFC1]: st=20 n=0
    13:34:19.138 > WriteRsp failed
    13:34:19.148 > GAP Link Terminated: status=0 h=0 reason=0x08
    13:34:19.158 > SimpleBLEPeripheral disconnected

    How do I resolve this error?

  • Under similar circumstances, I got WriteRsp[FFC1]: st=20 n=0
    and then WriteRsp failed almost right after sending the image header. Have you managed to solve this problem?