I'm working on another project which needs a WiFi connection. I've allready got a WiFi chip module from ZeroG Wireless, called ''ZeroG Wireless G2100''. Are there anybody who knows how to control this module with the STM32F103? OBS: I have programmed alot in Basic and C for other uC's (PIC & AVR), but I'm new to the Ride7 enviroment! Best Regards Thomas Jespersen
Are there anybody who knows how to control this module with the STM32F103?
The module neither knows nor cares what is being used to control it! You just need to do whatever the Datasheet tells you! Standard procedure for interfacing anything to anything else - irrespective of the specific devices involved - is:
Are there anybody who knows how to control this module with the STM32F103?
The module neither knows nor cares what is being used to control it! You just need to do whatever the Datasheet tells you! Standard procedure for interfacing anything to anything else - irrespective of the specific devices involved - is:
Yes, but you should take into account that maybe one does not have a spare month to reinvent the wheel and write a SPI low level driver then a TCP/IP stack over it from scratch. Better rather focusing on the application. Said that, I suppose that the question from tkjmail was: ''Is there any library or driver or application note for Zero-G modules on STM32 family?'' Ciao!
You come across as smart/caring STM user - you're certainly trying to assist. Must come to the defense of mon ami ST7 - he is pointing out that poster is a tad ''too quick'' on the trigger - allowing his need/desire to exceed his
The point is that the only parts that will be specific to the STM32 are the parts that deal directly with the STM32's specific features - such as the SPI. And, for those parts, the fact that it's talking to a ZG2100 is irrelevant.
So you can just look at any STM32 SPI examples for that. Similarly, the operation of ZG2100 is independent of what controller is being used - so you can look at generic examples for that. It is really important to understand this, as this is common to pretty much all projects! Understanding this allows you to correctly focus your activities - instead of looking for one unique STM32-specific solution, you can use any generic implementation, and concentrate just on the STM32 specifics. Of course, if you're not really interested in how to do it, but just want an ''out-of-the-box'' solution - then that's a different question!