• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 41 subscribers
  • Views 987 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.

CC3220: OTA customer CDN. How to do it?

Shamil Farsiev
Expert 1515 points
Part Number: CC3220
Other Parts Discussed in Thread: UNIFLASH

ok. step by step, like profy(you) with child (me, joke :-) )

1) i have a gentoo machine with our cervice drivers, apache web-server, sql db. right now it's my own developer sandbox. is it enough make customer CDN server, or not?
2) in what place i should put *.tar file with new firmware at CDN server?
3) i am trying to compile cloud_ota_CC3220SF_LAUNCHXL_nortos_ccs and nowhere in your docs i found about
otauser.h line 110:
/* add your customer server header here */
#include ""

this include. where can i take it *.h file?

3) Over The Air Update Guide / 3.2 Program by UniFlash Tool With Image Creator Inside / fig.8

how can i generate digcert_high_assurance_ca.der if i don't use github or dropbox?

4) otauser.h line 119
#define OTA_VENDOR_TOKEN 

where can i take/generate it?
ok. i may be i have it and define in otauser.h, where have put it at my CDN server?

5) right now i have working my own app for cc3220 without OTA.
i want OTA update (surprise!) - i need just include OTA lib to my code and thats all? and if my code+ota will work i mustn't to touch ota part of program?

6) i made a new pcb. flash blanked chip by my program. it works. i write a new version of my program and update it by OTA by same bin file? or i have to have two bin files for first flashing and OTA? and how many project in UniFlash i have to have? (sorry for my bad English)

general - how to integrate ota in own-ready-code?

7) i have two/thee/more... projects with cc3220sf sdk and one project i update with github, second with custom cdn, third with github but another token... is otauser.h is only one for all projects? or i can copy it to my project?

  • 0
    TI__Mastermind 28285 points
    Shamil,

    Have you used our Cloud OTA example in the past? my first step for you would be to understand how our OTA process works. You can read the following document:
    www.ti.com/.../swra510.pdf

    Also, Try going through our SLA example to familiarize yourself even more with flashing our device, and configuring the OTA library.
    dev.ti.com/.../

    Regards,
    Vince Rodriguez
  • 0 in reply to Vincent Rodriguez
    Expert 1515 points

    I talked to the project architect (my boss) and came to the conclusion that the current built-in OTA update implementation does not suit us.
    Why:
    1) you transfer the firmware is in a TAR archive while we transfer the binary file;
    2) we have our own protocol for encrypting and transmitting data and files;
    3) in the end, you have very poorly described what you need to do to raise your serv;
    I successfully updated through the githab and dropbox, but this is not exactly what we need.

    is it possible to custom the OTA update procedure?

    if no - where can i read about memory mapping? 

    and! none of you said: what needs to be done and what should be started for the computer to act as a CDN server. you made a wonderful chip and wrote a good SDK, but do you always poke into the documentation if there's nothing on the subject of the question?

  • 0 in reply to Shamil Farsiev
    TI__Guru 63006 points

    Hi Shamil,

    Our SDK examples are  provided as reference code.The library was built to enable generic OTA procedure (using all the CC3220 security features).

    It offers one way of building and parsing the OTA image and 2 options of the servers (github and dropbox).

    The OTA Application Guide (<SDK-ROOT>/docs/simplelink_mcu_sdk/Over_The_Air_Update_Guide.html) provides instructions for supporting a different CDN vendor.

    You can use the library sources to replace the TAR handling (in OtaArchive.c) with your specific implementation. 

    Basically we cannot support custom solutions. If you must implement one, you'll need to implement it as part of your application (all the required API are documented and their usage is demonstrated through our examples).

    Br,

    Kobi 

  • 0 in reply to Kobi Leibovitch
    Expert 1515 points
    and yes, and no.
    we wouldn't use your OTA ref. code or examples. This is not my decision.

    we have another way of self update.