Because of the holidays, TI E2E™ design support forum responses will be delayed from Dec. 25 through Jan. 2. Thank you for your patience.

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TDA4VM: TIFS loading Question

Part Number: TDA4VM

Hi Expert.

Thanks for your previouse answer.

about TIFS,i have another new questions:

1.tifs.bin is loaded from external media into wakeup domamin internal SRAM.

    -->who can modify tifs? only TI or the user can modify it?if user can moidfy it,where i can get more information about this?

2.if user can modify tifs.bin and tifs.bin is loaed into wakup domain(M3 core) internal SRAM.

   -->what is the size of this internal SRAM? where i can get this informaiton? i did not find wakup domain internal ROM/RAM size information from datasheet.

3.see following picture blue box,address 41C8_0000~41CC_0000 is used by SBL,but from 41C8_2000,it is the location of mcu_1_0 app which shall be loaded by SBL

   -->conflicting usage? or  SYSFW area(41C8_2000~41CC_0000) is released then mcu_1_0 app is loaded?

  • Hi,

        -->who can modify tifs? only TI or the user can modify it?if user can moidfy it,where i can get more information about this?

    The TIFS can not be modified by the customers. They can however work with AutoSAR vendors if they also want HSM functions to run on the M3 core alongside TIFS.

       -->what is the size of this internal SRAM? where i can get this informaiton? i did not find wakup domain internal ROM/RAM size information from datasheet.

    If you have access to the NDA TRM, this can be found in the NDA TRM Table 2-4.

       -->conflicting usage? or  SYSFW area(41C8_2000~41CC_0000) is released then mcu_1_0 app is loaded?

    This region is not used by the SBL at all, you can even have loadable sections of your MCU1_0 application in this region. I will check why is this referred to as SYSFW area in the doc. (this is not right).

    Please refer to the Memory Map Considerations, that is an accurate description.

    Regards

    Karan

  • Hi Karan

    Thanks for your answer.