Hello viraniac,
Could it be some hardware failure ? I flashed specifically the UBOOT image (VIM3L.uboot-mainline.emmc.aml.img) to my VIM3L then I booted on my SD card with OOWOW: after reinstallation of VOLUMIO, I lost access to my SD card…
You don’t need to press F button when oowow is flashed to sdcard. It should boot automatically. Could you please share how you flashed oowow to sdcard?
Not sure what VIM3L.uboot-mainline.emmc.aml.img is. Are you talking about khadas-uboot-mainline.emmc.kresq? Sadly I am getting 404 when trying to access it so can’t really try flashing the same to reproduce the issue. Assuming that flashed mainline u-boot to mmcblk0boot* partitions, you can try the following to wipe the same
- Go to volumio.local/dev in a web browser and click on enable button under ssh heading. This will allow you to ssh to the volumio instance. If you have changed your hostname, you can use that or your IP address in place of volumio.local.
- Then ssh into volumio instance. Username and password will both be volumio. Run the following commands to wipe your mmcblk0boot* partitions.
sudo /bin/bash -c "echo 0 > /sys/block/mmcblk0boot0/force_ro"
sudo dd if=/dev/zero of=/dev/mmcblk0boot0 bs=1M oflag=direct conv=sync status=progress
sudo /bin/bash -c "echo 0 > /sys/block/mmcblk0boot1/force_ro"
sudo dd if=/dev/zero of=/dev/mmcblk0boot1 bs=1M oflag=direct conv=sync status=progress
Try booting from sdcard again and it should work.
If it still doesn’t work, you can try wiping emmc to force booting from sdcard. Please note the following command will wipe volumio off your device, and your device will only boot from sdcard from then on until you flash an OS again.
sudo dd if=/dev/zero of=/dev/mmcblk0 bs=1M count=100 oflag=direct conv=sync status=progress
Hello viraniac,
As you said, there is normally no need to press F button when oowow is flashed on the SD. From my side I flash oowow using balena etcher (I download the image https://dl.khadas.com/firmware/vim3l/oowow/versions/vim3l/vim3l-oowow-241112.000-sd.img.gz).
I followed your advice with volumio and I could ssh to volumio instance. please find the errors message I got:
bash-5.0# sudo /bin/bash -c “echo 0 > /sys/block/mmcblk0boot0/force_ro”
bash-5.0# sudo dd if=/dev/zero of=/dev/mmcblk0boot0 bs=1M oflag=direct conv=sync status=progress
dd: error writing ‘/dev/mmcblk0boot0’: No space left on device
5+0 records in
4+0 records out
4194304 bytes (4.2 MB, 4.0 MiB) copied, 0.0742047 s, 56.5 MB/s
bash-5.0# sudo /bin/bash -c “echo 0 > /sys/block/mmcblk0boot1/force_ro”
bash-5.0# sudo dd if=/dev/zero of=/dev/mmcblk0boot1 bs=1M oflag=direct conv=sync status=progress
dd: error writing ‘/dev/mmcblk0boot1’: No space left on device
5+0 records in
4+0 records out
4194304 bytes (4.2 MB, 4.0 MiB) copied, 0.0813718 s, 51.5 MB/s
My SD card capacity is 32 GB
bash-5.0# df -a
Filesystem Size Used Avail Use% Mounted on
sysfs 0 0 0 - /sys
proc 0 0 0 - /proc
udev 1.1G 0 1.1G 0% /dev
devpts 0 0 0 - /dev/pts
tmpfs 206M 9.8M 196M 5% /run
/dev/mmcblk0p2 3.5G 704M 2.6G 22% /imgpart
/dev/loop0 614M 614M 0 100% /static
overlay 12G 104M 11G 1% /
securityfs 0 0 0 - /sys/kernel/security
selinuxfs 0 0 0 - /sys/fs/selinux
tmpfs 1.1G 19M 1.1G 2% /dev/shm
tmpfs 5.3M 4.1k 5.3M 1% /run/lock
tmpfs 1.1G 0 1.1G 0% /sys/fs/cgroup
cgroup2 0 0 0 - /sys/fs/cgroup/unified
cgroup 0 0 0 - /sys/fs/cgroup/systemd
pstore 0 0 0 - /sys/fs/pstore
bpf 0 0 0 - /sys/fs/bpf
cgroup 0 0 0 - /sys/fs/cgroup/devices
cgroup 0 0 0 - /sys/fs/cgroup/blkio
cgroup 0 0 0 - /sys/fs/cgroup/rdma
cgroup 0 0 0 - /sys/fs/cgroup/cpu,cpuacct
cgroup 0 0 0 - /sys/fs/cgroup/net_cls,net_prio
cgroup 0 0 0 - /sys/fs/cgroup/memory
cgroup 0 0 0 - /sys/fs/cgroup/pids
cgroup 0 0 0 - /sys/fs/cgroup/perf_event
cgroup 0 0 0 - /sys/fs/cgroup/freezer
cgroup 0 0 0 - /sys/fs/cgroup/cpuset
systemd-1 0 0 0 - /proc/sys/fs/binfmt_misc
debugfs 0 0 0 - /sys/kernel/debug
mqueue 0 0 0 - /dev/mqueue
tmpfs 1.1G 0 1.1G 0% /var/spool/cups
tmpfs 1.1G 4.1M 1.1G 1% /tmp
tmpfs 21M 70k 21M 1% /var/log
tmpfs 1.1G 0 1.1G 0% /var/spool/cups/tmp
sunrpc 0 0 0 - /run/rpc_pipefs
fusectl 0 0 0 - /sys/fs/fuse/connections
configfs 0 0 0 - /sys/kernel/config
/dev/mmcblk0p1 237M 91M 147M 39% /boot
/dev/sda1 31G 1.3G 30G 5% /media/oowow_dump
tmpfs 207M 0 207M 0% /run/user/1000
Thank you in advance
By the way, when I reboot, there was no change… The last command you suggest wiped the vim3l’s emmc so I recovered oowow this way… But this not a normal way to do I guess.
Best regards
This was the expected output.
Hmm… it should have booted oowow from sdcard even with volumio flashed to emmc. What exactly do you see when trying to boot oowow when emmc already has an OS? Does it boot directly to the OS in emmc or does it fail to boot with say black screen or something?
When I start the vim3l, I see a white light on the board, the screen is blanking and then I see volumio splashscreen…
But when I boot to oowow (without any OS installed), I can see some messages error: I am using a 5 V 4A PSU, and I catch one message talking about “voltage”…
So it goes straight to volumio. Thats different from what I get on my device. I wonder whats different between both of our setup.
I am afraid I do need serial console output to debug this oowow booting issue. If you can capture serial console output either by using a usb to uart adapter or by using another SBC, that will be great.
Can you try a different power supply? I am using official 30w adapter in my setup
Hello viraniac,
Please find some photos from the boot of my vim3l to oowow
I hope that may help you in the diagnosis of the issue I am facing.
Best regards
Are these screenshots captured after flashing volumio or some other OS to emmc or is it after wiping emmc?
Hello viraniac,
The photo I took are from a boot with a wiped emmc.
Best regards
Ok…Thats all normal output. There is nothing there that can help diagnose the issue.
Ok sorry I hoped that could be some error messages that could indicate some issues…
By the way, I noticed that when I use an USB stick to store some music, then Volumio works ok: I guess that the network management of the image has some problems to work out.
Thank you for you support.
Yes, will share new images with more fixes in couple of weeks. Thanks for all of the feedback and helping us make it better.