I'd swear I already asked this, but I can't find anything in the forum.
What are the differences between the WGM160P and the WGM110? I can't find any summary anywhere. Going through the data sheets and reference manuals line by line is excruciating, and with the holes in the WGM110's documentation I don't trust that all of the important differences are covered.
The WGM160P seems to be considerably less expensive, despite a faster processor with more memory. Does the new design sacrifice anything the WGM110 has? Is the 160 likely to see ongoing improvement in firmware and documentation? That's been a major problem with the WGM110.
Does the WGM160P have castellations like the AMW004? One image from the marketing materials shows it that way, but I suspect that may be artistic license on the part of some graphic designer - it's not shown in the datasheet, and the few actual photos I can find don't seem to show that. It's something I've been hoping for in any follow on to the 110, since it'd make soldering and inspection simpler for low-volume production. Is there any cross-pollination between the BlueGiga lineage parts and the Zentri ones, or are they going to stay separate product lines?
We really don't have much more than the comparison table on this page: https://www.silabs.com/products/wireless/wi-fi
Scroll down to "Pre-Certified Wi-Fi Modules".
To add to Tiago's comment, unlike the WGM110 module, the WGM160P Wi-Fi module is based on two Silicon Labs ICs:
Regarding the WGM160P software support, the module runs Gecko OS which is an upgrade over the Zentri OS solution (more information in the link https://docs.silabs.com/gecko-os/4/standard/latest/). In addition, we will introduce "open" examples on the WGM160P based on the WF200 Wi-Fi driver through Simplicity Studio in the coming months. Silicon Labs Wi-Fi module solutions have been merged, going forward there will be one single product line.
Last point on the castellations topic, I confirm the WGM160P does not have any. I hope this post answers some of your questions.
Thanks for the information. I always feel like I must be coming at this from the wrong direction when basic information is so hard to find. I've been subscribed to every marketing and technical document subscription I can find at SiLabs, and yet the first indication I had that a new WiFi product was available was that I started seeing references to it in the support forum.
I started out on Motorola MCUs and from my understanding they were often customer-specified parts - a large customer would give their requirements, Motorola would make the part, and then the part would be added to the catalog where us little guys would be able to order them as well. Is that the model that SiLabs follows for parts like this? Are they developed primarily for specific customers, with their wider availability being a secondary concern? If not, where is the 'front door'? Through what route are customers expected to find out about available parts and their capabilities?
The parameter table is more or less useless. Under "Apps Processor" we're comparing "BGScript" and "Yes". My first question is whether the WGM160P supports serving HTTPS. The datasheet, under "Servers", lists "HTTP(S)". That's a good start, but on the WGM110 "HTTPS" means "HTTP Server" and it does not in fact support HTTPS.
There's no reference manual under 'documentation'. There's nothing at all under 'software'. The only way I can find to get docs at all is to go to "Learn More" under the starter kit, then "Get Started", then way down at the bottom, "Quick Start Guide". That in fact seems to be the complete API reference, not a quick start guide, and I can't fathom why it's buried so far down in a development kit's docs and not attached to the part itself. I've spent two hours so far being interviewed by SiLabs' UX design contractor and giving my feedback on those issues, and those people seem to know what they're doing, but it's frustrating as heck to see that in the year or more since the first interview nothing seems to have changed.
Is it safe to assume that the WGM110 is now a dead end? It's been the bane of my existence for the last 3 years and it's looking more and more like its deficiencies will not be fixed. There's no BGAPI support on the WGM160P so I'd have to rewrite a huge amount of code, and it'd take weeks just to determine if there are any 'gotchas' where it wouldn't support something the WGM110 did. And for me that's all kind of irrelevant since we've got hundreds of customers to support that already have devices with the WGM110 and we can't just give up and move on. I'm having to give refunds to customers who have devices that won't stay connected to an AP because they just periodically die with "hardware failure" - something that happens even on the WSTK development kit with the demo apps sometimes. On certain APs, DHCP fails about 30% of the time. That's been a known issue for years.
I was excited when the WGM110 came out. I was hoping to contribute some code to expand on the meager BGAPI demos, and help work the bugs out since I'm apparently asking more of the modules than most developers. Instead it's been a fight to get answers and I've had to open dozens of trouble tickets. I would love to see that change with the WGM160P but so far the disorganization and lack of information doesn't have me convinced that it's going to be any different.
How can I keep up on WGM160P developments? There's nothing in the official blog, nothing in announcements. I can't even find a press release except by Googling the part number. That you have plans for "open" examples for the WGM160P is encouraging, but so far it still feels like something developed in private for big customers. As much as I hate Espressif, at least the ESP32 has a community of small independent developers - even if it's a bit overrun with hobbyists. What would I subscribe to or follow to see new examples and documents posted for the WGM160P?
I recommend using docs.silabs.com to follow the WGM160P/WFx200 available resources. All the software solutions provided around the Silicon Labs Wi-Fi solution are referenced on the Wi-Fi main page:
You can already find information about Gecko OS, the MCU full MAC driver and the Linux low MAC driver. Gecko OS is an OS solution delivered in binary format and running on a Gecko MCU. It enables an external host to discuss with the WGM160P through a UART/SPI command line interface or to run the application on-board the module using a C API. If you are looking at using the WFx200 Wi-Fi transceiver as a Wi-Fi Network Co-Processor, you will want to use the MCU/RTOS driver. In this architecture, your host MCU is running the IP stack.
I wanna add wifi module to efm32gg11 (host mcu). i wanna develope my webpage update data dynamically through wifi module.
Can you suggest me to pick wgm110 or wgm160.