Skip to content
Snippets Groups Projects
Commit 09a17b0d authored by Neha Malcom Francis's avatar Neha Malcom Francis Committed by Tom Rini
Browse files

doc: board: ti: k3: Mention TI_DM argument


Mention TI_DM argument can be used to fetch a custom DM binary in the
A72 build instructions for K3 devices.

Signed-off-by: default avatarNeha Malcom Francis <n-francis@ti.com>
Reviewed-by: default avatarAndrew Davis <afd@ti.com>
Reviewed-by: default avatarManorit Chawdhry <m-chawdhry@ti.com>
parent 3ef977e0
No related branches found
No related tags found
No related merge requests found
...@@ -320,6 +320,13 @@ use the `lite` option. ...@@ -320,6 +320,13 @@ use the `lite` option.
make CROSS_COMPILE=$CC64 BINMAN_INDIRS=$LNX_FW_PATH \ make CROSS_COMPILE=$CC64 BINMAN_INDIRS=$LNX_FW_PATH \
BL31=$TFA_PATH/build/k3/$TFA_BOARD/release/bl31.bin \ BL31=$TFA_PATH/build/k3/$TFA_BOARD/release/bl31.bin \
TEE=$OPTEE_PATH/out/arm-plat-k3/core/tee-raw.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 .. k3_rst_include_end_build_steps_uboot
At this point you should have every binary needed initialize both the At this point you should have every binary needed initialize both the
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment