• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 253 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-Q1: Cannot understand boot flow

K Kim
Prodigy 70 points
Part Number: TDA4VM-Q1
Other Parts Discussed in Thread: TDA4VM

Tool/software:

Hello

I can't fully understand the boot flow of TDA4VM TISDK. (User Guide Boot Flow)

1. Some arrows exist between DSMC, MCU R5, A72, and others in the flow. But I don't understand what this means.

For example, I guess arrows for "Reset rls" send some signal for resetting the core.

But I don't understand arrows in the Loading process. ("Load and auth tiboot3.bin", "Load system Config data" in R5 SPL)

Who does the loading, and what do these arrows mean? Does it mean "Loading the system config data from MCU R5 and passing it to DMSC"?

2. In "R5 SPL", there is "Start SYSFW" process. Does this mean triggering the start of the system firmware in DMSC or starting R5's system firmware(I'm not sure this exists).?

3. I don't know what "DM fw image" means in MCU R5's last process. Please explain what is loaded to where.

Sorry for asking this raw question. I have read the Technical Reference Manual but do not understand it well due to my lack of knowledge, so I am questioning.

Thanks a lot every time.

  • +1
    TI__Guru 69820 points

    Hi,

    K Kim said:
    1. Some arrows exist between DSMC, MCU R5, A72, and others in the flow. But I don't understand what this means.

    These are communication with other cores. One core depends on other core to perform required operation.

    K Kim said:
    For example, I guess arrows for "Reset rls" send some signal for resetting the core.

    Yes, DMSC core will release reset of MCU R5F.

    K Kim said:
    But I don't understand arrows in the Loading process. ("Load and auth tiboot3.bin", "Load system Config data" in R5 SPL)

    For Authenticating image it needs to check with Secure ROM core (DMSC core).

    K Kim said:
    Who does the loading, and what do these arrows mean? Does it mean "Loading the system config data from MCU R5 and passing it to DMSC"?

    Please refer to Image Formats, what contained in each core.
    https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-sk-tda4vm/09_02_00/exports/docs/linux/Foundational_Components/U-Boot/UG-General-Info.html#image-formats
    System config RM, PM, Board is part of R5F SPL before DM Firmware, For HS (High secure) config it needs SYSFW to authenticate.

    K Kim said:
    2. In "R5 SPL", there is "Start SYSFW" process. Does this mean triggering the start of the system firmware in DMSC or starting R5's system firmware(I'm not sure this exists).?

    It means start triggering the system firmware in DMSC. You could see SYSFW is under DMSC core.

    K Kim said:
    3. I don't know what "DM fw image" means in MCU R5's last process. Please explain what is loaded to where.

    Yes, DM fw image is last firmware running on MCU R5F.
    DM Firmware is Device manager for RM (Resource) and PM (Power) management for self and other cores, along with application required to run on MCU1_0.  Default IPC echo test example runs along device manager on MCU R5F.

    Best Regards,
    Sudheer