VOXL2 Sentinel no wifi after new SDK

groupo

@craigphoenix I had this issue as well. One of the devs said the connectors can come loose sometimes. Try pushing both ends tight through the heatshrink

craigphoenix

There are more problems. voxl-esc scan is showing errors like "Bus '12' is not initialized"

Essentially, this SDK upgrade seems to have broken many things. It seems like I can't downgrade, because the install script eventually hangs with the "Bus '12' is not initialized" error.

How can I fix this?

Zachary Lowell 0

@craigphoenix said in VOXL2 Sentinel no wifi after new SDK:

How can I fix this?

Reply

@craigphoenix did you ever configure the SKU or MPA? This will basically enable and reset all the sdk with the proper parameters to match the system you are running. First run voxl-configure-sku and select the options that fit your sentinel. Then run voxl-configure-mpa which will reconfigure the mpa with the right sensors. From that point do a hard reboot and please let us know the status.

As for the WLAN not being picked up on - that is almost always hardware based and something might've come loose from the connectors. If it is easier paste a photo in here of the connection and the errors you are getting.

As for the Bus 12 not initalized error does that happen when you are at the esc installation part? If so, you successfully downgraded the kernel and the SDK but the sdk did not finish unpacking so you have a half baked setup on the voxl-sdk side.

LMK if this helps.
Zach

craigphoenix

@Zachary-Lowell-0

My SKU is MRB-D0006-4-V1.2-C11-M7-T1-K1 according to my receipt. But I am unable to select options that give this exact SKU (there is no K1 or K anything). The closest I can get is MRB-D0006-4-V1-C11-T1-M7-X0.

voxl-configure-mpa gets hung up on voxl-esc setup_sentinel_v1. This is where the "Bus '12'" error happens. So, based on what you said in your last paragraph, it may be in some half-baked state that voxl-configure-mpa can't solve, since voxl-configure-mpa invokes voxl-esc setup_sentinel_v1.

Curiously, both voxl-esc-scan.py and voxl-esc-board-detect.py sometimes execute normally and sometime throw the "Bus '12'" error. But voxl-esc setup_sentinel_v1 always throws the error.

How do I leave this half-baked state? I have installed some of my own software but I can reinstall if needed. Is there a way to start anew at the factory state?

Alex Kushleyev

@craigphoenix , please save your files from the VOXL2 and try to re-install the same SDK 1.3.3.

The Bus 12 error when accessing the UART ports is coming from the DSP (where PX4 normally runs and accesses ports like I2C, SPI, UART). In order to run firmware update for the ESC from CPU, there is a UART bridge that goes through the DSP. This bridge is not working properly, potentially because your SDK update was incomplete and the old DSP libraries are used.

Alex

craigphoenix

@Zachary-Lowell-0 said in VOXL2 Sentinel no wifi after new SDK:

As for the Bus 12 not initalized error does that happen when you are at the esc installation part? If so, you successfully downgraded the kernel and the SDK but the sdk did not finish unpacking so you have a half baked setup on the voxl-sdk side.

Yes, it happens at esc installation.

The installation of 1.3.3 has now failed repeatedly. Both install.sh and voxl-configure-mpa produce the Bus 12 error. When that happens, the terminal hangs.

It is strange that voxl-esc-board-detect.py runs normally upon after boot. But if I run voxl-esc setup_sentinel_v1, I get the Bus 12 error. And after that, voxl-esc-board-detect.py gives the same error until I reboot.

craigphoenix

@Alex-Kushleyev The update to 1.3.3 using install.sh hangs during voxl-esc setup_sentinel_v1 with Bus 12 error. I have tried repeatedly. What else can I try?

craigphoenix

Thanks for the responses so far. Any help with fixing this? Our development has halted due to this issue.

Zachary Lowell 0

@craigphoenix said in VOXL2 Sentinel no wifi after new SDK:

It is strange that voxl-esc-board-detect.py runs normally upon after boot. But if I run voxl-esc setup_sentinel_v1, I get the Bus 12 error. And after that, voxl-esc-board-detect.py gives the same error until I reboot.

Reply

@craigphoenix if the SDK is hanging at the bus 12 error it most likely means there is an issue with your esc or with the px4 instance. I believe this part of the install actually occurs after the sys image is flashed so you should still be capable of adb shelling or sshing into the drone and then probing the esc via the other commands such as voxl-esc XXX - if this is the case what happens when you do this instead of leveraging the sys image install?

craigphoenix

@Zachary-Lowell-0 I am able to adb shell and do voxl-esc setup_sentinel_v1. This invariably causes the Bus 12 error.

Note that prior to attempting this upgrade, we were using SDK 1.0.0 without any issues. Should I try downgrading to that version?

craigphoenix

@Zachary-Lowell-0 Downgrading to SDK 1.0.0 using install.sh has failed again at the voxl-esc setup_sentinel_v1 with the Bus 12 error. Yet now the wifi is working again (???). How could changing back to the old SDK suddenly cause wifi to start working?

My Sentinel is obviously in a very confused state.
Screenshot 2024-10-11 at 3.40.31 PM.png Screenshot 2024-10-11 at 3.41.42 PM.png

craigphoenix

@Zachary-Lowell-0 Any ideas on the updates I posted? Thanks.

Alex Kushleyev

@craigphoenix , it looks like your ESC is fine since you can scan it with voxl-esc tools.

I would suggest the following:

upgrade to SDK 1.3.3 again and skip doing the vehicle (MPA) set up, so that the install script gets a chance to finish without updating the ESC
finish the install and reboot voxl
run voxl-configure-mpa to configure your vehicle
also check if wifi is working

I believe what is happening is that the new ESC update scripts are assuming the latest DSP firmware has been installed, but it actually does not take effect until voxl2 reboots, so hopefully this approach fixes your issue.

If postponing the ESC setup (part of voxl-configure-mpa) does not fix your issue, please let us know!

Alex

craigphoenix

@Alex-Kushleyev Thanks for your response.

I ran all of the steps in install.sh except voxl-configure-mpa for SDK 1.3.3. After that, I hard rebooted and ran voxl-configure-mpa. It did not solve the problem.

The wifi does not work.
All voxl-esc errors reported earlier persist.
Error in voxl-configure-cameras.

executing: voxl-configure-cameras 11
cat: /sys/module/voxl_platform_mod/parameters/config: No such file or directory
first try failed, executing a second time: voxl-configure-cameras 11
cat: /sys/module/voxl_platform_mod/parameters/conf

When I try to downgrade to SDK 1.0.0, the boot screen reports version 1.3.3, voxl-esc fails as before, but the wifi works (??). The downgrade does not restore its functionality to pre-upgrade state.

Alex Kushleyev

@craigphoenix , thank you for trying.

I think something is going wrong with the SDK 1.3.3 install.

@tom , what would you recommend doing in this case?

Alex

tom

@Alex-Kushleyev We did recently release SDK 1.3.5, that might be worth a try

craigphoenix

@tom SDK 1.3.5 did not work; same errors as reported in my previous post.

Can I send something back to ModalAI to be re-flashed, or have something sent to me?

tom

@craigphoenix If Alex doesn't have anything else for you to try then you're more than welcome to submit an RMA and our team will investigate:

https://www.modalai.com/pages/rma

craigphoenix

@Alex-Kushleyev Do you have any other suggestions? Thanks.

Alex Kushleyev

@craigphoenix , I think the SDK install is failing somewhere in the middle (but goes unnoticed) and the ESC update and wifi issue is a result of that. We have not see this behavior before, so it is best to send the board back for inspection.

Thanks!

Alex