From: Nishanth Menon <nm@ti.com>
To: Siddharth Vadapalli <s-vadapalli@ti.com>
Cc: <trini@konsulko.com>, <sjg@chromium.org>, <afd@ti.com>,
<vigneshr@ti.com>, <u-boot@lists.denx.de>, <dannenberg@ti.com>,
<srk@ti.com>
Subject: Re: [PATCH 00/10] Add support for Ethernet Boot on SK-AM62
Date: Fri, 12 Jan 2024 06:32:31 -0600 [thread overview]
Message-ID: <20240112123231.ivvcnryppxuqi5jr@sequel> (raw)
In-Reply-To: <20240112064759.1801600-1-s-vadapalli@ti.com>
On 12:17-20240112, Siddharth Vadapalli wrote:
> Hello,
>
> This series enables Ethernet Boot on SK-AM62 device.
> Product Link: https://www.ti.com/tool/SK-AM62
> User Guide: https://www.ti.com/lit/pdf/spruj40
>
> Ethernet Boot flow is as follows:
> 1. The BOOT MODE pins are configured for Ethernet Boot.
> 2. On powering on the device, ROM uses the Ethernet Port corresponding
> to CPSW3G's MAC Port 1 to transmit "TI K3 Bootp Boot".
> 3. The TFTP server and DHCP server on the receiver device need to be
> configured such that VCI string "TI K3 Bootp Boot" maps to the file
> "tiboot3.bin" and the TFTP server should be capable of transferring
> it to the device.
> 4. ROM loads and executes "tiboot3.bin" provided by the TFTP server.
> 5. The "tiboot3.bin" file is expected to be built using the config:
> am62x_evm_r5_ethboot_defconfig
> introduced in this series, which shall enable "tispl.bin" to be fetched
> over TFTP using "tiboot3.bin".
> 6. "tiboot3.bin" is configured to transmit "AM62X U-Boot R5 SPL" as its
> NET_VCI_STRING, thereby implying that the DHCP server and TFTP server
> need to be configured to transfer "tispl.bin" to the device.
> 7. "tiboot3.bin" loads and executes "tispl.bin" provided by the TFTP
> server.
> 8. The "tispl.bin" file is expected to be built using the config:
> am62x_evm_a53_defconfig
> which has been updated in this series to enable Ethernet Boot specific
> configs, allowing "u-boot.img" to be fetched over TFTP using
> "tispl.bin".
> 9. "tispl.bin" is configured to transmit "AM62X U-Boot A53 SPL" as its
> NET_VCI_STRING. The DHCP server and TFTP server need to be configured to
> transfer "u-boot.img" to the device for the aforementioned NET_VCI_STRING.
> 10. "tispl.bin" then fetches "u-boot.img" using TFTP and loads and
> executes it on the device, completing the process of Ethernet Boot on the
> device.
>
> NOTE: ROM configures CPSW3G's MAC Port 1 for 100 Mbps full-duplex mode
> of operation due to which it is expected that the Link Partner also
> supports the same mode of operation.
> Additionally, enabling "phy_gmii_sel" node at SPL stage will be
> necessary and is not added as a part of this series with the aim of
> adding the "bootph-all" property to its counterpart in Linux device-tree
> first.
NAK - instead of writing all this up in the commit message, why would
you not spend that time updating the excellent documentation we have?
>
> This series is based on commit:
> f28a77589e Merge tag 'dm-next-7jan23' of https://source.denx.de/u-boot/custodians/u-boot-dm into next
> of the next branch of u-boot.
>
> Regards,
> Siddharth.
>
> Andreas Dannenberg (1):
> arm: mach-k3: am62: Update SoC autogenerated data to enable Ethernet
> Boot
>
> Kishon Vijay Abraham I (7):
> board: ti: am62x: Init DRAM size in R5/A53 SPL
> firmware: ti_sci: Add No-OP for "RX_FL_CFG"
> soc: ti: k3-navss-ringacc: Initialize base address of ring cfg
> registers
> dma: ti: k3-udma: Add support for native configuration of chan/flow
> arm: mach-k3: am625_init: Probe AM65 CPSW NUSS
> configs: am62: Add configs for enabling ETHBOOT in R5SPL
> configs: am62x_evm_a53_defconfig: Enable configs required for Ethboot
>
> Siddharth Vadapalli (1):
> arm: dts: k3-am625-r5-sk: Enable DM services for main_pktdma
>
> Vignesh Raghavendra (1):
> soc: ti: k3-navss-ringacc: Fix reset ring API
>
> arch/arm/dts/k3-am625-r5-sk.dts | 5 ++
> arch/arm/mach-k3/am625_init.c | 10 +++
> arch/arm/mach-k3/r5/am62x/clk-data.c | 79 ++++++++--------
> board/ti/am62x/evm.c | 3 +
> configs/am62x_evm_a53_defconfig | 8 ++
> configs/am62x_evm_r5_ethboot_defconfig | 110 +++++++++++++++++++++++
> drivers/dma/ti/k3-udma.c | 6 ++
> drivers/firmware/ti_sci.c | 8 +-
> drivers/soc/ti/k3-navss-ringacc-u-boot.c | 9 +-
> drivers/soc/ti/k3-navss-ringacc.c | 7 +-
> 10 files changed, 202 insertions(+), 43 deletions(-)
> create mode 100644 configs/am62x_evm_r5_ethboot_defconfig
>
> --
> 2.34.1
>
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
next prev parent reply other threads:[~2024-01-12 12:32 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-12 6:47 [PATCH 00/10] Add support for Ethernet Boot on SK-AM62 Siddharth Vadapalli
2024-01-12 6:47 ` [PATCH 01/10] board: ti: am62x: Init DRAM size in R5/A53 SPL Siddharth Vadapalli
2024-01-12 12:26 ` Nishanth Menon
2024-01-12 12:31 ` Siddharth Vadapalli
2024-01-12 12:40 ` Nishanth Menon
2024-01-12 13:26 ` Tom Rini
2024-01-15 8:12 ` Siddharth Vadapalli
2024-01-20 16:41 ` Tom Rini
2024-01-22 4:41 ` Siddharth Vadapalli
2024-04-03 12:48 ` Chintan Vankar
2024-04-11 22:07 ` Tom Rini
2024-04-16 12:22 ` Chintan Vankar
2024-04-16 17:00 ` Tom Rini
2024-04-17 7:50 ` Chintan Vankar
2024-04-17 12:18 ` Sughosh Ganu
2024-04-17 16:04 ` Tom Rini
2024-04-18 10:38 ` Chintan Vankar
2024-04-18 12:00 ` Sughosh Ganu
2024-04-19 10:34 ` Chintan Vankar
2024-04-19 11:34 ` Sughosh Ganu
2024-04-19 11:52 ` Chintan Vankar
2024-04-19 12:00 ` Sughosh Ganu
2024-04-18 18:13 ` Tom Rini
2024-04-22 11:16 ` Chintan Vankar
2024-04-22 15:03 ` Tom Rini
2024-01-12 6:47 ` [PATCH 02/10] firmware: ti_sci: Add No-OP for "RX_FL_CFG" Siddharth Vadapalli
2024-01-12 6:47 ` [PATCH 03/10] soc: ti: k3-navss-ringacc: Initialize base address of ring cfg registers Siddharth Vadapalli
2024-01-16 11:43 ` Roger Quadros
2024-04-24 12:52 ` Chintan Vankar
2024-01-12 6:47 ` [PATCH 04/10] soc: ti: k3-navss-ringacc: Fix reset ring API Siddharth Vadapalli
2024-01-12 6:47 ` [PATCH 05/10] dma: ti: k3-udma: Add support for native configuration of chan/flow Siddharth Vadapalli
2024-01-12 6:47 ` [PATCH 06/10] arm: mach-k3: am62: Update SoC autogenerated data to enable Ethernet Boot Siddharth Vadapalli
2024-01-12 12:28 ` Nishanth Menon
2024-01-12 6:47 ` [PATCH 07/10] arm: mach-k3: am625_init: Probe AM65 CPSW NUSS Siddharth Vadapalli
2024-01-12 12:30 ` Nishanth Menon
2024-01-22 10:19 ` Chintan Vankar
2024-01-23 20:57 ` Nishanth Menon
2024-02-27 11:24 ` Chintan Vankar
2024-01-12 6:47 ` [PATCH 08/10] configs: am62: Add configs for enabling ETHBOOT in R5SPL Siddharth Vadapalli
2024-01-12 12:31 ` Nishanth Menon
2024-01-12 12:38 ` Siddharth Vadapalli
2024-01-12 6:47 ` [PATCH 09/10] configs: am62x_evm_a53_defconfig: Enable configs required for Ethboot Siddharth Vadapalli
2024-01-12 12:33 ` Nishanth Menon
2024-01-12 12:39 ` Siddharth Vadapalli
2024-01-12 6:47 ` [PATCH 10/10] arm: dts: k3-am625-r5-sk: Enable DM services for main_pktdma Siddharth Vadapalli
2024-01-12 12:32 ` Nishanth Menon [this message]
2024-01-12 12:36 ` [PATCH 00/10] Add support for Ethernet Boot on SK-AM62 Siddharth Vadapalli
2024-01-12 12:42 ` Nishanth Menon
2024-01-12 12:47 ` Siddharth Vadapalli
2024-01-12 13:01 ` Nishanth Menon
2024-01-15 8:16 ` Siddharth Vadapalli
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=20240112123231.ivvcnryppxuqi5jr@sequel \
--to=nm@ti.com \
--cc=afd@ti.com \
--cc=dannenberg@ti.com \
--cc=s-vadapalli@ti.com \
--cc=sjg@chromium.org \
--cc=srk@ti.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=vigneshr@ti.com \
/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