• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 615 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: [TDA4] What's different for u-boot.img between A53 & R5?

Gibbs Shih
Intellectual 760 points
Part Number: TDA4VM

Hi, Expert :

I have download Linux SDK, and I find two u-boot.img in SDK

one is in A53 folder:

ti-processor-sdk-linux-automotive-j7-evm-07_00_01\board-support\u-boot_build\a53\u-boot.img

another one is in R5 Folder :

ti-processor-sdk-linux-automotive-j7-evm-07_00_01\board-support\u-boot_build\r5\u-boot.img


What's the difference between these two u-boot.img? 

And which one for boot in "boot partition" (eMMC/SDCARD)?

If I need to debug u-boot by CCS, What's the file I should load in CCS

Many Thanks

Gibbs

  • 0
    TI__Guru**** 162770 points

    Hi Gibbs,

    The TDA4VM boot flow is here: https://git.ti.com/gitweb?p=ti-u-boot/ti-u-boot.git;a=blob_plain;f=board/ti/j721e/README;hb=HEAD

    So RoM code first gets the MCU R5 out of reset. The binary that contains the R5 SPL is tiboot3.bin. If you see the board-support\u-boot_build\r5 folder:
    you will have tiboot3.bin that contains the R5 SPL.

    As you can see from the above boot flow R5 u-boot.img is never used. R5 SPL loads the tispl.bin which includes OPTEE/ATF & A72 SPL.

    A53 implies A72 on TDA4VM. So once A72 SPL executes then that finally loads the A72 u-boot.img which is under A53 folder.
    In the boot partition You will need 4 binaries: tiboot3.bin, tispl.bin, u-boot.img, sysfw.itb.

    All the 4 binaries mentioned are described very well towards the end of the README link shared above.

    Lastly to debug from CCS for R5 SPL you need to load r5/spl/u-boot-spl.

    Hope it answers all of your questions. Please resolve if no other questions.


    Best Regards,
    Keerthy

  • 0 in reply to Keerthy J
    Intellectual 760 points

    Hi, Keerthy :

    One point makes me a little bit confuse.

    follow your explain :

    >> As you can see from the above boot flow R5 u-boot.img is never used. R5 SPL loads the tispl.bin which includes OPTEE/ATF & A72 SPL.

    Why should me load r5/spl/u-boot-spl for CCS, not a53/spl/u-boot-spl?

    Many Thanks

    Gibbs

  • 0 in reply to Gibbs Shih
    TI__Guru**** 162770 points

    Gibbs Shih said:
    Why should me load r5/spl/u-boot-spl for CCS, not a53/spl/u-boot-spl?

    The first core to boot is R5 so i mentioned you should first load R5 SPL.

    R5 SPL then loads A72 SPL at that point you can load A72 SPL which resides in a53/spl/u-boot-spl.

    Also R5/u-boot.img is not used because R5 SPL itself loads a firmware on to R5 and starts executing that.

    Hope i am clear and you can resolve the issue.

    Best Regards,
    Keerthy