Wi-Fi Combo Forum Discussions

I started poking around to see if I can get my build files packaged up so we can use them during manufacturing. It looks like the normal build command doesn't create build/$project/APP.bin, but we use that to jlink flash controllers during manufacturing. I started poking around to see how it gets pulled in and it looked like adding either "download" or "package" should build it. I confirmed it happens during download (but that tries to actually use jlink and download to a device). I noticed just adding "package" doesn't do anything. After digging in more I noticed it was setup like this:

package: $(RELEASE_PACKAGE)
    $(QUIET)$(ECHO) Created package successfully

$(RELEASE_PACKAGE): create_package_descriptor \
    $(STRIPPED_LINK_OUTPUT_FILE) display_map_summary \
    package_bootloader $(if $(findstring no_dct,$(MAKECMDGOALS)),,package_dct) package_app package_apps

in tools/makefiles/standard_platform_targets.mk, but RELEASE_PACKAGE isn't defined anywhere. If I pass in something defining it on the make line, I get the next issue:
make[1]: *** No rule to make target `create_package_descriptor',
I can't find any info on create_package_descriptor. I was wondering if this was meant to be removed and/or if I'm even going about this the right way. I'm currently using WICED-Studio-6.2.1.2 but I also tried on WICED-Studio-6.6.1 and saw the same issue. Any help or guidance would be appreciated.

Hi guys,

In our application, we connect to wifi AP and do stuffs. If we got some issues like request http error or disconnect with mqtt broker, we will retry to connect again. Incase retry not success we will disconnect with wifi AP and retry to connect current wifi AP again or connect the another wifi AP.

But sometime we got stuck forever in wiced_leave_ap.

I use CYW54907 with Wiced studio 6.6.

I just upgraded the version of Wiced we are using from 6.4 to 6.6.1.1. When the code tries to set wwd_wifi_fast_bss_transition_over_distribution_system the result is now WWD_WLAN_UNSUPPORTED.

The chip is a CY43012C0.

Any ideas why this no longer works?

Hi,

Is there a clear centralized exhaustive list (and history) of know vulnerabilities in the CYW4343W (or all chips) firmware ?

Browsing https://github.com/Infineon/wifi-host-driver commits to RELEASE.md (like that Upload wifi-host-driver 1.94.0.6931 · Infineon/wifi-host-driver@19968e1 (github.com)) I can see that there is a few changelogs related to the CYW4343W firmware.
--- 7.45.98.120 ---
Fix pmk caching
--- 7.45.98.117 ---
Security fixes
Memory usage reduction by disabling debug features
--- 7.45.98.110 ---
Fixed zero stall on UDP
Fixed Tx traffic too less then RX
--- 7.45.98.95 ---
Fixed zero stall on UDP
--- 7.45.98.92 ---
Security fix (KRACK all-zero-key)
--- 7.45.98.89 ---
Security fix(Dragonblood WPA3 attack)
TCP Keepalive Implementation
Security fix(CVE-2019-9501 / CVE-2019-9502)
--- 7.45.98.81 ---

This list is not easy to build and browse, the known vulnerabilities should be centralized.

Is this list exhaustive ?

How can we know what version exactly fixes a vulnerability ? This only show ranges...

Between 7.45.98.110 and 7.45.98.117, it is only mentioned "Security fixes"... Where can we get more details on this/these vulnerability(ies) ?

Looking at this blog post (Potential Fragmentation Vulnerabilities for Wi-Fi ... - Infineon Developer Community), it looks like the CYW4343W could by affected. How can we make sure whether it is or not ?

Any more information about firmware vulnerabilities is welcome.

Thanks and best regards

Measuring the 5.8g signal at the FCC test lab and only seeing 8 dbm, when the documents have 13 dbm as an average.  I retuned the antenna and still measuring 8 dbm.  Any ideas?

Hi there,

I am looking for an app note or more importantly some WICED sample code which will allow me to,  firstly connect a generic BT headset/speaker to the Sterling EWB (CYW4343W).   Secondly how to stream an audio signal connected to the BT_PCM pin on the CYW4343W to the headset.  There is no requirement to send audio from the headset back to the EWB module.

Hi, 

We have used CYW43455 for connection test, and we were unable to get IP address to run iperf even the AP can get the MAC address.  the following is our FW version and command process. can you advise ?

Version: 7.45.189 (r714228 CY) CRC: bdd6d3f5 Date: Thu 2019-05-02 02:42:20 PDT Ucode Ver: 1043.2132 FWID 01-ee766038 DVID 01-e048c631

wl down

wl country DE

wl band “b” or “a”

wl 2g_rate –r 1 ->  For 2G

wl up

wl join <SSID>

We have used Wiced SDK for Type 1LD development. Wiced doesn't supports LWM2M protocol. We are trying to port an open source LWM2M implementation like Wakaama/Anjay to Wiced SDK. But it seems like the mbedtls module available with Wiced /type 1ld have been tweaked at many places (compared to open source version). This creates a lot of issues in the UDP/TCP layer. We know that Wiced /type 1ld uses mbedtls to support many built in modules (like WiFi). Hence it is not possible to tweak or replace the Wiced /type 1ld mbedtls version. At this point, we think that it might not be possible to port an open source LWM2M implementation to Wiced SDK.

Hi,

Could you please give some clarifications on the setting of the listen_interval (wiced_wifi_set_listen_interval and wiced_wifi_set_listen_interval_assoc) ?

The documentation states that the first function should communicates the listen_interval to the AP. This seems to be true, but only during the association. If I change the listen_interval after that, the function does not communicate the new value to the connected AP, even though the change is effective.

Why is that ? Is there a problem with updating the listen_interval while connected ? How can I let the AP knows that I want to change / changed the listen_interval without disconnecting ?

Thanks for your support.

Best regards,
Mehdi