• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 584 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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: Communication between DMSC and MCU R5

wei yang
Prodigy 100 points
Part Number: TDA4VM

Hi, Ti

    In tda4 boot flow, i can not find how communicate DMSC and MCU R5(A72).
    I'd like to learn more about what each arrow does and what DMSC will do if an MCU R5 action  fails.

    Reference as follows:

    https://git.ti.com/cgit/ti-u-boot/ti-u-boot/tree/board/ti/j721e/README?h=ti-u-boot-2021.01

    

    Thank you very much for your help.

    Best regards

  • +1
    TI__Guru**** 163100 points

    Hi,

    1) MCU R5 RoM makes use of DMSC RoM services via Secure proxy IPC to authenticate tiboot3.bin & loads on to itself.

    2) R5 SPL fetches the sysfw.itb from the boot media & loads the sysfw tifs binary to DMSC. U-Boot directory file: arch/arm/mach-k3/sysfw-loader.c & function k3_sysfw_loader.

    3) The R5 SPL then extracts the board config data from the sysfw.itb. k3_sysfw_configure_using_fit function in arch/arm/mach-k3/sysfw-loader.c extracts the various config data and implements it.

    4) Finally the R5 SPL loads the ATF(ARM trusted firmware) to 0x70000000 & brings the A72 out of reset & A73 starts executing.

    If no further questions please click on verify answer.

    Best Regards,
    Keerthy