Hi Neha, On 15:12-20231205, Neha Malcom Francis wrote: > Mention TI_DM argument can be used to fetch a custom DM binary in the > A72 build instructions for K3 devices. > > Signed-off-by: Neha Malcom Francis <n-fran...@ti.com> > Reviewed-by: Andrew Davis <a...@ti.com> > --- > doc/board/ti/k3.rst | 7 +++++++ > 1 file changed, 7 insertions(+) > > diff --git a/doc/board/ti/k3.rst b/doc/board/ti/k3.rst > index a127215ce5..f19ee56f29 100644 > --- a/doc/board/ti/k3.rst > +++ b/doc/board/ti/k3.rst > @@ -320,6 +320,13 @@ use the `lite` option. > make CROSS_COMPILE=$CC64 BINMAN_INDIRS=$LNX_FW_PATH \ > BL31=$TFA_PATH/build/k3/$TFA_BOARD/release/bl31.bin \ > TEE=$OPTEE_PATH/out/arm-plat-k3/core/tee-raw.bin > + > +.. note:: > + It is also possible to pick up a custom DM binary by adding TI_DM argument > + pointing to the file. If not provided, it defaults to picking up the DM > + binary from BINMAN_INDIRS. This is only applicable to devices that utilize > + split firmware. > + > .. k3_rst_include_end_build_steps_uboot > > At this point you should have every binary needed initialize both the > -- > 2.34.1 >
For the series Reviewed-by: Manorit Chawdhry <m-chawd...@ti.com> Regards, Manorit