• State TI Thinks Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 2 answers
  • Subscribers 55 subscribers
  • Views 729 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.

CCS/CC1352P: OAD/OTA for Simple Central

harikrishna paritala
Intellectual 520 points

Part Number: CC1352P
Other Parts Discussed in Thread: CC2540

Tool/software: Code Composer Studio

Hi,This is harikrishna

Currently i am working on CC1352P  Simple Central application,So central is communicating with two more peripherals so and they are exchanging the information properly, Now we want to do OTA/OAD for Central application ,so my question, is it possible to do OAD for central application?


In examples we have found that off-chip and on-chip OAD process for simple peripheral not for central, and moreover in examples projects they are using Btool(Central) for this process. so in my case i can't use btool..

Is Simple Central Application can perform OTA/OAD process itself without connecting to any other wireless things??? if it is possible please suggest us way to do it...

Thanks 

  • 0
    TI__Expert 5345 points

    Hello Harikrishna,

    I will assign an expert to help you. Could you please indicate what SDK version you are using?

    Thanks,

    Luis

  • 0
    TI__Guru* 83751 points

    Hi Harikrishna,

    Yes it's possible to use a BLE central as the OAD target. The key here is to separate the BLE central/peripheral relationship from the GATT client/server relationship.

    I would recommend you to start at the SimpleLink Academy OAD lab. In this lab, we give instructions on how to add OAD to the multi role example. You should be able to adapt the instructions to simple central.

     

    Regarding the OAD distributer side, you can use BTool but you will have to run it as a BLE peripheral. 

  • 0 in reply to Luis M
    Intellectual 520 points

    HI LUis

    we are using simplelink_cc13x2_26x2_sdk_3_10_01_11(3.10.1.11)

    Thaks,

    Harikrishna

  • 0 in reply to Marie H
    Intellectual 520 points

    HI Marie H,

    As you suggested I tried to run the sample OAD application in the example using BTOOL but I'm getting OAD Download Not Successful Message every time.

    i followed as like mentioned in the document, Here is the link

    file:///C:/ti/simplelink_cc13x2_sdk_2_20_00_71/docs/ble5stack/ble_user_guide/html/oad/oad_offchip.html

    Used Two Launchpads of CC1352R1(C revision IC's Old one),

    One is loaded with Host_Test Hex file from C:\ti\simplelink_cc13x2_sdk_2_20_00_71\examples\rtos\CC1352R1_LAUNCHXL\ble5stack\hexfiles\cc13x2r1/ble5_host_test_cc13x2r1lp_app_FlashROM_Release

    Second Board is Loaded with the below process

    Step 1: flashed cc13x2r1lp_bim_offchip.

    Step 2: flashed ble5_simple_peripheral_oad_offchip_cc13x2r1lp_stack_library

    Step 3: flashed ble5_simple_peripheral_oad_offchip_cc13x2r1lp_app.

    Then I Connected my CC2540 Dongle.

    Btool - BLE PC Application V1.41.18

    CCS Version :9.1

    SDK Used :simplelink_cc13x2_sdk_2_20_00_71

    BTOOL is connected successfully with peripheral application Device, then I started OAD Process by read the image as like below screen shot.

    As I observed that all OAD profiles are not happening properly.

    I have changed  some of parameters in BTOOL but it wont work for me, and I unable to find out that where exactly problem lies 

    Please check that image and suggest me to any changes are need for BTOOL configuration for OAD. 

    Thanks

    Harikrishna Paritala

    7-10-2020 14:13:17.847 [RX] - <ESC>c<ESC>[2J<ESC>[10r<ESC>[11;1H<ESC>7<ESC>[10r<ESC>[10;0H<ESC>[2K<ESC>E<ESC>8<ESC>7<ESC>[10r<ESC>[1;1H<ESC>[2K*Simple Peripheral<ESC>8<ESC>7<ESC>[10r<ESC>[2;0H<ESC>[2K<ESC>E<ESC>8<ESC>7<ESC>[10r<ESC>[3;2H<ESC>[2K+Work with ><ESC>8<ESC>7<ESC>[10r<ESC>[4;0H<ESC>[2K<ESC>E<ESC>[2K<ESC>E<ESC>[2K<ESC>E<ESC>8<ESC>7<ESC>[10r<ESC>[7;1H<ESC>[2K====================<ESC>8<ESC>7<ESC>[10r<ESC>[1;1H<ESC>[2KSBP Off-chip OAD v0001<ESC>8<ESC>7<ESC>[10r<ESC>[8;1H<ESC>[2KInitialized<ESC>8<ESC>7<ESC>[10r<ESC>[13;1H<ESC>[2KDev Addr: 0x0081F94F7821<ESC>8<ESC>7<ESC>[10r<ESC>[11;1H<ESC>[2KAdv Set 0 Enabled<ESC>8<ESC>7<ESC>[10r<ESC>[11;1H<ESC>[2KAdv Set 1 Enabled<ESC>807-10-2020 14:14:04.749 [RX] - <ESC>7<ESC>[10r<ESC>[11;1H<ESC>[2KAdv Set 0 Disabled<ESC>8<ESC>7<ESC>[10r<ESC>[11;1H<ESC>[2KAdv Set 0 disabled after conn 0<ESC>8<ESC>7<ESC>[10r<ESC>[9;1H<ESC>[2KNum Conns: 1<ESC>8<ESC>7<ESC>[10r<ESC>[8;1H<ESC>[2KConnected to 0xD0FF506DFF33<ESC>8<ESC>7<ESC>[10r<ESC>[10;0H<ESC>[2K<ESC>E<ESC>8<ESC>7<ESC>[10r<ESC>[1;1H<ESC>[2K*Simple Peripheral<ESC>8<ESC>7<ESC>[10r<ESC>[2;0H<ESC>[2K<ESC>E<ESC>8<ESC>7<ESC>[10r<ESC>[3;2H<ESC>[2K+Work with ><ESC>8<ESC>7<ESC>[10r<ESC>[4;0H<ESC>[2K<ESC>E<ESC>[2K<ESC>E<ESC>[2K<ESC>E<ESC>8<ESC>7<ESC>[10r<ESC>[11;1H<ESC>[2KAdv Set 0 Enabled<ESC>807-10-2020 14:14:11.759 [RX] - <ESC>7<ESC>[10r<ESC>[9;1H<ESC>[2KLink Param Updated: 0xD0FF506DFF33<ESC>8

  • 0 in reply to harikrishna paritala
    TI__Guru* 83751 points

    Hi Harikrisna,

    I'm sorry I can't help you if you are using the Rev C device. Please update to the newest revision (Rev E). 

  • 0 in reply to Marie H
    Intellectual 520 points

    Hi Marie H,

    I tried same process already with 3.1 SDK (simplelink_cc13x2_26x2_sdk_3_10_01_11(3.10.1.11)), I observed Same results like as above, that's why roll back to older version to check my luck. But here I'm confused Because  I did same this as mention in the document.

    I Never touched any part of the code in examples, Should I need to modify anything? I able to see the BTOOL and off-chip OAD peripheral code are connected properly first time then OAD Process is stopped at same position.

    Please check this BTOOL Log and give me some help.

    Thanks

    Harikrishna Paritala

  • 0 in reply to harikrishna paritala
    TI__Guru* 83751 points

    Hi Harikrishna,

    Please confirm you are using CC13x2 or CC26x2 devices with chip revision E for both the OAD target and OAD distributor.