Going to close this ticket out since it seems to have resolved the issue for the user
LukeNow
Posts
-
Bots Unlimited Wifi Crash -
Bots Unlimited Wifi CrashHi @john-keller ,
Glad to hear that it works

As for the other issue, its possible that this is just a transient bus error somewhere that is causing the problem. If you encounter it again it would definitely be worth taking a closer look. Feel to open another post and tag me in it and I will take a look. Thanks!
-
Bots Unlimited Wifi CrashHi @davidtorres ,
To answer some of your questions:
- The RSSI_INFO looks like a symptom of something else and is not a known issue. The firmware for the Bots Sparrow board seems to be EOL so no updates or any fixes as far as I know,
- There is not an maximum load throughput as it depends on the signal strength, but 800M is very high and would be expected to queue packets, but it still should not be hanging like you are seeing.
- Yes those versions are shipped together as a part of our SDK and are expected
- The easiest way would be to set a udev rule that sets it on boot, something like
===========
ACTION=="add", SUBSYSTEM=="net", KERNEL=="mlan0", RUN+="<path to iw> reg set <country>"
===========
My questions for you:
- can you send the full dmesg log when you reproduce this along with the files produced by
sparrow-ba-fix.sh collectfrom the earlier workaround - How often do you see this when doing your UDP test at -b 800M and do you see it when its slower than that, 200M 400M?
- Did you run into this issue without the mitigation workaround from earlier installed? Was the issue earlier in the thread something you have also seen and made you apply the workaround?
- Are you running iperf3 with the voxl as the client or the server? If you could include the full commands you used on the host and client side that would be very helpful
Thanks!
-
Bots Unlimited Wifi CrashHi John,
No worries, also apologies for the delayed response. I should have asked for the SDK version you are on since we started packaging a voxl-sparrow-utils package that has that mlanutl bin that was missing in a later SDK version, I included the deb in the installer which should hopefully install correctly.
Here is the new one to try with the README.MD with the instructions: https://drive.google.com/drive/folders/1SBCSf8_EZkkYV3GnvDhC2poD7ckjDLWq?usp=sharing , Thanks!
- Luke
-
Bots Unlimited Wifi CrashHi 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=sharingIf 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
-
Bots Unlimited Wifi CrashHi 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
-
Bots Unlimited Wifi CrashHi 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!
-
GPIO 64 GPI_64_INT_N on J10 signal@mkriesel Hello,
I have pushed some changes to enable gpio64 as an input on the meta-vox2l-bsp branch link
To do that please follow the build docs here to rebuild the kernel image and to push it onto your device here
In the build docs, after you build the docker image and run it, add following line to qrb5165-common.sh top level file in the build docker
CI_META_VOXL2_BSP_BRANCH="feature/voxl2-mini-gpio64-export"
Then run the rest of the steps, sync patch and build, as normal to build the image.
Please also check if you need to build the kernel image with the -v var02 flag following the guide here - https://docs.modalai.com/m0054-versions/#m0054-1-and-m0054-2 , with the variant type being the same for the voxl2-mini m0104
Let me know if that works for you!
Thanks,
-Luke -
GPIO 64 GPI_64_INT_N on J10 signalHi @mkriesel, are you planning on using the UART functionality on the j10 connector?
-
GPIO 64 GPI_64_INT_N on J10 signalHi,
I don't believe that on the voxl2-mini anything is using that gpio so it might be possible to export. Let me look into that and get back to you.
For context are you just trying to use it as a regular GPIO like you are describing?
Thanks,
-Luke