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-CC2640R2: Second BTool OAD results to "OAD Download Not Successful" error?

Part Number: LAUNCHXL-CC2640R2

Hi,

   The first time I followed the On-Chip OAD Guide and was able to successfully do OAD using BTool. I modified the advertisement name and build. Then I try to do OAD again using BTool and results into "OAD Download Not Successful" error. Is that normal or not?

- kel

  • Hi,

    Do, I need to set a Slave Bluetooth Device Address at simple_peripheral.c in, so I can do another On-Chip OAD using BTool?

    - kel
  • Hi Markel,

    Could you give us more information on the failure? A sniffer log would reveal the reason, or we may be able to find it in the BTool log.

    It doesn't sound normal, the image might be getting rejected. (due to version issue?)

    Regards,
    Rebel
  • Hi A.Rebel.

    I followed the On-Chip OAD User's Guide as is and used the example program from CC2640R2 SDK. The Btool I used is from CC2640R2 SDK. I believe you can duplicate this at TI side. I will try to take a sniffer capture.

    C:\ti\simplelink_cc2640r2_sdk_1_00_00_22\tools\blestack\btool

    After first time successful On-Chip OAD, I notice that the 0A:D0:AD:0A:D0:AD address can not be found at BTool. I guess that is because Image B is already running.

    - kel
  • Hi Markel,

    When you finish on-chip OAD, system will reset and run Image-B. You can update Image-A or jump to Image-A update Image-B again.
  • YUHUA Hu said:
    You can update Image-A or jump to Image-A update Image-B again.

    When Image B is running, how do I update Image A using BTool. Should I set a Slave BD Address at Simple Peripheral. 

    From my understanding reading the documents, after BIM, Stack and Image is already programmed to CC2640R2, you are supposedly able to do On-Chip OAD Image B again and again.

    - kel

  • Hi Markel,

    As I know, address is not the point. If you want to update Image-A from Image-B, you need modify bim(you can check metadata(version)) to decide which image to run). If Image-B is running, you cannot update Image-B. You need go back Image-A(modify bim, maybe check GPIO) and update Image-B again
  • Hi YUHUA Hu,

    Thanks for your advice. I will study how to modify bim in order for me to update Image B.

    I will also review the sensortag codes, because the SensorTag App seems to be able to do firmware download or OAD, repeatedly, meaning replacing a running Image B with another Image B.

    - kel
  • Hi Markel,

    I am working on the same problem. I updated the image A and image B was running. Also, i would like to update image B for the next time.
    If you modify the BIM successfully, can you share how you do it ?

    Thanks