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.

TDA4VH-Q1: How to Guarantee Using Backup Bootmode when Uboot Image is not Complete

Part Number: TDA4VH-Q1
Other Parts Discussed in Thread: TDA4VH

Hi TI Experts,

Customer is working on TDA4VH SDK9.1.

They are using SPL. 

Their primary boot is eMMC and backup boot is DFU.

Currently they have a concern that if their Uboot image is not complete by mistake or due to some reasons, could we guarantee it could use the backup boot automatically or not?

We have studied the TRM about this part, and as you could see the below flow chart. There is a image integrity check, if this is passed, then it will continue using primary boot, if not, then the backup boot will be used.

The question is that could you provide some more details about the image integrity check here please

We need to know is it possible that the image integrity check is passed but actually the uboot image is not complete so that we might be stuck in the primary boot flow and could not reach to the uboot stage.

If this situation happens, what will be your suggestions to make it work?

Thanks a lot!

Kevin

  • Hello,

    Expert is Out of office please expect delay in response till 19th.

    Regards

    Tarun Mukesh

  • Hi Kevin,

    Integrity check validate the hash of the image with the hash present in the certificate.In case of GP device we make use of degenerate RSA keys to sign the image whereas in case of HS-SE device we use root trust keys.

    We need to know is it possible that the image integrity check is passed but actually the uboot image is not complete so that we might be stuck in the primary boot flow and could not reach to the uboot stage.

    The integrity check will only pass if it matches with the hash present in the certificate.

    Regards
    Diwakar