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.

CCS: LAUNCHXL-CC1350-4 Over Air Download

Other Parts Discussed in Thread: CC1350

Tool/software: Code Composer Studio

I have been working on BLE OAD with CC1350 Launchpad.
I tried some ways but they did not succeed.
one of them, I want to do OAD with my phone with Sensor Tag.
" dev.ti.com/.../project0_index.html
". I tried it but it did not work.
I could create a .bin file with "oad_image_tool.py"
I could connect to board with " Ti Sensor Tag" on my phone after i
load hex file to Launchpad
"rfWsnDmNode_CC1350_LAUNCHXL_tirtos_ccs.hex" .
if I use a .bin file in " Ti Sensor Tag", it is working but if I
create my bin file and use it, it is not working because of "Ti
Sensor Tag" shutdown after ı choose my .bin file.

there are two other ways:

I can OAD with 2 launchpads and 1 PC.
one of the launchpads is OAD server it connected to Pc with a USB cable.
The other launchpad is OAD Client it connected to OAD server with BLE.
I send new firmware to OAD server. OAD server send to it to Client.
or
I can OAD with 1 launchpad and 1 PC.
I send new firmware to Oad Client connected to PC with Bluetooth.

I have used SimpleLink Academy and TI E2E but I was not found the knowledge enough.
Thanks in advance.

  • Hi Murat,

    Which SDK version are you using?

    I cannot other than refer to documentation, as you do not provide enough detailed information to understand why it is failing.

  • Hi J Lindh,
    thank you for the response.
    my SDK version is "simplelink_cc13x0_sdk_3_20_00_23".
    I have been following "dev.ti.com/.../rfWsnNodeExtFlashOadClient_README.html".

    I have tried "rfWsnConcentratorOadServer_CC1350_LAUNCHXL_tirtos_ccs" and
    rfWsnNodeExtFlashOadClient_CC1350_LAUNCHXL_tirtos_ccs.

    I did them all item.
    I sent a bin file to the server with "oad_write"
    After, The server sent it to the chosen node of the client.
    Server and client sent "OAD Complete" on Serial port but Firmware did not work on the client after reset board.

  • HI,

    Are you attempting to use BLE or EasyLink as the transport for OAD?

  • Hi Sean,

    I want to do over-air download with BLE or EastLink.
    I have tried some way but it is not success.
    I use 2 CC1350 boards.
    one of them is OAD Server other board is OAD Client.
    I have tried "rfWsnConcentratorOadServer_CC1350_LAUNCHXL_tirtos_ccs" and
    rfWsnNodeExtFlashOadClient_CC1350_LAUNCHXL_tirtos_ccs.

    I sent a bin file to the server with "oad_write"
    After, The server sent it to the chosen node of the client.
    Server and client sent "OAD Complete" on Serial port but Firmware did not work on the client after reset board.
    thank you

  • Hello,

    >> I want to do over-air download with BLE or EastLink.

    Please decide which protocol you wish to perform OAD on so that we can point you to the right documentation

  • Hello Sien,
    I want to do OAD with Easy Link.
    ı can use 1 server board (CC1350 LaunchPad) or I can use my computer's Bluetooth.

    I tried some ways:
    for example

    I have worked on "CC1350-433 Mhz Launchpad" with BLE stack but I was not a success.
    I use some source code in CCS Studio 9 for example "bim_extflash_cc1350lp", "simple_peripheral_cc1350lp_app_FlashOnly_OAD_ExtFlash", "simple_peripheral_cc1350lp_stack_FlashROM". 
    I make .bin file by "oad_image_tool.py" after compile.
    I load "simple_peripheral_cc1350lp_OAD_bim-app-stack.hex" file to CC1350 Launchpad-433 Mhz. 
    I open it with Sensor Tag after I send .bin file to my mail. 
    Send new firmware after we choose TI OAD Service. Application has closed itself.

    or,

    I use 2 CC1350 boards.
    one of them is OAD Server other board is OAD Client. 
    I have tried "rfWsnConcentratorOadServer_CC1350_LAUNCHXL_tirtos_ccs" and 
    rfWsnNodeExtFlashOadClient_CC1350_LAUNCHXL_tirtos_ccs.

    I sent a bin file to the server with "oad_write"
    After, The server sent it to the chosen node of the client. 
    Server and client sent "OAD Complete" on Serial port but Firmware did not work on the client after reset board.

    Thank you for the response;