Because of the Thanksgiving holiday in the U.S., TI E2E™ design support forum responses may be delayed from November 25 through December 2. Thank you for your patience.

  • State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 51 subscribers
  • Views 293 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Original question:

LAUNCHXL-CC26X2R1: SimpleLink Connect app error while trying to update firmware/application using OAD

LAUNCHXL-CC26X2R1: OAD fails with Simplelink connect APP

Javier Soriano
Prodigy 90 points
Part Number: LAUNCHXL-CC26X2R1
Other Parts Discussed in Thread: UNIFLASH

Dear sirs,

We are trying to load new firmware (OAD) using Simplelink connect APP (latest version 1.3.4) from Android phones and it always fails with "Bad TLV Magic" message. 

We have uploaded the 3 images using Uniflash and when we repeat  the update firmware process with BTOOL it always uploads the firmware successfully.

We have already read other locked threads asking for solutions but we did not find any clear reason.

Any update on this issue?.

Many thanks

  • 0
    TI__Genius 12395 points

    Hello Javier,

    Thanks for reaching out.

    Are you using the out of the box example from the SDK?

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

    As a sanity check, 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.

  • 0 in reply to David
    Prodigy 90 points

    Thanks David for your reply. Find my answers below.

    We are using out of the box simple peripheral onchip OAD example.

    Yes, we are following the mentioned training laboratory for SDK 6.20. It is the same as the one of your link for 7.4. In fact, it works successfully when we follow the lab steps using BTOOL as indicated in the tutorial. The problem, as I said, come up when using Simplelink connect APP (android version). Then, the TLV Magic error is reported.

    Looking forward to you suggestions to find out the problem

    Regards

  • 0 in reply to Javier Soriano
    TI__Genius 12395 points

    Hello Javier,

    Thanks for the additional information. I am reviewing this with the respective team to see what could be happening.

    I have ran the test on my side with the out of the box example (using the same Simple Link connect APP - version 1.3.4) and it the OAD is successful. So in the meantime could you please help me clarifying the following?

    1. Are you using a custom simple_peripheral_oad_onchip.bim file as well as the one you upload or the one from the out of the box example?
    2. When you are about to start the OAD, are you selecting the correct device and firmware?
    3. Does the OAD loading % progress before TLV Magic error or does it go directly into it?

    BR,

    David.

  • 0 in reply to David
    Prodigy 90 points

    Hello David, 

    Please find our answers:

    1. Are you using a custom simple_peripheral_oad_onchip.bim file as well as the one you upload or the one from the out of the box example?


    We are using a custom simple_pheripheral_oad_onchip.bin as the first firmware image that is loaded using Uniflash. This file  is based on the simple_peripheral_oad_onchip official project.The persistent image is the one already included in the SDK.


    Afterwards, we modify the code (just the led frequency) to prepare a new bin file for the oad dowloading process. This file and process works fine when we download it with BTOOL. However it fails when we use the simple connect APP (version 1.3.4) to download it.

    2. When you are about to start the OAD, are you selecting the correct device and firmware?

    a. When we download our custom file we can not choose the device. We can just select our file. Our board has a CC2642R1 IC.
    First of all, we need to send the 0x01 to reset the device. Apparently the APP process does not send this value. We have seen in the simple peripheral code that it expects to receive it in order to reset and start the persistent image. In fact, when we send the 0x01, the persistent image starts working. Once it starts we select our custom simple_peripheral_oad_onchip.bin file and send it to the device.It fails with the Bad Magic TLV error. See attached images.

    b. When we repeat it with your own software, we select the CC2652R1 device and the onchip firmware. We also need to send the 0x01 value to reset it and start the persistent. The firmware update does not give the same TLV error but it does not progress remaining at 0%

    3. Does the OAD loading % progress before TLV Magic error or does it go directly into it?

    When we perform the process "a" as explained before, it jumps directly to the error BAD TLV Magic. We didn't find any information about this error

    Looking forward to your response

    Thanks

  • 0 in reply to Javier Soriano
    TI__Genius 12395 points

    Hello Javier,

    Thanks for the information. The issue you are describing looks very familiar to the one 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). In the mean time you can try the process that Markel Robregado has kindly shared in that thread using the SimpleLink Starter App.

    BR,

    David.