Hi Neha,
On Fri, 20 Jan 2023 at 03:19, Neha Malcom Francis n-francis@ti.com wrote:
To remain consistent with the build commands utilised for K3 devices, we add the paths where component binaries are located to BINMAN_INDIRS. Adding SYSFW_PATH for system firmware binaries, SYSFW_HS_INNER_CERT_PATH for HS device certificate and DM for Device Manager firmware. This way, the existing build command does not change even though we migrate to using binman.
Signed-off-by: Neha Malcom Francis n-francis@ti.com
Makefile | 16 ++++++++++++++++ 1 file changed, 16 insertions(+)
diff --git a/Makefile b/Makefile index c568a6e59a..218cb675fc 100644 --- a/Makefile +++ b/Makefile @@ -1317,6 +1317,22 @@ u-boot.ldr: u-boot # Use 'make BINMAN_VERBOSE=3' to set vebosity level default_dt := $(if $(DEVICE_TREE),$(DEVICE_TREE),$(CONFIG_DEFAULT_DEVICE_TREE))
+ifneq ($(SYSFW_PATH),) +override BINMAN_INDIRS += $(dir $(SYSFW_PATH)) +endif
+ifneq ($(SYSFW_HS_PATH),) +override BINMAN_INDIRS += $(dir $(SYSFW_HS_PATH)) +endif
+ifneq ($(SYSFW_HS_INNER_CERT_PATH),) +override BINMAN_INDIRS += $(dir $(SYSFW_HS_INNER_CERT_PATH)) +endif
+ifneq ($(DM),) +override BINMAN_INDIRS += $(dir $(DM)) +endif
quiet_cmd_binman = BINMAN $@ cmd_binman = $(srctree)/tools/binman/binman $(if $(BINMAN_DEBUG),-D) \ $(foreach f,$(BINMAN_TOOLPATHS),--toolpath $(f)) \ -- 2.34.1
Let's try to do this another way as it needs to use a bintool for the tool that you run. See my other comments.
Regards, Simon