mihanson Posted 12 hours ago Posted 12 hours ago (edited) I flashed a fresh image to my uSD card via dd. $ sudo unxz -c Armbian_25.5.1_Tritium-h5_trixie_current_6.12.30_minimal.img.xz | dd of=/dev/sdf bs=1M oflag=direct conv=fsync status=progress iflag=fullblock When I loaded the uSD into my Tritium-H5 all I got was just the red power light, but no activity. Tried a few different power supplies with the same result. I finally figured out that it appeared the bootloader was missing. I used Libre Tech's flash tool to flash their bootloader to my uSD card. Now I was able to get the Tritium-H5 outputting the boot sequesnce on the serial console. However, it stops at: Spoiler DRAM: 2048 MiB Trying to boot from MMC1 lz4 image NOTICE: BL31: v2.11.0(release):v2.8-3529-g5d9993261 NOTICE: BL31: Built : 22:45:37, Aug 20 2024 NOTICE: BL31: Detected Allwinner H5 SoC (1718) NOTICE: BL31: Found U-Boot DTB at 0x21386d8, model: Libre Computer ALL-H3-CC H5 NOTICE: PMIC: Assuming H5 reference regulator design SCP/INF: Crust v0.6.10000 U-Boot 2023.07+ (Aug 20 2024 - 22:45:45 -0400) Libre Computer ALL-H3-CC H5 DRAM: 2 GiB Core: 75 devices, 23 uclasses, devicetree: separate WDT: Not starting watchdog@1c20ca0 MMC: mmc@1c0f000: 1, mmc@1c11000: 0 Loading Environment from FAT... Unable to use mmc 1:1... ** File not found boot.ini ** Loading Environment from FAT... Unable to use mmc 1:1... ** File not found boot.ini ** Error (-1): cannot determine file size U-Boot 2023.07+ (Aug 20 2024 - 22:45:45 -0400) Libre Computer ALL-H3-CC H5 Model: Libre Computer ALL-H3-CC H5 Net: eth0: ethernet@1c30000 starting USB... Bus usb@1c1a000: USB EHCI 1.00 Bus usb@1c1a400: USB OHCI 1.0 Bus usb@1c1b000: USB EHCI 1.00 Bus usb@1c1b400: USB OHCI 1.0 Bus usb@1c1c000: USB EHCI 1.00 Bus usb@1c1c400: USB OHCI 1.0 Bus usb@1c1d000: USB EHCI 1.00 Bus usb@1c1d400: USB OHCI 1.0 scanning bus usb@1c1a000 for devices... 1 USB Device(s) found scanning bus usb@1c1a400 for devices... 1 USB Device(s) found scanning bus usb@1c1b000 for devices... 1 USB Device(s) found scanning bus usb@1c1b400 for devices... 1 USB Device(s) found scanning bus usb@1c1c000 for devices... 1 USB Device(s) found scanning bus usb@1c1c400 for devices... 1 USB Device(s) found scanning bus usb@1c1d000 for devices... 1 USB Device(s) found scanning bus usb@1c1d400 for devices... 2 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found 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': Scanning bootdev 'mmc@1c11000.bootdev': Card did not respond to voltage select! : -110 Scanning bootdev 'mmc@1c0f000.bootdev': 0 script ready mmc 1 mmc@1c0f000.bootdev.part_ /boot/boot.scr ** Booting bootflow 'mmc@1c0f000.bootdev.part_1' with script subfdt=sun50i-h5-libretech-all-h3-cc.dtb U-boot loaded from SD Boot script loaded from mmc 176 bytes read in 2 ms (85.9 KiB/s) subfdt=sun50i-h5-libretech-all-h3-cc.dtb Load fdt: /boot/dtb/allwinner/sun50i-h5-libretech-all-h3-cc.dtb Card did not respond to voltage select! : -110 ** Bad device specification mmc 0 ** 35129 bytes read in 6 ms (5.6 MiB/s) Working FDT set to 4fa00000 339 bytes read in 5 ms (65.4 KiB/s) Applying kernel provided DT overlay sun50i-h5-analog-codec.dtbo 4191 bytes read in 5 ms (818.4 KiB/s) Applying kernel provided DT fixup script (sun50i-h5-fixup.scr) ## Executing script at 45000000 17057194 bytes read in 707 ms (23 MiB/s) 38086664 bytes read in 1576 ms (23 MiB/s) Moving Image from 0x40080000 to 0x40200000, end=42740000 ## Loading init Ramdisk from Legacy Image at 4ff00000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 17057130 Bytes = 16.3 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 4fa00000 Booting using the fdt blob at 0x4fa00000 Working FDT set to 4fa00000 Loading Ramdisk to 48fbb000, end 49fff56a ... OK Loading Device Tree to 0000000048f4a000, end 0000000048fbafff ... OK Working FDT set to 48f4a000 Starting kernel ... I stumbled through the u-Boot recovery process and after remounting the partition r/w I got dpkg to install linux-u-boot-tritium-h5-current_25.5.1_arm64__2024.01-S866c-P42f9-Hc721-V3ed7-Bb703-R448a.deb However, when I rebooted the Tritium-H5 I was still stuck on the above spoiler. 👆 Am I doing something wrong? How can I get the Tritium-H5 to boot the Armbian image? Thanks! Edited 12 hours ago by mihanson 0 Quote
laibsch Posted 8 hours ago Posted 8 hours ago sorry to hear about your troubles The Tritium H5 is maintained by https://github.com/Tonymac32. Not sure if he is active here in the forum. 0 Quote
mihanson Posted 2 hours ago Author Posted 2 hours ago (edited) @laibsch thank you. @TonyMac32 any ideas? Update: The Bookworm minimal image does fully boot. Just not Trixie. Edited 2 hours ago by mihanson 0 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.