[U-Boot] [PATCH] cmd: spl: provide address and size of prepared FDT in environment

Anatolij Gustschin agust at denx.de
Thu Aug 17 19:01:48 UTC 2017

Writing prepared FDT to persistent storage should be possible in
scripts. Create environment variables containing address and size
of the updated FDT. Scripts can use these variables after running
'spl export fdt ...' command to write the new blob to persistent

Signed-off-by: Anatolij Gustschin <agust at denx.de>
 cmd/spl.c         | 5 +++++
 doc/README.falcon | 7 ++++++-
 2 files changed, 11 insertions(+), 1 deletion(-)

diff --git a/cmd/spl.c b/cmd/spl.c
index 057764a..3a2a15d 100644
--- a/cmd/spl.c
+++ b/cmd/spl.c
@@ -118,6 +118,11 @@ static int spl_export(cmd_tbl_t *cmdtp, int flag, int argc, char * const argv[])
 			printf("Argument image is now in RAM: 0x%p\n",
 				(void *)images.ft_addr);
+			setenv_addr("fdtargsaddr", images.ft_addr);
+			setenv_hex("fdtargslen", fdt_totalsize(images.ft_addr));
+			if (fdt_totalsize(images.ft_addr) >
+				puts("WARN: FDT size > CMD_SPL_WRITE_SIZE\n");
diff --git a/doc/README.falcon b/doc/README.falcon
index e9f8a75..9a7f0bc 100644
--- a/doc/README.falcon
+++ b/doc/README.falcon
@@ -118,7 +118,12 @@ after each run of 'spl export'. Unfortunately the position of temporary
 storage can not be predicted nor provided at commandline, it depends
 highly on your system setup and your provided data (ATAGS or FDT).
 However at the end of an succesful 'spl export' run it will print the
-RAM address of temporary storage.
+RAM address of temporary storage. The RAM address of FDT will also be
+set in the environment variable 'fdtargsaddr', the new length of the
+prepared FDT will be set in the environment variable 'fdtargslen'.
+These environment variables can be used in scripts for writing updated
+FDT to persistent storage.
 Now the user have to save the generated BLOB from that printed address
 to the pre-defined address in persistent storage

More information about the U-Boot mailing list