Hi Beleswar!
On January 8, 2025 thus sayeth Beleswar Padhi:
Include k3_rproc.env to access rproc boot commands and specify rproc firmware names for adding remoteproc support in J722S SoCs.
Signed-off-by: Beleswar Padhi b-padhi@ti.com
This patch is independent and puts the environment in place to boot remote processors at U-Boot stage.
However, for successfully loading the firmwares into remote cores, rproc DT node definitions are required. These DT changes have been merged into Linux and available with v6.12 tag[0]. Once the DT Sync happens in U-Boot, remote processors can be probed and booted with the help of env commands enabled with this patch.
Sample Boot Test logs after manually adding DT nodes in U-Boot: https://gist.github.com/3V3RYONE/0b5c7df5b5c88d2a2f273b6a04a3dd46
Thanks, Beleswar
board/ti/j722s/j722s.env | 6 ++++++ 1 file changed, 6 insertions(+)
diff --git a/board/ti/j722s/j722s.env b/board/ti/j722s/j722s.env index f8b6aff2c2f..10d62034e1a 100644 --- a/board/ti/j722s/j722s.env +++ b/board/ti/j722s/j722s.env @@ -1,6 +1,10 @@ #include <env/ti/ti_common.env> #include <env/ti/mmc.env>
+#if CONFIG_CMD_REMOTEPROC +#include <env/ti/k3_rproc.env> +#endif
name_kern=Image console=ttyS2,115200n8 args_all=setenv optargs ${optargs} earlycon=ns16550a,mmio32,0x02800000 @@ -13,3 +17,5 @@ mmcdev=1 bootpart=1:2 bootdir=/boot rd_spec=-
+rproc_fw_binaries= 0 /lib/firmware/j722s-mcu-r5f0_0-fw 2 /lib/firmware/j722s-main-r5f0_0-fw 3 /lib/firmware/j722s-c71_0-fw 4 /lib/firmware/j722s-c71_1-fw
For SE devices do these firmware have that *-sig suffix? My thinking is this seems fairly specific to yocto with other distributions like debian or QNX will have different names or paths. Should this be put in the env that yocto builds?
~Bryan