CC3200: OTA error -6 for dropbox

Hello Sundar, 

I have assigned this to the relevant expert.

Best,

Rogelio

Hi Sundar,

We are familiar with this issue but still don't understand what was changed in Dropbox to cause this.

I'll update here when we find a fix.

Note that in general we don't recommend using Dropbox for production since they are constantly changing their servers interfaces which causes issues to IOT device. It is recommended to use a more IOT focused cloud vendor. 

Hi Kobi,

Since we have installed the IOT devices in different locations, we cannot change the Dropbox.

Any update on this issue?

Regards,

Sundar

no update yet.

you can try to contact Dropbox directly with this issue. 

Hi Kobi,

I have created the ticket in the Drobox forum and they said no changes from their side.

www.dropboxforum.com/.../757521

Regards,

Sundar

Hi Kobi,

We have 100k devices installed in the client location. We need to update the firmware over OTA. If you are able to point out the exact issue with the Dropbox API, we can reach out to the Dropbox team and ask them to fix it.

Regards,

Sundar

I understand your situation but the problem is with the connection to Dropbox  (when started to check this we couldn't find any problem with the API - actually it passed in some cases). We are facing the same issue with CC3220//35 and the debugging is in progress. We will update once we find anything.

When communicating to Dropbox you should only present the HTTP Request (can be printed in sl_Send) and Response (in sl_Recv)  -  they are not familiar with our HTTP Client messages and error codes.

You can print the message in (or before) calling sl_Send or you can change the target to a Dump HTTP server (google for it, e.g. see https://httpdump.app/) and  check the log there.    

Hi Kobi,

I was not able to print the logs. Any update on your side?

Regards,

Sundar

not yet

Hi Kobi,

We have 90k devices installed all over the US. It is very difficult to ship the devices with the new firmware.

Please let us know if there is any update on this issue?

Regards,

Sundar

no update yet from our end.

Have you tried contacting Dropbox?

It looks like following the first request+response (list folder) the Dropbox server sends a TLS alert from some reason (downgrading the connection to unsecure).

I don't understand the reason (maybe the Dropbox contact can explain this).

If you delay the 2nd request (get-temporary-link) by few seconds (e.g "sleep(5)") the TLS connection will be reestablished and OTA will work.

Hi Kobi,

Thank you so much. I will pass this to drobox.

I'll get back to you when I have their reply.

Regards,

Sundar

Hi Kobi,

They want to reproduce the issue from their end. They are asking for network logs. Do you have anything to share with them?

https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/OTA-update-fails-in-CC3200/m-p/757746#M33136

Regards,

Sundar

This is what I have (the data is encrypted under the TLS):

The Alert is in frame 55151 

Hi Kobi,

Thank you so much for sharing the screenshot.

Now they are asking for the dump file to inspect the request/response. Could you please export the PCAP file and share with me?

Regards,

Sundar

cc32xx-dropbox-2.pcapng

Hi Kobi,

Thank you for the logs. Below is the Dropbox team answer.

I had the team look at this, but unfortunately, this dump appears to only contain the WiFi frames. Can you instead share a dump with the actual data (TCP + TLS frames) so we can inspect that particular alert, like shown in the earlier screenshot?

Regards,

Sundar

no. we can't. I was using an air sniffer log where the TLS content is encrypted. 

On the application side you can only publish the socket payload (i.e. if you print the data passed to sl_Send - it will include the HTTP content) but not the entire TCP/IP packets (i.e. it will be text file with http text and not a pcap file). I think one of our customers already provided this to them.

I'm quite sure they can capture the connection log on their server.