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.

DRA821U: About the DRA821U Main_R5F and MCU_R5F loading tech?

Part Number: DRA821U

https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j7200/08_00_00_12/exports/docs/psdk_rtos/docs/user_guide/developer_notes_mcu1_0_sysfw.html

Hi,

 This doc is too rough to understand how to load the MAIN R5F vs MCU R5F.

 Do we have a training slide to explain this Clear and SImply?

 Please have the training / slides for these questions need:

   A. How to set the Main / MCU R5F cores in DTSI?

   B. Why we need to load the R5F during the SPL? Is this for letting R5F early booting before the Linux kernel in order for fitting Auto-Motive Car applications?

   C. Can you show a clear chapter from 0 to 100 for letting the user how to config the Main R5F / MCU R5F and let those 4 R5F running together?

BR Rio

  • Why not just let the Developer to build the Main / MCU R5F image, and just simply to put the image onto the lib/firmware?

    Why need the RM/PM/SCI server / client so much things?

    I thought the RM/PM SCI server / client should be a default lib, developer shall no need to touch this area. Right?

  • Hi Rio,

       A. How to set the Main / MCU R5F cores in DTSI?

    Can you check the dts files under arch/arm64/boot/dts/ti/k3-j7200*?


     Do we have a training slide to explain this Clear and SImply?

    No. I believe there is no such training.

       B. Why we need to load the R5F during the SPL? Is this for letting R5F early booting before the Linux kernel in order for fitting Auto-Motive Car applications?

    Because the DMSC RoM brings R5 out  of reset first.

    Check the README under U-Boot directory of PSDKLA: board/ti/j721e/README. This will clear a lot of your doubts w.r.t boot flow.


    Can you show a clear chapter from 0 to 100 for letting the user how to config the Main R5F / MCU R5F and let those 4 R5F running together?

    I did not understand this.

    Why not just let the Developer to build the Main / MCU R5F image, and just simply to put the image onto the lib/firmware?

    Why need the RM/PM/SCI server / client so much things?

    Because after HSM re-architecture we have RM/PM functionality moved from DMSC SYSFW to MCU R5F0 firmware. This will be packed as DM firmware
    in tispl.bin which will be loaded by R5 SPL on to MCU R5F0.

    As I quoted above: Check the README under U-Boot directory of PSDKLA: board/ti/j721e/README. This will clear a lot of your doubts w.r.t boot flow.

    Best Regards,
    Keerthy

  • Hi Keerthy:

    Thanks for the replying.

    1. Both customers and us read  the "Readme as your pointed place".

        So, we still submit many E2E posted for the MCU_R5F, we cannot conclude a solid knowledge by reading the E2E's reply.

    2. ==> Can you check the dts files under arch/arm64/boot/dts/ti/k3-j7200*

       Yes, I ever study the dtsi in that folder you said.

       please read the below E2E I posted.

    https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1035531/j7200xsomxevm-dra821u-ipc-mcu-r5f0_0-mcu-r5f0_1-echo-test-firmware-not-functional/3829664

       My question is:

             If the "k3-j7200-main.dtsi" configured the Main R5F, why TI doesn't put the MCU R5F config in this file?

             And TI puts the MCU R5F config in this file? --> k3-j7200-mcu-wakeup.dtsi

             We all know the  "Low power mode" of J7 is not implemented finished yet, so, this "k3-j7200-mcu-wakeup.dtsi" will take effect?

    BR Rio

         

  •  If the "k3-j7200-main.dtsi" configured the Main R5F, why TI doesn't put the MCU R5F config in this file?

             And TI puts the MCU R5F config in this file? --> k3-j7200-mcu-wakeup.dtsi

    The dts is split as per the domains. Main domain peripherals are in main.dtsi & mcu/wkup domain are in k3-j7200-mcu-wakeup.dtsi.

    Regards,
    Keerthy

  • Hi Rio,

    The dtsi files are like header files. The peripherals are partitioned separately following MCU or MAIN domain, and both the k3-j7200-main.dtsi and k3-j7200-mcu-wakeup.dtsi are included in k3-j7200.dtsi.

    regards

    Suman

  • Hi Rio,

    Please also see the base TI-SCI documentation for you to better understand the foundation pieces of DM/RM/PM.

    https://software-dl.ti.com/tisci/esd/latest/1_intro/TISCI.html

    regards

    Suman 

  • Thanks, Suman, I'm knowing this well after got the training from you, appreciated.