<?xml version="1.0"?>
<rss version="2.0"><channel><title>Libre Tritium H5 Latest Topics</title><link>https://testforum.armbian.com/forum/243-libre-tritium-h5/</link><description>Libre Tritium H5 Latest Topics</description><language>en</language><item><title>No bootloader on Libre Tritium-H5 image</title><link>https://testforum.armbian.com/topic/54674-no-bootloader-on-libre-tritium-h5-image/</link><description><![CDATA[<p>
	I flashed a fresh image to my uSD card via dd. 
</p>

<pre class="ipsCode">$ 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</pre>

<p>
	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 <a href="https://github.com/libre-computer-project/libretech-flash-tool" rel="external nofollow">Libre Tech's flash tool</a> 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:
</p>

<div class="ipsSpoiler" data-ipsspoiler="">
	<div class="ipsSpoiler_header">
		<span>Spoiler</span>
	</div>

	<div class="ipsSpoiler_contents">
		<p>
			DRAM: 2048 MiB<br />
			Trying to boot from MMC1<br />
			lz4 image<br />
			NOTICE:  BL31: v2.11.0(release):v2.8-3529-g5d9993261<br />
			NOTICE:  BL31: Built : 22:45:37, Aug 20 2024<br />
			NOTICE:  BL31: Detected Allwinner H5 <abbr title="System On a Chip">SoC</abbr> (1718)<br />
			NOTICE:  BL31: Found U-Boot <abbr title="Device tree blob">DTB</abbr> at 0x21386d8, model: Libre Computer ALL-H3-CC H5<br />
			NOTICE:  PMIC: Assuming H5 reference regulator design<br />
			SCP/INF: Crust v0.6.10000
		</p>

		<p>
			<br />
			U-Boot 2023.07+ (Aug 20 2024 - 22:45:45 -0400) Libre Computer ALL-H3-CC H5
		</p>

		<p>
			DRAM:  2 GiB<br />
			Core:  75 devices, 23 uclasses, devicetree: separate<br />
			WDT:   Not starting watchdog@1c20ca0<br />
			MMC:   mmc@1c0f000: 1, mmc@1c11000: 0<br />
			Loading Environment from FAT... Unable to use mmc 1:1...<br />
			** File not found boot.ini **<br />
			Loading Environment from FAT... Unable to use mmc 1:1...<br />
			** File not found boot.ini **<br />
			Error (-1): cannot determine file size<br />
			U-Boot 2023.07+ (Aug 20 2024 - 22:45:45 -0400) Libre Computer ALL-H3-CC H5
		</p>

		<p>
			Model: Libre Computer ALL-H3-CC H5<br />
			Net:   eth0: ethernet@1c30000<br />
			starting USB...<br />
			Bus usb@1c1a000: USB EHCI 1.00<br />
			Bus usb@1c1a400: USB OHCI 1.0<br />
			Bus usb@1c1b000: USB EHCI 1.00<br />
			Bus usb@1c1b400: USB OHCI 1.0<br />
			Bus usb@1c1c000: USB EHCI 1.00<br />
			Bus usb@1c1c400: USB OHCI 1.0<br />
			Bus usb@1c1d000: USB EHCI 1.00<br />
			Bus usb@1c1d400: USB OHCI 1.0<br />
			scanning bus usb@1c1a000 for devices... 1 USB Device(s) found<br />
			scanning bus usb@1c1a400 for devices... 1 USB Device(s) found<br />
			scanning bus usb@1c1b000 for devices... 1 USB Device(s) found<br />
			scanning bus usb@1c1b400 for devices... 1 USB Device(s) found<br />
			scanning bus usb@1c1c000 for devices... 1 USB Device(s) found<br />
			scanning bus usb@1c1c400 for devices... 1 USB Device(s) found<br />
			scanning bus usb@1c1d000 for devices... 1 USB Device(s) found<br />
			scanning bus usb@1c1d400 for devices... 2 USB Device(s) found<br />
			       scanning usb for storage devices... 0 Storage Device(s) found<br />
			Hit any key to stop autoboot:  0<br />
			Scanning for bootflows in all bootdevs<br />
			Seq  Method       State   Uclass    Part  Name                      Filename<br />
			---  -----------  ------  --------  ----  ------------------------  ----------------<br />
			Scanning global bootmeth 'efi_mgr':<br />
			Scanning bootdev 'mmc@1c11000.bootdev':<br />
			Card did not respond to voltage select! : -110<br />
			Scanning bootdev 'mmc@1c0f000.bootdev':<br />
			  0  script       ready   mmc          1  mmc@1c0f000.bootdev.part_ /boot/boot.scr<br />
			** Booting bootflow 'mmc@1c0f000.bootdev.part_1' with script<br />
			subfdt=sun50i-h5-libretech-all-h3-cc.<abbr title="Device tree blob">dtb</abbr><br />
			U-boot loaded from SD<br />
			Boot script loaded from mmc<br />
			176 bytes read in 2 ms (85.9 KiB/s)<br />
			subfdt=sun50i-h5-libretech-all-h3-cc.<abbr title="Device tree blob">dtb</abbr><br />
			Load fdt: /boot/<abbr title="Device tree blob">dtb</abbr>/allwinner/sun50i-h5-libretech-all-h3-cc.<abbr title="Device tree blob">dtb</abbr><br />
			Card did not respond to voltage select! : -110<br />
			** Bad device specification mmc 0 **<br />
			35129 bytes read in 6 ms (5.6 MiB/s)<br />
			Working FDT set to 4fa00000<br />
			339 bytes read in 5 ms (65.4 KiB/s)<br />
			Applying kernel provided DT overlay sun50i-h5-analog-codec.dtbo<br />
			4191 bytes read in 5 ms (818.4 KiB/s)<br />
			Applying kernel provided DT fixup script (sun50i-h5-fixup.scr)<br />
			## Executing script at 45000000<br />
			17057194 bytes read in 707 ms (23 MiB/s)<br />
			38086664 bytes read in 1576 ms (23 MiB/s)<br />
			Moving Image from 0x40080000 to 0x40200000, end=42740000<br />
			## Loading init Ramdisk from Legacy Image at 4ff00000 ...<br />
			   Image Name:   uInitrd<br />
			   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)<br />
			   Data Size:    17057130 Bytes = 16.3 MiB<br />
			   Load Address: 00000000<br />
			   Entry Point:  00000000<br />
			   Verifying Checksum ... OK<br />
			## Flattened Device Tree blob at 4fa00000<br />
			   Booting using the fdt blob at 0x4fa00000<br />
			Working FDT set to 4fa00000<br />
			   Loading Ramdisk to 48fbb000, end 49fff56a ... OK<br />
			   Loading Device Tree to 0000000048f4a000, end 0000000048fbafff ... OK<br />
			Working FDT set to 48f4a000
		</p>

		<p>
			Starting kernel ...
		</p>
	</div>
</div>

<p>
	 
</p>

<p>
	 
</p>

<p>
	I stumbled through the <a href="https://docs.armbian.com/User-Guide_Troubleshooting/#u-boot-shell-access" rel="external nofollow">u-Boot recovery process</a> and after remounting the partition r/w I got dpkg to install 
</p>

<pre class="ipsCode">linux-u-boot-tritium-h5-current_25.5.1_arm64__2024.01-S866c-P42f9-Hc721-V3ed7-Bb703-R448a.deb</pre>

<p>
	However, when I rebooted the Tritium-H5 I was still stuck on the above spoiler. <span class="ipsEmoji">👆</span>  Am I doing something wrong? How can I get the Tritium-H5 to boot the Armbian image? Thanks!
</p>
]]></description><guid isPermaLink="false">54674</guid><pubDate>Thu, 21 Aug 2025 04:12:34 +0000</pubDate></item><item><title>Getting HiFiBerry AMP100 working on Tritium H5 (ALL-H3-CC H5)</title><link>https://testforum.armbian.com/topic/33005-getting-hifiberry-amp100-working-on-tritium-h5-all-h3-cc-h5/</link><description><![CDATA[<p>
	I have been reading into this for some hours now, and it seems like I will need to write (or perhaps modify from some existing) <abbr title="Device tree blob">DTB</abbr> overlay or something like that?
</p>

<p>
	 
</p>

<p>
	I tried following the instructions <a href="https://docs.armbian.com/User-Guide_Armbian_overlays/" rel="external nofollow">here</a>, and using a .dtbo file (hifiberry-amp100.dtbo) I copied from OSMC I have here on an <abbr title="Raspberry Pi">RPi</abbr> 3, but I don't think that's right as it mentions 'brcm,bcm2835' which I suppose means it can only be used with <abbr title="Raspberry Pi">RPi</abbr>.
</p>

<p>
	 
</p>

<p>
	The above mentioned .dtbo file seemed to be in some binary format, although I could still make out some text in it.  I can't even seem to find the uncompressed (plain text) versions, I searched OSMC and HiFiBerry repos (amongst others), I don't think I am looking in right place (maybe I need to look in <abbr title="Raspberry Pi">RPi</abbr> Foundation or Linux kernel sources?).
</p>

<p>
	 
</p>

<p>
	Any help or pointers will be appreciated.  This seems to be a non-trivial task (at least for a low to medium level wizard such as myself).
</p>
]]></description><guid isPermaLink="false">33005</guid><pubDate>Sun, 31 Dec 2023 06:20:54 +0000</pubDate></item><item><title>Libre Computer Tritium H5 does not boot from eMMC</title><link>https://testforum.armbian.com/topic/18386-libre-computer-tritium-h5-does-not-boot-from-emmc/</link><description><![CDATA[<p>
	Hello!
</p>

<p>
	 
</p>

<p>
	I have three Libre Computer Tritium H5 boards and three <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">eMMC</abbr></abbr> modules on hands. All three <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">eMMC</abbr></abbr> modules is flashed with exactly same Armbian image and exactly same uboot. I also use exactly same <abbr title="Power supply unit"><abbr title="Power supply unit">PSU</abbr></abbr> and cable for all three boards (however I reproduced this issue with four <abbr title="Power supply unit"><abbr title="Power supply unit">PSU</abbr></abbr> and three microUSB cables, no difference in behavior was found).
</p>

<p>
	 
</p>

<ol>
	<li>
		All three boards start just fine from microSD (so it's not exactly "Your board doesn't work?" case).
	</li>
	<li>
		One board never boot from <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">eMMC</abbr></abbr> on first power up, but almost always boot on second power up. That reproducible with all three <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">eMMC</abbr></abbr> modules.
	</li>
	<li>
		Two other boards just never boot from any <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">eMMC</abbr></abbr> module.
	</li>
</ol>

<p>
	 
</p>

<p>
	When board can not boot from <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">eMMC</abbr></abbr> it just stuck there:
</p>

<p>
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted">
<span class="pln">U-Boot SPL 2021.04-armbian (May 06 2021 - 19:52:02 +0000)
DRAM: 2048 MiB
Trying to boot from MMC2

U-Boot SPL 2021.04-armbian (May 06 2021 - 19:52:02 +0000)
DRAM: 2048 MiB
Trying to boot from MMC2

U-Boot SPL 2021.04-armbian (May 06 2021 - 19:52:02 +0000)
DRAM: 2048 MiB
Trying to boot from MMC2

U-Boot SPL 2021.04-armbian (May 06 2021 - 19:52:02 +0000)
DRAM: 2048 MiB
Trying to boot from MMC2

U-Boot SPL 2021.04-armbian (May 06 2021 - 19:52:02 +0000)
DRAM: 2048 MiB
Trying to boot from MMC2</span></pre>

<p>
	 
</p>

<p>
	That five power up attempt as you can see.
</p>

<p>
	 
</p>

<p>
	I tried to rollback uboot to 2020.04, but it behave in exactly same way.`
</p>

<p>
	All three boards was ordered at the same time, in one package.
</p>

<p>
	 
</p>

<p>
	Is anyone can reproduce this?
</p>

<p>
	Is there anything else to try, or I should just give up and stick with microSD for now? (Although I probably could left uboot and /boot on microSD and then put rootfs on <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">eMMC</abbr></abbr>, but that another story.)
</p>
]]></description><guid isPermaLink="false">18386</guid><pubDate>Sat, 12 Jun 2021 22:24:25 +0000</pubDate></item><item><title>usb gadget, g_ether.. on tritium h5?</title><link>https://testforum.armbian.com/topic/16519-usb-gadget-g_ether-on-tritium-h5/</link><description><![CDATA[<p>
	Hi all,
</p>

<p>
	I've read on the forum that support for usb gadget using the µ-usb port on the libre computer tritium needed a kernel reconfigure &amp;  recompile.
</p>

<p>
	I tried to start with that, but during configuration, I've seen full support already.
</p>

<p>
	So, was it supposed to just work ?
</p>

<p>
	I target armbian buster server variant.
</p>

<p>
	my need is to use IP over an usb (and power) cable between a linux machine (x86 and then arm) and a  tritium h5
</p>

<p>
	Thanks in advance
</p>
]]></description><guid isPermaLink="false">16519</guid><pubDate>Thu, 17 Dec 2020 15:35:58 +0000</pubDate></item><item><title>usb gadget, g_ether.. on tritium h5</title><link>https://testforum.armbian.com/topic/14563-usb-gadget-g_ether-on-tritium-h5/</link><description><![CDATA[<p>
	Hi all,
</p>

<p>
	I've read on the forum that support for usb gadget using the µ-usb port on the libre computer tritium needed a kernel reconfigure &amp;  recompile.
</p>

<p>
	I tried to start with that, but during configuration, I've seen full support already.
</p>

<p>
	So, was it supposed to just work ?
</p>

<p>
	I target armbian buster server variant.
</p>

<p>
	my need is to use IP over an usb (and power) cable between a linux machine (x86 and then arm) and a  tritium h5
</p>

<p>
	Thanks in advance
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">14563</guid><pubDate>Sat, 04 Jul 2020 18:19:31 +0000</pubDate></item><item><title>emmc install tritium h5</title><link>https://testforum.armbian.com/topic/8554-emmc-install-tritium-h5/</link><description><![CDATA[<p>
	I'm trying to install armbian to the attached emmc with armbian-config. However i get the message "There are no targets, please check your drive". With fdisk -l the emmc doesn't show up.<br>
	I do know the emmc is working properly because pull out the sd card (after shutting down) and reattach the power it boots from the emmc into android.
</p>

<p>
	 
</p>

<p>
	Does anyone know to fix this? 
</p>

<p>
	Systeminfo: http://ix.io/1q2B
</p>
]]></description><guid isPermaLink="false">8554</guid><pubDate>Thu, 25 Oct 2018 21:54:40 +0000</pubDate></item></channel></rss>
