LAUNCHXL-CC26X2R1: CC2642R1 BLE OAD : simple peripheral OAD ON Chip, the OAD process didn't start

Hello Terrence,

I apologize for the inconvenience you are having with the OAD and the mobile applications. The team has recently solved the issue related to TLV Magic (which I see you reported in your previous thread as well) and the fix will come in the next release of the mobile app.

I am working on reproducing this on my end and reviewing it with the SimpleLink Connect app.

The OAD process with the same files works fine using BTool? I know you have done this from your previous thread, but just wanted to confirm in case there is any modifications.

Could you please try as well to use the precompiled bim_onchip.hex file included in the SDK: <SDK>\examples\rtos\CC26X2R1_LAUNCHXL\ble5stack\hexfiles\bim_onchip\Release?

BR,

David.

David , thanks for your support and yes we have tried using the BTool and it works fine.

Do you have the ETA regarding the next release of the mobile app?

also tried to use the pre compiled bim_onchip.hex file included in the SDK, it failed too

Hello Terence,

The TLV magic issue is described in this e2e thread:/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1329123/launchxl-cc26x2r1-cannot-flash-oad-with-new-simplelink-connect-app. It has already been reported and the BAD TLV magic error has been recently solved as described in the thread. The new version of the Simple Link application should be released soon (during the next two weeks - although I cannot give a specific data).

After the OAD fails, does it boot into the persistent app or does it remains in the simple_peripheral_oad_onchipv1?

BR,

David.

The device booted into the persistent app and stuck there.

Hello Terence,

I will test your project files with the team using the new version of the Simple Link Connect app (not released yet) and report tomorrow morning. Could you also include a screenshot of how you are flashing the bim_onchip.hex, persisten_app.bin, and simple_peripheral_oad_onchip.bin using UNIFLASH? I would like to double check the addresses for the last two bin files.

Best Regards,

David.

Hi David, here is how we load our project through the Uniflash

Also attached the BIM, persist app and the app for you to try

ble5_simple_peripheral_oad_onchip_cc26x2r1lp_app_FlashROM_Release_oad.zip

Hello Terence,

May I ask if you can try flashing it under the following scheme:

Sorry it is taking one more day to test it with the new application.

BR,

David.

we need to use 0x28000-0x40000 for data logging hence we can't flash the persistence app in 0x38000

here is our memory mapping fyi

Hi,

Due to holidays, there may be delays in this thread. I apologize for any inconvenience this may cause. In the meantime,  can you check if the same behavior is observed when using the SimpleLink Starter application instead of SimpleLink Connect?

Best Regards,

Jan

Hi Jan

Similar when using SimpleLink starter app, device restart in OAD persistent app and doing nothing after that.

1) connect with SimpleLink starter app

2) Start the EOAD and restart device

3) Device restarted with the OAD Persistent App

4) It asked to restart the device again and just stuck there....

Hello Terence,

So we have tested this using your files and the new version of the Simple Link Connect app (not released yet) and it works with an additional step that we are still looking at.

Terence Kong said:

bim_onchip_CC26X2R1_LAUNCHXL_nortos_ticlang.zippersistent_app_CC26X2R1_LAUNCHXL_tirtos7_ticlang.zipsimple_peripheral_oad_onchip_CC26X2R1_LAUNCHXL_tirtos7_ticlang_oad.zip

Could you please try resetting the device and pressing the OK button at the same time when you get the "Device did not reset to OAD service" and see if the OAD process starts?

After OAD successful:

BR,

David.

hi David 

try again on simple link connect app and it is not working on my device still

ble5_simple_peripheral_oad_onchip_cc26x2r1lp_app_FlashROM_Release_oad.zip

1) Connect my device with the simple link connect

2) select the CC2652R1 and the local file.  My device is actually "CC2642R1F", not sure if this matter??

3) started the update and I observed my device restarted and the app pops up with the alert "OAD service not found

4) resetting the device and pressing the OK button at the same time but the download didn't start

I don't know what is wrong with the simple link connect or the starter app....I have to reiterate that the BTool works fine, hence the OAD persistence firmware should be working fine.

Here attached with the log from the BTool for your reference

OAD_BTool_log.zip 

oad.log

Hello Terence,

I apologize for the inconvenience and issues you are having. The test we did was with the next version of the Simple Link App which should be release very soon.

I will take a look on the OAD tools from BTool.

BR,

David.

Hi David, do you have any idea why BTool pass but fail on Simple Link?

Hello Terence,

The new version (1.3.5) of Simplelink Connect mobile app is now available on App Store and Google Play. I would kindly ask you to please try with this upgraded version.

BR,

David.

Hi David,

1) when I load the local image with version 1.3.5, it says unknown image type..

ble5_sp_oad_onchip.zip

2) When I select the "simple_peripheral_oda_onchip_CC26X2R1.....bin" from the pull down manual
I see my device restarted during update and the alert popped up with the OAD Service Not Found

Hi David, could you advice what's next to get this unblocked?

Hello Terence,

1. Regarding the local image. The application verifies the type of the image to see if it is identified as a bim (f2 sdk) or mcuboot (f3 sdk) image by checking the header. If the header does not match the expected pattern then an error is displayed. Could you please show me how the image was created?

2. After the reset, the device should advertise an OAD service (F000FFC0-0451-4000-B000-000000000000) with the Image Identify characteristic, the Alert and error notifications will come up if there is no such service. I understand the updating process didn't finish and gets interrupted, are you able to see more information in the serial terminal when this happens? For instance, in SimplePeripheral_processConnEvt(), if osal_snv_write() fails, then a Display_print1() prints a statement through UART. After the reset, does it boots into the persistent app?

The bin files you are working with still work fine if performing OAD through Btool correct? Have you checked that the application fits in memory considering the log data section?

BR,

David.

Hi David,

1) please find the local image created  6560.ble5_sp_oad_onchip.zip

it is created by the sdk example simple_peripheral_oad_onchip_cc26x2r1lp_app...."simplelink_cc13x2_26x2_sdk_2_40_00_81", 

oad_image_header.zip

2) I have added a debug LED in the persistent app and it blinks so it is confirmed that it does boot into the persistent app

3) Yes it is still working if we perform OAD through Btool, here attached with the OAD log FYI.  And the application is too big to fit into the log data section.

4011.oad.log

Hello Terence,

What modifications have you done to simple_peripheral_oad_onchip_cc26x2r1lp_app...."simplelink_cc13x2_26x2_sdk_2_40_00_81" in order to generate the .bin file? If possible could you please share with me the files (mcuboot, persistent and both applications) so I can test them on my end with the latest mobile app version, as well as the addresses you are using to flash them with uniflash please?

If you can provide details of the modifications you did to those projects (in order to generate the hex and bin files that you shared) I can try to reproduce that with the latest SDK projects as I am still unsure using the old SDK version is not bringing us issues (Btool version is the same as the SDK).

BR,

David.

Hi David,

I can share with you with more information, but I think we cannot share our project application files in the public forum.
Can you share your email contact? Do you have a secure upload site to share files?

Hello Terence,

If you could point to me the bear minimum changes you did to the OAD on chip example from the SDK in order for me to reproduce this issue and get help from the mobile app team, that would be very helpful. Also, you mentioned at some point you did a test with the latest SDK, can you walk me through how you did it? Because from what I remembered you used the out of the box example.

Do you have a TI sales representative?

BR,

David.

Hi David, I have contacted the TI FAE Alex W, he will share the files with you shortly

Hello Terence,

I have received the files and reproduced the issue. I am working with the CC26X2R1 device, so I think that rule outs the issue being caused by a different device being selected in the app interface.

I am assuming you are using the simple_peripheral_oda_onchip_CC26X2R1.....oad-v2.0.0.bin which pops out automatically and it is not a custom .bin file correct? Are you using the same ...v2.0.0.bin file when executing from BTool?

BR,

David.

Hi David.

on the phone app I tried both the image from the pull down menu "simple_peripheral_oda_onchip_CC26X2R1.....bin "and our custom image " ble5_simple_peripheral_oad_onchip_cc26x2r1lp_app_FlashROM_Release_oad.bin"

When executing from BTool, we tried with our custom image " ble5_simple_peripheral_oad_onchip_cc26x2r1lp_app_FlashROM_Release_oad.bin" and the OAD can complete successfully 

Hello Terence,

Okay thanks for the clarification. I am requesting help from the app team.

May I ask if trying with the latest SDK is a possibility here for the entire project?

BR,

David.

Hi David, thanks for the update.  Please understand we are about to release the firmware, and not possible to change to the latest SDK now.

Hello Terence,

I have discuss this with the team and there is a similar issue that has been resolved for the latest SDK. The simplelink_cc13x2_26x2_sdk_2_40_00_81 version does not contain several improvements/fixes and I am afraid a migration is required. This is also necessary if the idea is to certify the product for release. Apologies for the inconvenience here.

BR,

David.

Hi David, 

Can you confirm this OAD issue is not fixable on the simplelink_cc13x2_26x2_sdk_2_40_00_81 version or from the mobile app? We will have to delay or even cancel the project...

If it can work on the Btool, in theory the mobile app should work too, unless the OAD logic are different.  Have you compare what is the different between the Btool and the mobile app?

Hi Terence,

Thank you for reaching out.

David and I have discussed your case and I would like to share a few thoughts.

1) We highly recommend going to production with a newer SDK version. The SDK you are using is 5-year old and cannot be used to Bluetooth-certify new products. On the top of this, several critical bugfixes have been introduced since its release. Migration to the new SDK version may require some efforts now but should payoff on the long term.

2) The issues encountered are caused by versions incompatibility between the SDK and the mobile app.

In order to fix the issue, the following options are available - options are ordered to start with the most recommended ones:

• Option 1: Migrate to the newest SDK
• Option 2: Use an older version of the app - This would require to re-build the app on your own as the official app markets don't allow to deliver older versions. Here are some resources you may want to consider:
  • https://www.ti.com/tool/SENSORTAG-SW
  • https://git.ti.com/cgit/sensortag-20-android
  • https://git.ti.com/cgit/sensortag-ios-source-code-example

  • https://git.ti.com/cgit/simplelink-ble-oad-android/simplelink-ble-oad-android/
    https://git.ti.com/cgit/simplelink-ble-oad-ios/simplelink-ble-oad-ios/

  • https://github.com/rlimberger/OADKit/tree/swift3

• Option 3: Review the differences in the OAD handling in SDK 2_40 and SDK 7_40.
  • I expect changes in the BIM, in the OAD application and the tools
  • You can use the porting guides available here: https://software-dl.ti.com/simplelink/esd/simplelink_cc13xx_cc26xx_sdk/7.40.00.77/exports/docs/ble5stack/ble_user_guide/html/ble-stack-5.x-guide/migration-cc13xx_cc26xx.html#porting-guides

I hope this will help,

Best regards,

tried option 2 

rebuild the old android app from https://git.ti.com/cgit/simplelink-ble-oad-android/simplelink-ble-oad-android/

It doesn't work either, wondering what is missing here

From the BTool I can see the device did respond with the OAD service characteristics..