• State Resolved
  • Locked Locked
  • Replies 10 replies
  • Answers 4 answers
  • Subscribers 41 subscribers
  • Views 508 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-CC3235S: Quaries Reagarding Over the Air update

venkatesh vasanthapu
Intellectual 355 points
Part Number: LAUNCHXL-CC3235S
Other Parts Discussed in Thread: UNIFLASH

Hallo TI,

Currently I am working with CC3235S-LAUNCHXL and I am using it in station mode.  I am flashing the board using code composer studio or Uniflash. I would really like to update the software over the air. Is it possible to update the software via OTA, if I am using CC3235S-LAUNCHXL in station mode?

If yes how can I do ? 

If not what are the other possible ways to update CC3235S-LAUNCHXL over the air?

Best Regards,

Venkatesh Vasanthapu.

  • 0
    Guru 80405 points

    Hi,

    Yes OTA is supported. Please see cloud_ota and local_ota examples in CC32xx SDK.

    Jan

  • 0 in reply to Jan D
    Intellectual 355 points

    Thank you for the info.

    I was following the steps they mentioned in http://dev.ti.com/tirex/explore/node?node=ACE5ggZRybEJNZUcnzc3ww__fc2e6sr__LATEST but I am having some issues. As per the documentation if I press SW2 button then the output should be like the following

    But I  am always getting the following messages.

    Is there some configuration I am missing.

    Thank you.

    Best Regards,

    Venkatesh.

  • 0 in reply to venkatesh vasanthapu
    TI__Guru 63006 points

    Hi Venkatesh,

    Seems that you are having basic problem with the connection to the local network (i.e. to your access point) before the OTA can start.

    Have you been able to connect the same AP (and ping it or exchanging data) with other example? 

    Br,

    Kobi

  • 0 in reply to Kobi Leibovitch
    Intellectual 355 points

    Hello kobi,

    I did not try that. Can you please make a suggetion that which example I can Check? As I am bit new to this topics its bit hard to figure out.

    And I have one more basic Doubt. My github account looks like the following:

    https://github.com/OTA_3030/OTA_58 

    Below are my changes in the code otauser.h file

    #define OTA_VENDOR_DIR  "OTA_58"

    /* Github server info */
    #define OTA_SERVER_NAME "api.github.com"
    #define OTA_SERVER_IP_ADDRESS 0x00000000
    #define OTA_SERVER_SECURED 1

    /* Github vendor info */
    #define OTA_VENDOR_ROOT_DIR "/repos/OTA_3030/OTA_58  "
    #define OTA_VENDOR_TOKEN "OTA_3030"

    Is it the right way to do?

    Thank you.

    BR,

    Venkatesh

  • 0 in reply to venkatesh vasanthapu
    TI__Guru 63006 points

    Hi Venkatesh,

    The OTA configuration seems ok (of course, it should correspond to your github project).

    I've noticed that you have an extra space in the OTA_VENDOR_ROOT_DIR, you should remove it.

    But again, you current issue is not about the OTA, but about the basic wifi connection.

    You can use the NetworkTerminal example to try connecting to your access point.

    You can also check other simple example (such as the "httpget") to make sure you can access remote (internet) servers.

    Once you know how to enable the connectivity, you will be able to test the OTA.

    Br,

    Kobi 

  • 0 in reply to Kobi Leibovitch
    Intellectual 355 points

    Hallo Kobi,

    Thank you for the Info. Icould fix that issue. But currently I am getting an error while connecting to the socket. The following is the response I am getting. 

    I used the git hub configurations as mentioned above.What else could be the problem?

    Thank you.

    Best Regards

    venkatesh vasanthapu

  • 0 in reply to venkatesh vasanthapu
    TI__Guru 63006 points

    The -456 means one of the following:

    1. The root CA certificate is not found in the path you've provided in OTA_SERVER_ROOT_CA_CERT (make sure the full path of the file matches exactly to the content of your file system). 

    2. The root CA file in the file system has a bad format. Please make sure you are providing a valid DER formatted file (a DER file can be opened in Windows and you can inspect the content) or PEM file.The best way is to download the certificate from your computer (in Windows, open the certificate manager by pressing windows+R to open the "Run..." dialog, then typing in "certlm.msc" and go to "Trusted Root Certification Authorities/Cerificates" and look for the required root CA. When you open the file, go to "Details" where you can copy the file).

    br

    Kobi

  • 0 in reply to Kobi Leibovitch
    Intellectual 355 points

    Hallo Kobi,

    Thank you for the Info. It was a problem with the OTA_SERVER_ROOT_CA_CERT. I was able to do the OAT for the sample project mentioned in the http://dev.ti.com/tirex/explore/node?node=ACE5ggZRybEJNZUcnzc3ww__fc2e6sr__LATEST  using GIt.

    Here is a short descrption about what I am doing right now:

    I created a .tar file from the httpget application and placed it in my git folder. I would like to update my board with this file. I gave the

    OTA_VENDOR_DIR,  OTA_VENDOR_Token and OTA_Vendor_root_dir and tried to use OAT. I have the following problems

    OTA_run: call CdnClient_ConnectServer OTA server=api.github.com
    CdnClient_ConnectServer: HttpClient_Connect api.github.com
    HttpClient_Connect: IP_ADDR=140.82.118.6
    HttpClient_Connect: WARNING Socket Connect, status=-468, Ignored...
    OTA_run: CdnClient_ReqOtaDir, VendorDir=venkatesh_udp
    CdnGithub_SendReqDir: uri=/repos/venkatesh3030/venkatesh_udp/contents/
    HttpClient_RecvSkipHdr: http error code HTTP/1.1 404
    CdnGithub_ParseRespDir: ERROR HttpClient_RecvSkipHdr, status=-20310
    OTA_run: ERROR CdnClient_ReqOtaDir, Status=-20310

    _OtaCheckConsecutiveErrors: ConsecutiveOtaErrors=4/5, return only WARNNING
    OtaRunStep: WARNING Ota_run, Status=20004, continue fornext OTA retry

    OTA_run: call CdnClient_ConnectServer OTA server=api.github.com
    CdnClient_ConnectServer: HttpClient_Connect api.github.com
    HttpClient_Connect: IP_ADDR=140.82.118.6
    HttpClient_Connect: WARNING Socket Connect, status=-468, Ignored...
    OTA_run: CdnClient_ReqOtaDir, VendorDir=venkatesh_udp
    CdnGithub_SendReqDir: uri=/repos/venkatesh3030/venkatesh_udp/contents/
    HttpClient_RecvSkipHdr: http error code HTTP/1.1 404
    CdnGithub_ParseRespDir: ERROR HttpClient_RecvSkipHdr, status=-20310
    OTA_run: ERROR CdnClient_ReqOtaDir, Status=-20310

    I just added my github credentilas to the working example. But it seems not working. How can I update my own application?

    Thank you.

    Best Regards,

    Venkatesh Vasanthapu.

  • 0 in reply to venkatesh vasanthapu
    TI__Guru 63006 points

    You get the HTTP 404 error which mean that the URL was not found.

    Please make sure the OTA_VENDOR_ROOT_DIR definition matches exactly your github project structure. 

    br,

    Kobi

  • 0 in reply to Kobi Leibovitch
    Intellectual 355 points

    Hallo Kobi,

    That was the problem with the URL. It is working now.

    Thank you.

    Best Reagrds,

    venkatesh