<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.nixos.org/w/index.php?action=history&amp;feed=atom&amp;title=Talk%3ANixOS_on_ARM%2FInstallation</id>
	<title>Talk:NixOS on ARM/Installation - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.nixos.org/w/index.php?action=history&amp;feed=atom&amp;title=Talk%3ANixOS_on_ARM%2FInstallation"/>
	<link rel="alternate" type="text/html" href="https://wiki.nixos.org/w/index.php?title=Talk:NixOS_on_ARM/Installation&amp;action=history"/>
	<updated>2026-06-18T02:22:55Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.45.1</generator>
	<entry>
		<id>https://wiki.nixos.org/w/index.php?title=Talk:NixOS_on_ARM/Installation&amp;diff=17392&amp;oldid=prev</id>
		<title>Ppenguin: /* Build SD-card images based on u-boot specific defconfig */ new section</title>
		<link rel="alternate" type="text/html" href="https://wiki.nixos.org/w/index.php?title=Talk:NixOS_on_ARM/Installation&amp;diff=17392&amp;oldid=prev"/>
		<updated>2024-09-13T13:57:50Z</updated>

		<summary type="html">&lt;p&gt;&lt;span class=&quot;autocomment&quot;&gt;Build SD-card images based on u-boot specific defconfig: &lt;/span&gt; new section&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;== Build SD-card images based on u-boot specific defconfig ==&lt;br /&gt;
&lt;br /&gt;
While trying to build an SD image for a `BananaPi-M2-Berry` I got almost immediately stuck, because [this article](https://wiki.nixos.org/wiki/NixOS_on_ARM/Banana_Pi) just starts with how to build `u-boot` out of the blue, without providing any context how this would relate to any `img` one might need. The &amp;quot;next step&amp;quot; refers [here](https://wiki.nixos.org/wiki/NixOS_on_ARM#NixOS_installation_.26_configuration), which essentially tells me that if I&amp;#039;m on a standard `aarch64` device I can download an image, if not ... _&amp;lt;looks for banana pi, finds link and clicks it&amp;gt;_ ... and we&amp;#039;re back at the `u-boot` page.&lt;br /&gt;
&lt;br /&gt;
It would be cool if we&amp;#039;d have a brief explanation how we can actually make a booting SD card image based on `u-boot`. I&amp;#039;m starting to understand (?) that the way forward might be something that overrides a `pkgs.ubootSomething.override { defconfig = &amp;quot;bananapi_m2_berry_defconfig&amp;quot;; }` and then somehow use `populateFirmwareCommands` to copy the outputs of that derivation to some intermediate `firmware/` directory???&lt;br /&gt;
&lt;br /&gt;
Then there&amp;#039;s the question what to do about `.dts` files? The one that seems to be necessary in this case (`sun8i-v40-bananapi-m2-berry.dtb`) is actually available within the rource of `u-boot` (`./arch/arm/dts/sun8i-v40-bananapi-m2-berry.dtb`), so we can/should copy it as well with `populateFirmwareCommands`? How? Where? (And looking at the `armbian` image for this device, I noticed there is no separate `FIRMWARE` partition. How does that relate to this?)&lt;br /&gt;
&lt;br /&gt;
Does anyone have an idea how this is supposed to work? I guess the nice thing is that if some actual context would be available, we would have all `u-boot` supported systems instantly covered with an actual actionable recipe? [[User:Ppenguin|Ppenguin]] ([[User talk:Ppenguin|talk]]) 13:57, 13 September 2024 (UTC)&lt;/div&gt;</summary>
		<author><name>Ppenguin</name></author>
	</entry>
</feed>