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: Question about OTA updates example

Part Number: LAUNCHXL-CC3235S

Hello, 

I am currently working on testing the CC3235 EVMs to replace the MSP432 in an IoT system, and I was curious about the operation of the OTA updates example.

I see there are 3 different ways to OTA update: Cloud (reaching out to Github/Dropbox), Local (uploading the file yourself), and through the file system (locally on the board). However, I have a system where I want the MCU to reach out to another computer on its local network for the OTA update. I thought that the best way to do this would be to set up a local Git server and have the MCU reach out to it, however, the program requires a Github token, which I can't set up on a local Git server.

I was wondering if I could get some input on what my best option would be:

1.) Modify the method the example uses to update from the file system. I assume this would include just reaching out through an HTTP GET for the .tar file on the local network.

2.) Find some way to not have to use the Github token to reach out to my local Git server. Not sure if this is possible, but if it is, that would be great.

Thanks in advance for any help/input,

Greg