public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Lothar Rubusch <l.rubusch@gmail.com>
To: u-boot@lists.denx.de, trini@konsulko.com, marex@denx.de,
	simon.k.r.goldschmidt@gmail.com, tien.fong.chee@intel.com
Cc: l.rubusch@gmail.com
Subject: [PATCH 5/9] ARM: socfpga: add Enclustra AA1 demo env files
Date: Thu, 12 Sep 2024 06:06:45 +0000	[thread overview]
Message-ID: <20240912060649.190-6-l.rubusch@gmail.com> (raw)
In-Reply-To: <20240912060649.190-1-l.rubusch@gmail.com>

Provide additional uboot.env text environment files meant as a generic
demo. The default environment uses a uboot.env. The default environment
works somehow. This environment provides better support but only shows
one possible approach used in the Enclustra reference design setups.

Signed-off-by: Lothar Rubusch <l.rubusch@gmail.com>
---
 board/enclustra/mercury_aa1/mercury_aa1.env | 65 +++++++++++++++++++++
 1 file changed, 65 insertions(+)
 create mode 100644 board/enclustra/mercury_aa1/mercury_aa1.env

diff --git a/board/enclustra/mercury_aa1/mercury_aa1.env b/board/enclustra/mercury_aa1/mercury_aa1.env
new file mode 100644
index 0000000000..07b4a95a75
--- /dev/null
+++ b/board/enclustra/mercury_aa1/mercury_aa1.env
@@ -0,0 +1,65 @@
+// SPDX-License-Identifier: GPL-2.0+
+/*
+ * Copyright (C) 2024 Enclustra GmbH
+ * <info@enclustra.com>
+ *
+ * This is an example configuration file for uboot.env generation.
+ *
+ * Given ENV_FAT_FILE defaults to "uboot.env" and ENV_SIZE defaults to 0x80000
+ * (see configuration options). Then adjust the configuration to your needs and
+ * build the a binary .env file as follows
+ * $ ./tools/mkenvimage -s 0x80000 -o uboot.env ./board/enclustra/mercury_aa1/mercury_aa1.env
+ *
+ * NB: Without providing this binary uboot.env the board is supposed to come up
+ * with the generic environment based on the architecture. This can be helpful
+ * when upgrading and/or recuding environments.
+ */
+bitstream_size=0xD00000
+bootargs=earlycon console=ttyS0,115200 rw rootwait root=/dev/mmcblk0p3
+bootargs_qspi=earlycon console=ttyS0,115200 rw root=/dev/ram0
+bootm_size=0x0a000000
+devnum=0
+devtype=mmc
+distro_bootpart=1
+env_size=0x80000
+fdt_addr_r=0x10000000
+fdtfile=system.dtb
+fdtload=
+	load ${devtype} ${devnum}:${distro_bootpart} ${fdt_addr_r} ${bootdir}/${fdtfile};
+	load ${devtype} ${devnum}:${distro_bootpart} ${fdto_addr_r} ${bootdir}/${fdtofile};
+	fdt addr $fdt_addr_r;
+	fdt resize 8192;
+	fdt apply $fdto_addr_r
+fdtload_qspi=
+	sf probe;
+	sf read ${fdt_addr_r} ${qspi_offset_addr_devicetree} ${fdt_size};
+	sf read ${fdto_addr_r} ${qspi_offset_addr_dtoverlay} ${fdto_size};
+	fdt addr ${fdt_addr_r};
+	fdt resize 8192;
+	fdt apply ${fdto_addr_r}
+fdto_addr_r=0x100c0000
+fdtofile=socfpga_enclustra_mercury_sdmmc_overlay.dtbo
+fdto_size=0x40000
+fdt_size=0x40000
+kernel_addr_r=0x11000000
+kernel_size=0x1000000
+qspiboot=source ${scriptaddr}
+qspiload=
+	setenv bootargs ${bootargs_qspi};
+	sf probe;
+	sf read ${scriptaddr} ${qspi_offset_addr_boot_script} ${scriptsize}
+qspi_offset_addr_bitstream=0x300000
+qspi_offset_addr_boot_script=0x200000
+qspi_offset_addr_devicetree=0x280000
+qspi_offset_addr_dtoverlay=0x2c0000
+qspi_offset_addr_kernel=0x1000000
+qspi_offset_addr_rootfs=0x2000000
+qspi_offset_addr_spl=0x0
+qspi_offset_addr_uboot=0x100000
+qspi_offset_addr_uboot_env=0x180000
+rootfs_addr_r=0x12000000
+rootfs_size=0x2000000
+scriptaddr=0x10800000
+scriptsize=0x80000
+spl_size=0x100000
+uboot_size=0x80000
-- 
2.25.1


  parent reply	other threads:[~2024-09-12  6:13 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-12  6:06 [PATCH 0/9] add support for Enclustra Mercury AA1 SoMs Lothar Rubusch
2024-09-12  6:06 ` [PATCH 1/9] doc: board: enclustra: add Enclustra Intel AA1 SoM Lothar Rubusch
2024-09-12 23:01   ` Marek Vasut
2024-09-14 20:08     ` Lothar Rubusch
2024-09-12  6:06 ` [PATCH 2/9] ARM: dts: socfpga: add Enclustra Intel AA1 Lothar Rubusch
2024-09-12 23:02   ` Marek Vasut
2024-09-14 20:14     ` Lothar Rubusch
2024-09-25 22:49     ` Lothar Rubusch
2024-09-26  1:33       ` Marek Vasut
2024-09-26 22:53         ` Lothar Rubusch
2024-09-26 23:13           ` Marek Vasut
2024-09-27 22:47             ` Lothar Rubusch
2024-09-29 15:20               ` Marek Vasut
2024-09-29 19:19                 ` Lothar Rubusch
2024-10-05  1:23                   ` Marek Vasut
2024-10-07 10:20                     ` Sumit Garg
2024-10-07 13:59                       ` Lothar Rubusch
2024-09-12  6:06 ` [PATCH 3/9] ARM: socfpga: add Enclustra AA1 SoM support Lothar Rubusch
2024-09-12 17:45   ` Tom Rini
2024-09-14 20:17     ` Lothar Rubusch
2024-09-16 20:42       ` Tom Rini
2024-09-12  6:06 ` [PATCH 4/9] ARM: socfpga: add Enclustra AA1 extra env settings Lothar Rubusch
2024-09-12  6:06 ` Lothar Rubusch [this message]
2024-09-12  6:06 ` [PATCH 6/9] ARM: socfpga: add Enclustra AA1 boot scripts Lothar Rubusch
2024-09-12  6:06 ` [PATCH 7/9] ARM: socfpga: AA1: support MAC from secure eeprom Lothar Rubusch
2024-09-12  6:06 ` [PATCH 8/9] ARM: socfpga: add si5338 clock generator support Lothar Rubusch
2024-09-12 23:04   ` Marek Vasut
2024-09-14 20:05     ` Lothar Rubusch
2024-09-12  6:06 ` [PATCH 9/9] ARM: socfpga: make AA1 use si5338 clock gen Lothar Rubusch

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=20240912060649.190-6-l.rubusch@gmail.com \
    --to=l.rubusch@gmail.com \
    --cc=marex@denx.de \
    --cc=simon.k.r.goldschmidt@gmail.com \
    --cc=tien.fong.chee@intel.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.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