What is the cause of SDIO CMD_52 error with FMAC driver?

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
LeonH
Level 4
Level 4
Distributor - Arrow(GC)
100 sign-ins First solution authored 50 sign-ins

Hi Sir,

We try to use Azurewave CYW43455 module in Sigmastar platform with FMAC driver.

But it always show error message as below while we run ping or hostapd function. 

  1. cfg80211: failed to load regulatory.db  ==> Already put the clm_blob file, it still happened.
  2. [sdmmc_1] Err: #Cmd_52 (0x92003E01)=>(E: 0x0008)(S: 0x00001002)__(L:1065)

Do you know what causes these error to happen?

FMAC: v5.10.9-2022_0321

Platform: Sigmastar

========================================================================

Loading modules backported from Linux version v5.10.9-2022_0321-0-ga0971bc0b123
Backport generated by backports.git v5.10.42-1-0-gbee5c545
cfg80211: Loading compiled-in X.509 certificates for regulatory database
platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
cfg80211: failed to load regulatory.db
brcmfmac: brcmf_fw_alloc_request: using cypress/cyfmac43455-sdio for chip BCM4345/6
usbcore: registered new interface driver brcmfmac
brcmfmac: brcmf_fw_request_firmware: no board-specific nvram available (ret=-2), device will use cypress/cyfmac43455-sdio.txt
brcmfmac: brcmf_fw_alloc_request: using cypress/cyfmac43455-sdio for chip BCM4345/6
brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Jan 17 2022 21:19:40 version 7.45.244 (408afbc CY) FWID 01-4639b629
/ # ifconfig wlan0 up
>> [sdmmc_1] Err: #Cmd_52 (0x92003E01)=>(E: 0x0008)(S: 0x00001002)__(L:1065)
/tmp # ./wpa_supplicant/wpa_passphrase Cisco07472 87654321 > ./wpa.conf
/tmp # ./wpa_supplicant/wpa_supplicant -D nl80211 -i wlan0 -c ./wpa.conf -B
Successfully initialized wpa_sup>> [sdmmc_1] Err: #Cmd_52 (0x92003E01)=>(E: 0x0008)(S: 0x00001002)__(L:1065)
plicant
nl80211: kernel reports: Registration to specific type not supported
/tmp # >> [sdmmc_1] Err: #Cmd_52 (0x92003E01)=>(E: 0x0008)(S: 0x00001002)__(L:1065)

/tmp # >> [sdmmc_1] Err: #Cmd_52 (0x92003E01)=>(E: 0x0008)(S: 0x00001002)__(L:1065)
if/tmp # ifcon/tmp # ifconfig wlan0 192.168.1.133
/tmp # rou/tmp # route add default gw 192.168.1.1 wlan0
/tmp # ping -I wlan0 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 56 data bytes
64 bytes from 192.168.1.1: seq=0 ttl=64 time=36.429 ms
64 bytes from 192.168.1.1: seq=6 ttl=64 time=56.861 ms
>> [sdmmc_1] Err: #Cmd_52 (0x92003E01)=>(E: 0x0008)(S: 0x00001002)__(L:1065)
64 bytes from 192.168.1.1: seq=19 ttl=64 time=19.641 ms
>> [sdmmc_1] Err: #Cmd_52 (0x92003E01)=>(E: 0x0008)(S: 0x00001002)__(L:1065)
64 bytes from 192.168.1.1: seq=28 ttl=64 time=66.175 ms
>> [sdmmc_1] Err: #Cmd_52 (0x92003E01)=>(E: 0x0008)(S: 0x00001002)__(L:1065)
[sdmmc]---Hal_SDMMC_SendCmdAndWaitProcess--1057--MIEEvent = 1--Trig_MIE_INTR = 1--MIE_EVENT[00] = 0x 40- MIE_INT_EN[01] = 0x 1b---SD_STS[0D] = 0x 640--

0 Likes
1 Solution
lock attach
Attachments are accessible only for community members.
Vivek_gunapati
Moderator
Moderator
Moderator
250 replies posted 10 likes given 50 solutions authored

Hi @LeonH, Attached is a test patch for the driver, could you please try it and me know if this works. If applying the patch fails try porting it manually.  After applying the patch the driver needs to be compiled again.

Regards
Vivek.

View solution in original post

0 Likes
5 Replies
lock attach
Attachments are accessible only for community members.
Vivek_gunapati
Moderator
Moderator
Moderator
250 replies posted 10 likes given 50 solutions authored

Hi @LeonH, Attached is a test patch for the driver, could you please try it and me know if this works. If applying the patch fails try porting it manually.  After applying the patch the driver needs to be compiled again.

Regards
Vivek.

0 Likes

Hi @LeonH , Could you please let us know if the issue persists with the CMD patch attached in the previous comment. ?

0 Likes
LeonH
Level 4
Level 4
Distributor - Arrow(GC)
100 sign-ins First solution authored 50 sign-ins

Hi @Vivek_gunapati , thank you~ SDIO CMD issue have been resolved by patch.

Do you know what does this warning mean in the message after running wpa_supplicant successfully ? Is kernel version too old ?

nl80211: kernel reports: Registration to specific type not supported.

0 Likes
Vivek_gunapati
Moderator
Moderator
Moderator
250 replies posted 10 likes given 50 solutions authored

Hi @LeonH , 
I also see this warning on my test setup running  4.14.78, but it does not seem to affect the Wi-Fi operations. Maybe you could check the nl80211 wpa_supplicant code for more details of the error.  Since the original issue is solved can i close the thread?

0 Likes
LeonH
Level 4
Level 4
Distributor - Arrow(GC)
100 sign-ins First solution authored 50 sign-ins

Hi Vivek,

Yes, this issue can be closed.

Thank you.

0 Likes