Meestor_X

find /boot/overlay-user -type f /boot/overlay-user/pwm.dtbo /boot/overlay-user/pwm.dts So, using the included /boot/dtb/rockchip/overlay/ files like rk3308-b@1.3ghz.dtbo, rk3308-s0-ext-antenna.dtbo and rk3308-sdio@10mhz.dtbo and my own overlay in /boot/overlay-user/ named pwm.dtbo The ONLY way it works is this: (important lines in /boot/armbianEnv.txt): overlay_prefix=rk3308 . . . user_overlays=pwm overlays=b@1.3ghz s0-ext-antenna sdio@10mhz

Do you happen to know if the S0 has an ADC input? (Got the overlays working finally)

Very cool! I didn't even know that would be possible to send triggers to GPIOs like that. I'd love to learn more about what's possible with GPIOs. Are these LEDs already on the S0 or they're ones you are connecting to the header?

Here's the fix if anyone hasn't figured it out... sudo chmod +x /etc/update-motd.d/*

motd is no longer showing on boot with my rockpi-s and rock s0. (same cpu) I feel like this started when I updated from 24.8.3 to 24.11.1 Anyone else having this problem? This looks suspect... root@rock-s0:/etc# cat /etc/motd cat: /etc/motd: No such file or directory root@rock-s0:/etc# cat /var/run/motd cat: /var/run/motd: No such file or directory root@rock-s0:/etc# cd /etc/ root@rock-s0:/etc# ls -l motd lrwxrwxrwx 1 root root 13 Nov 24 15:27 motd -> /var/run/motd root@rock-s0:/etc# cd /var/run root@rock-s0:/var/run# ls -l motd ls: cannot access 'motd': No such file or directory

Ok, that doesn't work either! 😉 I understand what you mean, now, @MaxT The added "-" messes everything up. root@rock-s0:~# cat /boot/armbianEnv.txt verbosity=1 bootlogo=false console=serial fdtfile=rockchip/rk3308-rock-s0.dtb extraargs=cma=16M rootdev=UUID=edc1b473-11f6-4b32-bf33-0986876f47d1 rootfstype=ext4 overlays=rk3308-b@1.3ghz rk3308-s0-ext-antenna rk3308-sdio@10mhz user_overlays=pwm usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u Found U-Boot script /boot/boot.scr 3633 bytes read in 4 ms (886.7 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 1:1 294 bytes read in 4 ms (71.3 KiB/s) 14325592 bytes read in 610 ms (22.4 MiB/s) 30097920 bytes read in 1275 ms (22.5 MiB/s) 54150 bytes read in 11 ms (4.7 MiB/s) Failed to load '/boot/dtb/rockchip/overlay/-rk3308-b@1.3ghz.dtbo' Failed to load '/boot/dtb/rockchip/overlay/-rk3308-s0-ext-antenna.dtbo' Failed to load '/boot/dtb/rockchip/overlay/-rk3308-sdio@10mhz.dtbo' 538 bytes read in 5 ms (104.5 KiB/s) Applying user provided DT overlay pwm.dtbo Moving Image from 0x680000 to 0x800000, end=2560000

Looks like the latest armbian-config is better, but it's still not respecting the overlay_prefix. Used armbian-config to add the sdio@10mhz overlay, and it did this to armbianEnv.txt. root@rock-s0:/boot# cat armbianEnv.txt verbosity=1 bootlogo=false console=serial overlay_prefix=rk3308 fdtfile=rockchip/rk3308-rock-s0.dtb extraargs=cma=16M rootdev=UUID=edc1b473-11f6-4b32-bf33-0986876f47d1 rootfstype=ext4 overlays=rk3308-sdio@10mhz usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u Of course, it didn't load the overlay, due to the prefix being added. Found U-Boot script /boot/boot.scr 3633 bytes read in 4 ms (886.7 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 1:1 260 bytes read in 3 ms (84 KiB/s) 14325592 bytes read in 611 ms (22.4 MiB/s) 30097920 bytes read in 1275 ms (22.5 MiB/s) 54150 bytes read in 10 ms (5.2 MiB/s) Failed to load '/boot/dtb/rockchip/overlay/rk3308-rk3308-sdio@10mhz.dtbo' Moving Image from 0x680000 to 0x800000, end=2560000 My suggestion would be to have armbian change the armbianEnv.txt file to not include the overlay_prefix= line by default. Not sure if it serves any useful purpose?

Ok, so one issue is that armbian-config doesn't create the correct line for the overlays. The overlay_prefix is automatically added to the name, and the command is "overlays=", not "ftd_overlays=" root@rock-s0:~# cat /boot/armbianEnv.txt verbosity=1 bootlogo=false console=serial overlay_prefix=rk3308 fdtfile=rockchip/rk3308-rock-s0.dtb extraargs=cma=16M rootdev=UUID=edc1b473-11f6-4b32-bf33-0986876f47d1 rootfstype=ext4 user_overlays=pwm overlays=b@1.3ghz s0-ext-antenna sdio@10mhz usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u Found U-Boot script /boot/boot.scr 3633 bytes read in 4 ms (886.7 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 1:1 295 bytes read in 3 ms (95.7 KiB/s) 14324658 bytes read in 609 ms (22.4 MiB/s) 30097920 bytes read in 1274 ms (22.5 MiB/s) 54895 bytes read in 9 ms (5.8 MiB/s) 459 bytes read in 6 ms (74.2 KiB/s) Applying kernel provided DT overlay rk3308-b@1.3ghz.dtbo 1204 bytes read in 7 ms (168 KiB/s) Applying kernel provided DT overlay rk3308-s0-ext-antenna.dtbo 226 bytes read in 6 ms (36.1 KiB/s) Applying kernel provided DT overlay rk3308-sdio@10mhz.dtbo 538 bytes read in 6 ms (86.9 KiB/s) Applying user provided DT overlay pwm.dtbo Moving Image from 0x680000 to 0x800000, end=2560000 ## Loading init Ramdisk from Legacy Image at 04000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 14324594 Bytes = 13.7 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 02800000 Booting using the fdt blob at 0x2800000 Loading Ramdisk to 1d17d000, end 1df26372 ... OK ERROR: reserving fdt memory region failed (addr=0 size=0 flags=0) Loading Device Tree to 000000001d107000, end 000000001d17cfff ... OK Starting kernel ...

Ok, tried some adding some other overlays via armbian-config and I see that they DIDN'T load.. . root@rock-s0:~# cat /boot/armbianEnv.txt verbosity=1 bootlogo=false console=serial overlay_prefix=rk3308 fdtfile=rockchip/rk3308-rock-s0.dtb extraargs=cma=16M rootdev=UUID=edc1b473-11f6-4b32-bf33-0986876f47d1 rootfstype=ext4 user_overlays=pwm fdt_overlays=rk3308-bs@1.3ghz rk3308-bs rk3308-s0-ext-antenna rk3308-sdio@10mhz usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u Found U-Boot script /boot/boot.scr 3633 bytes read in 4 ms (886.7 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 1:1 331 bytes read in 4 ms (80.1 KiB/s) 14324658 bytes read in 610 ms (22.4 MiB/s) 30097920 bytes read in 1275 ms (22.5 MiB/s) 54895 bytes read in 8 ms (6.5 MiB/s) 538 bytes read in 6 ms (86.9 KiB/s) Applying user provided DT overlay pwm.dtbo Moving Image from 0x680000 to 0x800000, end=2560000 ## Loading init Ramdisk from Legacy Image at 04000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 14324594 Bytes = 13.7 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 02800000 Booting using the fdt blob at 0x2800000 Loading Ramdisk to 1d17d000, end 1df26372 ... OK ERROR: reserving fdt memory region failed (addr=0 size=0 flags=0) Loading Device Tree to 000000001d107000, end 000000001d17cfff ... OK

NM, I see that it did load. Applying user provided DT overlay pwm.dtbo It didn't actually enable the PWM, but it does look like it loaded at least! I'll have to try some system ones and see what happens.

Ok, I've gotten the serial monitor working for a Rock S0 (same CPU and armbian build as the Rockpi-S AFAIK). I created an overlay to enable PWM, and added it to armbianEnv.txt: cat /boot/armbianEnv.txt verbosity=1 bootlogo=false console=serial overlay_prefix=rk3308 fdtfile=rockchip/rk3308-rock-s0.dtb extraargs=cma=16M rootdev=UUID=edc1b473-11f6-4b32-bf33-0986876f47d1 rootfstype=ext4 user_overlays=pwm usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u Here's what I see on the serial log: ---- Opened the serial port /dev/tty.usbserial-12240 ---- DDR Version V2.06 20211109 CHIP ID = 0x00003308 REG2C: 0x00000034, 0x00000034 In 589MHz DDR3 Col=10 Bank=3 Row=15 Size=512MB OUT: sdram_init finish. Boot1 Release Time: Mar 24 2022 08:28:57, version: 1.36 ROM VER:0x56323030, 19 chip_id:330800,0 ChipType = 0x13, 510 DPLL = 1300 MHz ...nandc_flash_init enter... No.1 FLASH ID:ff ff ff ff ff ff DPLL = 1300 MHz sfc nor id: ff ff ff DPLL = 1300 MHz sfc_nand id: ff ff ff NeedKHz=200KHz,clock=12000KHz NeedKHz=200KHz,clock=12000KHz NeedKHz=200KHz,clock=12000KHz mmc2:cmd8,20 mmc2:cmd5,20 mmc2:cmd55,20 DPLL = 1300 MHz NeedKHz=18000KHz,clock=650000KHz DPLL = 1300 MHz NeedKHz=48000KHz,clock=650000KHz mmc2:cmd19,100 SdmmcInit=2 0 BootCapSize=2000 UserCapSize=7456MB FwPartOffset=2000 , 2000 NeedKHz=200KHz,clock=12000KHz NeedKHz=200KHz,clock=12000KHz NeedKHz=200KHz,clock=12000KHz mmc0:cmd5,20 DPLL = 1300 MHz NeedKHz=24000KHz,clock=650000KHz DPLL = 1300 MHz NeedKHz=40000KHz,clock=650000KHz SdmmcInit=0 0 BootCapSize=0 UserCapSize=60906MB FwPartOffset=2000 , 0 StorageInit ok = 258238 SecureMode = 0 Secure read PBA: 0x4 Secure read PBA: 0x404 Secure read PBA: 0x804 Secure read PBA: 0xc04 Secure read PBA: 0x1004 SecureInit ret = 0, SecureMode = 0 atags_set_bootdev: ret:(0) GPT 0x3306530 signature is wrong recovery gpt... GPT 0x3306530 signature is wrong recovery gpt fail! LoadTrust Addr:0x4000 No find bl30.bin No find bl32.bin Load uboot, ReadLba = 2000 Load OK, addr=0x600000, size=0x994a8 RunBL31 0x40000 @ 335685 us INFO: Preloader serial: 0 NOTICE: BL31: v1.3(release):30f1405 NOTICE: BL31: Built : 17:08:28, Sep 23 2019 INFO: Lastlog: last=0x100000, realtime=0x102000, size=0x2000 INFO: ARM GICv2 driver initialized INFO: Using opteed sec cpu_context! INFO: boot cpu mask: 1 INFO: plat_rockchip_pmu_init: pd status 0xe b INFO: BL31: Initializing runtime services WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK ERROR: Error initializing runtime service opteed_fast INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x600000 INFO: SPSR = 0x3c9 U-Boot 2022.04-armbian-2022.04-Se4b6-P2db4-He13b-Vc245-Bda0a-R448a (Nov 16 2024 - 02:36:02 +0000) Model: Radxa ROCK S0 DRAM: 510 MiB Core: 275 devices, 20 uclasses, devicetree: separate MMC: dwmmc@ff480000: 1, dwmmc@ff490000: 0 Loading Environment from nowhere... OK In: serial Out: serial Err: serial Model: Radxa ROCK S0 rockchip_dnl_key_pressed read board id failed Net: eth0: ethernet@ff4e0000 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 3633 bytes read in 4 ms (886.7 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 1:1 251 bytes read in 3 ms (81.1 KiB/s) 14324658 bytes read in 610 ms (22.4 MiB/s) 30097920 bytes read in 1274 ms (22.5 MiB/s) 54895 bytes read in 9 ms (5.8 MiB/s) 538 bytes read in 5 ms (104.5 KiB/s) Applying user provided DT overlay pwm.dtbo Moving Image from 0x680000 to 0x800000, end=2560000 ## Loading init Ramdisk from Legacy Image at 04000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 14324594 Bytes = 13.7 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 02800000 Booting using the fdt blob at 0x2800000 Loading Ramdisk to 1d17d000, end 1df26372 ... OK ERROR: reserving fdt memory region failed (addr=0 size=0 flags=0) Loading Device Tree to 000000001d107000, end 000000001d17cfff ... OK Starting kernel ... Not really seeing where the overlays are loading or not in this text - but I may have missed it?

I’ve done some searching, but haven’t found a clear answer. i have a rockpi-s with a built in eMMC that has a bootable armbian image. When i insert a micro-SD card into the RP, and the card has a bootable image, it happily boots off of the card. Remove the card, and it boots off the eMMC. Perfect. Now, how do I duplicate this same functionality with a usb key? no key or sd = boot from eMMC SD inserted = boot from SD USB inserted = boot from USB I’ve been able to get the RP to boot from the usb using armbian-install to set it up, but then if I remove the USB, it no longer boots from the eMMC.

Well, it's all a bit of a mystery. Learning as much I can, but I sure wish there were more experts here that could offer some help!

Is there a way I can use this in the same way that armbian-install works? I want to automate the copying a complete image from an SD card to the eMMC, exactly the way armbian-install does, but via commandline so I can automate it. Using your tool, I tried creating an image file and then dd-ing it to the eMMC, but it wouldn't boot. I assume there's some fstab stuff that would need to be done when sending the image to another disk?

Ok, I see the problem, but not the solution. In main() there is this code to find which mmcblk# device is the eMMC and which is the SD card. # find real mmcblk device numbered 0, 1, 2 for eMMC, SD for ret in $(find /dev -name 'mmcblk[0-2]' -and -type b) do if [ -b ${ret}boot0 ];then emmc_dev=$ret else sd_dev=$ret fi done The issue is that there's no "boot0" file at either device. I've no idea how to ACTUALLY determine which is which, except I know in my case the eMMC is ALWAYS mmcblk0 and the SD card is ALWAYS mmcblk1. I expect that's not always true, but for my purposes, I can do: emmc_dev='/dev/mmcblk0' sd_dev='/dev/mmcblk1' and the names populate correctly in the menu. Again, not a solution by any means, I've done some scouring on the 'net to see if there's any good way to determine the block name of the SD and eMMC, but I can't find anything.