We’re Still Here to Help (Even Over the Holidays!) - find out more here.
Forum Discussion
OTA update fails in CC3200
Hi All,
We are using the Dropbox API to do an OTA upgrade. We have a webclient application running on the TI microcontroller CC3200. We are using the Drop Box API from 2017 onwards, and it is working fine. When we tested the OTA functionality yesterday, it was unable to receive the CDN file URL.
It is able to receive the file information from Dropbox but is unable to get the temporary link from Dropbox.
Do you know what is causing this issue? Is there any recent API upgrade that has failed to respond?
Please help us to fix this issue ASAP.
TI CC3200 logs:
sl_extLib_OtaRun: call OtaClient_ConnectServer OTA server=api.dropbox.com
OtaClient_ConnectServer: http_connect_server api.dropbox.com
0 OTA run = 0
sl_extLib_OtaRun: OtaClient_UpdateCheck, vendorStr=Vid01_Pid00_Ver0302100000
OtaClient_UpdateCheck: call http_build_request /1/metadata/auto/
CdnDropbox_SendReqDir: uri=/2/files/list_folder
metadata file=/Vid01_Pid00_Ver0302100000/f80_sys_mcuimgA.bin, size=142888
sl_extLib_OtaRun: OtaClient_UpdateCheck, numUpdates=1
0 OTA run = 0
sl_extLib_OtaRun: OtaClient_GetNextUpdate: file=/Vid01_Pid00_Ver0302100000/f80_sys_mcuimgA.bin, size=142888
OtaClient_ResourceMetadata: call http_build_request /1/media/auto
OtaClient_ResourceMetadata: file flags=80,metadata flags=80
CdnDropbox_SendReqFileUrl: uri=/2/files/get_temporary_link
0 OTA run = 0
sl_extLib_OtaRun: ResourceMetadata CDN file URL = f=
CdnClient_ConnectByUrl: ERROR, http_extract_domain_by_url, status=-1
sl_extLib_OtaRun ERROR: Failed on CdnClient_ConnectByUrl
0 OTA run = -6
OTA run = -6
OTA: Error with OTA server
Regards,
Sundar
68 Replies
Replies have been turned off for this discussion
- Greg-DB
Dropbox Community Moderator
Thanks for the context!
Hi Greg,
I really appriciate your help in finding the RCA for the issue. We don't have any control over the client's device (100K IOT device). The Dropbox API service is the only way to connect to the device. As I mentioned before, this is the highest priority issue in our organization. Since OTA functionality worked before and not working now, few of our customers continuousely started asking for the update. It is affecting the entire business. So please escalate as much as possible and deploy the changes.
Regards,
Sundar
- Greg-DB
sundares80 I will follow up here with any news on this, but again just to be clear, at this point I cannot say if the team will or won't be deploying any changes for this.
Hi Greg,
Thank you for the update. Please let us know once you deploy the changes
Regards,
Sundar
- Greg-DB
sundares80 Thanks for confirming that. I've raised this to the team to ask that they change the server to accept requests with the extra new line. Again though, please note that I can't promise if/when such a change would be deployed. I'll follow up here with any updates on that.
Also, as Здравко noted, please be aware that the client behavior of sending this extra new line is a bug. If the team deploys a change on the server to accommodate malformed requests with the extra new line like this, such a change should not be considered permanent, and so clients should be updated to not send the extra new line.
I'd also like to thank Здравко again for going above and beyond to debug this!
Haha... They don't understand still that it's a bug... and they care about how to keep this bug. 🤷
Hi Greg,
TI confirms that removing the new line resolves the issue.
Once you make those changes in production, our devices will do an OTA update without any code modification on the client side. Please correct me if I am wrong.
Regards,
Sundar
Hi Greg,
Thank you for the clarification.
I have posted your message in the TI forum
I have asked to remove the extra line and test the issue.
Regards,
Sundar
- Greg-DB
sundares80 To clarify, we have not made any changes on the Dropbox servers to address this. Здравко helpfully identified a potential cause of the problem, which is that your devices may be sending an unexpected new line at the end of the request body payload. In order to validate if that is the cause of the issue, and if addressing that would resolve the issue for you, I asked you to change one of your devices to make it not send that new line and see if it then works. If so, that would validate that as the cause of the issue so that I could then request that the team address that server-side.
Sundaresan Thangeswaran1:Hi Kobi,
Dropbox says they fixed "new line" issue. Could you please check if that issue resolves our OTA issue without code changes on the device. https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/OTA-update-fails-in-CC3200/m-p/771280#M33736
Regards,
Sundar
Kobi Leibovitch TI__Guru:I'll be able to check next week. Is it regarding a "new line" within the HTTP headers or at the end of the payload?
Have you checked that you can now complete the update?
Sundaresan Thangeswaran1:Hi Kobi,
I don't know where he wants to add a line.
They have not updated the changes in production yet. Anyway, I tested today, and it is not working.
Below is their answer.
"Would you be able to modify a device you have access to in order to have it not send the additional new line as a test? If you can verify that fixes the issue, I can ask the team to look into changing the server to allow that (though please note I can't make any promises on that)"
Please let us know if this fix our issue.
Regards,
Sundar
Kobi Leibovitch TI__Guru:so need to better understand where they expect the extra new line.
again, i'll be able to check this only next week (but you can try yourself as the SDK contains all the sources and maefiles.
OMG 🤣😂, What kind of comedy!!! 😁 Some comedy actors may left without engagement. Here it's not a play, it's something native.
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
