TDA4VM: MCU1_0 reset vectors in ATCM

Which SDK version and which application ?

Regards

Vineet

Hi Vineet,

I use SDK7.0.

Regards!

HJ

Hi Vineet,

The linker file is posted below.

Regards!

HJ

/* linker options */
--fill_value=0
--stack_size=0x2000
--heap_size=0x1000

#define ATCM_START 0x00000000

-e __VECS_ENTRY_POINT

SECTIONS
{
    .vecs       : {
        __VECS_ENTRY_POINT = .;
    } palign(8) > R5F_TCMB0
    .init_text  : {
                     boot.*(.text)
                     *(.text:ti_sysbios_family_arm_MPU_*)
                     *(.text:ti_sysbios_family_arm_v7r_Cache_*)
                  }  > R5F_TCMB0
    .text:xdc_runtime_Startup_reset__I     : {} palign(8) > R5F_TCMB0
    .text       : {} palign(8)   > DDR_MCU1_0
    .cinit      : {} palign(8)   > DDR_MCU1_0
    .bss        : {} align(8)    > DDR_MCU1_0
    .const      : {} palign(8)   > DDR_MCU1_0
    .data       : {} palign(128) > DDR_MCU1_0
    .sysmem     : {} align(8)    > DDR_MCU1_0
    .stack      : {} align(4)    > DDR_MCU1_0
    .bss:taskStackSection > DDR_MCU1_0

    .resource_table : {
        __RESOURCE_TABLE = .;
    } > DDR_MCU1_0_RESOURCE_TABLE

    .bss:ddr_shared_mem     (NOLOAD) : {} > DDR_MCU1_0_LOCAL_HEAP
    .bss:app_log_mem        (NOLOAD) : {} > APP_LOG_MEM
    .bss:tiovx_obj_desc_mem (NOLOAD) : {} > TIOVX_OBJ_DESC_MEM
    .bss:ipc_vring_mem      (NOLOAD) : {} > IPC_VRING_MEM
}

Hi HJ,

Any specific reason to use ATCM and not BTCM? 

Regards,

Brijesh

Hi Brijesh,

In u-boot the ATCM is enabled, hence the application should have its reset vectors in ATCM.I need to have the mcu1_0 reset vectors in ATCM when I try to load mcu1_0 firmware from u-boot.

Regards!

HJ

Hi HJ,

But are you using vision apps? I mean are you building mcu1_0 firmware from vision apps? Then vision apps already puts the init code and reset vectors in the TCMB, i was asking why do you require to change it? 

Regards,

Brijesh

Hi Brijesh,

I use vision apps now.Let me explain it.As for functional safety,R5F mcu 1_0 runs in lock_step.And I think mcu 1_0 firmware should be located in spi flash rather than unstable eMMC.So I want to boot mcu 1_0 firmware from OSPI and other core firmwares from eMMC .But with the SDK7.0, R5 SPL doesn't support loading the R5F firmware from OSPI.So I have to load the mcu 1_0 firmware from u-boot.

Regards!

HJ

Hi HJ,

ok, understood, please rename firmware for mcu1_0, because if you use default firmware, SPL will try to load it from /lib/firmware directory.

Even if uboot is trying to load firmware on mcu1_0, you could still use BTCM, correct? I am trying to understand why you have to change to ATCM. 

Regards,

Brijesh

Hi Brijesh,

Please refer to the FAQ e2e.ti.com/.../3382578 .In u-boot the ATCM is enabled, hence the application should have its reset vectors in ATCM. Booting from anywhere apart from ATCM is not possible in case if the ATCM is enabled.

Regards,

HJ

Also what issue do you see when you put code in ATCM? can you try connecting to mcu1_0 using ccs and configured the code is loaded correctly?

Hi Brijesh,

It stops at 0x00000010 when the code is loaded.It seems that  it fails to load the code .I'm not sure if reset vectors is configured in ATCM correctly.Can you test it in vision apps?

Regards,

HJ

Hi HJ,

Is this thread and https://e2e.ti.com/support/processors/f/791/t/961923 this one talking about the same vision_apps MCU1_0 firmware load from u-boot from SDK7.0?

Regards,

Karan

Hi Karan,

Yes,in fact the two threads are both talking about the same vision_apps MCU1_0 firmware.

Regards,

HJ

Hi Karan,

Thanks for your reply.I will close this post.

Regards,

HJ