• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 122 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.

PROCESSOR-SDK-AM64X: Help: Normal Bootflow vs combined Bootflow on TMDS64EVM

Jun Tu
Expert 1570 points
Part Number: PROCESSOR-SDK-AM64X
Other Parts Discussed in Thread: TMDS64EVM

Tool/software:

hI

I am running the TMDS64EVM evaluation board. According to the Bootflow Migration Guide, there are two boot flows: Normal Bootflow and Combined Bootflow.

Could you please advise how to demonstrate or verify that the Normal Bootflow is equivalent to the Combined Bootflow on this board?

How can I prove that the outcome are equivalent? Do you have any supporting documentation, test plans, or register status validation guidelines for this?

Thanks.

Reference: downloads.ti.com/.../BOOTFLOW_MIGRATION_GUIDE.html

  • 0
    TI__Genius 11945 points

    Hi Jun Tu,

    The end goal is to boot all the required images (SBL, SYSFW and BoardCfg). In the normal bootflow, RBL loaded SBL and after that SBL loaded the rest of the images. In the combined bootflow it was changed such that RBL itself loads all three image, so as long as the correct images are booted there should be no issues, and the end goal of loading these images is achieved so in that sense they are equivalent, Let me know if there is any confusion regarding this or if there is something that led you to suspect that the outcome of these 2 bootflows could be different.

    Jun Tu said:
    How can I prove that the outcome are equivalent? Do you have any supporting documentation, test plans, or register status validation guidelines for this?

    As long as the SoC is able to boot the SBL, SYSFW, BoardCfg and all the other subsequent images, you can confirm that a bootflow is working. We have not faced any major issues while booting using the combined bootflow (Combined bootflow was introduced in SDK version 8.4). Let me know if you are facing some problem while booting using this.

    Best Regards,

    Meet. 

  • 0 in reply to Meet Thakar
    Expert 1570 points

    Hi, Meet:

    Both boot modes works perfect fine. I don't have any programing issue. 

    It is all related to documentation and test plan and proof.

    Eg: In ti safety manual, it mentioned that, all those driver or register init by the RBL should be re-initialized by SBL, right?

    "
    Reinitialization by Initial Software As mentioned earlier, it is highly recommended that initial software (secondary boot loader or SBL) re-initializes all the boot ROM specific device initialization. Table 4-1 lists the expectation and behavior of TI provided SW."


    Since it is a black box, do you have a list register, or pheripherals once it reach to sbl main()  in  ospi boot. 

    eg: as far as I know, eg: read basic mpu, read flash memory (peripheral init) shall work, check mpu setting,  check PLL,  is there a guideline for these initial value?

    Thanks.

  • +1 in reply to Jun Tu
    TI__Genius 11945 points

    Hi Jun Tu,

    All the necessary configurations have been done in the SBL example provided in the SDK, you can take the same as the reference.

    Best Regards,
    Meet.