# Bots Unlimited Wifi Crash

Source: https://forum.modalai.com/topic/5362/bots-unlimited-wifi-crash
Category: General Questions (https://forum.modalai.com/category/2/general-questions)
Posted: 2026-08-03 19:19:17 UTC by John Keller
Replies: 8 · Views: 463

## John Keller · 2026-08-03 19:19:17 UTC

We are using the Bots Unlimited wifi board attached directly to our voxl2 board. It seems like the wifi driver will sometimes randomly crash with this message being repeated in dmesg: "Block woal_cfg80211_scan in abnormal driver state". When this happens the drone can no longer connect to wifi. We couldn't find any way in software to reboot the wifi board. To get it working again we have to power cycle the drone. Is there a fix for this?

## Reply by John Keller · 2026-08-04 18:39:21 UTC

Here is the relevant part from dmesg 

```
[ 2130.644295] FW trigger fw dump
[ 2130.644332] =====FW trigger dump====
[ 2130.644347] ==== Start Receive FW dump event  ====
[ 2130.645036] Create directory /data/dump_2130 successfully
[ 2130.645058] Firmware Dump directory name is /data/dump_2130
[ 2130.645078] === START DRIVER INFO DUMP===
[ 2130.645180] DRV dump data in /data/dump_2130/file_drv_info
[ 2130.653905] Drv info total bytes = 205002 (0x320ca)
[ 2130.653933] === DRIVER INFO DUMP END===
[ 2131.373918] ==== FW DUMP END: 1381912 bytes ====
[ 2131.374101] Start to process hanging
[ 2131.374170] Cancel all pending cmd and txrx queue
[ 2131.374381] Block woal_cfg80211_del_key in abnormal driver state
[ 2131.374408] Block woal_cfg80211_del_key in abnormal driver state
[ 2131.374430] Block woal_cfg80211_del_key in abnormal driver state
[ 2131.374451] Block woal_cfg80211_del_key in abnormal driver state
[ 2131.374472] Block woal_cfg80211_del_key in abnormal driver state
[ 2131.374493] Block woal_cfg80211_del_key in abnormal driver state
[ 2131.477115] Block woal_cfg80211_scan in abnormal driver state
[ 2132.479524] Block woal_cfg80211_scan in abnormal driver state
[ 2133.481978] Block woal_cfg80211_scan in abnormal driver state
[ 2134.484164] Block woal_cfg80211_scan in abnormal driver state
[ 2135.486210] Block woal_cfg80211_scan in abnormal driver state
[ 2136.489052] Block woal_cfg80211_scan in abnormal driver state
[ 2137.491936] Block woal_cfg80211_scan in abnormal driver state
```

## Reply by Hector Nevarez (ModalAI staff) · 2026-08-04 18:57:46 UTC

Hi John,

I can help take a look at this issue. I'll first need to try and reproduce this issue, so give me a bit here to try and do so.

Also just for my understanding can you send the output of `voxl-wifi getmode` so I can which wifi mode the device was configured in.

## Reply by John Keller · 2026-08-05 16:20:36 UTC (in reply to Hector Nevarez)

@Hector-Nevarez Hi Hector,

Here is the output of `voxl-wifi getmode`

```
WiFi is currently set up as follows:
	Mode: station
	Hardware: Concurrent STA+AP capable (AP:uap0, STA:mlan0)
	Station: Active on mlan0 - "Chiron"
	SoftAP: Disabled

```

Thank you!

## Reply by LukeNow (ModalAI staff) · 2026-08-13 21:23:00 UTC

Hi John, 

We are still looking at the issue and trying to reproduce and will get back to you if we find anything. 

If its possible could you also upload that /data/dump file to this ticket? If the size is not supported possibly uploading to google drive or similar file sharing service for us to inspect would be very helpful.

Thanks!

## Reply by John Keller · 2026-08-14 17:55:44 UTC

Thank you for looking into it. Here is a google drive link. [https://drive.google.com/drive/folders/1cRrAo7wXScs-se2wVErIZE_t8HV11EbR?usp=sharing](link url)
 containing the /data/dump. dump_958 is from a crash that just happened. The other files in there are things that claude thought might be relevant.

## Reply by LukeNow (ModalAI staff) · 2026-08-18 01:51:09 UTC

Hi John, 

Thanks for the data dumps. Could you run this wifi_capture.sh on your board and send us the data when you reproduce the crash along with the dump file again? It should be here along with a simple readme https://drive.google.com/drive/folders/14nMhkvOMeHJ6zLJYMW4scAglTfkRYY8N?usp=sharing 

Could you also briefly describe how you are connecting/what devices you are connecting? Also does this happen under any specific workloads or is it sporadic? It seems like a firmware crash so any additional information would be very useful if we end up needing to report it.

Thanks! 
- Luke

## Reply by John Keller · 2026-08-24 17:28:08 UTC

Hi Luke,

I uploaded the wifcap and corresponding dump file here https://drive.google.com/drive/folders/11nv9jt6RslnnnDXi7DgAw6W-eMBwbSsG.

The crash is sporadic in general but I was able to make it happen pretty consistently by viewing the hires_small_color image though the web gui. We have the rgb camera, forwards and downward tracking camera, and tof sensor. The only modifications we have done are removing the downward range sensor, adding some neopixel leds, and putting a larger ground plane on the gps. We have seen the crash before removing the range sensor and adding the leds. We usually run a ros2 autonomy stack and stream the hires camera via gstreamer. We see it happen randomly while doing this.

Thanks,
John

## Reply by LukeNow (ModalAI staff) · 2026-08-26 23:07:41 UTC

Hi John, 

Thank you for the information it was very helpful for analysis.
It seems as though the firmware crash happens on stream timeouts and causes the firmware to crash. 
Here is a potential workaround with the installer, I kept all the claude output in case that helps with any analysis on your end: https://drive.google.com/drive/folders/1sbwS3RZ4wgmC2raH7SnDKZz3OYSOavSg?usp=sharing    

If you could try running that and using the device normally, hopefully that stops it from crashing. We also do have routing on that expansion board for the RESET pin but for some reason the firmware does not respect it. If you keep seeing the issue that might be the next place to look, but NXP has marked this chip as EOL and won't support any fixes there, so our best hope is to workaround whatever is happening. 

Let us know how that goes and any other findings. Thanks! 
- Luke