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.

CC3220SF-LAUNCHXL: CC3220SF

Part Number: CC3220SF-LAUNCHXL
Other Parts Discussed in Thread: CC3220SF, UNIFLASH

I'm Trying to use cloud_ota_CC3220SF_freertos_css demo, the update is not working for me and what I receive after running the program on the PC terminal is the following:

 

 

 

********************************************************************************

                OTA APP Application - Version 0.10.00.03       

********************************************************************************

 

 

SimpleLinkInitCallback: started in role 0

Host Driver Version: 2.0.1.22

Build Version 3.5.0.0.31.2.0.0.0.2.2.0.5

 

STA connected to AP --------, BSSID is xx:xx:xx:xxxx:xx

IPv4 acquired: IP = 192.168.0.100

Gateway = 192.168.0.1

 

Pinging GW...!

 

Ping done. Success rate: 100%

 

HandlePingComplete: PingCounter=1

Pinging GW...!

 

Ping done. Success rate: 100%

 

HandlePingComplete: PingCounter=2

Pinging GW...!

 

Ping done. Success rate: 100%

 

HandlePingComplete: PingCounter=3

Pinging GW...!

 

Ping done. Success rate: 100%

 

HandlePingComplete: PingCounter=4

Pinging GW...!

 

Ping done. Success rate: 100%

 

HandlePingComplete: OTA Command arrived

 

OtaInit: statistics = 0, 0, 0

OtaInit: call Ota_init

OtaConfig: call OTA_set EXTLIB_OTA_SET_OPT_SERVER_INFO, ServerName=api.github.com

OtaConfig: call OTA_set EXTLIB_OTA_SET_OPT_VENDOR_ID, VendorDir=OTA_CC3220SF

 

OtaRunStep: WARNING Ota_run, Status=20006, continue for next OTA retry

 

 

OtaRunStep: WARNING Ota_run, Status=20006, continue for next OTA retry

 

 

OtaRunStep: WARNING Ota_run, Status=20006, continue for next OTA retry

 

 

OtaRunStep: WARNING Ota_run, Status=20006, continue for next OTA retry

 

 

OtaRunStep: ignore it just for loop testing

 

 

ProcessRestartMcu: reset the platform...

 

 

 can you please tell me what I'm doing wrong. ???

What do you mean by OTA_VENDOR_TOKEN ?? what should I put on that define ???

 

  • Hi,

    Please read documentation for OTA update ( www.ti.com/.../swra510 ).

    Jan
  • Hi Jan,
    I appreciate your help.
    I did read the OTA documentation, and in the previous mail I attached what I receive ??
    One thing that I didn't understand from the documentation is where I can find the OTA_VENDOR_TOKEN from GitHub?? I don't know if it's my problem!!
  • Dear Adham - 

    pls. see also ==>  

    and

     

  • Hello Josh,

    I authorized the app and insert all the data needed as below:

    But still Receiving "OtaRunStep: WARNING Ota_run, Status=20006, continue for next OTA retry" on the terminal and OTA is not completed!

  • Hi Adham,

    The parameters you show here (from ota user.h) relates to a Dropbox configuration.

    On the top of the file you should define the server you are connecting to. Please choose the github definition (which is your target if I understand correctly) and fill the github specific configuration.

    Br,

    Kobi

  • Hi Kobi,
    Thank you for you assistance.
    Sorry the first log was for GitHub (we decided later to work with dropbox)

    The definition for the GitHub server is set in the code :
    #define OTA_SERVER_TYPE OTA_SERVER_DROPBOX_V2

    and the correct log is:


    ********************************************************************************
    OTA APP Application - Version 0.10.00.03
    ********************************************************************************


    SimpleLinkInitCallback: started in role 0
    Host Driver Version: 2.0.1.22
    Build Version 3.5.0.0.31.2.0.0.0.2.2.0.5

    STA connected to AP xxxxxxx, BSSID is xxxxxxxxx

    IPv4 acquired: IP = 192.168.1.100
    Gateway = 192.168.1.1

    Pinging GW...!

    Ping done. Success rate: 100%

    HandlePingComplete: PingCounter=1
    Pinging GW...!

    Ping done. Success rate: 100%

    HandlePingComplete: PingCounter=2
    Pinging GW...!

    Ping done. Success rate: 100%

    HandlePingComplete: PingCounter=3
    Pinging GW...!

    Ping done. Success rate: 100%

    HandlePingComplete: PingCounter=4
    Pinging GW...!

    Ping done. Success rate: 100%

    HandlePingComplete: OTA Command arrived

    OtaInit: statistics = 0, 0, 0
    OtaInit: call Ota_init
    OtaConfig: call OTA_set EXTLIB_OTA_SET_OPT_SERVER_INFO, ServerName=api.dropboxapi.com
    OtaConfig: call OTA_set EXTLIB_OTA_SET_OPT_VENDOR_ID, VendorDir=OTA_R2_MCU

    OtaRunStep: WARNING Ota_run, Status=20006, continue for next OTA retry


    OtaRunStep: WARNING Ota_run, Status=20006, continue for next OTA retry


    OtaRunStep: WARNING Ota_run, Status=20006, continue for next OTA retry


    OtaRunStep: WARNING Ota_run, Status=20006, continue for next OTA retry


    OtaRunStep: ignore it just for loop testing


    ProcessRestartMcu: reset the platform...
  • Guys,

    I'm trying to make the ota_cloud from SDK v1_50_00_06 work, but always I receive error 20006 no matter what I do..

    OtaRunStep: WARNING Ota_run, Status=20006, continue for next OTA retry

    I'm working with the dropbox and I defined all the parameters in the demo code according to the guide of TI !

    Please help....

  • Hi Adham,

    Please enable the OTA library trace (SL_ENABLE_OTA_DEBUG_TRACES in otauser.h). You'll need to recompile the library and application.

    This will add required debug information.

    br,

    Kobi

  • Hi Kobi,

    This defined is enabled. and the previous log was from that code.

  • The log doesn't show the OTA library trace.

    Probably, you are not linking the application with the library.

    Make sure the new compiled library (ota.a) is included in the  "Project Properties -> Build -> Arm Linker -> File Search Path".

    Check if the library is built within the SDK or in your workspace folder.

    Br,

    Kobi

  • Hi Kobi,

    You are right that was one problem. and now I'm receiving the full log from the development kit. another issue was that the "DigCert_High_Assurance_CA" file name was different from the file in the uniflash.

    Thank you for your help ans assistance.

    Best Regards,

    Adham