TDA4VM: Linker and link files

Hi Team,

SDK: ti-processor-sdk-rtos-j721e-evm-08_01_00_13

According to the demo ti-processor-sdk-rtos-j721e-evm-08_01_00_13/ti-processor-sdk-rtos-j721e-evm-08_01_00_13/mcusw/mcuss_demos/profiling/can, the customer wants to compile code which can run on MCU3_0 and MCU3_1. Adding the following command to the makefile: 

Command 1:

ifeq ($(CORE),mcu3_0)
    APPEND_LNKCMD_FILE += overrides/$(SOC)/$(CORE)/linker_r5f_mcu3_0_freertos.lds
	APPEND_LNKCMD_FILE += overrides/$(SOC)/$(CORE)/memory_map_ddr.cmd
endif

It reported the following error:

This error indicates that there is no corresponding link file in mcusw /build/j 721e/mcu3_0/. However, in the reference demo, the command is as follows:

ifeq ($(BUILD_OS_TYPE), freertos)
	EXTERNAL_LNKCMD_FILE_LOCAL = overrides/$(SOC)/$(CORE)/linker_r5_freertos.lds
else
	EXTERNAL_LNKCMD_FILE_LOCAL = overrides/$(SOC)/$(CORE)/linker_r5_sysbios.lds
endif

It compiles normally with command 1, and there is no link script for mcu3_0 in the mcusw /build/j 721e/ directory, but it is specified in the overrides/mcu3_0 directory.

1) Where to use these two variables EXTERNAL_LNKCMD_FILE_LOCAL and APPEND_LNKCMD_FILE? 

What is the calling procedure and the difference? If the customer wants to develop other cores, how should the link script be determined?

2) In the mcusw/build/makeruls/env.mk file, what is the purpose of CONFIG_BLD_LNK_r5f and the difference from the above variables? (See figure below) 

Could you please help check this case? Thanks.

Best Regards,

Cherry