Wi-Fi Combo Forum Discussions
Hi there,
I'm looking for a Wi-Fi/BLE module with FCC certification.
Does anyone know if there are any FCC certified BCM43341 modules available?
I could easily find some modules with BCM43362, but not with BCM43341 so far.
Is BCM43341 too new or something else is recommended?
Show Less"I’ve heard that WI-FI can’t meet the requirements of V1.8.1. Is it true, and what is it about WI-FI that causes this?
If you’ve read through the IEEE 802.11 standard, you will see that it includes mechanisms for medium access control or spectrum sharing. Chip manufacturers haven’t implemented that function in the firmware. In order to meet the conformance requirements of V1.8.1, non-adaptive equipment with RF power output of 10mW e.i.r.p. or greater must conform to the medium utilization requirements. But based on the high duty cycle of 802.11, the medium utilization requirement can’t be met. So without adaptivity, 802.11 devices must limit power to less than 10mW e.i.r.p, and for most manufacturers, that’s unacceptable."
Can anyone from Broadcom comment on whether or not BCM43362 (wiced 2.4) and BCM43341 (wiced 3.1.2) will pass the new EN 300 328 standard? We are currently in testing and are having problems figuring out if we can even pass the test or if it's futile.
I rather think that wiced_dct_write_wifi_config_section should write the WIFI section, not the DCT section... As a GIT-style diff this is the fix:
diff --git a/WICED/internal/waf.c b/WICED/internal/waf.c
index 72e37bc..12b07b8 100644
--- a/WICED/internal/waf.c
+++ b/WICED/internal/waf.c
@@ -163,7 +163,7 @@ wiced_result_t wiced_dct_read_wifi_config_section( platform_dct_wifi_config_t* w
wiced_result_t wiced_dct_write_wifi_config_section( const platform_dct_wifi_config_t* wifi_config_dct )
{
- return wiced_dct_write( wifi_config_dct, DCT_SECURITY_SECTION, 0, sizeof( *wifi_config_dct ) );
+ return wiced_dct_write( wifi_config_dct, DCT_WIFI_CONFIG_SECTION, 0, sizeof( *wifi_config_dct ) );
}
I found it in 3.1.2, so it's probably been there for ages.
Show LessSo I have installed the SDK onto my macbook and have downloaded XCode. However, I'm finding it difficult to figure out where to go from here. The Quick Start Guide is exclusive to Windows. And whenever I try and load a new project to Xcode, it doesn't work. Can anyone walk me through the process or point me in the right direction? It would be greatly appreciated!
Show LessWe have a device that needs to be configured in the field to establish what SSID and passphrase it should connect to by default. The default AP that a client connects to in the SDK (3.2.2) is hard coded, and there does not seem to be a mechanism to set the default SSD as the connection logic uses the hard coded values or looks in the stored_app_list information in the wifi config dct to select the AP to autoconnect with.
So to do what we need to do, the plan is to do a wifi scan and look for the SSID of interest so we can collect the access point details.
We could then save this information and when the device resets, do a manual wiced_wifi_join call to establish our connection.
It would seem structurally better to populate the stored_app_list in the dct with the information we get from the scan, and let the default behavior of bringing up the services do its job, so that in future releases of the SDK if there are additional requirements to establish the connection, we don't have to re-code our app to deal with it if the change is not completely encapsulated in the wiced_wifi_join call.
But I don't like hacking on SDK internal data structures that are also subject to change that would percolate upstream and cause us rework.
Is there a better way to implement this feature that gives us better isolation from SDK changes?
Show LessUsing V 3.2.2 SDK on BDM943341WCD1
I have an app that brings up a soft ap for configuration. I use the wiced_wifi_scan_networks to get a list of SSIDs in the neighborhood so I can validate the SSID that I collect from the user over a UDP socket that a client app uses send the configuration info the the soft AP server.
My scanning code that uses the wiced_wifi_scan_networks api works fine if I run it before I bring the the soft ap (similar in concept to what the snip.scan demo code does.
But if I bring up the soft AP so I can collect configuration parameters, the wiced_wifi_scan_networks function returns WICED_SUCCESS when I call it, but does not actually scan, so my callback function never gets executed.
I tried starting a worker thread to run the wiced_wifi_scan_networks in, but that behaves the same.
I also shut down the soft AP prior to running the scan, but that has no effect.
Looking at the underlying library code, I don't see anything obvious that would cause it to fail if a soft ap were running, or had been running and shut down.
There must be some shutdown logic that is needed to make this work, but I don't see anything in the documentation that suggests a fix.
Anyone have a clue what is preventing the scanner from working?
Show LessHi,
I'm trying to interface SN8000x with my stm32f429 custom board using SPI, since my board uses SPI6 I had to make some changes in the code, while digging through it I could find a statement in wwd_spi.c
/* Clear the CS pin and the DMA status flag */ | |
GPIO_SetBits( SPI_BUS_CS_BANK, ( 1 << SPI_BUS_CS_PIN ) ); /* CS high (to deselect) */ | |
DMA_ClearFlag( DMA1_Stream3, DMA_FLAG_TCIF4 ); | |
DMA_ClearFlag( DMA1_Stream4, DMA_FLAG_TCIF3 ); |
I think DMA_ClearFlag( DMA2_Stream6, xxxxxxxxxxxx); has to clear DMA_FLAG_TCIF3 instead of TCIF3, similarly in second one has to clear TFIF4 , I think both got swapped while writing drivers..
Am I right, or it has to be like this???
Show LessHi,
I'm designing a custom PCB based on the SN8200.
The design is heavily based on the "Discover Wifi" board schematics. Further, I'm not using the optional 32.768 KHz slow clock input. Relevant pins are grounded or left unconnected in respect to the datasheet.
I am able to flash the firmware using the STM32-STLINK utility through the SWD interface. Flashing the board works perfectly, I can download and verify the code without any problems. The code seems to be running as I can halt the core and check the values of the registers. For instance, I can confirm the PC is changing.
Nevertheless, even when flashed with the proper firmware, the SN8200 doesn't seem to emit any WiFi signal. For instance, by configuring a firmware using the SN8200 SNIC Monitor, making the AP enable on this firmware, and downloading this firmware, the hotspot is not created. The very same firmware on my "Discover WiFi" board is working.
What kind of issue can explain this behavior? Bad wiring? Damaged SN8200? Poor power supply? (even if I've checked the 3.6V WiFi power supply and it doesn't seem to be the source of my troubles).
Thanks !
skerr yfang@murata.com hhyogo keith ghouse
Show Less