From: Vignesh Raghavendra <vigneshr@ti.com>
To: u-boot@lists.denx.de
Subject: [PATCH v2 10/12] board: ti: Update AM65x and J721e READMEs for OSPI boot
Date: Tue, 4 Feb 2020 11:09:57 +0530 [thread overview]
Message-ID: <20200204053959.8802-11-vigneshr@ti.com> (raw)
In-Reply-To: <20200204053959.8802-1-vigneshr@ti.com>
Update AM65x and J721e README files with instructions for flashing OSPI
images.
Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
---
board/ti/am65x/README | 55 +++++++++++++++++++++++++++++++++++++++++++
board/ti/j721e/README | 47 ++++++++++++++++++++++++++++++++++++
2 files changed, 102 insertions(+)
diff --git a/board/ti/am65x/README b/board/ti/am65x/README
index 2e3fd9c4a810..86868e8c705f 100644
--- a/board/ti/am65x/README
+++ b/board/ti/am65x/README
@@ -262,6 +262,61 @@ To boot kernel from eMMC, use the following commands:
=> setenv bootpart 0
=> boot
+OSPI:
+-----
+ROM supports booting from OSPI from offset 0x0.
+
+Flashing images to OSPI:
+
+Below commands can be used to download tiboot3.bin, tispl.bin, u-boot.img,
+and sysfw.itb over tftp and then flash those to OSPI at their respective
+addresses.
+
+=> sf probe
+=> tftp ${loadaddr} tiboot3.bin
+=> sf update $loadaddr 0x0 $filesize
+=> tftp ${loadaddr} tispl.bin
+=> sf update $loadaddr 0x80000 $filesize
+=> tftp ${loadaddr} u-boot.img
+=> sf update $loadaddr 0x280000 $filesize
+=> tftp ${loadaddr} sysfw.itb
+=> sf update $loadaddr 0x6C0000 $filesize
+
+Flash layout for OSPI:
+
+ 0x0 +----------------------------+
+ | ospi.tiboot3(512K) |
+ | |
+ 0x80000 +----------------------------+
+ | ospi.tispl(2M) |
+ | |
+ 0x280000 +----------------------------+
+ | ospi.u-boot(4M) |
+ | |
+ 0x680000 +----------------------------+
+ | ospi.env(128K) |
+ | |
+ 0x6A0000 +----------------------------+
+ | ospi.env.backup (128K) |
+ | |
+ 0x6C0000 +----------------------------+
+ | ospi.sysfw(1M) |
+ | |
+ 0x7C0000 +----------------------------+
+ | padding (256k) |
+ 0x800000 +----------------------------+
+ | ospi.rootfs(UBIFS) |
+ | |
+ +----------------------------+
+
+Kernel Image and DT are expected to be present in the /boot folder of UBIFS
+ospi.rootfs just like in SD card case. U-Boot looks for UBI volume named
+"rootfs" for rootfs.
+
+To boot kernel from OSPI, at the U-Boot prompt:
+=> setenv boot ubi
+=> boot
+
UART:
-----
ROM supports booting from MCU_UART0 via X-Modem protocol. The entire UART-based
diff --git a/board/ti/j721e/README b/board/ti/j721e/README
index 5be7d099db96..739d4933fcf3 100644
--- a/board/ti/j721e/README
+++ b/board/ti/j721e/README
@@ -225,3 +225,50 @@ Image formats:
| | Secure config | |
| +-------------------+ |
+-----------------------+
+
+OSPI:
+-----
+ROM supports booting from OSPI from offset 0x0.
+
+Flashing images to OSPI:
+
+Below commands can be used to download tiboot3.bin, tispl.bin, u-boot.img,
+and sysfw.itb over tftp and then flash those to OSPI at their respective
+addresses.
+
+=> sf probe
+=> tftp ${loadaddr} tiboot3.bin
+=> sf update $loadaddr 0x0 $filesize
+=> tftp ${loadaddr} tispl.bin
+=> sf update $loadaddr 0x80000 $filesize
+=> tftp ${loadaddr} u-boot.img
+=> sf update $loadaddr 0x280000 $filesize
+=> tftp ${loadaddr} sysfw.itb
+=> sf update $loadaddr 0x6C0000 $filesize
+
+Flash layout for OSPI:
+
+ 0x0 +----------------------------+
+ | ospi.tiboot3(512K) |
+ | |
+ 0x80000 +----------------------------+
+ | ospi.tispl(2M) |
+ | |
+ 0x280000 +----------------------------+
+ | ospi.u-boot(4M) |
+ | |
+ 0x680000 +----------------------------+
+ | ospi.env(128K) |
+ | |
+ 0x6A0000 +----------------------------+
+ | ospi.env.backup (128K) |
+ | |
+ 0x6C0000 +----------------------------+
+ | ospi.sysfw(1M) |
+ | |
+ 0x7C0000 +----------------------------+
+ | padding (256k) |
+ 0x800000 +----------------------------+
+ | ospi.rootfs(UBIFS) |
+ | |
+ +----------------------------+
--
2.25.0
next prev parent reply other threads:[~2020-02-04 5:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 5:39 [PATCH v2 00/12] TI: AM654/J721e: Add support to boot from OSPI Vignesh Raghavendra
2020-02-04 5:39 ` [PATCH v2 01/12] drivers: Descend to drivers/soc unconditionally Vignesh Raghavendra
2020-06-02 13:46 ` Simon Glass
2020-02-04 5:39 ` [PATCH v2 02/12] ARM: mach-k3: arm64-mmu: map 64bit FSS MMIO space in A53 MMU Vignesh Raghavendra
2020-02-04 5:39 ` [PATCH v2 03/12] ARM: mach-k3: sysfw-loader: Use SPI memmapped addr when loading SYSFW Vignesh Raghavendra
2020-02-04 5:39 ` [PATCH v2 04/12] ARM: dts: k3-am65: Add OSPI DT nodes Vignesh Raghavendra
2020-02-04 5:39 ` [PATCH v2 05/12] ARM: dts: k3-j721e: " Vignesh Raghavendra
2020-02-04 5:39 ` [PATCH v2 06/12] configs: am65x_evm: Setup mtdparts for OSPI Vignesh Raghavendra
2020-02-04 5:39 ` [PATCH v2 07/12] configs: j721e_evm: " Vignesh Raghavendra
2020-02-04 5:39 ` [PATCH v2 08/12] configs: j721e_evm_defconfig: Enable OSPI configs Vignesh Raghavendra
2020-02-04 5:39 ` [PATCH v2 09/12] configs: am65x_evm_defconfig: " Vignesh Raghavendra
2020-02-04 5:39 ` Vignesh Raghavendra [this message]
2020-02-04 5:39 ` [PATCH v2 11/12] configs: ama65x_hs_evm: Enable OSPI related configs Vignesh Raghavendra
2020-02-04 5:39 ` [PATCH v2 12/12] configs: j721e_hs_evm: " Vignesh Raghavendra
2020-02-04 13:36 ` [PATCH v2 00/12] TI: AM654/J721e: Add support to boot from OSPI Andreas Dannenberg
2020-02-23 8:13 ` Lokesh Vutla
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=20200204053959.8802-11-vigneshr@ti.com \
--to=vigneshr@ti.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