Nick A

@boggy have you tried another SD card? You have a lot of mmc errors. which miniarch image booted for you? Maybe we can use the mmc settings from that image.

@boggy do you have a boot log from armbian?

@boggy Try my Transpeed 8K618T image. It includes the most critical DTS settings for this hardware. All your Dram settings in the dts have dram_type = <0x03> or DDR3. dram_para1 { device_type = "dram_para1"; dram_clk = <0x258>; dram_type = <0x03>; cd-gpios = <&pio 8 16 GPIO_ACTIVE_LOW>; /* PI16 */ sdmmc@04020000 { compatible = "allwinner,sunxi-mmc-v4p1x"; device_type = "sdc0"; . . . cd-gpios = <0x53 0x08 0x10 0x06 0x01 0x03 0xffffffff>; can you find the wifi chip on your board?

@José Manuel Márquez Luque try these images https://github.com/NickAlilovic/build/releases/tag/20250306

@Bob-the-great try these images https://github.com/NickAlilovic/build/releases/tag/20250306

@tin harden A7A mainline is still a WIP.

@Thur_Wander For debugging purposes, UART is highly recommended. Use balena Etcher to write the compiled image to your SD card.

@Thur_Wander Here are the steps to create a secure boot image. This example is using the tanix-tx6s-axp313 defconfig. You probably want one of the X96q defconfig's.

@Octavio Cuatrochio@Thur_Wander Maybe it has secure boot enabled.

@Morales Morales

@BoringNameHave you tried building a new image? Use the image and kernel headers from that specific build. I believe the problem exists because the DTS source was updated after the header release. I updated the linux kernel headers. https://github.com/NickAlilovic/build/releases/download/20250306/linux-headers-edge-sunxi64_25.05.0-trunk_arm64__6.12.11-S62b2-Da873-P6755-C1a9bH02eb-HK01ba-Vc222-B9bbb-R448a.deb

@sicxnull This might be the patch that fixed it. It's in mainline u-boot now. I would use a newer u-boot. https://lists.denx.de/pipermail/u-boot/2025-March/582900.html

@sicxnull I would need to look at your sources. Not sure if it's a dts or u-boot patch fix.

@MeJune You can check out my work starting with the 'Add warpme kernel 6.17' commit here: https://github.com/NickAlilovic/build/commits/v20251014/ I’m using warpme patches from his minimyth2 repo, though I’ve modified them to ensure they apply correctly. I also used my own patches for Transpeed, as his implementation differs from mine. u-boot: https://github.com/warpme/minimyth2/tree/master/script/bootloaders/u-boot-aw/files https://github.com/warpme/minimyth2/blob/master/script/bootloaders/u-boot-aw/Makefile kernel: https://github.com/warpme/minimyth2/tree/master/script/kernel/linux-6.19/files https://github.com/warpme/minimyth2/blob/master/script/kernel/linux-6.19/Makefile An easier way to do this is to create a board config and use the official Armbian patch set. While Transpeed is already mainlined, the implementation is incomplete. You will still need a patch to include your missing Transpeed DTS nodes. If you are happy with 6.17, then use this build: https://github.com/NickAlilovic/build/commits/v20251014/ This build generates a kernel .deb package in output/debs. You can use it to upgrade your existing Armbian installation. I haven't tried this myself, so I make no promises that it will work; please ensure you have a backup before proceeding. Backing Up the SD Card (from another PC) The most reliable way to back up an SD card is to create a full disk image on a separate computer. sudo dd if=/dev/sdX of=armbian_backup.img bs=1M status=progress If your system is running on eMMC, you can back it up to an external USB or SD card using built-in Armbian tools. Using armbian-ddbr: Many Armbian builds include this utility specifically for eMMC backup/restore. Boot Armbian from an external SD card (so the eMMC is not in use). Run the command: sudo armbian-ddbr. Select the backup option to create a compressed image of your internal storage. Using armbian-config: Some versions offer a "Backup" or "Clone" option under the System or Maintenance menus

@billymore I got this from AI. It's not perfect. I haven't done this before. To convert a standard Armbian root filesystem (typically an ext4 partition) into the rootfs.cpio.lzma.uboot format required for RAM booting, you must package the file tree into a CPIO archive, compress it with LZMA, and then wrap it with a U-Boot header. 1. Extract the Armbian RootFS First, you need the actual files from your Armbian image. Mount the image to a temporary directory on your Linux PC: mkdir -p /tmp/armbian_root If you have your Armbian .img file ready, run this command to find the start sector of the root partition (usually the second partition): fdisk -l armbian_image.img Multiply that Start number by 512 to get the exact offset for the mount command. sudo mount -o loop,offset=YOUR_OFFSET armbian_image.img /tmp/armbian_root A standard Armbian rootfs doesn't have an init file in the root directory; it uses sbin/init (a symlink to systemd). A RAM disk requires an executable at /init. sudo ln -s sbin/init /tmp/armbian_root/init 2. Create the CPIO Archive Pack the entire filesystem into a newc format CPIO archive. It is critical to perform this step as root to preserve file permissions. cd /tmp/armbian_root sudo find . | sudo cpio -H newc -o > /tmp/rootfs.cpio 3. Compress with LZMA Compress the archive using the LZMA algorithm to minimize its size for RAM loading: lzma -9 /tmp/rootfs.cpio # This creates /tmp/rootfs.cpio.lzma 4. Add the U-Boot Header Use the mkimage tool (from the u-boot-tools package) to add the 64-byte legacy header that U-Boot uses to identify the ramdisk. mkimage -A arm64 -O linux -T ramdisk -C lzma -n "Armbian Initramfs" -d /tmp/rootfs.cpio.lzma /tmp/rootfs.cpio.lzma.uboot -A arm: Target architecture (use arm64 if applicable). -T ramdisk: Identifies the image type as a RAM filesystem. -C lzma: Specifies the compression used. -d: Input data file. sunxi-fel -v uboot u-boot-sunxi-with-spl.bin \ write 0x40080000 Image \ write 0x4fa00000 dtbs/allwinner/sun50i-h313-tanix-tx1.dtb \ write 0x4fe00000 rootfs.cpio.lzma.uboot (Note: If you are using a raw Image instead of a uImage, use booti instead of bootm). Once U-Boot initializes over the USB cable, it will drop to a prompt. You must run this to start the OS: Armbian’s default kernel might not have a large enough ramdisk_size allocated in its config. Update your bootargs to include a size limit (in KB). If your rootfs is 500MB: setenv bootargs "console=ttyS0,115200 root=/dev/ram0 rw" booti 0x40080000 0x4fe00000 0x4fa00000 ramdisk_size=600000