Werner

If it is not available from the download page build it by yourself: https://github.com/armbian/build/

Hi, There is a known naming issue with overlays on rk3588. Check /boot directory for available overlays and add manually.

Yes. This measure is necessary unfortunately to prevent abuse. This restriction will partially lift with time and released content (forum posts to say).

https://github.com/armbian/build/blob/main/config/boards/orangepi5-max.csc

Hi, considered doing by yourself? There are lots of examples on how to add software: https://github.com/armbian/configng/pulls?q=is%3Apr+is%3Aclosed

Try enabling "legacy" branch besides vendor and edge here: https://github.com/armbian/build/blob/0397a2492ddd7f87d3ab0a7875f1ec8346266ae0/config/boards/orangepi5.conf#L8 Then build an image using "legacy" as kernel. May build and boot, may not. This branch is abandoned. Dont ask for support when playing with it.

1.5Mbaud, everything else default

Get an USB UART adapter to attach serial console. Otherwise debugging is somewhere between hard and impossible https://debug.armbian.de

You are not using Armbian. You are using a fork that uses the name Armbian without permission. They do not participate in the core development process and trick you inkt thinking you'd get some sort of support at official place (here to say). Ask for help where you got the image from.

Did you test the nvme on a different system to check if its not defective?

Mainline support is still under heavy development. Not all features are there yet. If you need an almost feature-complete kernel you have to use vendor 6.1.y for now. Retry with this kernel.

bad sdcard isn't uncommon. One of the two first aid things to check if something is weird is switch sdcard to a known good one. The other is switch psu

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

IIRC he prefered to stay independent which I understood. Though that was a year ago where his motivation was still high. Now things have changed. We told him he'd be more than welcome to join forces and share the burden.

As you have mentioned in chat you tried this with mainline 6.10.y which I don't expect to even work. Support for rk3588 soc is still under heavy development and I don't think anything NPU related has been pushed upstream yet. You should try with 6.1.y vendor kernel. Why? https://docs.armbian.com/User-Guide_FAQ/#why-does-hardware-feature-xy-work-in-old-kernel-but-not-in-more-recent-one

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

He starts to feel the pain we feel for years already. It is hard to not tell people simply to fuck off. When I first came across his project I thought he must be crazy to do this all by himself. Kudos for doing this that long.

moved to tvboxes

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

Huh awesome As mentioned I am unsure about vfat is actually an issue or not. So perhaps you may want to dive a bit deeper. This is what I found: https://superuser.com/questions/763366/rsync-seems-to-overwrite-already-existing-file-on-exfat/1785111#1785111 As a workaround for now I simply duplicated the line where rsync is exected silently a second time to catch any missing files, adjusted a bit and used that to copy over the contents of /boot. However this UUID still needs to be adjusted manually.

I could narrow it down a bit. If there is a separate boot partition rsync for some reason fails to copy its contents over even though it is mounted into the file system. Also I read somewhere that some rsync parameters might be incompatible with vfat but I guess this only goes into effect when writing to vfat and not when reading from. The same OS without dedicated boot partition installs just fine.

Doesn't make much sense, indeed. I need to give this another shot to make them permanently visible. Those weren't touched for a while, not sure how up to date they are.

Hi. You can find them here: https://forum.armbian.com/terms While being logged out they should be visible as link at the bottom.

armbian-install issue. The contents of /boot were not copied over. After doing so and adjust UUID it boots just fine.

Retried with kwiboo's 2024.10 branch. No luck either DDR 2d653b3476 typ 24/01/20-15:04:19,fwver: v1.21 In LP4/4x derate en, other dram:1x trefi ddrconfig:0 LPDDR4X, 324MHz BW=32 Col=10 Bk=8 CS0 Row=16 CS=1 Die BW=16 Size=2048MB tdqss: cs0 dqs0: -48ps, dqs1: -96ps, dqs2: -96ps, dqs3: -168ps, change to: 324MHz PHY drv:clk:36,ca:36,DQ:29,odt:0 vrefinner:24%, vrefout:41% dram drv:40,odt:0 clk skew:0x64 rx vref: 24.4% tx vref: 36.0% change to: 528MHz PHY drv:clk:36,ca:36,DQ:29,odt:0 vrefinner:24%, vrefout:41% dram drv:40,odt:0 clk skew:0x58 rx vref: 28.4% tx vref: 34.0% change to: 780MHz PHY drv:clk:36,ca:36,DQ:29,odt:60 vrefinner:16%, vrefout:41% dram drv:40,odt:0 clk skew:0x58 rx vref: 15.6% tx vref: 32.0% change to: 1560MHz(final freq) PHY drv:clk:36,ca:36,DQ:29,odt:60 vrefinner:16%, vrefout:22% dram drv:40,odt:80 vref_ca:00000071 clk skew:0x2b rx vref: 15.6% tx vref: 19.8% cs 0: the read training result: DQS0:0x34, DQS1:0x34, DQS2:0x34, DQS3:0x30, min : 0xe 0x10 0x11 0xe 0x2 0x6 0xa 0x7 , 0xb 0x9 0x2 0x2 0xe 0xe 0xf 0xc , 0xf 0xf 0xc 0xa 0x3 0x2 0x2 0x7 , 0xc 0x7 0x5 0x2 0xe 0x10 0xc 0x13 , mid :0x2a 0x2a 0x2c 0x29 0x1d 0x21 0x25 0x23 ,0x26 0x24 0x1d 0x1d 0x2a 0x28 0x29 0x27 , 0x2b 0x2b 0x26 0x25 0x1e 0x1d 0x1d 0x21 ,0x26 0x22 0x20 0x1c 0x29 0x2b 0x28 0x2c , max :0x46 0x45 0x47 0x44 0x39 0x3d 0x40 0x3f ,0x42 0x40 0x38 0x39 0x46 0x42 0x44 0x42 , 0x48 0x47 0x41 0x41 0x3a 0x38 0x38 0x3c ,0x41 0x3d 0x3b 0x37 0x44 0x46 0x44 0x46 , range:0x38 0x35 0x36 0x36 0x37 0x37 0x36 0x38 ,0x37 0x37 0x36 0x37 0x38 0x34 0x35 0x36 , 0x39 0x38 0x35 0x37 0x37 0x36 0x36 0x35 ,0x35 0x36 0x36 0x35 0x36 0x36 0x38 0x33 , the write training result: DQS0:0x22, DQS1:0x18, DQS2:0x18, DQS3:0xa, min :0x69 0x6c 0x6e 0x6b 0x5e 0x62 0x64 0x63 0x65 ,0x5a 0x58 0x51 0x51 0x5e 0x5c 0x5c 0x5c 0x59 , 0x63 0x62 0x5d 0x5c 0x54 0x53 0x53 0x5a 0x5b ,0x54 0x51 0x4e 0x49 0x56 0x59 0x53 0x5a 0x50 , mid :0x83 0x86 0x88 0x84 0x77 0x7b 0x7d 0x7c 0x7d ,0x73 0x72 0x6a 0x6a 0x78 0x75 0x75 0x75 0x71 , 0x7e 0x7e 0x77 0x77 0x6f 0x6c 0x6d 0x73 0x75 ,0x6e 0x6b 0x68 0x63 0x71 0x73 0x6f 0x74 0x6b , max :0x9d 0xa1 0xa2 0x9e 0x90 0x94 0x96 0x96 0x96 ,0x8d 0x8d 0x84 0x84 0x92 0x8f 0x8f 0x8e 0x8a , 0x9a 0x9a 0x92 0x92 0x8a 0x86 0x88 0x8d 0x8f ,0x89 0x85 0x82 0x7d 0x8d 0x8d 0x8b 0x8f 0x86 , range:0x34 0x35 0x34 0x33 0x32 0x32 0x32 0x33 0x31 ,0x33 0x35 0x33 0x33 0x34 0x33 0x33 0x32 0x31 , 0x37 0x38 0x35 0x36 0x36 0x33 0x35 0x33 0x34 ,0x35 0x34 0x34 0x34 0x37 0x34 0x38 0x35 0x36 , CA Training result: cs:0 min :0x49 0x45 0x3f 0x37 0x3d 0x35 0x40 ,0x49 0x42 0x3e 0x35 0x3b 0x37 0x40 , cs:0 mid :0x86 0x86 0x7b 0x78 0x79 0x74 0x6d ,0x85 0x82 0x7a 0x74 0x77 0x77 0x6d , cs:0 max :0xc3 0xc8 0xb7 0xb9 0xb6 0xb4 0x9b ,0xc2 0xc2 0xb6 0xb3 0xb4 0xb7 0x9a , cs:0 range:0x7a 0x83 0x78 0x82 0x79 0x7f 0x5b ,0x79 0x80 0x78 0x7e 0x79 0x80 0x5a , out U-Boot SPL 2024.10-rc6-armbian-2024.10-rc6-Saf53-P0000-H3950-Vea36-Bda0a-R448a+ (Oct 22 2024 - 13:08:19 +0200) Trying to boot from SPI ## Checking hash(es) for config config-1 ... OK ## Checking hash(es) for Image atf-1 ... sha256+ OK ## Checking hash(es) for Image u-boot ... sha256+ OK ## Checking hash(es) for Image fdt-1 ... sha256+ OK ## Checking hash(es) for Image atf-2 ... sha256+ OK ## Checking hash(es) for Image atf-3 ... sha256+ OK ## Checking hash(es) for Image atf-4 ... sha256+ OK ## Checking hash(es) for Image atf-5 ... sha256+ OK ## Checking hash(es) for Image atf-6 ... sha256+ OK INFO: Preloader serial: 2 NOTICE: BL31: v2.3():v2.3-645-g8cea6ab0b:cl, fwver: v1.44 NOTICE: BL31: Built : 16:36:43, Sep 19 2023 INFO: GICv3 without legacy support detected. INFO: ARM GICv3 driver initialized in EL3 INFO: pmu v1 is valid 220114 INFO: l3 cache partition cfg-0 INFO: dfs DDR fsp_param[0].freq_mhz= 1560MHz INFO: dfs DDR fsp_param[1].freq_mhz= 324MHz INFO: dfs DDR fsp_param[2].freq_mhz= 528MHz INFO: dfs DDR fsp_param[3].freq_mhz= 780MHz INFO: Using opteed sec cpu_context! INFO: boot cpu mask: 0 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 = 0xa00000 INFO: SPSR = 0x3c9 ns16550_serial serial@fe660000: pinctrl_select_state_full: uclass_get_device_by_phandle_id: err=-19 U-Boot 2024.10-rc6-armbian-2024.10-rc6-Saf53-P0000-H3950-Vea36-Bda0a-R448a+ (Oct 22 2024 - 13:08:19 +0200) Model: Radxa ROCK 3A DRAM: 2 GiB PMIC: RK809 (on=0x40, off=0x00) Core: 343 devices, 31 uclasses, devicetree: separate MMC: mmc@fe000000: 2, mmc@fe2b0000: 1, mmc@fe310000: 0 Loading Environment from nowhere... OK In: serial@fe660000 Out: serial@fe660000 Err: serial@fe660000 Model: Radxa ROCK 3A Net: eth0: ethernet@fe010000 Hit any key to stop autoboot: 0 Scanning for bootflows in all bootdevs Seq Method State Uclass Part Name Filename --- ----------- ------ -------- ---- ------------------------ ---------------- Scanning global bootmeth 'efi_mgr': Card did not respond to voltage select! : -110 Card did not respond to voltage select! : -110 Card did not respond to voltage select! : -110 No EFI system partition No EFI system partition Failed to persist EFI variables Scanning bootdev 'mmc@fe2b0000.bootdev': Card did not respond to voltage select! : -110 Scanning bootdev 'mmc@fe310000.bootdev': Card did not respond to voltage select! : -110 pcie_dw_rockchip pcie@fe260000: PCIe-0 Link Fail No EFI system partition Failed to persist EFI variables No EFI system partition Failed to persist EFI variables Scanning bootdev 'nvme#0.blk#1.bootdev': pcie_dw_rockchip pcie@fe260000: PCIe-0 Link Fail scanning bus for devices... Bus usb@fd000000: Register 2000140 NbrPorts 2 Starting the controller USB XHCI 1.10 Bus usb@fd800000: USB EHCI 1.00 Bus usb@fd880000: USB EHCI 1.00 Bus usb@fd8c0000: USB OHCI 1.0 scanning bus usb@fd000000 for devices... 1 USB Device(s) found scanning bus usb@fd800000 for devices... 2 USB Device(s) found scanning bus usb@fd880000 for devices... 1 USB Device(s) found scanning bus usb@fd8c0000 for devices... 1 USB Device(s) found pcie_dw_rockchip pcie@fe260000: PCIe-0 Link Fail ethernet@fe010000 Waiting for PHY auto negotiation to complete........ done BOOTP broadcast 1 BOOTP broadcast 2 BOOTP broadcast 3 BOOTP broadcast 4 BOOTP broadcast 5 DHCP client bound to address 172.17.117.201 (3780 ms) Scanning bootdev 'ethernet@fe010000.bootdev': missing environment variable: pxeuuid Retrieving file: pxelinux.cfg/01-f2-87-c0-75-70-d7 *** ERROR: `serverip' not set Retrieving file: pxelinux.cfg/AC1175C9 *** ERROR: `serverip' not set Retrieving file: pxelinux.cfg/AC1175C *** ERROR: `serverip' not set Retrieving file: pxelinux.cfg/AC1175 *** ERROR: `serverip' not set Retrieving file: pxelinux.cfg/AC117 *** ERROR: `serverip' not set Retrieving file: pxelinux.cfg/AC11 *** ERROR: `serverip' not set Retrieving file: pxelinux.cfg/AC1 *** ERROR: `serverip' not set Retrieving file: pxelinux.cfg/AC *** ERROR: `serverip' not set Retrieving file: pxelinux.cfg/A *** ERROR: `serverip' not set Retrieving file: pxelinux.cfg/default-arm-rk3568-evb_rk3568 *** ERROR: `serverip' not set Retrieving file: pxelinux.cfg/default-arm-rk3568 *** ERROR: `serverip' not set Retrieving file: pxelinux.cfg/default-arm *** ERROR: `serverip' not set Retrieving file: pxelinux.cfg/default *** ERROR: `serverip' not set Scanning bootdev 'ethernet@fe010000.bootdev': BOOTP broadcast 1 DHCP client bound to address 172.17.117.201 (23 ms) *** ERROR: `serverip' not set Cannot autoload with TFTPGET No more bootdevs --- ----------- ------ -------- ---- ------------------------ ---------------- (0 bootflows, 0 valid) I guess it all boils down to "pcie_dw_rockchip pcie@fe260000: PCIe-0 Link Fail" How I switched uboot: shamelessly copied from another board function post_family_config_branch_edge__rock-3a_use_mainline_uboot() { display_alert "$BOARD" "Mainline U-Boot overrides for $BOARD - $BRANCH" "info" declare -g BOOTCONFIG="rock-3a-rk3568_defconfig" # override the default for the board/family declare -g BOOTDELAY=1 # Wait for UART interrupt to enter UMS/RockUSB mode etc declare -g BOOTSOURCE="https://github.com/Kwiboo/u-boot-rockchip" # We ❤️ mainline U-Boot declare -g BOOTBRANCH="branch:rk3xxx-2024.10" declare -g BOOTPATCHDIR="asdf" # empty declare -g BOOTDIR="u-boot-${BOARD}" # do not share u-boot directory declare -g UBOOT_TARGET_MAP="BL31=${RKBIN_DIR}/${BL31_BLOB} ROCKCHIP_TPL=${RKBIN_DIR}/${DDR_BLOB};;u-boot-rockchip.bin u-boot-rockchip-spi.bin" unset uboot_custom_postprocess write_uboot_platform write_uboot_platform_mtd # disable stuff from rockchip64_common; we're using binman here which does all the work already # Just use the binman-provided u-boot-rockchip.bin, which is ready-to-go function write_uboot_platform() { dd "if=$1/u-boot-rockchip.bin" "of=$2" bs=32k seek=1 conv=notrunc status=none } function write_uboot_platform_mtd() { flashcp -v -p "$1/u-boot-rockchip-spi.bin" /dev/mtd0 } }