DistroKit Mailinglist
 help / color / mirror / Atom feed
From: Roland Hieber <rhi@pengutronix.de>
To: distrokit@pengutronix.de
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>,
	Roland Hieber <rhi@pengutronix.de>
Subject: [DistroKit] [PATCH 5/5] doc: add FairyTux 2 documentation
Date: Tue,  3 Feb 2026 18:33:15 +0100	[thread overview]
Message-ID: <20260203173409.3995749-5-rhi@pengutronix.de> (raw)
In-Reply-To: <20260203173409.3995749-1-rhi@pengutronix.de>

From: Ahmad Fatoum <a.fatoum@pengutronix.de>

These are the steps needed to flash the FairyTux 2 eMMC.

Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
Tested-by: Roland Hieber <rhi@pengutronix.de>
[rhi: ported from distrokit-fairytux; adapt the image paths and fastboot
 partition names, remove the unneccesary usbgadget call since it starts
 automatically at boot, reformulate to make the fastboot process a bit
 clearer, and add the short Maintenance Status section.]
Signed-off-by: Roland Hieber <rhi@pengutronix.de>
---
 doc/hardware_v7a_fairytux_2.rst | 55 +++++++++++++++++++++++++++++++++
 1 file changed, 55 insertions(+)
 create mode 100644 doc/hardware_v7a_fairytux_2.rst

diff --git a/doc/hardware_v7a_fairytux_2.rst b/doc/hardware_v7a_fairytux_2.rst
new file mode 100644
index 000000000000..ca9350ab7cac
--- /dev/null
+++ b/doc/hardware_v7a_fairytux_2.rst
@@ -0,0 +1,55 @@
+LXA FairyTux 2
+==============
+
+The FairyTux 2 is a Octavo STM32MP1 SiP-based board like the MC-1,
+but unlike it, exclusively boots from eMMC.
+
+Initial Setup
+-------------
+
+If the eMMC is unprovisioned, the system must be bootstrapped via USB DFU
+initially.
+
+On your development host, run:
+
+.. code-block:: bash
+
+  $ cd platform-v7a/images
+  $ dfu-util --alt 1 -D stm32mp1-tf-a-stm32mp153c-lxa-fairytux2.stm32
+  $ dfu-util --alt 3 -D stm32mp153c-lxa-fairytux2.fip
+  $ dfu-util --alt 0 -e
+
+Or via Labgrid:
+
+.. code-block:: bash
+
+  $ cd platform-v7a/images
+  $ labgrid-client dfu download 1 stm32mp1-tf-a-stm32mp153c-lxa-fairytux2.stm32
+  $ labgrid-client dfu download 3 stm32mp153c-lxa-fairytux2.fip
+  $ labgrid-client dfu detach 0
+
+Then flash the eMMC via Android Fastboot from your development host:
+
+.. code-block:: bash
+
+  $ fastboot flash bbu-mmc stm32mp153c-lxa-fairytux2-emmcboot.img
+
+Now Barebox will start from the eMMC boot partition on future boots.
+
+Flashing the eMMC
+-----------------
+
+When the board is running barebox,
+you can populate the eMMC with the Linux and userspace image with Fastboot:
+
+.. code-block:: bash
+
+  $ fastboot flash mmc1 lxa-fairytux2.hdimg
+
+When Fastboot has finished, type ``boot`` on the Barebox prompt.
+
+Maintenance Status
+------------------

+Pengutronix has at least two board running in a remote lab (labgrid place names
+``gutefee-00001`` (Gen 1) and ``gutefee-00011`` (Gen 2)).
-- 
2.47.3




  parent reply	other threads:[~2026-02-03 17:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-03 17:33 [DistroKit] [PATCH 1/5] v7a: tf-a: version bump v2.12 -> v2.14 Roland Hieber
2026-02-03 17:33 ` [DistroKit] [PATCH 2/5] v7a: tf-a: enable support for LXA FairyTux 2 Roland Hieber
2026-02-03 17:33 ` [DistroKit] [PATCH 3/5] v7a: barebox: " Roland Hieber
2026-02-03 17:33 ` [DistroKit] [PATCH 4/5] v7a: add and enable image generation for the " Roland Hieber
2026-02-03 17:33 ` Roland Hieber [this message]
2026-02-03 17:37   ` [DistroKit] [PATCH] fixup! doc: add FairyTux 2 documentation Roland Hieber

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260203173409.3995749-5-rhi@pengutronix.de \
    --to=rhi@pengutronix.de \
    --cc=a.fatoum@pengutronix.de \
    --cc=distrokit@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox