sundares80 Helpful | Level 6

Hi Greg, Any update? Regards, Sundar

Hi Greg, Any update? Regards, Sundar

Hi Greg, I have tested just now, but i see the same error. I did not get the temporary download link. Regards, Sundar

Thanks for the update, Greg. Once you deploy, the same day we will test and let you know about the result. Regards, Sundar

Hi Здравко, First of all, there are no bugs or problems in our firmware. For several years, we have been using Dropbox API for pushing OTA updates to our devices installed at our client sites. Recently we learned that your product (Existing Dropbox API) no longer supports the same functionality that we have been using for…

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…

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…

Hi Greg, Thank you for the update. Please let us know once you deploy the changes Regards, Sundar

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-error--6-for-dropbox/5203134#5203134 Once you make those changes in production, our devices will do an OTA update without any code modification on the client…

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

@"Здравко"Thank you for your analysis. Yes, we agree. We have to redesign our HTTP client library. but I cannot access the physical IOT device since it is installed in multiple locations in the US and Europe. The only way I can update the client code is by doing an OTA update. @"10"/Здравко As per the packet capture, our…

Hi @"Здравко", We are in a critical situation. We have installed 100K IOT devices throughout the US. We cannot access the device now. The only thing we can do is perform an OTA update, which is currently not working due to your changes. Please remove this TLS alert message for 6–8 months. During that period, we will do an…

Hi Greg, As per TI, this extra TLS alert stopping the client code execution. Could you please remove this. Regards, Sundar

@"Здравко" Thank you so much for recreating the issue. @"10" Please find my new packet capture in the google drive link. Please let me know if it works https://drive.google.com/file/d/1v4dUI2lMIRJ-1Qg-u2Phl10IhSpVuCJr/view?usp=sharing Regards, Sundar

Hi Greg, Below is the answer provided by TI 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…

Hi Greg, Please download the wireshark pcap file from below link. https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/968/cc32xx_2D00_dropbox_2D00_2.pcapng Regards, Sundar

Hi Greg, Thank you both of them for checking this. Here is the packet capture I got from TI. This is what I have (the data is encrypted under the TLS): https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1337191/cc3200-ota-error--6-for-dropbox/5162901#5162901 If the screenshot not clear, Please…

Hi Greg, Thank you so much for the reply. TI is saying it is a TLS handshake issue. request/response structure looks good. But there is a performance related issue. Please refer to the link in the in the attached thread.…

Hi Greg, Thank you for reply. We have many WIFI module chipsets like CC3200, CC3220, CC3235. All of them failed to receive the data from Dropbox. Texas instruments claims that the chipset could not able to send and receive data using their low level HTTP Client library. Did you modified anything related API (TCP/IP layer…

Thank you for confirmation