Hi @shaun_wu ,
Thanks again for your time.
We wanted to clarify and update you on the issue. Initially, we suspected that swapping the antenna connections (ANT_A ↔ ANT_B) on the Murata LBEE5XV1YM module (USB8997) was causing the firmware crash during Wi-Fi initialization. Based on that assumption, we raised a query regarding possible RF calibration mismatch or gain mapping issues.
However, after further hardware and signal debugging, we now believe the root cause is not related to antenna swapping.
Current Issue (updated):
The USB8997-based Wi-Fi module (Murata Type 1YM) crashes during initialization. (We have seen this often, especially on immediate power off and on.) This happens regardless of whether antennas are swapped or connected normally.
Now, the issues I am facing are a bit tricky.
1. Sometimes, while loading the drivers for the wifi module, it crashes. Below are the error/crash logs
```
wfd_name=p2p
max_vir_bss=1
cal_data_cfg=none
drv_mode = 7
rx_work=0 cpu_num=1
WLAN FW is active
Register NXP 802.11 Adapter mlan0
Register NXP 802.11 Adapter uap0
[streamer_msg] msg_callback() msg_context->pszHost=asc_host, msg_context->pszCmd=ae_get
AE_OPTION_CURR_SHUTTER(0): dwCurrShutter(8808), dwCurrSensorGain(1000), dwCurrISPGain(1000), dwCurrWgtLuma(38)
1.000000
IR OFF Counter: 7
tx_cmd_urb_pending = 0
tx_data_urb_pending = 0
tx_data2_urb_pending = 0
rx_data_urb_pending = 6
Host:buildroot Timestamp:c2cdbb1c
Driver version = USB8997---16.197.121.p1-MX5X16505.p7.2-(FP197)
main_state = 4
ioctl_pending = 1
tx_pending = 0
wmm_tx_pending[0] = 0
wmm_tx_pending[1] = 0
wmm_tx_pending[2] = 0
wmm_tx_pending[3] = 0
rx_pending = 0
lock_count = 79
malloc_count = 8
mbufalloc_count = 7
hs_skip_count = 0
hs_force_count = 0
Media state = "Disconnected"
carrier on
tx queue 0: started
tx queue 1: started
tx queue 2: started
tx queue 3: started
mlan0: num_tx_timeout = 0
uap0: num_tx_timeout = 0
p2p%d: num_tx_timeout = 0
[streamer_msg] msg_callback() msg_context->pszHost=asc_host, msg_context->pszCmd=ae_get
AE_OPTION_CURR_SHUTTER(0): dwCurrShutter(8808), dwCurrSensorGain(1000), dwCurrISPGain(1000), dwCurrWgtLuma(39)
1.000000
IR OFF Counter: 8
[INFO] Wi-Fi AP init complete.
[streamer_msg] msg_callback() msg_context->pszHost=asc_host, msg_context->pszCmd=ae_get
AE_OPTION_CURR_SHUTTER(0): dwCurrShutter(8808), dwCurrSensorGain(1000), dwCurrISPGain(1000), dwCurrWgtLuma(38)
1.000000
IR OFF Counter: 9
fw_dump_timer fired.
Start to process hanging
IOCTL failed: c254b100 id=0x90000, sub_id=0x90001 action=2, status_code=0x80000007
11D: Error setting domain info in FW
11D: Error setting domain info in FW
get fw info failed! status=-1, error_code=0x0
woal_init_priv: get_fw_info failed
Register NXP 802.11 Adapter p2p0
wlan: version = USB8997---16.197.121.p1-MX5X16505.p7.2-(FP197)
[streamer_msg] msg_callback() msg_context->pszHost=asc_host, msg_context->pszCmd=ae_get
AE_OPTION_CURR_SHUTTER(0): dwCurrShutter(8808), dwCurrSensorGain(1000), dwCurrISPGain(1000), dwCurrWgtLuma(39)
Block woal_cfg80211_scan in abnormal driver state
uap0: Skip change virtual intf type on uap: from 3 to 2
```
2. Now we do a delay of 10 seconds for the power-on and power-off cycle, then the chances of getting this crash decrease. But by immediately powering on and off the device, the issue is observed more frequently.
Flow:
1. The board starts
2. Sleep 10 sec
3. insmod mlan.ko
4. insmod usb8997.ko mod_para=murata_wifi_fw/wifi_mod_para.conf fw_name=murata_wifi_fw/usbusb8997_combo_v4.bin
```
wifi_mod_para.conf:
USB8997 = {
cfg80211_wext=0xf
wfd_name=p2p
max_vir_bss=1
cal_data_cfg=none
drv_mode=7
}
What has already been tried:
1. auto_fw_reload=1
2. Hard reset the USB8997 on boot up, before loading the driver.
P.S. This is not reproducible every time. This is very unstable. Sometimes I get the issue, and sometimes I don't.
The thing is, I want to conclude this activity and get an RC for this type of behaviour. Your guidance on this matter will be really helpful.
Thanks for your continued support.
Kind regards,
Rikin
