From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Sat, 12 Oct 2019 16:25:46 -0400 Subject: [U-Boot] [PATCH v2 19/26] env: ti: am65x_evm: Add env support to boot the MCU R5F rprocs In-Reply-To: <20190904103151.20121-20-lokeshvutla@ti.com> References: <20190904103151.20121-1-lokeshvutla@ti.com> <20190904103151.20121-20-lokeshvutla@ti.com> Message-ID: <20191012202546.GF16029@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Wed, Sep 04, 2019 at 04:01:44PM +0530, Lokesh Vutla wrote: > From: Suman Anna > > Add support to boot the MCU domain R5F Core0 remoteproc at U-boot prompt > on the AM65x EVM boards by using the 'boot_rprocs' and other env variables > defined in the common environment file k3_rproc.h, and updating the > 'DEFAULT_RPROCS' macro. > > The default configuration is to use the MCU R5F in Split mode, so both > the R5F Core0 and Core1 are started before loading and booting the Linux > kernel using the following firmware: > MCU R5FSS0 Core0 (Split) : 0 /lib/firmware/am65x-mcu-r5f0_0-fw > MCU R5FSS0 Core1 (Split) : 1 /lib/firmware/am65x-mcu-r5f0_1-fw > > The MCU R5FSS was initially running the R5 SPL in LockStep mode with ATCM > disabled, and is actually shutdown to enable it to be reconfigured and > booted by either A53 U-Boot or Linux kernel in remoteproc mode and using > ATCM. > > The MCU R5FSS would need to be reconfigured for Lockstep mode through > DT if a fault-tolerant/safety application were to be run on the cluster > with the DEFAULT_RPROCS macro updated to remove the Core1 firmware. > > Signed-off-by: Suman Anna > Signed-off-by: Lokesh Vutla Applied to u-boot/master, thanks! -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: