Fatal SLPI error causing system restart on Voxl 2

[m1baldwin]

I've got a fresh Voxl 2 board which I powered on for the first time. The board powers on and seems to start in a good state, but some 26seconds after boot the device is crashing and reporting some slpi error with px4.

[tom]

@m1baldwin Can you tell me what release is loaded on there with voxl-version as well as the serial number on the VOXL2.
The serial number should be on a white sticker with a barcode or QR code and is in the form MXX00000XXX or similar

[m1baldwin]

Sure, I will check and send the information. Strangely, we actually ordered 3 and a second of the three is also having this issue. The third is working fine.

[viralp]

@tom Hello, I work with @m1baldwin and he has asked me to share this information with you.

Board 1 - Serial no: M22000004FP
Version: 0.9.4

Board 2- Serial no: M22000004H7
Version: 0.9.4

I hope this helps. Let us know if anything else is required.
Thanks.

[Eric Katzfey]

@viralp If you disable voxl-px4 does the error go away? (i.e. systemctl disable voxl-px4 then sync then reboot)

[tom]

@viralp Thank you, do you have any other hardware connected to the VOXL2 when this problem occurs? Or is it a bare board with just power and USB-C?

[m1baldwin]

@tom for the boards we tested, we tested one fresh out of the package with nothing else connected and this error. The other, we tried different combinations of cameras plugged in, along with nothing plugged in, and still saw this.

On the question of whether this goes away when disabling and stopping voxl-px4 service, we did try this once but still saw the issue. However, the time we tried it we did not give the “sync” command after stopping the service. But we did give the systemctl stop and saw the error happen right after. There’s only a window of about 30 seconds after boot to get in and give any command, it’s a bit tricky.

Could completely reflashing starting with the qdl tool be an option here?

@viralp for visibility

[tom]

@m1baldwin Yeah so if you're disabling voxl-px4 you'll have to do systemctl disable voxl-px4 and then power cycle the VOXL2 before shelling back in.

In that dmesg log there are some camera errors which makes me think it could be a camera issue as well.

But try the above and see if adb still crashes

[m1baldwin]

Hi @tom just an update after the weekend. Sort of surprisingly, we cannot now recreate the SLPI error on the boards. Both with and without the voxl-px4 service enabled, both boards are booting up and staying alive.

We've done a couple boot cycles with voxl-px4 enabled and things seem stable. We are putting these boards into a larger enclosure and so I'll wait till the team tests that to declare victory

Just out of curiosity, is it a Modal SDK process that was triggering that board reboot before, or something lower level?

[tom]

@m1baldwin With that platform release PX4 crashing causes ADB to crash as well, so that's one possibility. (This is fixed in future releases)

If it was a camera issue, that would be low level device tree code causing the crash