• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 51 subscribers
  • Views 311 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

LAUNCHXL-CC26X2R1: oad function of simple link start app doesn't run.

BubbleTomato
Intellectual 260 points

Part Number: LAUNCHXL-CC26X2R1

Hi.

I am doing simple peripheral oad on-chip example project.

but it fail as the following. (There is no response even if the start oad button is pressed.)

  • 0
    TI__Mastermind 25810 points

    Hello,

    Can you provide us with the version of Simple Starter you have, as well as your Android version? Additionally, what SDK is the SP on chip OAD project from?

    Do you experience this issue with a different project, like Project Zero? Have you tried performing an OAD using a second Launchpad flashed with host_test (running BTOOL as the OAD distributor)?

  • 0 in reply to Ammar N
    Intellectual 260 points

    hi,

    1. the version of Simple Starter which I have is v5.7.5(Build 86).

    2. sdk is simplelink_cc13x2_26x2_sdk_4_40_00_44.

    3. I have no issue with a different project. and Project Zero example run well. but Project Zero is oad-off-chip.

    4. currently, i have three Launchpad board and that same as the issue.

  • +1 in reply to BubbleTomato
    TI__Mastermind 25810 points

    Hey Bubble,

    I tested this out. You'll have to hit Reset Target first to reset the onchip device, allowing it to boot into the persistent image. Then, back out of this screen and reconnect to the device. At this point, you should see a section called "TI OAD Service". Here, you will be able to select a FW image and proceed with the OTA update.

    You are only able to perform an OAD to the second image by first booting into the persistent image.

  • 0 in reply to Ammar N
    Intellectual 260 points

    Hi Ammer N

    I tried as your way.

    step 1. I hit Reset Target Button of Simple Start App.

    step 2. I pushed back button of Simple Start App and disconnected.

    step 3. I scanned ble device lists in Simple Start App.

    step 4. I founded my ble device and touched my ble device but it did not connected.

    I tried step 1~4 several times. but I did fail.

    can you upload your test hex and bin???

    and then I am going to test your files.

    thank you. 

  • +1 in reply to BubbleTomato
    TI__Mastermind 25810 points

    Hey Bubble,

    I used the prebuilt hex files located in C:\ti\simplelink_cc13x2_26x2_sdk_4_40_04_04_s\examples\rtos\CC26X2R1_LAUNCHXL\ble5stack\hexfiles 

    I used bim_onchip (unsecure), the persistent app hex. For the simple_peripheral example, I imported this project from the SDK and built it without any modifications.

    Let me know if this works for you.

  • 0 in reply to Ammar N
    Intellectual 260 points

    Hi Ammer N

    I succeed SW Update via on-chip oad.

    I did not know this combine that is bim.hex + persistant.hex + app.bin.

    but I saw and know your comment.

    Thank you.