Git/Installer Release Version: simplelink_cc2640r2_sdk_2_40_00_18_eng

Platform: CC2640R2 LaunchPad

Application: simple_peripheral_oad_onchip

Problem Reproducibility: 100%

Problem Description: When performing an unsecure on-chip OAD with a secure BLE connection, the OAD Target device resets and runs the user app after receiving the reset command; the persistent app is supposed to run after the reset command is received. After re-bonding with the user app and sending the reset command again, the device successfully boots into the persistent app and the OAD can proceed after bonding with the persistent app.

The issue only affects the first unsecure on-chip OAD and does not happen during secure on-chip OAD with a secure BLE connection

Steps to re-create problem:

1. Use CCS 8.2 to build unsecure build configurations of simple_peripheral_oad_onchip projects from the CC2640R2 SDK with the OAD_BLE_SECURITY predefined symbol for the simple_peripheral_cc2640r2lp_oad_onchip_app and persistent_app_cc2640r2lp projects.
2. Flash a CC2640R2 launchpad with the prebuilt host test image from the SDK and flash another CC2640R2 launchpad with on-chip images in the following order
   1. persistent app .hex image
   2. onchip stack .hex image
   3. onchip bim .hex image
   4. simple peripheral onchip oad app .bin image
3. Use BTool from the SDK to pair and bond with the OAD Target. Instructions are in the 'Using BLE Security' section of the BTool user's guide
4. Observe COM port output of OAD Target device and perform on-chip OAD. After BTool sends the reset command, the red LED on the launchpad will blink and COM port output will refresh to indicate  the device has booted into the user app.