"Error battery voltage" on VOXL2

[tanguy sagere]

Hi! I was setting up internet access to the VOXL2 (rather than sharing my laptop internet with it), working in root after ssh'ing into it from my laptop via my laptop Ethernet-> USB-A to JST adapter -> debug board USB2 Host-> VOXL2 when I suddenly couldnt connect anymore to the VOXL2 from my network manager (and so ssh wouldnt work).

As that seemed weird, I rebooted the chip into normal mode and screened into it using the debug console (laptop connected to debug board with micro USB) but nothing would appear on screen. So I tried the same thing in fastboot mode; and the following happened (and keeps happening after changing cables, power socket, etc...) :

This shortly pops up when screening the chip after fastbooting it

Handling Cmd: getvar:version Error battery voltage: 0 Requireed voltage: 3600, can flash: 0

Then this loops continuously :

LmhIsenseInit Post GPU  TIME 2ms 
Entering in func1 of NPU  TIME 2ms NPU IDDQ 41 LmhIsenseSubSysEntry Post SubSysEntryCb  TIME 0ms 
LmhIsenseSubSysEntry Post 
LmhIsenseSubSysInit  TIME 0ms 
LmhIsenseInitSubSys Post SubSysEntry  TIME 0ms 
LmhIsenseInitSubSys Post SubSysTrim  TIME 0ms 
LmhIsenseInitSubSys Post SubSysExit  TIME 0ms 
LmhIsenseInit Post NPU  TIME 2ms 
isense  TIME 5ms ISENSE TOTAL TIME 5ms 
Disp init wait [ 1670] 
 ----------------------------- 
Platform Init  [ 1687] BDS 
UEFI Ver   : 5.0.220324.BOOT.XF.3.2-00354-SM8250-
1 
Platform           : QRD 
Chip Name          : QRB5165 
Chip Ver           : 2.1 
Chip Serial Number : 0x5A93EBEB 
Silver cluster Core 0 Freq: 1516 MHz 
----------------------------- 
UEFI Total : 524 ms 
POST Time      [ 1717] OS Loader 
Loader Build Info: Feb 18 2022 17:53:29 
VB: Non-secure device: Security State: (0xF7F) 
VB: RWDeviceState: Succeed using devinfo! 
KeyPress:2, BootReason:0 
Fastboot=1, Recovery:0 
GetVmData: making ScmCall to get HypInfo 
GetVmData: No Vm data present! Status = (0x3) 
VM Hyp calls not present 
Launching fastboot 
Fastboot Build Info: Feb 18 2022 17:53:28 
usb_shared_hs_phy_init: hs phy cfg size: 12 
usb_shared_ss_phy_init: ss phy cfg size: 143 
ssusb_phy_init_success_lane_A: 0 
Fastboot: Initializing... 
VB: Non-secure device: Security State: (0xF7F) 
Fastboot: Processing commands 
Failed to get the graphics output protocol. 
Failed to get the graphics output protocol. 
Failed to get width or height Failed to get the graphics output protocol. 
Failed to get the graphics output protocol. 
Unable to show fastboot menu on screen: Out of Resources 
Dev_Common_Speed: Bus Speed: Super 
Dev_Common_Speed: Bus Speed: Super Handling 
Cmd: getvar:product Handling Cmd: 
getvar:version

Upon ssh'ing to it with the debug board I get the following message :

ssh: connect to host xx.xx.x.xxx port 22: Network is unreachable

It should be noted that the chip still pops up in "fastboot devices" as well as in "dmesg -w", so its still alive. Whats going on and how can I fix this?

[tanguy sagere]

For the sake of completeness, I flashed the modalai platform voxl2_platform_1.3.1-0.8.tar.gz on the device with the debug board disconnected (direct connection with USB-C). The flashing process completed successfully with install.sh but ;

• The device appears in dmesg as "qcom Kona" which is correct.
• sudo adb shell does not work.
• sudo adb devices lists no devices.
• I still see no output from the debug board serial debug monitor.
• ethtool still says "no link detected" when connecting Ethernet to the debug board.

I should also mention that I have been working with an ESD-bracelet and at no point was the VOXL2 subjected to contact with a conductive surface other than my hand, nor dropped or otherwise physically threatened.

[modaltb]

Hi @tanguy-sagere ,

We've seen this error message and have a fix in our next release, when it gets into this state we've typically been able to get out of it by reflashing following this process (which I'm sure you've done, but to be sure we want to remove USB cable when forcing into fastboot). Can you try again with the process in this video?

https://docs.modalai.com/voxl2-system-image/#force-voxl-2-into-fastboot

Thanks!

[tanguy sagere]

I followed the video you recommended, forcing into fastboot with USB-C disconnected at first and then flashing system image. Flashing goes well :

===================================================== 
|     Done installing voxl-suite for QRB5165        |
...
[INFO] Done installing voxl-suite
----Installation Completed----

But then when I restart the VOXL2 in normal boot and screen into it using the debug board serial debug monitor to observe the booting process; this is all that appears :

Decompressing kernel image done: 3156 ms
Dtbo hdr magic mismatch 0, with D7B7AB1E
Best match DTB tags 455/0000000B/0x00000003/20001/3001E/20020/20027/20021/(offset)0x9A781B37/(size)0x0008B3AB
Using pmic info 0x3001E/0x20020/0x20027/0x20021 for device 0x3001E/0x20020/0x20027/0x20021
Memory Base Address: 0x80000000
Cmdline: noinitrd  earlycon=msm_geni_serial,0xa90000 androidboot.hardware=qcom androidboot.console=ttyMSM0 androidboot.memcg=1 lpm_levels.sleep_disabled=1 video=vfb:640x400,bpp=32,memsize=3072000 msm_rtb.filter=0x237 service_locator.enable=1 androidboot.u
RAM Partitions
Add Base: 0x0000000080000000 Available Length: 0x000000003B800000 
Add Base: 0x0000000180000000 Available Length: 0x0000000100000000 
Add Base: 0x00000000C0000000 Available Length: 0x00000000C0000000 
ERROR: Could not get splash memory region node
kaslr-Seed is added to chosen node

Shutting Down UEFI Boot Services: 3227 ms
Start EBS        [ 3228] 
BDS: LogFs sync skipped, Unsupported
App Log Flush : 34 ms
Exit EBS        [ 3280] UEFI End

Is there a hardware defect with the VOXL2 or with the Debug board? Was this also part of the bug you encountered?

Thanks for your time and help

[tanguy sagere]

@tanguy-sagere said in "Error battery voltage" on VOXL2:

For the sake of completeness, I flashed the modalai platform voxl2_platform_1.3.1-0.8.tar.gz on the device with the debug board disconnected (direct connection with USB-C). The flashing process completed successfully with install.sh but ;

The device appears in dmesg as "qcom Kona" which is correct.
sudo adb shell does not work.
sudo adb devices lists no devices.
I still see no output from the debug board serial debug monitor.
ethtool still says "no link detected" when connecting Ethernet to the debug board.

Quick recap :

• The device appears in dmesg as "qcom Kona" which is correct.
• sudo adb shell works and sudo adb devices lists the VOXL2 since using a new USB-C cable.
• In normal boot : I get a "ERROR: Could not get splash memory region node" error from the debug board serial debug monitor.
• In forced fastboot : I get a "Unable to show fastboot menu on screen: Out of Resources" error from the debug board serial debug monitor.
• ethtool still says "no link detected" when connecting Ethernet to the debug board.

Im starting to think that the debug board failed mechanically for whatever reason. Is there a software fix for this or should I contact support personally to have the debug board replaced as per warranty?

For information : I am using the "5G Model Carrier Board, USB HUB, I/O Breakout for VOXL 2 Carrier Board"

[modaltb]

Hi @tanguy-sagere ,

OK the last part of that console output above "looks OK" for the non-debug kernel, I've captured my system here (note I'm rebooting over adb for connivence to show when thing are happening).

Is this roughly what you see?

https://www.youtube.com/watch?v=5axL8w-Zb6c

The standard system image doesn't provide you a login over the debug console. You need to flash a debug kernel if you want to see the full bootup output (like dmesg but over the serial port) and you also can get a login over that same terminal, but the boot up time goes from ~10 seconds to like ~90 seconds, hence why we don't ship with a debug kernel!

[tanguy sagere]

Yep that's what I was seeing! Ok I'm using a custom OS here with a debug kernel already included so flashing that again solved the issue. I'll make sure to have everything disconnected when I reboot it from now on. Is there any other way to prevent this from happening in the future? I mean we`d like to have the VOXL2 on a drone with all cables attached and be able to just toggle the power supply without having to dettach and reattach everything everytime. Thanks!

[modaltb]

Hi @tanguy-sagere ,

Generally you don't need to disconnect anything to boot successfully into fastboot using the button, but in the case where this battery warning shows up, and until we release our System Image 1.4.x which has a bootloader fix, the work around is to remove the USBC cable if this bootup issue displays.

[wilkinsaf]

@modaltb This worked for me. Removing the USBC cable, booting up, and then plugging in.