88W9098(WLAN:SDIO) loading driver with mmc error message

[Andy_Hsieh]

Hi Support,

We encountered an issue while testing 88W9098(WLAN:SDIO) on openwrt 22.03.3 with kernel 5.10.161.

While loading driver, the mmc error message appeared and there's no wireless interface at all.

Using below commands to load driver.
# insmod mlan.ko
# insmod moal.ko drv_mode=7 cal_data_cfg=none fw_name=nxp/sdiouart9098_combo_v1.bin

Andy_Hsieh_0-1680838373118.png

Could you please help guide how to load driver with correct commands and suitable parameters?

What could be the reason for showing mmc related error message?

Please advise.

[weidong_sun]

Hello @Andy_Hsieh ,

I checked your schematic of M.2 card.  you are using AW-XM458 LGA module, and VIO_SD is 3.3V. then I also found CPU uSDHC IO level is 3.3V.

1. Your design is non-standard M.2 card

According to M.2 Spec, SDIO signals should be 1.8V IO.

But for your design, the card can also work. because both sides lO level are matched (both 3.3V)

2. Just comfirming some points with you

(1) PIN 23 on M.2

it  should be pulled up high in your dts. or populate R8.

weidong_sun_0-1681806268252.png

(2) GPIO[16] & GPIO[15]

weidong_sun_1-1681806756735.png

GPIO16 & GPIO15 are used to select work clock, if GPIO16 =1 & GPIO15=1, 40MHz clock will be used.

About these pins' status, you should confirm them with AW Engineer, To confirm if floating them is OK.

(3) About your logs

According to your logs, I didn't see logs related to loading firmware.  Could you confirm if the firmware ,sdiouart9098_combo_v1.bin has been placed to /lib/firmware/nxp directory.

After checking or correcting above items, use the following commands, please!

# insmod mlan.ko

# insmod moal.ko 'cfg80211_wext=0xf max_vir_bss=1 drv_mode=7 ps_mode=2 auto_ds=2 fw_name=nxp/sduart9098_combo_v1.bin cal_data_cfg=none host_mlme=1'

[Note]

SD9098 driver, it 's firmware name is 'sduart9098_combo_v1.bin', BUT yours is sdiouart9098_combo_v1.bin , did you rename it?

Try it , please!

Regards,

weidong

[Andy_Hsieh]

Hi Weidong,

Thank you for your information.

Regarding your suggestion for PIN 23 on M.2, does it mean that we must have to pull up high?

Regarding your suggestion for GPIO[15] & [16], could you please explain more in details?

Should we modify the current design for GPIO[15] & [16]?

Actually, according to the driver source package I have, FW file name is "sdiouart9098_combo_v1.bin" as below screenshot.

Andy_Hsieh_0-1681826804829.png

BTW, may I know whether it could be a driver issue?

Do you have any other version of driver that I can test?

Thanks.

[weidong_sun]

Hello @Andy_Hsieh ,

>>Regarding your suggestion for PIN 23 on M.2, does it mean that we must have to pull up high?

Yes, it should be pulled up to HIGH. 

Do it on hardware or software , either of them is OK.

>>Regarding your suggestion for GPIO[15] & [16], could you please explain more in details?

GPIO[15] & [16]=11, means that 9098 will use 40MHz clock. default settings for these 2 pins, one is PD(pull down), the other is PU, so default is GPIO[16:15]=01.  SO you should confirm it with AW engineer , to check if GPIO16 is pulled up in 458 LGA module. if yes, it means the current level of GPIO[16:15]=11, so don't need to do anything for these 2 pins, floating them is no problem.

>>may I know whether it could be a driver issue?

No, we can't say that. Because there are no firmware messages in your logs, we are not sure if firmware has been loaded correctly. SO confirm if firmware is at the path /lib/firmware/nxp, which is very important step.

>>Do you have any other version of driver that I can test?

We are not authorized to share driver source code to customers.  if customer has NDA & access rights , she can download wifi materials from nxp website. 

additonally, your current driver should be no problem for your platform.

Try it, please!

then tell me result, please!

Regards,

weidong

[Andy_Hsieh]

Hi weidong, 

Test result is still the same with your previous suggestions. 

Please find following screenshot and attached dmesg log for reference.

Andy_Hsieh_0-1683095643574.png

Could you please advise about this wlan_sdio mmc error issue?

Is there any other information you need to have further analysis?

Thank you in advance.

[weidong_sun]

Hello @Andy_Hsieh ,

Here is my personal email address:  [email protected]

please send your full schematic of platform & full schematic of wifi card to me!

the current issues you encounterred is a typical error on MMC communications. so let me see your hardware design again. 

Thanks!

Regards,

weidong

[Andy_Hsieh]

Hi weidong,

Currently, the driver seems to be loaded successfully.

But here comes the other issue while testing station mode.

We tested on openwrt and refered to https://github.com/Ahrotahn/openwrt-nxp-pcie9098/tree/master.

Andy_Hsieh_0-1683281597172.png

ifconfig:

Andy_Hsieh_1-1683281605613.png

When scanning on the page, it is possible to see a prompt indicating the detection of 6 access points (APs), but it is not possible to obtain detailed information. Additionally, while continuing the scan, an error message "Block woal_cfg80211_scan in abnormal driver state" may appear, and the completion of the scan will not be displayed.

Andy_Hsieh_2-1683281643973.jpeg

Configuration:

Andy_Hsieh_3-1683281785830.png

Do you have any idea or suggestion for such error message while scanning?

If you need any other information, please feel free to let me know.

Thank you in advance.

[weidong_sun]

Hello @Andy_Hsieh ,

For Radio 0--WiFi 6:  configure it to be 5g .   default interface: mlan0/uap0/wfd0

For Radio 1--WiFi 5:   configure it to be 2.4.   default interface : mmlan0/muap0/mwfd0

Probably your interfaces are different from above.

Try it, please!

Regards,

weidong

[Andy_Hsieh]

Hi weidong,

We've steup both 2.4g and 5g in /etc/config/wireless but still the same result.

Do you need any other information or do you have any idea?

Appreciate.

[weidong_sun]

Hello @Andy_Hsieh ,

I added you to my microsoft teams.

if need, we can have a call discussing the issue you encountered.

Additionally, for you question, don't forget your hardware design is VIO_SD 3.3V, which means your wifi will only work at SDIO2.0 mode and max speed is 50M.  you should add no-1-8-v to device tree.

Regards,

weidong

[Andy_Hsieh]

Hi Olivier,

1. host : Microchip sama5d35
2. AZW-XM458
3. 88W9098 is LGA type

[ocourson]

Dear @Andy_Hsieh 

Could you please:

1/ confirm you are using AW-XM458MA-SUR (and not AW-XM458MA-PUR) ?

2/ confirm the host OS (openWRT) and OS version

3/ explain how you connect the AW-XM458MA to your host ? (picture might help)

4/ provide wifi driver and FW version

Regards,

Olivier

[Andy_Hsieh]

Hi Olivier,

1. Actuaclly, we used AW-XM458MA LGA type and modified WLAN interface to SDIO with following instructions shared from Azurewave's datasheet.

Andy_Hsieh_0-1681204750844.png

2. OS is Openwrt 22.03.3 with kernel 5.10.161.

3. Sorry, I don't have the device now so can't provide a photo for your reference.

4. Driver package as attachment.

[ocourson]

Dear @Andy_Hsieh 

You first need to make sure that SDIO is correctly detected by the Linux kernel:

$ dmesg | grep mmc

Shoud return 'mmcX: new high speed SDIO card at address 0001' message

If you do not get that message, it is useless to load the Wifi driver.

In that case, you need to check that SDIO is correctly configured in the device tree.

Do you have SDIO correclty detected ?

Regards,

Olivier

Regards,

Olivier

[Andy_Hsieh]

Hi Olivier,

Please refer to below screenshot, it seems that SDIO is correctly detected by system.

Andy_Hsieh_0-1681260303723.png

[ocourson]

Dear @Andy_Hsieh 

Could you please check if SDIO IO level is the same on both host and AW-XM458 module side ? (basically, both should be 1.8V)

Regards,

Olivier

[Andy_Hsieh]

Hi Olivier,

For both sides, they're with 3.3V.

According to datasheet, it should be working, right?

Andy_Hsieh_0-1681288659881.png

[ocourson]

Dear @Andy_Hsieh 

Then we should add  no-1-8-v; to usdhc node in dts.

If the same error occurs, please provide the schematics so we can crosscheck your design.

Regards,

Olivier

[Andy_Hsieh]

Hi Olivier,

Regarding your response "Then we should add  no-1-8-v; to usdhc node in dts.", could you please explain more details so that I could understand your suggestion and know how to do.

Thank you in advance.

[ocourson]

Dear @Andy_Hsieh 

no-1-8-v option should be added to your Linux kernel device tree (usdhc node).

Regards,

Olivier

[Andy_Hsieh]

Hi Olivier,

Result is still the same after adding no-1-8-v to device tree. Here's our device tree configuration for your reference.

Andy_Hsieh_0-1681350131688.png

Is there any other possibility which may cause such issue?

Please advise.