SIMPLELINK-CC2640R2-SDK: BLE 5 Off-Chip OAD Example Program FAIL?

Hi TI,

I change my setup to 2 CC2640R2 Launchpad. 1 launchpad programmed with cc2640r2lp_host_test.hex from C:\simplelink_cc2640r2_sdk_1_35_00_33\examples\rtos\CC2640R2_LAUNCHXL\ble5stack\hexfiles. Same results. The Advertisement name did not change.

- kel

Hi TI,

     I have done the Off-Chip Out of Box Demo procedures several times and it really does not work. At Btool it says "OAD Download Successful". But actually it is a failed OAD. Here below are last BTool Message. I need to implement OAD at my work and I am stuck with this problem. I hope to get helpful replies soon. 

[10667] : <Rx> - 10:12:42.542
-Type           : 0x04 (Event)
-EventCode      : 0x00FF (HCI_LE_ExtEvent)
-Data Length    : 0x09 (9) bytes(s)
 Event          : 0x051B (1307) (ATT_HandleValueNotification)
 Status         : 0x00 (0) (Success)
 ConnHandle     : 0x0000 (0)
 PduLen         : 0x03 (3)
 Handle         : 0x003C (60)
 Value          : 00
Dump(Rx):
0000:04 FF 09 1B 05 00 00 00 03 3C 00 00             .........<..
--------------------------------------------------------------------
[10668] : <Info> - 10:12:42.551
OAD Image Status
Status = 0x00 OAD_SUCCESS
--------------------------------------------------------------------
[10669] : <Info> - 10:12:42.554
OAD Waiting For Device Disconnect
--------------------------------------------------------------------
[10670] : <Info> - 10:12:43.117
Device Disconnected
Handle = 0x0000
Addr Type = 0x00 (Public)
BDAddr = 0A:D0:AD:0A:D0:AD
--------------------------------------------------------------------
[10671] : <Info> - 10:12:43.140
OAD Download Successful
--------------------------------------------------------------------
[10672] : <Rx> - 10:12:43.112
-Type           : 0x04 (Event)
-EventCode      : 0x00FF (HCI_LE_ExtEvent)
-Data Length    : 0x06 (6) bytes(s)
 Event          : 0x0606 (1542) (GAP_TerminateLink)
 Status         : 0x00 (0) (Success)
 ConnHandle     : 0x0000 (0)
 Reason         : 0x08 (8) (Supervision Timeout)
Dump(Rx):
0000:04 FF 06 06 06 00 00 00 08                      .........
--------------------------------------------------------------------

- kel

Hi TI,

     Yesterday, I change the BIM SPI pins to launchpad original and I had one successful Off-Chip OAD. I see the Advertisement Name changed.

     So, I thought I must have modified something with the code that cause the OAD failure. I have a backup installation of SDK v1.35 at C:\. I copy the backup off-chip bim, app , and stack to my SDK v1.35 at C:\ti. I follow the Off-Chip OAD procedure again actually about more than 10x already. I get a OAD_FLASH_ERR and OAD Download Not Successful error message. See, last BTool Log below. This is a big issue for us, since the On-Chip OAD BLE 5 is not supported and now the Off-Chip OAD demo does not work. My setup is 2 CC2640R2F Launchpad. 1 CC2640R2F Launchpad has host test program.

[93] : <Info> - 08:59:59.980
OAD Block Size = 16
--------------------------------------------------------------------
[94] : <Rx> - 08:59:59.977
-Type           : 0x04 (Event)
-EventCode      : 0x00FF (HCI_LE_ExtEvent)
-Data Length    : 0x09 (9) bytes(s)
 Event          : 0x051B (1307) (ATT_HandleValueNotification)
 Status         : 0x00 (0) (Success)
 ConnHandle     : 0x0000 (0)
 PduLen         : 0x03 (3)
 Handle         : 0x003C (60)
 Value          : 02
Dump(Rx):
0000:04 FF 09 1B 05 00 00 00 03 3C 00 02             .........<..
--------------------------------------------------------------------
[95] : <Info> - 08:59:59.998
OAD Image Status
Status = 0x02 OAD_FLASH_ERR
--------------------------------------------------------------------
[96] : <Info> - 09:00:00.000
OAD - Restore Connection Settings
--------------------------------------------------------------------
[97] : <Error> - 09:00:00.004
OAD Download Not Successful
--------------------------------------------------------------------
[98] : <Tx> - 09:00:00.004
-Type           : 0x01 (Command)
-OpCode         : 0xFE11 (GAP_UpdateLinkParamReq)
-Data Length    : 0x0A (10) byte(s)
 ConnHandle     : 0x0000 (0)
 IntervalMin    : 0x0050 (80)
 IntervalMax    : 0x0050 (80)
 ConnLatency    : 0x0000 (0)
 ConnTimeout    : 0x07D0 (2000)
Dump(Tx):
0000:01 11 FE 0A 00 00 50 00 50 00 00 00 D0 07       ......P.P.....
--------------------------------------------------------------------
[99] : <Rx> - 09:00:00.037
-Type           : 0x04 (Event)
-EventCode      : 0x00FF (HCI_LE_ExtEvent)
-Data Length    : 0x06 (6) bytes(s)
 Event          : 0x067F (1663) (GAP_HCI_ExtentionCommandStatus)
 Status         : 0x00 (0) (Success)
 OpCode         : 0xFE11 (GAP_UpdateLinkParamReq)
 DataLength     : 0x00 (0)
Dump(Rx):
0000:04 FF 06 7F 06 00 11 FE 00                      .........
--------------------------------------------------------------------
[100] : <Rx> - 09:00:00.098
-Type           : 0x04 (Event)
-EventCode      : 0x00FF (HCI_LE_ExtEvent)
-Data Length    : 0x0B (11) bytes(s)
 Event          : 0x0607 (1543) (GAP_LinkParamUpdate)
 Status         : 0x00 (0) (Success)
 ConnHandle     : 0x0000 (0)
 ConnInterval   : 0x0050 (80)
 ConnLatency    : 0x0000 (0)
 ConnTimeout    : 0x07D0 (2000)
Dump(Rx):
0000:04 FF 0B 07 06 00 00 00 50 00 00 00 D0 07       ........P.....
--------------------------------------------------------------------

- kel

Hi Zahid,

I confirmed the original out of box demo to be working. The cause of the failed OAD_FLASH_ERR is that at CC2640R2_LAUNCHXL.h, I added another #define with same pin as the SPI Flash CS.

- kel