Wi-Fi Bluetooth for Linux Forum Discussions
Package Version
ahd-2023_1221
Release Date
2023-12-21
Description
Infineon Android release for the broad market.
This release has been qualified on IMX8 SDIO platform and Hikey960 PCIE platform running Android 13.
Customers wishing to leverage the Android Open Source Platform now have an out of the box Android solution for Infineon's connectivity parts.
The release package includes:
* ahd
* 4373-Android13-SDIO
*43012-Android13-SDIO
*43022-Android13-SDIO
*54591-Android13-PCIE
*55572-Android13-SDIO
*AHDBinaries
*device
*firmware
*nvram
* Android13_55572_SDIO_Release_Notes.pdf
* Infineon_55572_Wi-Fi_6_6E_User_Guide.pdf
* confs
* hostapd_supplicant_src
* Android13_PCIE_Bringup.pdf
* Android13_SDIO_Bringup.pdf
* Android13_Feature_Bringup.pdf
Test Environment:
* IMX8 SDIO setup
* Hikey960 PCIE setup
* 55572, 43012, 43022, 54591 and 4373 Sanity, 6G and 11ax features (55572), WOWL via OOB(55572)
and PNO scan offload(55572, 43022)
Show LessDescription
The package contains all the required files (including AIROC™ Bluetooth® stack for ARMv8 Linux, Bluetooth® porting layer, and sample code examples of Bluetooth® profiles) to evaluate and test Bluetooth® Classic and Low Energy on AIROC™ combo chip (CYW4373, CYW43439, CYW55573/2/1).
What's new?
Package comes with codes examples to demonstrate Bluetooth LE Audio capability of CYW55573/2/1 in hosted mode. The code example demonstrates Bluetooth® LE Audio unicast and broadcast functionality.
Functions include:
- Broadcast audio stream scanning
- Receiving broadcast audio stream
- Unicast audio stream establishment
- Unicast audio stream release
- Unicast sink connect to source (1 CIG, 1 CIS)
Bluetooth® Linux Code Examples & Supported Chip
Code example |
Feature demonstration |
Supported chip |
LE Audio CIS Source |
Implements the Unicast Source application using BTSTACK and LE-Audio profile library |
CYW55573/CYW55572/CYW55571 |
LE Audio CIS Sink |
Implements the Unicast Sink application using BTSTACK and LE-Audio profile library |
CYW55573/CYW55572/CYW55571 |
LE Audio BIS Source |
Demonstrates the ability of LE Audio broadcast |
CYW55573/CYW55572/CYW55571 |
LE Audio BIS Sink |
Demonstrates the ability to receive LE Audio broadcast |
CYW55573/CYW55572/CYW55571 |
Linux Bluetooth® Find me |
Demonstrates the Find Me profile which defines the behavior when a button is pressed on one device to cause an alerting signal on a peer device |
CYW55573/CYW55572/CYW55571 |
Linux Bluetooth® hello sensor |
Demonstrates GATT database and device configuration initialization, sending data to the client and processing write requests from the client |
CYW55573/CYW55572/CYW55571 CYW43439,CYW4373 |
Linux Bluetooth® Wi-Fi onboarding |
Demonstrates the feature that enables devices to connect to a Wi-Fi access point without requiring a physical interface |
CYW55573/CYW55572/CYW55571 CYW43439,CYW4373 |
Linux Bluetooth® Headset |
Multiple profile code example that demonstrates the use cases and ability of audio-related functions such as A2DP, AVRCP CT, and HFP |
CYW55573/CYW55572/CYW55571 |
Linux Bluetooth® SPP |
Demonstrates how two devices can establish a wireless communication link that emulates a traditional serial port connection |
CYW43439,CYW4373 |
Package GitHub link: https://github.com/Infineon/ifx-linux-bluetooth
Release notes
Please go through the attached released notes for more details on the package.
Show Lessv5.15.58-2024_0118
Release Date
2024-01-18
Github Link
V5.15.58 backport package: Link
V6.1.19 patch: link
Description
This is Cypress's Linux brcmfmac driver and firmware support package.
Brcmfmac is an open-source driver project.
Files in this release:
Part 1: cypress-fmac-v5.15.58-2023_1128.zip
* Backports package (cypress-backports-v5.15.58-2023_1128-module-src.tar.gz)
* Firmware/clm_blob files (cypress-firmware-v5.15.58-2023_1128.tar.gz)
* Cypress fmac patch files (cypress-patch-v5.15.58-2023_1128.tar.gz)
* Device tree files (cypress-devicetree-2023-11-28.tar.gz)
* hostapd/wpa_supplicant patch (cypress-hostap_2_10-2023_1128.tar.gz)
* Cypress customer patch (cypress-custom-patch-5.4.21.tar.gz)
* Cirrent Agent (cypress-cirrent-1.60.tar.gz)
* Documents (docs/)
* README
Part 2: cypress-patch-v6.1.19-2023_1128.zip
* Cypress fmac patch files for Vanilla v6.1.19(cypress-patch-v6.1.19-2023_1128.tar.gz)
* Infineon-Vanilla-Kernel-v6.1.19-Bring-up-Reference_20201221.pdf
Checksum
cypress-fmac-v5.15.58-2023_1128 sha256sum:
990b5f6beeb9530525f254977569fd25936e09f9ef1bf36ca52118e73dff3e68 cypress-backports-v5.15.58-2023_1128-module-src.tar.gz
ce3bb31020e5ffe24fe549802440c137d14a05ad77af3e8e1fb9e184db96ed55 cypress-cirrent-1.60.tar.gz
0c8da2efe289115f2242aa3f69de5bc616cb893ecd411e11194c4c008418bb2e cypress-custom-patch-5.4.21.tar.gz
c38cca05bb05db6198af7809c7a2e519cb33a06b02ebd4d626588c9038f7259b cypress-devicetree-2023-11-28.tar.gz
92608ceb4509cc02730833ce2119662b3c116a3956ca303245e97378186dc2a3 cypress-firmware-v5.15.58-2023_1128.tar.gz
771099830bd106307e77ebdd4d27a3e18de27bb60889c4db4bca81f44ade495d cypress-hostap_2_10-2023_1128.tar.gz
8fe7d8b677032fb04374615aae27c5a3131499956dc22ddb420847a3876974c6 cypress-patch-v5.15.58-2023_1128.tar.gz
cypress-patch-v6.1.19-2023_1128 sha256sum:
933ac3a50f0146b4078beb5e398c75a93ab0a1979a93d120a1c0ba2a06ab0ff7 Infineon-Kernel-v6.1.19-Bring-up-Reference.pdf
ac23fabed00e5c5ab0c3720fa0eb6fa135a589e009714f783701fe557abe3fe7 v6.1.19-2023_1128.tar.gz
Part 3: cypress-fmac-v5.15.58-2024_0118.zip
8ccbebf31bf69c85dc7d05fb7e3597fa282c3ba5373d76b2a65364191abb14d0 cypress-backports-v5.15.58-2024_0118-module-src.tar.gz
ce3bb31020e5ffe24fe549802440c137d14a05ad77af3e8e1fb9e184db96ed55 cypress-cirrent-1.60.tar.gz
92e7196a896fa65138c8297d4202a1811564605360f807faa2c8af310eddeb2e cypress-custom-patch-5.4.21.tar.gz
40dd314cee28149028a2d524ccd5d25f20336c7314e1e26654daecf4c9a796d2 cypress-devicetree-2024-01-18.tar.gz
739d1fae54d885e136847af2957821324c18c68622f204992e268b991172da53 cypress-firmware-2024_0118.tar.gz
2a411fb64818b054498645f64e3ef3b29e4db9a36b65987d9a3af76c2d60f765 cypress-hostap_2_10-2024_0118.tar.gz
8e43bc4487c5d4e77880e2fc9d3152a011063c5b0f3871e277561f0108a88304 cypress-patch-v5.15.58-2024_0118.tar.gz
[Change Log]
2023-12-18 Initial Post
2023-12-22 Add cypress-patch-v6.1.19 to support build brcmfmac on 6.1.19
2024-01-18 Fix for system crash post suspend and resume with CYW55572/55573 [PCIe]
The BT assets of AIROC Bluetooth Stack (Linux) Release are all on GitHub now.
Description:
AIROC Bluetooth Stack is Infineon's Bluetooth Host Protocol Stack implementation. The stack is optimized to work with Infineon Bluetooth controllers. The BTSTACK supports Bluetooth BR/EDR and BLE core protocols. This page provides the Github links to get started with application developments in Linux platform using AIROC Bluetooth Stack.
Please find the code examples :
Code Examples:
https://github.com/Infineon/linux-example-btstack-wifi-onboarding
https://github.com/Infineon/linux-example-btstack-wakeonle
https://github.com/Infineon/linux-example-btstack-bas
https://github.com/Infineon/linux-example-btstack-hello-sensor
https://github.com/Infineon/linux-example-btstack-alert-client
https://github.com/Infineon/linux-example-btstack-alert-server
https://github.com/Infineon/linux-example-btstack-headset
https://github.com/Infineon/linux-example-btstack-a2dp-source
https://github.com/Infineon/linux-example-btstack-a2dp-sink
https://github.com/Infineon/linux-example-btstack-spp
https://github.com/Infineon/linux-example-btstack-handsfree-unit
https://github.com/Infineon/linux-example-btstack-handsfree-ag
Show Less
The latest Infineon Linux Wi-Fi driver (FMAC) release can be accessed here:
Sr. No. | Driver release name | Release link |
1 | Backports v5.15.58-2023_1128 |
Public forum link: https://community.infineon.com/t5/Wi-Fi-Bluetooth-for-Linux/Cypress-Linux-WiFi-Driver-Release-FMAC-2023-11-28/td-p/662238 |
2 | 6.1 Latest kernel for RPI : RPI-6.1.21 IFXFMAC |
Github: https://github.com/Infineon/rpi-linux-kernel/releases/tag/6.1.21-hedorah-IFXFMAC-20231128 |
3 | 6.1 Kernel on BRCMFMAC |
Github: https://github.com/Infineon/ifx-wireless-drivers/tree/RTM/v6.1.19-hedorah |
Documentation is available in docs folder of cypress-fmac-v5.15.58-2023_1128.zip available at this link https://community.infineon.com/t5/Wi-Fi-Bluetooth-for-Linux/Cypress-Linux-WiFi-Driver-Release-FMAC-2023-11-28/td-p/662238
The older/archived Wi-Fi driver releases can be accessed here:
Show Less
Package Version
ahd-2022_1223
Release Date
2023-01-03
Description
Cypress Android release for the broad market.
This release has been qualified on Hikey 960 platform.
Customers wishing to leverage the Android Open Source Platform now have an out of the box Android solution for Cypress's connectivity parts.
The release package includes:
* ahd
* device
*hikey960
* firmware
* nvram
* 55572_AndroidBringup.pdf
Test Environment:
* Hikey 960
* 55572 Sanity and VTS
Change Log
[2022-12-23]
* Initial post
Show LessHi there,
We are trying to fcc wifi certify our project which uses a custom buildroot toolchain and arm processor.
We need help to compile the wl_tool so we can proceed with certification, but we need it to be cross compiled for our architecture (arm 32bit).
Can I ask a representative to help us to compile it with our custom toolchain?
CPU Info:
- armv7l
- little-endian
- hard-float ABI
- neon/vfpv4
Custom Toolchain Instructions:
- download toolchain
- extract toolchain:
tar jxf arm-co6-linux-uclibcgnueabihf_sdk-buildroot_2021.02.1.tar.xz - cd to arm-co6-linux-uclibcgnueabihf_sdk-buildroot
- ./relocate_sdk.sh
- add toolchain into path e.g.
export PATH="$PATH:$PWD/usr/bin" - Set cross compile variables:
export ARCH=arm
export CROSS_COMPILE=arm-co6-linux-uclibcgnueabihf-
Tagging @VinayakS_26 / @raks_99 / @DoubleLo as I found they have helped another customer to do this.
Show Less
Hi,
I have a board mounting a CYW43364-based module running a linux-based system.
I want to change sdio drive strength for the chip.
According to brcmf_sdio_drivestrengthinit in drivers/net/wireless/brcm80211/brcmfmac/sdio.c it seems I cannot do it, but since the device is treated as CYW43430 and that I don't have an application manual of the chip (a document describing registers) I need some hint.
For instance it seems to be possible to achieve this goal when using a CYW43362 device...
Also devicetree bindings documentation doesn't help so much since it is the same for all brcmfmac devices ["brcm,drive-strength : drive strength used for SDIO pins on device in mA (default = 6)."].
I checked also mainline 4.20 kernel version and the mentioned function (brcmf_sdio_drivestrengthinit) shed no more light.
Thank you for an help
Show LessHello,
I am using Murata WLAN Combo Module SP-HY1MW-F chip which has BCM43455 inside it.
I am using Broadcom generic fmac driver. The firmware & nvram is downloaded from https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/brcm.
I am struggling to enable Wifi AP & STA mode at a time:
1) When I use connmanctl tether command, it disables the client mode & enables the AP mode, but not both at a time.
2) When I try creating new interface of managed mode for tethering, it throws an error: Not supported (-95)
3) When I try creating bridge manually using ip commnd & connecting wlan0 with bridge as a master, it also throws me the error: Not supported (-95)
Can you please help me with the issue?
Thanks & Regards,
Brinda Pathak
Show LessHi,
We are working with the brcmfmac driver (version v4.14.34-2018_0716) + wpa_supplicant on CYW43455 on i.MX6 Linux.
In this case we are assocating to a WPA2-Enterprise network using PEAP-MSCHAPv2.
When roaming we often see longer than expected roaming times since the device is slow to respond to the first EAP Request. The trace extract below shows a case where there's 150 milliseconds between RX EAPOL and TX EAPOL.
The delay seems to be caused by the CYW43455 firmware being slow to send the "ROAM" event to the brcmfmac driver, which in turn prevents the wpa-supplicant from sending the first EAP response.
Here are some extracts from the driver and supplicant logs:
Aug 08 05:03:12.095765 kernel: brcmfmac: brcmf_rx_event Enter: mmc0:0001:1: rxp=86801540
Aug 08 05:03:12.095935 kernel: brcmfmac: brcmf_fweh_event_worker 1533704592.: event LINK (16) ifidx 0 bsscfg 0 addr 1c:aa:07:c7:6b:ca
Aug 08 05:03:12.095968 kernel: brcmfmac: brcmf_fweh_event_worker 1533704592.: version 2 flags 1 status 0 reason 0
Aug 08 05:03:12.098155 wpa_supplicant[536]: l2_packet_receive: src=1c:aa:07:c7:6b:ca len=69
Aug 08 05:03:12.098308 wpa_supplicant[536]: wlan0: RX EAPOL from 1c:aa:07:c7:6b:ca
Aug 08 05:03:12.098362 wpa_supplicant[536]: RX EAPOL - hexdump(len=69): 02 00 00 41 01 01 00 41 01 00 6e 65 74 77 6f 72 6b 69 64 3d 41 57 53 56 6f 69 63 65 2c 6e 61 73 69 64 3d 57 53 53 45 47 4f 54 41 57 4c 4
Aug 08 05:03:12.098551 wpa_supplicant[536]: wlan0: Not associated - Delay processing of received EAPOL frame (state=COMPLETED bssid=1c:aa:07:7b:5c:3a)
Aug 08 05:03:12.223541 kernel: brcmfmac: brcmf_rx_event Enter: mmc0:0001:1: rxp=86ac7cc0
Aug 08 05:03:12.223708 kernel: brcmfmac: brcmf_fweh_event_worker event ROAM (19) ifidx 0 bsscfg 0 addr 1c:aa:07:c7:6b:ca
Aug 08 05:03:12.223742 kernel: brcmfmac: brcmf_fweh_event_worker version 2 flags 0 status 0 reason 1
<some lines removed>
Aug 08 05:03:12.248937 wpa_supplicant[536]: TX EAPOL: dst=1c:aa:07:c7:6b:ca
Aug 08 05:03:12.248966 wpa_supplicant[536]: TX EAPOL - hexdump(len=16): 01 00 00 0c 02 01 00 0c 01 57 48 31 41 57 53 56
Any suggestions on why this delay occurs and how we can avoid it would be greatly appreciated. Could the "LINK" event from the firmware (which is not delayed) be used to trigger the start of EAP negotiation?
Best regards,
Fredrik
Show LessSpecs:
Board: i.MX7D SABRESD RevA
CPU: Freescale i.MX7D rev1.2 at 792 MHz
Brcm chip: 43455 (SDIO)
Firmware: brcm/brcmfmac43455-sdio.bin
Kernel + FMAC used: https://community.cypress.com/docs/DOC-15932
I am trying to put the drivers into APSTA mode, where the board can connect to an upstream AP and can allow clients to connect downstream.
I have verified that drivers can be placed into STA mode, by configuring them for STA and connecting to a WPA2-PSK SSID and passing ping traffic.
I have tried running the drivers in AP mode, but have failed. I have configured the driver to broadcast an SSID on a particular channel, and have even associated a client to that SSID, but failed to pass any ping traffic. The linux wlan0 interface is up but not RUNNING, when driver is in AP mode. The wl commands for configuring in AP mode are below.
ifconfig wlan0
ifconfig wlan0 up
wl -i wlan0 down
wl -i wlan0 ap 1
wl -i wlan0 country US
wl -i wlan0 5g_rate auto
wl -i wlan0 bw_cap 5g 0x7
wl -i wlan0 ssid "001_mesh_open"
wl -i wlan0 bss 1
wl -i wlan0 chanspec 36/20
wl -i wlan0 txchain 7
wl -i wlan0 rxchain 7
wl -i wlan0 up
wl -i wlan0 bss 1
wl -i wlan0 status
wl -i wlan0 msglevel + assoc + error + info
ifconfig wlan0 up
What am I missing? Does the driver need to be compiled differently? Does the above firmware support AP/STA mode simultaneously?
Any help is greatly appreciated.
Show LessHi All,
We are trying to bring-up Wake on Wireless Feature on CYW43455 (Murata 1MW) module using IMX6ULL-EVK board.
We are using Version2.0 Interconnect Adapter for connecting BT and Control signals to IMX board using ribbon cable from Murata 1MW module.
Configured Jumper settings as below for SDIO 3.3v supply and enabling WiFi on Murata Module
- Shorted Pad TP14
- Closed Jumper TP7 and TP9
- Connected Ribbon Cable to IMX board
- Inserted SDIO connector to IMX board
- By default WL_REG_ON is not becoming high using ribbon cable connector so connected a wire from TP21(WL_REG_ON pin) to a GPIO on IMX board that will drive 3.3v to enable WiFi on Murata module
Monitoring WL_HOST_WAKE pin:
- Connected a wire on TP20 (WL_HOST_WAKE) and connected the other end to Logical Analyser to monitor signal level on this pin.
- Always the signal on this pin is LOW (Considering 3.3v as HIGH in this line)
Kernel DTB File:
- Used default imx6ul-evk-btwifi.dtsi file
- Also configured oob gpio taken from imx6ul-evk-btwifi-oob.dtsi file and added to imx6ul-evk-btwifi.dtsi as below
brcmf: bcrmf@1 {
/*reg = <1>;
compatible = "brcm,bcm4329-fmac";*/
interrupt-parent = <&gpio2>;
interrupts = <15 IRQ_TYPE_LEVEL_HIGH>; /* WL_HOST_WAKE = GPIO2_IO15 active high. Change to IRQ_TYPE_EDGE_RISING for 1BW and SN8000. */
interrupt-names = "host-wake";
};
Attached dtb file used after modifying with WL_HOST_WAKE changes
Steps followed to Suspend and Resume Host:
- Connect to Wireless Network
- Configure Wake On Wlan feature so that will trigger wake signal on disconnection from WiFi Network wl wowl 4
- Put Host on suspend to memory echo mem >/sys/power/state
- Disconnect WiFi from Network
Observations:
- WL_HOST_WAKE pin signal is always LOW, no change whether HOST is in suspended mode or normal mode.
- Using both default DTB file and Modified DTB file as mentioned above there is no change in WL_HOST_WAKE signal
Queries:
- Steps to enable Wake on Wlan feature using WL_HOST_WAKE (OOB interrupt) ?
- what is the Voltage level of WL_HOST_WAKE pin ? is it 1.8v or 3.3v ?
- For enabling oob interrupts do we need to do any hardware rework changes on Murata module ?
- Is there any dependency on Host oob GPIO configuration to enable Wake On Wlan feature using WL_HOST_WAKE for just monitoring WL_HOST_WAKE pin on Logic Analyser directly without dependency on Host?
Hi,
We have disabled roam Firmware offloading by loading brcmfmac module with roamoff=1 module param
Also disabled BRCMF_FEAT_FWSUP feature by disabling below line in feature.c under brcmf_feat_attach()
//brcmf_feat_iovar_int_get(ifp, BRCMF_FEAT_FWSUP, "sup_wpa");
When loading modules with above configuration Group Key Renewal is failing with WPA2 Authentication
Also connection is failing when WPA is configured during Group Key Exchange.
AP is sending Deauth with reason code 15 (4-way-Handshake Failed) with failing Group Key Exchange.
Attaching GTK Renewal Failed log at Controller/AP side.
Looks like even-though firmware roam-offload and FWSUP is disable the response to Group Key (M5) message is sent by Firmware instead of forwarding request to wpa_supplicant. Because of this Group Key renewal is getting failed.
Please provide us any details to configure WiFi Module to forward handling of Group Keying to wpa_supplicant instead of handled by FWSUP.
Show LessHi,
We would like to bring-up monitor mode on CYW43455 (Murata 1MW) module.
We tried using wl command to enable monitor mode as below but not successful
wl monitor 1
Also tried using iw commands to create Monitor mode interface but it returns below error
#ip link set IFACE down
#iw IFACE set monitor control
#command failed: Operation not supported (-95)
When we checked the discussion on below link it says "There is no limitation on the firmware side as such for entering monitor mode."
https://community.cypress.com/message/177118#177118
Let us know do we need to use specific Drivers/Firmware to enable this feature.
Please share us necessary steps to bring-up monitor mode
Let us know if any more details are required.
Below are the S/W version details:
Loading modules backported from Linux version v4.14.52-manda-RTM-0-g897c6ceBackport generated by backports.git v4.14-rc2-1-70-g694b78fbrcmfmac: brcmf_fw_map_chip_to_name: using brcm/brcmfmac43455-sdio.bin for chip 0x004345(17221) rev 0x000006usbcore: registered new interface driver brcmfmacbrcmfmac: brcmf_c_preinit_dcmds: Murata Customized Version: imx-rocko-manda_r1.0;brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Sep 21 2018 04:08:34 version 7.45.173 (r707987 CY) FWID 01-d2799ea2
1.21 RC0.0wl0: Sep 21 2018 04:08:34 version 7.45.173 (r707987 CY) FWID 01-d2799ea2
vendorid 0x14e4deviceid 0x43abradiorev 0x58030bchipnum 0x4345chiprev 0x6chippackage 0x2corerev 54.0boardid 0x6e4boardvendor 0x14e4boardrev P201driverrev 7.45.173.0ucoderev 0x0bus 0x0phytype 0xbphyrev 20.0anarev 0x0nvramrev 498373
Below is the output of iw phy phy0 info
Wiphy phy0
max # scan SSIDs: 10
max scan IEs length: 2048 bytes
max # sched scan SSIDs: 16
max # match sets: 16
max # scan plans: 1
max scan plan interval: 508
max scan plan iterations: 0
Retry short limit: 7
Retry long limit: 4
Coverage class: 0 (up to 0m)
Device supports roaming.
Supported Ciphers:
* WEP40 (00-0f-ac:1)
* WEP104 (00-0f-ac:5)
* TKIP (00-0f-ac:2)
* CCMP-128 (00-0f-ac:4)
* CMAC (00-0f-ac:6)
Available Antennas: TX 0 RX 0
Supported interface modes:
* IBSS
* managed
* AP
* P2P-client
* P2P-GO
* P2P-device
Band 1:
Capabilities: 0x1022
HT20/HT40
Static SM Power Save
RX HT20 SGI
No RX STBC
Max AMSDU length: 3839 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 16 usec (0x07)
HT TX/RX MCS rate indexes supported: 0-7
Bitrates (non-HT):
* 1.0 Mbps
* 2.0 Mbps (short preamble supported)
* 5.5 Mbps (short preamble supported)
* 11.0 Mbps (short preamble supported)
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
Frequencies:
* 2412 MHz [1] (20.0 dBm)
* 2417 MHz [2] (20.0 dBm)
* 2422 MHz [3] (20.0 dBm)
* 2427 MHz [4] (20.0 dBm)
* 2432 MHz [5] (20.0 dBm)
* 2437 MHz [6] (20.0 dBm)
* 2442 MHz [7] (20.0 dBm)
* 2447 MHz [8] (20.0 dBm)
* 2452 MHz [9] (20.0 dBm)
* 2457 MHz [10] (20.0 dBm)
* 2462 MHz [11] (20.0 dBm)
* 2467 MHz [12] (20.0 dBm)
* 2472 MHz [13] (20.0 dBm)
* 2484 MHz [14] (20.0 dBm)
Band 2:
Capabilities: 0x1062
HT20/HT40
Static SM Power Save
RX HT20 SGI
RX HT40 SGI
No RX STBC
Max AMSDU length: 3839 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 16 usec (0x07)
HT TX/RX MCS rate indexes supported: 0-7
VHT Capabilities (0x00001020):
Max MPDU length: 3895
Supported Channel Width: neither 160 nor 80+80
short GI (80 MHz)
SU Beamformee
VHT RX MCS set:
1 streams: MCS 0-9
2 streams: not supported
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
VHT RX highest supported: 0 Mbps
VHT TX MCS set:
1 streams: MCS 0-9
2 streams: not supported
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
VHT TX highest supported: 0 Mbps
Bitrates (non-HT):
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
Frequencies:
* 5170 MHz [34] (20.0 dBm)
* 5180 MHz [36] (20.0 dBm)
* 5190 MHz [38] (20.0 dBm)
* 5200 MHz [40] (20.0 dBm)
* 5210 MHz [42] (20.0 dBm)
* 5220 MHz [44] (20.0 dBm)
* 5230 MHz [46] (20.0 dBm)
* 5240 MHz [48] (20.0 dBm)
* 5260 MHz [52] (20.0 dBm)
* 5280 MHz [56] (20.0 dBm)
* 5300 MHz [60] (20.0 dBm)
* 5320 MHz [64] (20.0 dBm)
* 5500 MHz [100] (20.0 dBm)
* 5520 MHz [104] (20.0 dBm)
* 5540 MHz [108] (20.0 dBm)
* 5560 MHz [112] (20.0 dBm)
* 5580 MHz [116] (20.0 dBm)
* 5600 MHz [120] (20.0 dBm)
* 5620 MHz [124] (20.0 dBm)
* 5640 MHz [128] (20.0 dBm)
* 5660 MHz [132] (20.0 dBm)
* 5680 MHz [136] (20.0 dBm)
* 5700 MHz [140] (20.0 dBm)
* 5720 MHz [144] (20.0 dBm)
* 5745 MHz [149] (20.0 dBm)
* 5765 MHz [153] (20.0 dBm)
* 5785 MHz [157] (20.0 dBm)
* 5805 MHz [161] (20.0 dBm)
* 5825 MHz [165] (20.0 dBm)
Supported commands:
* new_interface
* set_interface
* new_key
* start_ap
* set_bss
* join_ibss
* set_pmksa
* del_pmksa
* flush_pmksa
* remain_on_channel
* frame
* set_wiphy_netns
* set_channel
* start_sched_scan
* start_p2p_device
* connect
* disconnect
* crit_protocol_start
* crit_protocol_stop
* update_connect_params
Supported TX frame types:
* managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
Supported RX frame types:
* managed: 0x40 0xd0
* P2P-client: 0x40 0xd0
* P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* P2P-device: 0x40 0xd0
WoWLAN support:
* wake up on disconnect
* wake up on magic packet
* wake up on pattern match, up to 8 patterns of 1-128 bytes,
maximum packet offset 1500 bytes
software interface modes (can always be added):
valid interface combinations:
* #{ managed } <= 1, #{ P2P-device } <= 1, #{ P2P-client, P2P-GO } <= 1,
total <= 3, #channels <= 2
* #{ managed } <= 1, #{ AP } <= 1, #{ P2P-client } <= 1, #{ P2P-device } <= 1,
total <= 4, #channels <= 1
Device supports scan flush.
ip link
set
wlan0 down
Hi colleagues,
We use Cypress chip CYW43362 based module and would like to upgrade to latest FMAC driver from https://github.com/murata-wireless/cyw-fmac
But to do this we need a WL utility for FCC certification.
Toolchain/system/kernel info:
WiFI Chip: CYW43362
linux 4.9.89
glibc 2.27-57
gcc 7.x
CPU Chip: at91sam9g15ek
Instruction set: ARM, LittleEndian
CPU: arm926t (armv5)
Our toolchain is arm-buildroot-linux-gnueabi
Can you please compile it and share binary?
Please let's know if you need any further information.
Thanks,
Sergey Kulyk
Show LessCYW89359 stores configuration parameters in OTP.
OTP means One Time Programmable nonvolatile memory inside chip.
I think that this memory is like a flash memory without erase function support.
Could you tell me the actual value of the data retention time of this memory?
Show LessHi
I made own custom board with raspberry pi compute module 3 and 1DX module.
1DX is connected to Raspberry pi via SDIO 1.
I downloaded all of NVRAM file from GitHub - murata-wireless/cyw-fmac-nvram and copied to /lib/firmware/brcm.
(refer to en:users:drivers:brcm80211 [Linux Wireless] )
However wifi didn't work.
There were several errors about MMC1.
Here is dmesg log.
What should I do any other thing beside copying NVRAM files?
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.14.93-v7+ (pi@raspberrypi) (gcc version 6.3.0 20170516 (Raspbian 6.3.0-18+rpi1+deb9u1)) #1 SMP Tue Jan 15 16:25:38 KST 2019
[ 0.000000] CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d
[ 0.000000] CPU: div instructions available: patching division code
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] OF: fdt: Machine model: Raspberry Pi Compute Module 3 Rev 1.0
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] cma: Reserved 8 MiB at 0x37800000
[ 0.000000] On node 0 totalpages: 229376
[ 0.000000] free_area_init_node: node 0, pgdat 80c852c0, node_mem_map b7014000
[ 0.000000] Normal zone: 2016 pages used for memmap
[ 0.000000] Normal zone: 0 pages reserved
[ 0.000000] Normal zone: 229376 pages, LIFO batch:31
[ 0.000000] percpu: Embedded 17 pages/cpu @b6fbd000 s38668 r8192 d22772 u69632
[ 0.000000] pcpu-alloc: s38668 r8192 d22772 u69632 alloc=17*4096
[ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 227360
[ 0.000000] Kernel command line: bcm2708_fb.fbwidth=1824 bcm2708_fb.fbheight=984 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:24:DA:1D vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=PARTUUID=4c556536-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles
[ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] Memory: 887452K/917504K available (7168K kernel code, 576K rwdata, 2080K rodata, 1024K init, 698K bss, 21860K reserved, 8192K cma-reserved)
[ 0.000000] Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xb8800000 - 0xff800000 (1136 MB)
lowmem : 0x80000000 - 0xb8000000 ( 896 MB)
modules : 0x7f000000 - 0x80000000 ( 16 MB)
.text : 0x80008000 - 0x80800000 (8160 kB)
.init : 0x80b00000 - 0x80c00000 (1024 kB)
.data : 0x80c00000 - 0x80c9023c ( 577 kB)
.bss : 0x80c980cc - 0x80d468e0 ( 699 kB)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[ 0.000000] ftrace: allocating 25205 entries in 74 pages
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[ 0.000000] arch_timer: cp15 timer(s) running at 19.20MHz (phys).
[ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
[ 0.000007] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns
[ 0.000018] Switching to timer-based delay loop, resolution 52ns
[ 0.000265] Console: colour dummy device 80x30
[ 0.000283] console [tty1] enabled
[ 0.000305] Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=192000)
[ 0.000320] pid_max: default: 32768 minimum: 301
[ 0.000621] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.000636] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.001570] Disabling memory control group subsystem
[ 0.001643] CPU: Testing write buffer coherency: ok
[ 0.002042] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[ 0.002440] Setting up static identity map for 0x100000 - 0x10003c
[ 0.002561] Hierarchical SRCU implementation.
[ 0.003227] smp: Bringing up secondary CPUs ...
[ 0.003946] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[ 0.004727] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
[ 0.005492] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
[ 0.005594] smp: Brought up 1 node, 4 CPUs
[ 0.005604] SMP: Total of 4 processors activated (153.60 BogoMIPS).
[ 0.005609] CPU: All CPU(s) started in HYP mode.
[ 0.005613] CPU: Virtualization extensions available.
[ 0.006525] devtmpfs: initialized
[ 0.016264] random: get_random_u32 called from bucket_table_alloc+0x100/0x254 with crng_init=0
[ 0.017030] VFP support v0.3: implementor 41 architecture 3 part 40 variant 3 rev 4
[ 0.017247] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.017263] futex hash table entries: 1024 (order: 4, 65536 bytes)
[ 0.017835] pinctrl core: initialized pinctrl subsystem
[ 0.018570] NET: Registered protocol family 16
[ 0.021275] DMA: preallocated 1024 KiB pool for atomic coherent allocations
[ 0.026106] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[ 0.026113] hw-breakpoint: maximum watchpoint size is 8 bytes.
[ 0.026307] Serial: AMBA PL011 UART driver
[ 0.027925] bcm2835-mbox 3f00b880.mailbox: mailbox enabled
[ 0.059541] bcm2835-dma 3f007000.dma: DMA legacy API manager at b8813000, dmachans=0x1
[ 0.061044] SCSI subsystem initialized
[ 0.061267] usbcore: registered new interface driver usbfs
[ 0.061318] usbcore: registered new interface driver hub
[ 0.061401] usbcore: registered new device driver usb
[ 0.070087] raspberrypi-firmware soc:firmware: Attached to firmware from 2018-11-04 16:35
[ 0.071512] clocksource: Switched to clocksource arch_sys_counter
[ 0.147063] VFS: Disk quotas dquot_6.6.0
[ 0.147148] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 0.147328] FS-Cache: Loaded
[ 0.147526] CacheFiles: Loaded
[ 0.156252] NET: Registered protocol family 2
[ 0.156963] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.157072] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[ 0.157257] TCP: Hash tables configured (established 8192 bind 8192)
[ 0.157387] UDP hash table entries: 512 (order: 2, 16384 bytes)
[ 0.157431] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[ 0.157650] NET: Registered protocol family 1
[ 0.158094] RPC: Registered named UNIX socket transport module.
[ 0.158100] RPC: Registered udp transport module.
[ 0.158105] RPC: Registered tcp transport module.
[ 0.158110] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.159716] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 7 counters available
[ 0.162407] workingset: timestamp_bits=14 max_order=18 bucket_order=4
[ 0.170302] FS-Cache: Netfs 'nfs' registered for caching
[ 0.170900] NFS: Registering the id_resolver key type
[ 0.170926] Key type id_resolver registered
[ 0.170931] Key type id_legacy registered
[ 0.170946] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[ 0.172903] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
[ 0.173031] io scheduler noop registered
[ 0.173038] io scheduler deadline registered (default)
[ 0.173209] io scheduler cfq registered
[ 0.173215] io scheduler mq-deadline registered
[ 0.173221] io scheduler kyber registered
[ 0.175893] BCM2708FB: allocated DMA memory f7910000
[ 0.175918] BCM2708FB: allocated DMA channel 0 @ b8813000
[ 0.221460] Console: switching to colour frame buffer device 228x61
[ 0.247329] bcm2835-rng 3f104000.rng: hwrng registered
[ 0.247466] vc-mem: phys_addr:0x00000000 mem_base=0x3ec00000 mem_size:0x40000000(1024 MiB)
[ 0.247908] vc-sm: Videocore shared memory driver
[ 0.248181] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000
[ 0.257724] brd: module loaded
[ 0.266576] loop: module loaded
[ 0.266588] Loading iSCSI transport class v2.0-870.
[ 0.267274] libphy: Fixed MDIO Bus: probed
[ 0.267377] usbcore: registered new interface driver lan78xx
[ 0.267428] usbcore: registered new interface driver smsc95xx
[ 0.267444] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
[ 0.295352] dwc_otg 3f980000.usb: base=0xf0980000
[ 0.495575] Core Release: 2.80a
[ 0.495585] Setting default values for core params
[ 0.495616] Finished setting default values for core params
[ 0.695880] Using Buffer DMA mode
[ 0.695886] Periodic Transfer Interrupt Enhancement - disabled
[ 0.695890] Multiprocessor Interrupt Enhancement - disabled
[ 0.695896] OTG VER PARAM: 0, OTG VER FLAG: 0
[ 0.695907] Dedicated Tx FIFOs mode
[ 0.696279] WARN::dwc_otg_hcd_init:1046: FIQ DMA bounce buffers: virt = 0xb7904000 dma = 0xf7904000 len=9024
[ 0.696303] FIQ FSM acceleration enabled for :
Non-periodic Split Transactions
Periodic Split Transactions
High-Speed Isochronous Endpoints
Interrupt/Control Split Transaction hack enabled
[ 0.696310] dwc_otg: Microframe scheduler enabled
[ 0.696362] WARN::hcd_init_fiq:459: FIQ on core 1 at 0x805ef5f0
[ 0.696373] WARN::hcd_init_fiq:460: FIQ ASM at 0x805ef948 length 36
[ 0.696385] WARN::hcd_init_fiq:486: MPHI regs_base at 0xf0006000
[ 0.696437] dwc_otg 3f980000.usb: DWC OTG Controller
[ 0.696466] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1
[ 0.696497] dwc_otg 3f980000.usb: irq 62, io mem 0x00000000
[ 0.696542] Init: Port Power? op_state=1
[ 0.696546] Init: Power Port (0)
[ 0.696743] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 0.696754] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 0.696762] usb usb1: Product: DWC OTG Controller
[ 0.696770] usb usb1: Manufacturer: Linux 4.14.93-v7+ dwc_otg_hcd
[ 0.696778] usb usb1: SerialNumber: 3f980000.usb
[ 0.697355] hub 1-0:1.0: USB hub found
[ 0.697398] hub 1-0:1.0: 1 port detected
[ 0.697913] dwc_otg: FIQ enabled
[ 0.697918] dwc_otg: NAK holdoff enabled
[ 0.697923] dwc_otg: FIQ split-transaction FSM enabled
[ 0.697932] Module dwc_common_port init
[ 0.698179] usbcore: registered new interface driver usb-storage
[ 0.698340] mousedev: PS/2 mouse device common for all mice
[ 0.698416] IR NEC protocol handler initialized
[ 0.698421] IR RC5(x/sz) protocol handler initialized
[ 0.698427] IR RC6 protocol handler initialized
[ 0.698432] IR JVC protocol handler initialized
[ 0.698437] IR Sony protocol handler initialized
[ 0.698442] IR SANYO protocol handler initialized
[ 0.698447] IR Sharp protocol handler initialized
[ 0.698451] IR MCE Keyboard/mouse protocol handler initialized
[ 0.698457] IR XMP protocol handler initialized
[ 0.699159] bcm2835-wdt 3f100000.watchdog: Broadcom BCM2835 watchdog timer
[ 0.699432] bcm2835-cpufreq: min=600000 max=1200000
[ 0.699800] sdhci: Secure Digital Host Controller Interface driver
[ 0.699805] sdhci: Copyright(c) Pierre Ossman
[ 0.700151] mmc-bcm2835 3f300000.mmc: could not get clk, deferring probe
[ 0.700463] sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe
[ 0.700561] sdhci-pltfm: SDHCI platform and OF driver helper
[ 0.700992] ledtrig-cpu: registered to indicate activity on CPUs
[ 0.701071] hidraw: raw HID events driver (C) Jiri Kosina
[ 0.701193] usbcore: registered new interface driver usbhid
[ 0.701198] usbhid: USB HID core driver
[ 0.701866] vchiq: vchiq_init_state: slot_zero = b7980000, is_master = 0
[ 0.703412] [vc_sm_connected_init]: start
[ 0.713065] [vc_sm_connected_init]: end - returning 0
[ 0.713605] Initializing XFRM netlink socket
[ 0.713626] NET: Registered protocol family 17
[ 0.713725] Key type dns_resolver registered
[ 0.714269] Registering SWP/SWPB emulation handler
[ 0.714847] registered taskstats version 1
[ 0.720636] uart-pl011 3f201000.serial: cts_event_workaround enabled
[ 0.720714] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 87, base_baud = 0) is a PL011 rev2
[ 0.720777] console [ttyAMA0] enabled
[ 0.722795] mmc-bcm2835 3f300000.mmc: mmc_debug:0 mmc_debug2:0
[ 0.722804] mmc-bcm2835 3f300000.mmc: DMA channel allocated
[ 0.782121] sdhost: log_buf @ b7907000 (f7907000)
[ 0.816705] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
[ 0.818269] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[ 0.819834] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[ 0.822634] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
[ 0.824182] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[ 0.826653] mmc1: queuing unknown CIS tuple 0x80 (6 bytes)
[ 0.861531] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)
[ 0.862562] of_cfs_init
[ 0.862656] of_cfs_init: OK
[ 0.863191] Waiting for root device PARTUUID=4c556536-02...
[ 0.899614] random: fast init done
[ 0.911680] Indeed it is in host mode hprt0 = 00021501
[ 0.993878] mmc0: new high speed MMC card at address 0001
[ 0.994401] mmcblk0: mmc0:0001 M52516 14.3 GiB
[ 0.994649] mmcblk0boot0: mmc0:0001 M52516 partition 1 4.00 MiB
[ 0.994903] mmcblk0boot1: mmc0:0001 M52516 partition 2 4.00 MiB
[ 0.995136] mmcblk0rpmb: mmc0:0001 M52516 partition 3 4.00 MiB
[ 0.996618] mmcblk0: p1 p2
[ 1.008238] mmc1: error -110 whilst initialising SDIO card
[ 1.032026] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[ 1.032080] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[ 1.032657] devtmpfs: mounted
[ 1.036121] Freeing unused kernel memory: 1024K
[ 1.090777] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
[ 1.092820] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[ 1.094869] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[ 1.098528] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
[ 1.121577] usb 1-1: new high-speed USB device number 2 using dwc_otg
[ 1.121714] Indeed it is in host mode hprt0 = 00001101
[ 1.273399] mmc1: error -110 whilst initialising SDIO card
[ 1.361870] usb 1-1: New USB device found, idVendor=0424, idProduct=3803
[ 1.361887] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1.362555] hub 1-1:1.0: USB hub found
[ 1.362631] hub 1-1:1.0: 3 ports detected
[ 1.518649] systemd[1]: System time before build time, advancing clock.
[ 1.545696] mmc1: error -110 whilst initialising SDIO card
[ 1.638123] NET: Registered protocol family 10
[ 1.639200] Segment Routing with IPv6
[ 1.648589] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 1.665500] random: systemd: uninitialized urandom read (16 bytes read)
[ 1.670915] systemd[1]: systemd 232 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN)
[ 1.671481] systemd[1]: Detected architecture arm.
[ 1.672443] systemd[1]: Set hostname to <raspberrypi>.
[ 1.681574] usb 1-1.2: new full-speed USB device number 3 using dwc_otg
[ 1.711442] random: systemd: uninitialized urandom read (16 bytes read)
[ 1.739483] uart-pl011 3f201000.serial: no DMA platform data
[ 1.745600] random: systemd-gpt-aut: uninitialized urandom read (16 bytes read)
[ 1.814962] usb 1-1.2: New USB device found, idVendor=20b1, idProduct=0011
[ 1.814978] usb 1-1.2: New USB device strings: Mfr=1, Product=3, SerialNumber=0
[ 1.814988] usb 1-1.2: Product: XMOS VocalFusion Spk (UAC1.0)
[ 1.814996] usb 1-1.2: Manufacturer: XMOS
[ 1.815473] usb 1-1.2: rejected 1 configuration due to insufficient available bus power
[ 1.815484] usb 1-1.2: no configuration chosen from 1 choice
[ 1.815492] usb 1-1.2: No support over 100mA
[ 1.911575] usb 1-1.3: new high-speed USB device number 4 using dwc_otg
[ 1.945780] mmc1: error -110 whilst initialising SDIO card
[ 2.042075] usb 1-1.3: New USB device found, idVendor=1a40, idProduct=0101
[ 2.042090] usb 1-1.3: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 2.042099] usb 1-1.3: Product: USB 2.0 Hub
[ 2.042775] hub 1-1.3:1.0: USB hub found
[ 2.042869] hub 1-1.3:1.0: 4 ports detected
[ 2.177883] systemd[1]: Listening on Journal Socket.
[ 2.179012] systemd[1]: Created slice System Slice.
[ 2.182278] systemd[1]: Starting Create list of required static device nodes for the current kernel...
[ 2.186106] systemd[1]: Mounting Debug File System...
[ 2.187559] systemd[1]: Created slice system-getty.slice.
[ 2.188658] systemd[1]: Created slice system-serial\x2dgetty.slice.
[ 2.196672] systemd[1]: Starting Load Kernel Modules...
[ 2.245060] i2c /dev entries driver
[ 2.361671] usb 1-1.3.3: new high-speed USB device number 5 using dwc_otg
[ 2.509222] usb 1-1.3.3: New USB device found, idVendor=148f, idProduct=5370
[ 2.509241] usb 1-1.3.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2.509250] usb 1-1.3.3: Product: 802.11 n WLAN
[ 2.509258] usb 1-1.3.3: Manufacturer: Ralink
[ 2.509266] usb 1-1.3.3: SerialNumber: 1.0
[ 2.611676] usb 1-1.3.4: new full-speed USB device number 6 using dwc_otg
[ 2.746829] usb 1-1.3.4: New USB device found, idVendor=046d, idProduct=c52b
[ 2.746845] usb 1-1.3.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2.746854] usb 1-1.3.4: Product: USB Receiver
[ 2.746863] usb 1-1.3.4: Manufacturer: Logitech
[ 2.854067] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[ 2.937041] systemd-journald[103]: Received request to flush runtime journal from PID 1
[ 2.948353] logitech-djreceiver 0003:046D:C52B.0003: hiddev96,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-3f980000.usb-1.3.4/input2
[ 3.221444] input: Logitech K800 as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3.4/1-1.3.4:1.2/0003:046D:C52B.0003/0003:046D:2010.0004/input/input0
[ 3.224862] logitech-hidpp-device 0003:046D:2010.0004: input,hidraw1: USB HID v1.11 Keyboard [Logitech K800] on usb-3f980000.usb-1.3.4:1
[ 3.233748] input: Logitech K370s/K375s as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3.4/1-1.3.4:1.2/0003:046D:C52B.0003/0003:046D:4061.0005/input/input1
[ 3.234980] logitech-hidpp-device 0003:046D:4061.0005: input,hidraw2: USB HID v1.11 Keyboard [Logitech K370s/K375s] on usb-3f980000.usb-1.3.4:2
[ 3.245935] input: Logitech MX Master as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3.4/1-1.3.4:1.2/0003:046D:C52B.0003/0003:046D:4041.0006/input/input2
[ 3.247104] logitech-hidpp-device 0003:046D:4041.0006: input,hidraw3: USB HID v1.11 Keyboard [Logitech MX Master] on usb-3f980000.usb-1.3.4:3
[ 3.273321] usb 1-1.3.3: reset high-speed USB device number 5 using dwc_otg
[ 3.412548] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 5390, rev 0502 detected
[ 3.442246] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 5370 detected
[ 3.471052] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[ 3.472928] usbcore: registered new interface driver rt2800usb
[ 3.688334] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned.
[ 3.711215] bcm2835_alsa bcm2835_alsa: card created with 8 channels
[ 5.242200] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2870.bin'
[ 5.243872] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.36
[ 5.440066] random: crng init done
[ 5.440086] random: 7 urandom warning(s) missed due to ratelimiting
[ 5.588619] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 6.795893] Adding 102396k swap on /var/swap. Priority:-2 extents:1 across:102396k SSFS
[ 6.833911] wlan0: authenticate with b0:6e:bf:dd:89:38
[ 6.879695] wlan0: send auth to b0:6e:bf:dd:89:38 (try 1/3)
[ 6.882778] wlan0: authenticated
[ 6.891644] wlan0: associate with b0:6e:bf:dd:89:38 (try 1/3)
[ 6.895376] wlan0: RX AssocResp from b0:6e:bf:dd:89:38 (capab=0x411 status=0 aid=11)
[ 6.902655] wlan0: associated
[ 7.138419] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Show Less