Hello @manovella ! I was experiencing similar issues as yours.
Here’s a couple of things you can try:
-
Run axdevice --refresh and axdevice --reboot commands. You can run them with additional verbose output for easier debugging: axdevice --refresh -v
-
Turn off your host system, remove the M.2 card, reconnect it, power on your host system and try the above again
You can also try rolling back to a previous version of the Voyager SDK as a temporary fix and reinstalling it. This helped in my case, sharing in case it works for you!
Can you share your version of the Voyager SDK? A git log command might reveal this
hi @dbrenes ! thank you very much for your support; I tried your advices but I have not solved yet..
trying axdevice:
[libtriton_linux.c:1082] Device communication timed out: device did not respond within 1 seconds. (0)
WARNING: Failed to get valid board type for device metis-0:1:0 got 6
Device 0: metis-0:1:0 board_type=unknown (not responding)
trying axdevice --reboot:
[libtriton_linux.c:1082] Device communication timed out: device did not respond within 1 seconds. (0)
WARNING: Failed to get valid board type for device metis-0:1:0 got 6
WARNING: Rebooting metis-0:1:0 please wait several seconds. Some timeout messages are expected
[libtriton_linux.c:1082] Device communication timed out: device did not respond within 1 seconds. (0)
[AxeleraDevice.cpp:549] Failed to execute a cold_boot
ERROR: Failed to execute reboot
ERROR: AXR_ERROR_CONNECTION_ERROR: Failed to execute reboot
trying axdevice --refresh:
0000:01:00.0 : Device
[libtriton_linux.c:1082] Device communication timed out: device did not respond within 1 seconds. (0)
WARNING: Failed to get valid board type for device metis-0:1:0 got 6
[libtriton_linux.c:1082] Device communication timed out: device did not respond within 1 seconds. (0)
ERROR: Failed to load runtime stage0: /opt/axelera/device-1.3.3-1/omega/bin/start_axelera_runtime_stage0.bin
ERROR: AXR_ERROR_CONNECTION_ERROR: Failed to load runtime stage0: /opt/axelera/device-1.3.3-1/omega/bin/start_axelera_runtime_stage0.bin
git log tell me: Release version 1.3.3
Hi @manovella ,
- Did Metis work properly before trying to upgrade the FW?
- How did you install Voyager SDK v1.3.3?
- Which steps did you do to upgrade the FW?
- Have you tried to power cycle the Orange Pi 5 Plus? Unplug and plug back
Let’s check the following:
Check what your driver version is with:
cat /sys/class/metis/version
That should display the following driver version for Voyager SDK v1.3.3:
You can find which driver version is expected for each Voyager SDK release in https://github.com/axelera-ai-hub/voyager-sdk/blob/v1.3.3/cfg/config-ubuntu-2204-arm64.yaml :
Can you also check that your driver is loaded with:
lsmod | grep metis
Looking forward to your reply.
Best,
Victor
Hi @Victor Labian,
Is it possible that the problem is caused by a failed firmware update?
If so, is it possible to flash the firmware to fix it?
Hi @manovella
Thank you for all the information, it allowed us to understand better what can be going on. We will contact you privately as soon as possible to solve this issue.
Best,
Victor
