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?

@ValdikSS Didn't work. Do I also need to apt update && apt upgrade before or after running the dpkg command? Do I need to do something regarding my eMMC?

Is there a TL;DR method now for updating the Rockpi-S past 24.11.1 so it will boot? Do I run the dpkg command that @ValdikSS suggested and then armbian-install/update boot loader? Tried that. Didn't work.

Seems there were others with a similar problem. I can't tell if there's a clear solution contained within these threads?

Been using 24.11.1 Bookworm for a while, but yesterday did an apt update && apt upgrade, only to find that the resulting image would no longer boot. No "activity" light at all on the front on reboot. Downloaded 25.5.0 Trixie "just to see", but it doesn't boot either. What happened after 24.11.4? Is there something different I should be doing if I want to run a later version of Armbian?

NB - evtest does not come with Armbian Bookworm. A quick "apt install evtest" and we're away! root@radxa-e20c:~# evtest /dev/input/event0 Input driver version is 1.0.1 Input device ID: bus 0x19 vendor 0x1 product 0x1 version 0x100 Input device name: "gpio-keys" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 185 (KEY_F15) Key repeat handling: Repeat type 20 (EV_REP) Repeat code 0 (REP_DELAY) Value 250 Repeat code 1 (REP_PERIOD) Value 33 Properties: Testing ... (interrupt to exit) Event: time 1739040710.916095, type 1 (EV_KEY), code 185 (KEY_F15), value 1 Event: time 1739040710.916095, -------------- SYN_REPORT ------------ Event: time 1739040711.050330, type 1 (EV_KEY), code 185 (KEY_F15), value 0 Event: time 1739040711.050330, -------------- SYN_REPORT ------------ Do you know where I can find information on how to change settings for this button?

Thank you so much, @Torte! I'll have to bookmark this as my next rabbithole. 🙂

Oh! I thought those commands were needed for your custom dts. What do you know! All I had to do was: echo enp1s0 > device_name echo 1 > rx And it "just works"! Also, this "just works": root@radxa-e20c:/dev/input# cat event0 To see when the user button is pressed. Although, I'm not sure what data is being produced from it! root@radxa-e20c:/dev/input# cat event0 | hexdump -C 00000000 8b 8a a7 67 00 00 00 00 5c 14 0f 00 00 00 00 00 |...g....\.......| 00000010 01 00 b9 00 01 00 00 00 8b 8a a7 67 00 00 00 00 |...........g....| 00000020 5c 14 0f 00 00 00 00 00 00 00 00 00 00 00 00 00 |\...............| 00000030 8c 8a a7 67 00 00 00 00 3e 65 01 00 00 00 00 00 |...g....>e......| 00000040 01 00 b9 00 00 00 00 00 8c 8a a7 67 00 00 00 00 |...........g....| 00000050 3e 65 01 00 00 00 00 00 00 00 00 00 00 00 00 00 |>e..............| I had no idea it was that easy. Is this a Linux thing? Armbian thing? Radxa thing? Where can I read up on this kind of hardware control?

TY for your reply. They definitely can be controlled by echoing values to the `/sys/class/leds/` and even though the "trigger" is set to "netdev" and tx and rx files appear, I'm not seeing any activity on those LEDs with network activity. I can manually make the LEDs blink by doing something like echo heartbeat > /sys/class/leds/lan-led/trigger cat /sys/class/leds/lan-led/trigger will show the available triggers, and a [] around the currently selected one. cat trigger none usb-gadget usb-host rc-feedback bluetooth-power rfkill-any rfkill-none kbd-scrolllock kbd-numlock kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock mmc0 timer oneshot disk-activity disk-read disk-write ide-disk mtd nand-disk heartbeat backlight gpio cpu cpu0 cpu1 cpu2 cpu3 activity default-on transient flash torch panic [netdev] mmc1 It looks very configurable, just doesn't seem to be "automatically" working to show network activity.

How did you figure this out? I can't really understand anything that's in the dts file or what you've got going in that script... as per the info here: https://github.com/armbian/build/pull/7157 I should be able to get the LEDs working for the ethernet connection on the E20C. Not sure if I need an overlay, or a script like yours or both?

TY, I couldn't figure out where to post as the e20c doesn't have a tag. Did you just add it? NM, I was looking for e20c, didn't realize the tag was Radxa-E20C.