CC1352R: Switching to Persistant App does not work correctly

I have assigned someone from the BLE team to look into this.

BR

Siri

Hi,

The problem is likely due to not processing event.

Please review the Simple Link Academy lab dealing with OAD for details.

Regards,

Hi, Clément 

Do you mean that this is a error in our code? This problem occurs in the simple_peripheral_oad_onchip project from the SDK samples folder.

Hi,

I will have a look to this example, too. Let me know if you need more assistance.

Regards,

Thank you, we will be waiting for your reply.

Hi Vitaliy, 

Are you using a custom board or a LaunchPad?
If custom board, have you tested with a LaunchPad?

What are you connecting the device to, another CC1352R device or phone? 

Have you made any modifications to the SDK example?

Thanks, 
Elin

Hi, Elin.

We used a LaunchPad LAUNCHXL-CC1352R1. We connected to the LaunchPad using an Android smartphone with the SimpleLink Starter app. We did not make any changes to the SDK.

Hi Vitaliy, 

Apologies for the delay and thanks for checking. 

There is a new version of the SDK available here: http://www.ti.com/tool/SIMPLELINK-CC13X2-26X2-SDK

Can you test with the new SDK and see if you see the same issue?

Thanks, 
Elin

Hi, Elin W 

We just tested example from the SDK 4.10.0.78 on Launchpad and found the same problem.

Hi Vitaliy,

Thanks for testing. I will test and see if I can reproduce the problem. I'll let you know as soon as I have an update. 

Thanks, 
Elin

Hi, Elin W 

Thank you. We'll waiting for your reply.

Hi Vitaliy, 

Sorry for the lack of progress over the last weeks. I'm going to test it this week but would you mind sharing a step-by-step list on how you test to see this issue?

Thanks, 
Elin

Hi, Elin W

Steps to reproduce:

1. Flash to LAUNCHXL-CC1352R1 Launchpad simple_peripheral_oad_onchip_CC13X2R1_LAUNCHXL_tirtos_ccs, ble5_simple_peripheral_oad_onchip_cc13x2r1lp_persistent_app and cc13x2r1lp_bim_onchip from SDK examples folder. We tested on SDK v.3.40.0.02 and v.4.10.0.78.

2. Connect to device with SimpleLink Starter.

3. Write 0x01 to OAD Start/Reset characteristic.

4. Disconnect from device.

5. Scan the available BLE devices and make sure that a device with the name SP OAD on-chip is discovered.

Expected: OAD Persistent App is discovered on 5th step.

6. After trying to connect to the SP OAD on-chip after the 5th step, the connection fails, but after that the device switches to the Persistant App.

Hi Vitaliy, 

Thanks for providing the steps. 

The phone typically saves the name of the devices so to see the updated name, the cache has to be cleared first or the name is updated when reconnecting to the device. So if you clear the cache on the phone between steps 4 and 5, you should see the updated name on the app when scanning. 

Having said that, I tried the same thing with the CC26x2R LaunchPad (I unfortunately didn't have a CC1352R LaunchPad at home) and I am encountering the same problem when trying to reconnect to the device, but only sometimes. When I don't refresh the list of BLE devices, it always takes me a couple of tries to reconnect, and sometimes it times out and cannot connect. But when I refresh before trying to reconnect then it usually connects on the first try. 

But I never see that the name changes to the persistent app. I'll perform some more tests and get back to you as soon as I have an update. 

Thanks, 
Elin

Hi, Elin W 

You, apparently, misunderstood me. Our problem is not that the device name is not updated, but that Simple Peripheral does not switch to the Persistant App (the red and green LEDs do not blink, indicating the beginning of the Persistant App) when disconnecting from the device. This only happens when you try to connect again.
P.S. We’ll clarify that this problem appears only on the Android-smartphone (on the iPhone, switching occurs immediately after disconnecting from the device).