cancel
Showing results for 
Search instead for 
Did you mean: 

Wireless

PaJa_4811526
New Contributor II

Hi

I´m using a custom board with WIFI module 1MW. While connecting with Network switch I get sometimes random errors. I´m still able to communicate and transfer data but I´m pretty sure the messages should no occur. I´m using kernel 5.4.24 (NXP rel_imx_5.4.24_2.1.0 / Yocto-zeus 3.0). Any idea why these messages occur?

 

 

 

 

 

root@test:~# iw dev wlan0 link
Connected to FF:FF:FF:FF:FF:FF (on wlan0)
        SSID: TP-Link_0655
        freq: 2462
        RX: 13192 bytes (54 packets)
        TX: 4029 bytes (23 packets)
        signal: -45 dBm
        rx bitrate: 150.0 MBit/s
        tx bitrate: 11.0 MBit/s

        bss flags:      short-slot-time
        dtim period:    1
        beacon int:     100
root@test:~# udhcpc -i wlan0
udhcpc: started, v1.31.0
udhcpc: sending discover
udhcpc: sending select for 192.168.2.153
udhcpc: lease of 192.168.2.153 obtained, lease time 86400
/etc/udhcpc.d/50default: Adding DNS 192.168.2.1
root@test:~# brcmfmac: brcmf_sdio_isr: failed backplane access
brcmfmac: brcmf_sdio_isr: failed backplane access
brcmfmac: brcmf_sdio_isr: failed backplane access
brcmfmac: brcmf_sdio_isr: failed backplane access
brcmfmac: brcmf_sdio_isr: failed backplane access
root@test:~#

 

 

 

 

 

 

regards

0 Likes
1 Solution
Zhengbao_Zhang
Moderator
Moderator

Hello:

    I have  a check about the brcmf_sdio_isr,   I can see even the log printed we don't return the function directly ,  So I assume this is not a fatal print.    Actually , I can see a lot of sdio interface error with this print,  but they are continuous which is different with yours,   and the final results are crash with a continuous error printing,    So your board may encounter an ISR timing or status check issue .

I recommend you to do a long-run test to confirm the robust of the interface. 

View solution in original post

0 Likes
4 Replies
Zhengbao_Zhang
Moderator
Moderator

Hello:

   just confirm again , even the failed log was printed , the chip was still running well .

and would you please capture more logs with timestamp ?   I want to check if the err is a continuous list , or just once a time.   

0 Likes
PaJa_4811526
New Contributor II

Hello,

yes even the failed log was printed, the chip is still running well.

I prepare the debug messages with timestamp and send it later.

In attachment you can find the log file.

0 Likes
Zhengbao_Zhang
Moderator
Moderator

Hello:

    I have  a check about the brcmf_sdio_isr,   I can see even the log printed we don't return the function directly ,  So I assume this is not a fatal print.    Actually , I can see a lot of sdio interface error with this print,  but they are continuous which is different with yours,   and the final results are crash with a continuous error printing,    So your board may encounter an ISR timing or status check issue .

I recommend you to do a long-run test to confirm the robust of the interface. 

View solution in original post

0 Likes
PaJa_4811526
New Contributor II

Hello:

I will do a long-run test to verify the robustness of the interface.

0 Likes