CC2340R5: On-chip OAD via SIMPLELINK-CONNECT

Hi Seamus,

Understood. Can you clarify what image is running on the CC2340R5? Is it host_test or basic_ble OAD?

Best Regards,

Jan

Hi Jan,

The images in CC2340R5 are mcuboot_onchip + basic_persistent + basic_ble_oad_onchip

Best Regards,

Seamus

Hi Seamus,

Jan is out of the office (until Monday).

Can you provide a screenshot showing the status when the OAD transfer stops?

Also, can you please confirm this issue is the one you are discussing with Jan over email? Is it the case related to the HW you have shipped to Jan?

Best regards,

Hi Clement,

In my test, most of the failure cases stop at 0% - 5% (5 times) and the other stopped in the middle (1 times).

No, I think this issue is with the SIMPLELINK-CONNECT app. I tested on different EVMs and the issue was observed on both.

Best Regards, 

Seamus

Seamus Pu Do you try to use BTool to do OAD and check if you have similar failure rate?

Hi YK,

Yes, I've tested different EVMs with BTool and found no issues.

Best Regards,

Seamus

Seamus PuOK, we see similar unstable issue on SIMPLELINK-CONNECT app.

Hi Seamus,

As a quick test, could you try disabling standby mode on the on the BLE projects that you are using on the device? I would like to ensure there isn't an issue 

This can be done by unchecking the power management option inside the advanced settings tab within the BLE module in SysConfig.

Best Regards,

Jan

Hi Jan,

I disabled standby mode on basic_ble_oad_onchip and basic_persistent seems to have disabled it.

After the change of setting, for BTool OAD is still good, but APP OAD even the worse, it never succeeded even once.

Best Regards,

Seamus

Hi,

Got it. Thank you for the test. One last thing, I would like you to verify is if the issue occurs on Android devices as well. Do you have access to an Android device? If so, then could you try performing OAD using the android version of the application? Also, please re-enable the power management setting.

Best Regards,

Jan

Hi Jan,

For Android, I only tested it five times and it worked every time.

So the issue is on IOS APP?

Best Regards,

Seamus

Hi Seamus,

It is possible that this is an IOS issue. I will try to source an iOS device to test this with to see if I can reproduce the same behavior. In the meantime, could you share the Android device and OS version you are using for your successful test?

Best Regards,

Jan

Hi Jan,

I use HUAWEI nova 3i, and Android version is 9.

Best Regards,

Seamus

Hi Seamus,

I did some testing on my side. I sourced an iPhone 8 (Running IOS 16.6) and did 10 runs. I was able to succesfully perform the OAD 7/10 times. Two failures occured and the last run succeeded, but the OAD was extremely slow so I will consider that one a fail. App version was also 1.2.2.

However, I tested this on Android 13 (Using a Pixel 6 Pro) as well and saw 10/10 success which is leading me to believe this behavior is an issue on the iOS version of the application.

I have filed a ticket to get this addressed in a future release and truly apologize for the inconvenience this may be causing.

In the meantime, to ensure we are seeing the same behavior, are you able to reset the CC2340R5 when OAD fails and get into the persistent app?

Best Regards,

Jan

Hi Jan,

Thanks for reproducing the issue.

Yes, I guess I'm the same as you. When the OAD fails, I reset the CC2340R5 and it will get into the persistent app.

Best Regards,

Seamus  

Hi Seamus,

That matches the behavior I saw on my side. I will make sure to let the development team to know about this issue so it is address in a future release of the app.

Best Regards,

Jan