asoilole

Hi everyone! This is my first time attempting to boot Armbian on my Orange Pi RV2, but I can't get it to work. It gets stuck during the boot process. I've tried both the latest Armbian release and building the image myself, but every attempt gets stuck at boot. The official Ubuntu image works fine, so I don't think it's a hardware issue. What am I missing here? U-Boot SPL 2022.10_armbian-2022.10-Sd61c-Pbf4f-H0027-Vc38c-B3ba1-R448a (Nov 09 2026 - 13:47:57 +0000) [ 0.366] DDR type LPDDR4X [ 0.367] set ddr tx odt to 80ohm! [ 0.376] Enable & config CLK/CA ODT [ 0.387] lpddr silicon init consume 20ms [ 0.388] Change DDR data rate to 2400MT/s [ 0.644] Boot from fit configuration x1_orangepi-rv2 [ 0.646] ## Checking hash(es) for config conf_18 ... OK [ 0.651] ## Checking hash(es) for Image uboot ... crc32+ OK [ 0.662] ## Checking hash(es) for Image fdt_18 ... crc32+ OK [ 0.689] ## Checking hash(es) for config config_1 ... OK [ 0.692] ## Checking hash(es) for Image opensbi ... crc32+ OK [ 0.736] U-Boot 2022.10_armbian-2022.10-Sd61c-Pbf4f-H0027-Vc38c-B3ba1-R448a (Nov 09 2026 - 13:47:57 +0000) [ 0.743] CPU: rv64imafdcv [ 0.746] Model: ky x1 orangepi-rv2 board [ 0.750] DRAM: 8 GiB [ 0.815] Core: 414 devices, 29 uclasses, devicetree: board [ 0.828] WDT: Started PMIC_WDT with servicing (60s timeout) [ 0.832] WDT: Started watchdog@D4080000 with servicing (60s timeout) [ 0.841] MMC: [ 0.948] initialize_console_log_buffer [ 0.949] Have allocated memory for console log buffer [ 0.954] In: serial [ 0.956] Out: serial [ 0.959] Err: serial [ 1.096] SF: Detected XM25QU128C with page size 256 Bytes, erase size 64 KiB, total 16 MiB List of MTD devices: [ 1.103] * nor0 [ 1.104] - device: flash@0 [ 1.107] - parent: spi@d420c000 [ 1.110] - driver: jedec_spi_nor [ 1.114] - path: /soc/spi@d420c000/flash@0 [ 1.118] - type: NOR flash [ 1.121] - block size: 0x10000 bytes [ 1.124] - min I/O: 0x1 bytes [ 1.127] - 0x000000000000-0x000001000000 : "nor0" [ 1.132] - 0x000000000000-0x000000010000 : "bootinfo" [ 1.137] - 0x000000010000-0x000000020000 : "private" [ 1.142] - 0x000000020000-0x000000060000 : "fsbl" [ 1.147] - 0x000000060000-0x000000070000 : "env" [ 1.152] - 0x000000070000-0x0000000a0000 : "opensbi" [ 1.157] - 0x0000000a0000-0x000001000000 : "uboot" [ 1.164] RGMII interface [ 1.165] eth0: ethernet@cac80000 [ 1.168] K1X: :_load_env_from_blk [ 1.193] Failed to load 'env_k1-x.txt' [ 1.194] Net: eth0: ethernet@cac80000 [ 1.199] Hit any key to stop autoboot: 0 [ 2.206] Loading K1 environment [ 2.255] Booting from mmc 0:1 ... [ 2.255] Retrieving file: /boot/extlinux/extlinux.conf [ 2.288] 1: Armbian-unofficial [ 2.288] Retrieving file: /boot/uInitrd [ 3.140] Retrieving file: /boot/Image [ 4.104] append: root=UUID=e26b749c-00f0-4581-9681-1245d3b715b7 earlycon=sbi console=tty1 console=ttyS0,115200 loglevel=7 rw no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 ignore_loglevel [ 4.120] Retrieving file: /boot/dtb/spacemit/k1-orangepi-rv2.dtb [ 4.174] Uncompressing Kernel Image [ 4.539] Moving Image from 0x10000000 to 0x200000, end=29ee000 [ 4.561] ## Loading init Ramdisk from Legacy Image at 21000000 ... [ 4.564] Image Name: uInitrd [ 4.568] Image Type: RISC-V Linux RAMDisk Image (gzip compressed) [ 4.574] Data Size: 13555067 Bytes = 12.9 MiB [ 4.579] Load Address: 00000000 [ 4.582] Entry Point: 00000000 Verifying Checksum ... OK [ 4.647] ## Flattened Device Tree blob at 31000000 [ 4.648] Booting using the fdt blob at 0x31000000 [ 4.653] Loading Ramdisk to 7d0aa000, end 7dd9757b ... OK [ 4.668] Loading Device Tree to 000000007d08a000, end 000000007d0a922b ... OK Starting kernel ... sys: 0x200 try sd... bm:3 j... U-Boot SPL 2022.10_armbian-2022.10-Sd61c-Pbf4f-H0027-Vc38c-B3ba1-R448a (Nov 09 2026 - 13:47:57 +0000) [ 0.366] DDR type LPDDR4X [ 0.368] set ddr tx odt to 80ohm! [ 0.377] Enable & config CLK/CA ODT [ 0.388] lpddr silicon init consume 20ms [ 0.389] Change DDR data rate to 2400MT/s [ 0.644] Boot fr [10:44:18.395] Disconnected console.log build.log

I managed to boot armbian from SD card without eMMC. The way achived this is by create a bootable insomwrt with venodr u boot, using my script `./run.sh custom` then replace the ROOTFS with armbian's ROOTFS from there I could boot armbian and fix the fstab. So far it's working fine root@aml-s9xx-box:~# lsblk -f NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS mmcblk1 ├─mmcblk1p1 vfat FAT16 BOOT 1C34-0D25 200.9M 18% /boot └─mmcblk1p2 ext4 1.0 ROOTFS 6f2edfb1-adb2-4f1b-8087-46d189763c9b 5.2G 20% /var/log.hdd / zram0 root@aml-s9xx-box:~# uname -a Linux aml-s9xx-box 6.1.66-DBAI #1 SMP PREEMPT Fri Nov 29 09:52:27 +07 2024 aarch64 GNU/Linux root@aml-s9xx-box:~# uptime 01:44:24 up 19 min, 1 user, load average: 0.00, 0.00, 0.00 root@aml-s9xx-box:~# cat /etc/os-release PRETTY_NAME="Armbian 26.2.0-trunk.563 trixie" NAME="Debian GNU/Linux" VERSION_ID="13" VERSION="13 (trixie)" VERSION_CODENAME=trixie DEBIAN_VERSION_FULL=13.3 ID=debian HOME_URL="https://www.armbian.com" SUPPORT_URL="https://forum.armbian.com" BUG_REPORT_URL="https://www.armbian.com/bugs" ARMBIAN_PRETTY_NAME="Armbian 26.2.0-trunk.563 trixie" root@aml-s9xx-box:~#

@hexdump I also have the exact constraints, I've detached eMMC from my HG680P. I've tried your u-boot using armbian and velvet's image tester, but boot of them failed to boot, and on UART I can't see anything. Any idea what should I try next ? Anyway, I managed to boot custom OpenWrt and I attached the scripts that I used to generate image run.sh insomwrt_with_vendor_u_boot.log