Wi-Fi Combo Forum Discussions
Does Cypress provide the frequency range (MHZ) &output Watts or FCC test firmware for the PSoC® 6 WiFi-BT Pioneer Kit (CY8CKIT-062-WiFi-BT)?
Because I already read the guideline, but cannot find related information, if possible, please let me know if there's any related documents, thank you!
Show LessHi - Is there any information on how the network information is stored in DCT for 4343 chips? Is the network password stored in plain text or with some encryption? If not supported via WICED, is there a suggested way to make the network information?
Show LessDear All:
Our product has a WIFI/BT combo module,which use BCM43353 as main processor,and we need test RF characteristics of the product.
When test BT RX characteristics,we need check if received packet number is same as transmit packet number of SG .So we need achive this packet counter,and reset this counter to next step.
Our supplyer provide 3 file for test: "test, TL.INI, bcm43353bt.hcd".but they told us can't get this counter.
We want know:How to achive packet counter when test BT RX characteristics and how to reset this counter. Any HCI Command can support our requirement?
Thanks!
li min
Show Lessi have a wireless device that needs to be paired to its dock to work. is there a way to force the CYRF6936 into binding mode when a bind button isn't present on the board?
Show LessHi,
I am trying to get a Murata Type1LV module working with the STM32F412G Discovery board with WICED using the snip.scan application.
I have an Embedded Artists 1LV M.2 Module (with the Murata Type1LV module on it) plugged into an Embedded Artists uSD-M.2 Adapter that is plugged into the SD card slot of the Discovery board. I also have WL_REG_ON and WL_HOST_WAKE connected to a GPIO pin on the STM32F412.
Bluetooth works fine, but WiFi does not complete initialisation and reports "Could not set Country code" after the call to wwd_sdpcm_send_iovar() times out in wwd_management_wifi_on().
It seems that everything works fine up to that point and I can step through the initialisation and see that the SDIO bus is working and SDIO interrupts are happening.
I have tried it with and without WICED_DISABLE_MCU_POWERSAVE and have also tried configuring WWD_PIN_SDIO_OOB_IRQ to connect an STM32F4 GPIO to WL_HOST_WAKE.when WICED_DISABLE_MCU_POWERSAVE is not defined. None of these made any difference.
Initially I could not get it to enumerate the SDIO bus, but after I changed wwd_bus_init() to reset the module properly by turning off and on WL_REG_ON that now works.
I have noticed that there is some code in ww_sdio() that treats the SDIO Interrupt differently for the STM32F412xG, but there are no comments to explain why. There are other posts in this forum that mention this, but they don't come to any conclusions.
With that code in it does get SDIO interrupts up until before the wwd_sdpcm_send_iovar() to set the country code. After wwd_sdpcm_send_iovar() times out the SDIOIT bit in the SDIO STA register is set.
I have tried removing the STM32F412G specific code, but then it gets repeated SDIO interrupts.
The makefile has WLAN_CHIP_REVISION := C0 I I cannot find any information about what revision chip is in the Murata modules.
Can anyone suggest what I could try to get this working?
regards,
Charles
Show LessI have a quick question: Does anyone know if enabling SFLASH encryption disables the serial port input?
When I add SECURE_SFLASH=1 into the make command, then it appears that the serial port outputs data, but no longer accepts input from the console.
Show LessI'm running SDK 3.7.0 with the BCM94343WWCD1 platform and when I enable mcu powersaving through wiced_platform_mcu_enable_powersave the system will not keep track of the current time correctly. Also, wiced_rtos_delay_milliseconds does not work correctly either. I've attached a small sample application that connects to an AP, sets the time through sntp and just loops printing the current time every 10 seconds.
Some output of the application. The timestamp on the left is from the computer, and the other time is what the wiced platform is reporting it is.
09:36:58 Obtaining IPv4 address via DHCP
09:36:58 DHCP CLIENT hostname WICED IP
09:37:06 IPv4 network ready IP: 192.168.0.140
09:37:06 Setting IPv6 link-local address
09:37:09 IPv6 network ready IP: FE80:0000:0000:0000:000A:F7FF:FEF4:D780
09:38:22 Getting NTP time... Sending global request ... success
09:38:22 Current time is: 2016-07-26T13:38:22.048248
09:38:22 Time is: 2016-07-26T13:38:22.052248Z
09:38:33 Time is: 2016-07-26T13:38:32.055248Z
09:38:43 Time is: 2016-07-26T13:38:42.060248Z
09:38:50 Time is: 2016-07-26T13:39:26.036464Z <- 7 seconds passed, time skipped 44 seconds forward
09:39:00 Time is: 2016-07-26T13:39:36.039464Z
09:39:10 Time is: 2016-07-26T13:39:46.043464Z
09:39:20 Time is: 2016-07-26T13:39:56.047464Z
09:39:30 Time is: 2016-07-26T13:40:06.049464Z
09:39:41 Time is: 2016-07-26T13:40:16.051464Z
09:39:51 Time is: 2016-07-26T13:40:26.049464Z
09:40:01 Time is: 2016-07-26T13:40:36.050464Z
09:40:04 Time is: 2016-07-26T13:41:16.056928Z <-- 3 seconds passed, time skipped 40 seconds
09:40:14 Time is: 2016-07-26T13:41:26.058928Z
09:40:19 Time is: 2016-07-26T13:42:07.001392Z <-- 5 seconds passed, time skipped 41 seconds
09:40:29 Time is: 2016-07-26T13:42:17.006392Z
09:40:35 Time is: 2016-07-26T13:43:00.048464Z
Thanks,
-Rob
Show LessI am working around a condition when an AP to which the WICED device is connected stops unexpectedly. This can happen when AP loses internet access or somehow goes down. This usually results in a disconnect callback and my app tries to reconnect using the http_client_connect() API. At this point if I make this connect call I get an error 7014(socket close) and then 9(host down).
Repeated calls in such a situation seems to be causing memory usage growth in v6.4 as compared to v6.1.
There is a link down callback to handle a host down situation, but memory growth is concerning as this also happens on a socket close error(AP is not down, but loses internet access).
I have attached a basic test app to recreate this. It can run on both v6.4 and v6.1. I simulate by creating a hotspot to which the WICED device connects. If I close the hotspot after the test app initiates and and keep calling the connect API, memory keeps growing in v6.4 but not in v6.1. Has there been a change from 6.1 to 6.4 that would warrant a different way to handle this call - like a clean-up?
Also attached two logs when I ran the program on both versions. Platform is 43438, 1LD. Hope you can give some suggestions.
Show LessIs 802.11v currently supported? If yes, could you please clarify how the WNM Sleep Mode can be used?