TI E2E Community
Low Power RF & Wireless Connectivity
Urgent! CC3000 based Web Server: Debug version ok but Release version will not connect to Wireless AP
== Urgent! ==Modified version of CC3000 FRAM Web Server Example has been ported to a 66 MHz, 32bit processor (Microblaze on Xilinx Spartan6 FPGA).This is now fully functional on "Debug version", running on the FPGA
1) When executing "Release version" of the same code, the CC3000 no longer connects to the Wireless Access Point.(This occurs even when the Release version is compiled with same GCC compiler Optimization and Debugger settings!)
2) Operation of the functional "Debug version" is also not that robust. ie. When subjected to successive mouse-clicks, occasional delays and errors are apparent in the browser user interface.
Question: I think the above 2 issues are possibly related and that the hard-coded delays within the code may be the problem area...ie. in serverMain() [in httpserver.c] and main() [in webserver.c] Please advise what these delays need to be? (in time units not MSP430 clock cycles) ...and/or where else to look for resolution of this issue?
PS: The porting of CC3000 host driver software was done following the attached guidelines (received from- and discussed in detail with Gustavo Litovsky)
Thanks for your attention on this :-)Peter Fenn
2703.Notes from TI on porting CC3000 host driver software.pdf
It was the gcc compiler optimization setting that caused the “Release version” to fail. I’d set it to “Optimize for size” and this caused web server to fail and not connect to router.
The 2nd issue remains:Please advise what delay-loops are needed and how long these should be for reliable webserver operation?
There is a new version of this sample application coming out soon. I think it removes the delay-loops. I am checking with the team and come back to you.
Can I please request early access to the mentioned new material? This is urgent, context is the the CC3000-based board being demo'd at Avnet's worldwide XFEST events right now
I confirmed and there is a new feature in the host driver that indicates when all thje packets have been transmitted and therefore you dont have to wait in a loop. The release is coming out in around a week. Would that work?
Thanks for confirming that. Sooner than a week's time would be much better! :-)This board is being demo'd right now at XFEST events in Europe this week.
The new release is that only a new version of the cc3000 host lib ?
or is it also a new firmware in the CC3000 ? if, yes is it possible to firmware update my Murata EM Board ?
It will be a change in the host driver and the CC3000 EEPROM. A tool and instructions to update it will be provided.
Any update as to when this new version of the WebServer application will be available?
I'm also waiting on Code Composer compatible source and project for the WebServer application.
Please advise as to when this will be available.
We are wrapping up the packages currently. I expect they will come out sometime early next week. Thank you for your patience.
Has the Code Composer version of the CC3000 FRAM WebServer app been posted yet? I don't see a new version yet on the downloads page.
Can you please provide a date when the CCS version of the CC3000 FRAM WebServer app will be available?
Has that updated Webserver code been posted yet?
We apologize for the delay. We are having some internal delays. Right now, estimated time line is late next week.
It's been over two weeks since your last post. Has the Code Composer version of the CC3000 FRAM WebServer app been posted yet? I don't see a new version yet on the downloads page.
Can you please provide a definite date when the CCS version of the CC3000 FRAM WebServer app will be available so that we can determine if we need to go with a different platform that has currently available support?
We are pending finalization of the patch programmer license, the patch will improve the first time configuration, but is not required to run the attached package, which includes the new version of the web server. It has a new host driver, and one of the added features is to send the TX complete after all packets have been acknowledged. This feature is utilized in the web server and will wait for tx completion after sending all the html pages, before closing the socket.
Let us know if the package worked, we will post it in the wiki page shortly but will be nice to know if you have found any serious bugs.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.