cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Are you interested in hearing how one of our Community members uses Dropbox for sailing trips? Read all about it here.

Dropbox API Support & Feedback

Find help with the Dropbox API from other developers.

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Re: OTA update fails in CC3200

OTA update fails in CC3200

sundares80
Explorer | Level 3

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

61 Replies 61

Greg-DB
Dropbox Staff

@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.

sundares80
Explorer | Level 3

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

 

sundares80
Explorer | Level 3

Hi Greg,

 

TI confirms that removing the new line resolves the issue. 

 

https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1337191/cc3200-ota-e...

 

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

 

 

 

Здравко
Legendary | Level 20

Haha... They don't understand still that it's a bug... and they care about how to keep this bug. 🤷

Greg-DB
Dropbox Staff

@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!

sundares80
Explorer | Level 3

Hi Greg,

 

Thank you for the update. Please let us know once you deploy the changes  

 

Regards,

Sundar

Greg-DB
Dropbox Staff

@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.

sundares80
Explorer | Level 3

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
Dropbox Staff

Thanks for the context!

sundares80
Explorer | Level 3

Hi Greg,

 

We have over 100k of our devices installed globally used by 1000’s of hospitals, pharmacies, food processing and other businesses. The ability for us to update the firmware with OTA functionality using Dropbox is critical for us and clients. As discussed, the function is not working now due to your recent update on the Dropbox API server. We have been waiting for Dropbox to fix the API issue for almost a month, but there is no update from Dropbox. This issue has been escalated to our executives and SensoScientific CTO is questioning when it will be fixed. Can you escalate and schedule a call with your executive/management to further discuss this issue and timing of the resolution. We are trying to address this before it becomes a legal issue and proceeding.

 

Regards,

Sundar

Need more support?