Meestor_X

NM. Stupid user error. Gotta uncompress the image first! xz -d Armbian_25.2.2_Rockpi-s_bookworm_current_6.12.15_minimal.img.xz then dd if=/media/images/Armbian_25.2.2_Rockpi-s_bookworm_current_6.12.15_minimal.img of=/dev/mmcblk0 bs=4M status=progress Works as expected, but as you say, you do need to make sure you have a new UUID, and change /boot/armbianEnv.txt (and maybe /etc/fstab too)?

Can I not just dd a downloaded armbian image file directly to the emmc? i.e. put the image file in a folder on the µSD card or on an external flash drive and dd it to the emmc? I tried that but it doesn't seem to work. I don't end up with a bootable emmc. -EDIT- NM. Stupid user error. I didn't decompress the image file before copying. Works fine once I do that.

The usual way to get the a headless linux box up and running is to flash a disk image to a µSD card and then insert that card into the linux box, boot, answer some questions and it's done. Can I not do the same thing with an image file that I put on the µSD card (in addition to the µSD card having a complete linux OS that the box can boot from) and copy that to the emmc? Then pull the card and boot from the emmc? Does the image file used for a µSD card differ from the image file that should be written to the emmc? e.g. I have an armbian image, say "Armbian_25.2.2_Rockpi-s_bookworm_current_6.12.15_minimal.img.xz", on my µSD card at /media/images The emmc is at /dev/mmcblk0 Can I not just go: dd if=/media/images/Armbian_25.2.2_Rockpi-s_bookworm_current_6.12.15_minimal.img.xz of=/dev/mmcblk0 bs=4M status=progress I tried this, but it did not create a bootable image on the emmc.

NM, I think I have it working. However, I don't seem to be able to log in via SSH. I'll have to check into that...

I haven't been able to find a step-by-step for enabling a USB OTG Network on the RockPi-S. Anyone have a link to the steps? I'm referring to the ability to connect a USB cable between the RockPi-S and a computer and be able to ssh or network to it. My usb port is in peripheral mode and I'm using Network Manager on Armbian Bookworm.

Would these be the correct commands? dd if=/usr/lib/linux-u-boot-current-rockpi-s/idbloader.bin of=/dev/mmcblk0 seek=64 conv=notrunc status=none dd if=/usr/lib/linux-u-boot-current-rockpi-s/uboot.img of=/dev/mmcblk0 seek=16384 conv=notrunc status=none dd if=/usr/lib/linux-u-boot-current-rockpi-s/trust.bin of=/dev/mmcblk0 seek=24576 conv=notrunc status=none Are the "seek" numbers always the same or do they need to be calculated?

Thank you for your reply. Do you know what the command is for installing the bootloader? I want to automate the process and armbian-install doesn't seem to have a way to be run via command line. Reading and following the operation of armbian-install is next to impossible.

Wish I could find an ELI5 document for how to create a bootable copy of an Armbian image using the command line.

Understood. I'm still on 24.x.x so I don't know if the later ones are better. I tried for a while without, but honestly, you gotta get yourself a TTL -> USB that works so you can follow the log. Once you do that, you'll see the errors clear as day as to why the overlays aren't being loaded. Not sure what country you're in, but in NA they're quite inexpensive. This is the one I got: https://www.amazon.com/Serial-Adapter-Signal-Prolific-Windows/dp/B08BLKBK1K

It's been a while, but I believe it was the prefix issue. Perhaps it's been fixed now? https://github.com/armbian/configng/issues/360#issuecomment-2573855215 A big part of getting to the bottom of overlay issues is to use a TTL->USB adapter to watch the boot process.

Can anyone point me in the right direction on what needs to be done to make a partition boot?

Edited both /boot/armbianEnv.txt and /etc/fstab but it still doesn't boot. Blue light never even comes on.

So, looking to create a CLI version of armbian-install. Only has to work with the rockpi-s and from the SD card to the eMMC. Looking at this script: If it works to clone the SD to eMMC (with some changes?) then I need to tell armbian to boot from the eMMC when the SD card isn't inserted, same way that armbian-install does. Do I simply change the UUID line in /boot/armbianEnv.txt to the UUID of the eMMC, or do I need to edit /etc/fstab or ??

The fix is in the first thread above.

Ok, I'll try again, perhaps I did something incorrectly. My fault. After the install it decided to change IP addresses. Rookie move. Now both the eMMC and SD card seem to be booting. Even upgraded to trixie and all still seems to be ok. TY for your help! Is this fixable so that these extra steps are not needed?