Wi-Fi Combo Forum Discussions
Hi,
I am using an STM32F412 microcontroller with the CYW43012 and I need to reserve some space in Flash memory to save some non-volatile data.
What is the recommended way to modify the linker script for a WICED project?
My project seems to be using 43xxx_Wi-Fi/WICED/platform/MCU/STM32F4cc/GCC/STM32F412/memory_with_bootloader.ld so I could edit that file, but I would rather contain the changes to my application (which I currently just check out into 43xxx_Wi-Fi/apps) and not change the WICED supplied code.
regards,
Charles
Show LessWe are currently using the Sterling LWB which uses the cyw43430 firmware version 7.45.98.65 and experience the following problem.
In our software application we are using bluetooth to continuously alternate between scanning passively (99% of the time) and connecting shortly (mostly <120 seconds) with a BLE peripheral, the application also requires a wifi connection to communicate with a central server. However, we noticed that during normal operation the wifi speed is highly affected by the bluetooth communication (average download speed of 20-50kbytes/s). If we disable the bluetooth communcation in general, download speeds up to 2 Mbyte/s are achieved.
Additionally, we've noticed the 'btc_mode' and 'btc_params' in '/lib/firmware/brcm/brcmfmac43430-sdio.txt' which can be tweaked for wifi and bluetooth coexistence. Sadly enough it is nowhere to be found what they mean.
One thing we've tested had a significant impact on the download and upload speed (however with reduced bluetooth stability). We've disabled (at least we think we did) bluetooth coexistence by setting 'btc_mode=0'. Disabling btc_coex improved the download speed which went up to 2 Mbyte/s, at the same time the bluetooth stability was reduced (i.e. time to set up connection increases + more failures). This seems similar to the 'BLE througput with coex enabled' test done in Coexistence Throughput Test. Though by disabling bluetooth coexistence we would expect everything to work very bad, but it did the opposite which seems very odd. After a while we did notice the following error which made the firmware unusable:
Oct 14 20:26:15 NODP-19-01111 kernel: brcmfmac: brcmf_sdio_readshared sdpcm_shared address 0x0004136C
Oct 14 20:26:15 NODP-19-01111 kernel: brcmfmac: brcmf_sdio_hostmail: Unknown mailbox data content: 0x40012
Oct 14 20:26:21 NODP-19-01111 kernel: brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
Oct 14 20:26:21 NODP-19-01111 kernel: brcmfmac: brcmf_sdio_readshared sdpcm_shared address 0x0004136C
Oct 14 20:26:21 NODP-19-01111 kernel: brcmfmac: brcmf_sdio_checkdied firmware not built with -assert
Oct 14 20:26:21 NODP-19-01111 kernel: brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
Oct 14 20:26:21 NODP-19-01111 kernel: brcmfmac: brcmf_do_escan: error (-110)
Oct 14 20:26:21 NODP-19-01111 kernel: brcmfmac: brcmf_cfg80211_scan: scan error (-110)
Oct 14 20:26:21 NODP-19-01111 wpa_supplicant[479]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-110
We've noticed this mailbox issue more frequent in 7.45.41.47 but was resolved by a newer release, though disabling bt_coex somehow triggers the error. In firmware version 7.45.41.47 we notice higher upload speeds but almost identical download speeds.
In addition I've added 2 boxplots showing download and upload speeds and bluetooth connection time (and a txt file with additional statistics). The speed is the result of an iperf test (over a 1 hour period) in kilobytes/s. The connect time is the time needed to set up a connection with a ble peripheral (in milliseconds).
The 3 boxplots mean following:
- btc_mode=0 -> firmware version 7.45.98.65 with bluetooth coexistence disabled
- 7.45.98.65 -> firmware version 7.45.98.65 without additions
- 7.45.41.47 -> firmware version 7.45.41.47 without additions
Additional tests that do not give significant changes:
- using btc_params used by RPI (firmware-nonfree/brcmfmac43430-sdio.txt at master · RPi-Distro/firmware-nonfree · GitHub)
btc_params8=0x4e20
btc_params1=0x7530
- using bluez 5.50
- using laird btc_params (which are commented out by default)
- btc_params8=45000
- btc_params10=20000
- changing baudrate for brcm_patchram_plus (default value is 3000000) decreased gradually to 9600
The questions we currently remain unanswered are:
- what is the meaning of the btc_params ?
- does btc_mode=0 really disable coexistence or why do we achieve unexpected results?
Hi Cypress,
May I know if CYW4356 supports concurrent Station and AP operation?
Is there Linux driver and configuration ready for this concurrent Station and AP operation?
thanks!
Show LessHello Gentlemen,
We are planning to do a CE certification for my product. We have prepared the FCC, CE, IC certification test scripts. But especially for the CE EN300328 RF adaptivity test, we need to communicate our CYW43438 Soc to CMW500 WiFi simulator.
Any utility or test script is available for communicating CYW434538 with CMW500?
Let us know if any other solutions are available?
Show LessI'm getting to: wiced_assert( "ThreadX stack overflow", 0 != 0 ); when I try to run my application in debug mode. Memory exploration indicates that there is not actually an overflow going on. It happens when I receive the 2nd character via a UART connection (I've explored the receive buffer, first char is in the ring buffer) and from the stack trace indicated in the debugger is happening in the driver UART ISR.
I'ts preventing me from actually debugging, and I've tried ridiculously large stack sizes to no help.
I've also seen this discussion, ThreadX stack overflow when DEBUG enabled but increasing my stack size did not solve the problem.
Debug screen showing the assert, memory view of the stack area, thread details including stack pointer/start/end, and call trace here:
Show Less
Hi,
I understand CYW43907 is perhaps not quite designed to act as a "network gateway" for another MCU/MPU and I am keen to explore this Use Case. I am essentially looking to share the WiFi network from the CYW43907 to an external system, pretty much as a NAT gateway. Can this be achieved either via USB ECM acting as a WiFi dongle essentially, ethernet RMII (direct MAC to MAC without a PHY) or as a SDIO slave? I am excluding UART here with something like SLIP as I am looking for >= 10Mbps speeds.
I did find a past thread alluding that this functionality was under consideration, but I'd like to understand if this is something that is being worked on and is/will be available?
Alternatively, does Cypress have any other Wireless MCUs (not standalone radio only) that can support this Use Case at present?
Thanks!
Will.
Show LessI'm having a probelm installing Wiced Studo on my Mac, I’m trying to install Version 6.4.0.61, here is the error I get:
I’m running macOS Catalina, version 10.15.1
Is there a known issue with Catalina?
Thanks!
Show LessWe have reached a point of uploading a larger amount of DATA into the cloud - we are talking a few tens of MBytes. It seems that Azure provides support for both protocols, though MQTT seems simpler.
My question is if we should expect speed / robustness limitations with the current MQTT 3.1.1 from inside WICED and should we consider WICED AMQP 1.0 instead ?
Has anyone run this scenario of streaming data over WIFI with the current version of WICED MQTT ? What kind of upload speeds would saturate WICED MQTT 3.1.1 implemention ? -- Thanks, BM
Show LessHi all.
I'm new of community (sorry in advance for wrong procedure during request).
I'm working to integrate JODY-W1 in yocto distribution based on linux 3.14.55.
I would need of documentation, driver and application S/W for WLAN/Bluetooth.
Are available these information in some sections of this community?
Thank in advance for the response.
Best regards.
Fabrizio Crudo.
Show LessLaird Connectivity Webinar
Navigate IoT Design Challenges Using Laird Connectivity's Wi-Fi & Bluetooth Modules
As wireless connectivity becomes ubiquitous, designers are faced with a host of design challenges involving software integration, coexistence, antenna design and worldwide regulatory certification. Because of this, manufacturers are looking for a reliable, market tested, and innovative partner for adding wireless technology to their existing and future products. Laird Connectivity is a global Cypress ecosystem partner with a long history of solving these design challenges using globally certified modules, world-class design services and manufacturing, along with unparalleled customer support that is recognized throughout the industry.
As a strategic ecosystem partner of Cypress, Laird Connectivity leverages Cypress’ industry leading Wi-Fi/Bluetooth combo and Bluetooth stand-alone radio chipsets in their certified module portfolio. This webinar will serve as a helpful educational tool and launch pad for manufacturers looking to add world class Wi-Fi/Bluetooth connectivity to their next IoT device while overcoming the complex and expansive nature of wireless design.
Date: Wednesday December 4th, 2019
Time: 10:00 AM PST
Agenda:
- Design Considerations for WiFi & Bluetooth
- Laird Connectivity Wireless Module Offering (Powered by Cypress)
- Example Success Stories & Use Cases
- How to Get Started & Resources
Register here: Laird Connectivity Webinar
Show Less