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

@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?

@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.

1. The wifi does not work.
2. All voxl-esc errors reported earlier persist.
3. 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.

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

@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.

@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?

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

@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?

@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.

@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?