I want to run WGM160P_commissioning_micriumos example on my WGM160P module using simplicity studio v5. Unfortunately, I was not able to implement it. Code implementation struck in some infinite loop.
Whereas when I import similar example from the wfx_fmac_driver into Simplicity studio v4, example is running flawlessly.
I did not get why Version 5 is unable to utilize the examples listed in the IDE.
Can someone suggest how to resolve issues and make use of the example code on Simplicity Studio V5!
This thread has been moved from the Simplicity Studio forum to the Wi-Fi forum which is more relevant to your topic.
We don't have WGM160P_commissioning_micriumos example under Ssv5 yet, but you can get inspired with the same example running on EFM32GG11 Giant Gecko Starter Kit (SLSTK3701A) to make it run on WGM160.
In the Ssv5 launcher search the product name EFM32GG11 Giant Gecko Starter Kit (SLSTK3701A) and click start
Select the [EXAMPLE PROJECTS] tab in [Launcher] perspective.
Search for the example [Platform - Wi-Fi Commissioning Micrium OS Kernel] from the Software Examples list.
Click on the [Create] button of the example.
Click on [Finish].
I have flashed this Wi-Fi Commissioning Micrium OS example code to WGM160P module as it contains EFM32GG11 with few modifications. I have reconfigured the example to work with SDIO. I have utilized the initialization routine used in WGM160P_commissioning_micriumos example of Ssv4. Selected the pins which required for WUP, WIRQ, LP_CLK, RESET as per the version 4 example. I have successfully compiled the code.
During debugging, I have noticed that wifi_start() function is successfully passing through the following APIs sl_wfx_init_bus(), sl_wfx_init_chip(), sl_wfx_download_run_bootloader(), sl_wfx_host_setup_waited_event(), sl_wfx_download_run_firmware(), sl_wfx_enable_irq() but as soon as the API sl_wfx_set_access_mode_message() is called nothing is being returned, without which WiFi initializing sequence is left incomplete. Application is becoming idle while the OS is running in the background.
Can I get a quick solution in using WGM160P with Simplicity Studio v5.
I'm in a similar boat to Kiran with trying to bring up the WGM160P with SSv5. I'm familiar with Micrium and the Gecko SDK from doing EFM32 and EFR32 development in IAR Embedded Workbench, but I completely new to using Simplicity Studio. So I am not only getting up to speed on a new hardware platform, I'm getting up to speed on the toolset as well. I'd prefer to stick with SSv5 instead of learning both SSv4 and SSv5, and may go back to the BG22 workshops as a way to learn the tools better.
When I tried to switch to WFx Bus SDIO, I needed to install a BRD8022A component to satisfy a dependency. But I was able to go back to the Overview to remove that and switch back to the BRD4321A (WGM160P).
And now it's asking for a `sl_wfx_pds.h`. If I include an empty header file, I get an "WFX Board component (BRD8022A or BRD8023A) not installed" error.
Is there an estimated date for when the WGM160P will be supported in SSv5? What files would end-users need to create as a stopgap until that time comes?
And why isn't the I/O line configuration between the EFM32 and WF200 better documented? I expected to see details in the schematic or UG384. In other forum posts here I see customers directed to header files for the pinouts. If the WGM160P was fully supported in SSv5, would I be able to skip over the WFx component configuration steps? I was surprised when I had to specify the I/O lines for the two LEDs and buttons, but maybe that's also due to missing configuration files in SSv5 for the WGM160P hardware.