LAUNCHXL-CC26X2R1: CC2642R1 BLE OAD : simplelink starter app ios, how to upload custom image?

Hello Terence,

Thanks for reaching out.

What type of OAD are you executing? (on-chip, off-chip)

For me to have a reference of the process, could you please confirm you have followed the steps provided in this training laboratory: Bluetooth Low Energy - Over the Air Download (OAD) Fundamentals

BR,

David.

Hi David, I am using On-Chip OAD and following the steps in the OAD fundamentals.  And I am using simplelink_cc13x2_26x2_sdk_2_40_00_81 FYI

Hello Terence,

I will try to reproduce this on my end and report back.

What version of the Simple Link App are you working with?

Would it be possible to consider working with a more updated version of the SDK?

BR,

David.

Hi David, I am using the following tools for the development 

Sensor controller studio 2.9.0.208

CCS version 10.1.1.0004

SDK version simplelink_cc13x2_26x2_sdk_2_40_00_81

CC26X2R1 LaunchPad + Our own device(CC2642R1)

I can consider to work with a more updated version of SDK if it is compatible with my existing projects

thanks!

Hello Terence,

I mean the version of the Simple Link Connect Application that you downloaded into your iphone.

Could you please confirm as well that you are selecting the correct device and firmware when you are about to start the OAD?

Could you please try the same process with the out of the box simple_peripheral_oad_onchip_.bin file and see if it works with the app?

Are you also modifying the persistent app or using the one that comes in the example and only modifying the simple_peripheral_oad_onchip_.bin file?

Terence Kong said:

my persistent and BIM image works fine

BR,

David.

on the phone, I am using TI SimpleLink Starter version 5.12

we commented out some of followings for our purpose.

And we have tested it on the BTool and the OAD works on BTool.

Hello Terrence,

Could you please try with the Simple Link Connect app (https://www.ti.com/tool/SIMPLELINK-CONNECT-SW-MOBILE-APP) instead of using the Starter version?

Terence Kong said:

TI SimpleLink Starter version 5.12

Is it possible to get a Bluetooth sniffer log?

I will try to reproduce this on my end. If it is possible (not confidential information) that you can share the .bin files (persistent and application) that have been modified in this thread? (just drag and drop in the chat).

BR,

David.

Hi David, I can share with you the bin files but not in the forums, could you share your company email?

I have tried with Simple Link Connect app, and here is what I found.

1) Connect with my device

2) Select FW update with CC2652R1 and the local bin file

3)Start the update, I observed my device restarted..
Then the app alert with OAD Service not found

4) I rescan the device in the app and my device name has changed to OAD Persistent App

5) Then I restart the FW update again in step 

The app alert with Device did not reset to OAD service..

6) According to the app, I pressed the reset button on my device
The app alert with OAD Service not found

It is also observed, after the FW update, my device no longer running with the application but the OAD persistent

Hi,

Do not use the SimpleLink Connect App for OAD it has issues. Use the SimpleLink Starter App. I have detailed the procedure for Off Chip OAD here. For On Chip OAD you just need to program the correct images using Uniflash.

https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1329123/launchxl-cc26x2r1-cannot-flash-oad-with-new-simplelink-connect-app

-kel

Hi David, 

uploaded the wireshark sniffer log "CC2642R1_OAD.pcapng" for your information

David.

rename the wireshark sniffer log  "CC2642R1_OAD.pcapng" to  "CC2642R1_OAD.pcapng.log"

OAD failed on the Simple Link Connect app

CC2642R1_OAD.pcapng.log

Also attached to OAD log which finished successfully by the BTool

BTool_OAD.log

Hello Terence,

Thanks for the update, I will take a look.

In the meantime, could you please evaluate the possibility of upgrading the SDK version to the latest one: 7.40.00.77? OAD related issues have been solved between the SDK releases and we have found a similar issue to yours recently solved in the newest SDK.

Please let me know if you could do a quick test with the modified files using this new SDK.

BR,

David.

hi David, I will study the possibility to upgrade the SDK, but because our project has been using the old dev environment, that may involve a lot of work and time to launch is critical now.. not sure it's justify to make the upgrade at this moment.

Hello Terence,

Understood. Another point to justify the effort would be that if your product has not been released to production yet, it will require a SDK update as well in order to go through certification.

BR,

David.

Hi David,

I am running some test on the SDK7.40.00.77.

And seems there is issue...

1) Frist I compiled three projects from the SDK examples

- bim_onchip_CC26X2R1_LAUNCHXL_nortos_ticlang

- project_zero_CC26X2R1_LAUNCHXL_tirtos7_ticlang_oad

- simple_peripheral_oad_onchip_CC26X2R1_LAUNCHXL_tirtos7_ticlang_oad

Image files as attached in the zip file

SDK7_test.zip

2) I use uniflash to load the bim_onchip and the project_zero images. 

3) Use the latest iphone SimpleLink to scan the device and found the project zero device

4) Select FW update and load the simple_peripheral image from local

5) The OAD did finished

6) Restart the device and reconnect using both SimpleLink Connect and Starter

Both showing Project Zero instead of Simple Peripheral, seems the OAD didn't do anything???

Another test case by just changing the device name to "Project Zero123"

1) I created the image file "project_zero123_CC26X2R1_LAUNCHXL_tirtos7_ticlang_oad"

- project_zero123_CC26X2R1_LAUNCHXL_tirtos7_ticlang_oad.zip

2) I use uniflash to load the bim_onchip and the project_zero images. 

3) Use the latest iphone SimpleLink Connect to scan the device and found the project zero device

4) Select FW update and load the project_zero123_CC26X2R1_LAUNCHXL_tirtos7_ticlang_oad image from local

5) Then the app alert with bad TLV image

Hi Terence,

Just use SimpleLink Starter App. If after OAD you still see the same device name, turn off the Bluetooth and on again. After that scan again for devices.

-kel

Markel Robregado, I already did restart the BLE device and it is still showing the same device name.  That tells me the OAD wasn't get through even though the app says success.

Hi Terence,

There are 2 types of OAD the Off-Chip OAD and On-Chip OAD.

Off-Chip OAD example programs in the SDK.

1. Project Zero example program.
2. Simple Peripheral Off-Chip OAD example program.

For Off-Chip OAD procedure just follow the procedure in this post. You can use Uniflash. After flashing using Uniflash power off and on the board.

https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1329123/launchxl-cc26x2r1-cannot-flash-oad-with-new-simplelink-connect-app

For On-Chip OAD the only example program is Simple Peripheral On-Chip OAD example program. The required images at Uniflash are below.

1. BIM on chip hex.
2. Persistent app hex.
3. Simple Peripheral On-Chip OAD bin.

Unfortunately the SimpleLink Starter App does not support On-Chip OAD. I just tried to do it.

-kel

David , do you have chance to review the sniffer log and figure out what is wrong with the OAD?

it is too late for us to switch to 7.40.00.77 now

Hello Terence,

The ProjectZero example is meant to be use for off-chip OAD, please see: Task 1 – Run ProjectZero Project inside of our training material. Therefore, you must have the bim_offchip project present in the internal flash of the device first for the project to work correctly. Could you please try with off chip in that case, or with the persistent app if using on-chip OAD?

BR,

David.

David , I am using on-chip OAD indeed, and have rerun the test using on-chip OAD FYI

Here attached with the BLE sniff log again.

OAD_OnChip.zip

Also attached the persistence and the BIM image FYI

cc26x2r1lp_bim_onchip.zipble5_simple_peripheral_oad_onchip_cc26x2r1lp_persist_app_FlashROM_Release.zip

Hi Terence,

You are encountering On-Chip OAD issues using SimpeLink Connect App. From my testing On-Chip OAD does not work using SimpleLink Starter App. However, as you have mentioned On-Chip OAD works using Btool. The On-Chip OAD issues using SimpleLink Connect App or SimpleLink Starter App should not be a major block to your project development. You should work with an app developer to create a custom app with working On-Chip OAD.

-kel

Hi Markel Robregado, they should remove the On-Chip OAD feature from their app if this is not working.  This is waste of our time to debug it ...