• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Subscribers 31 subscribers
  • Views 387 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.

Original question:

AM2434: have send errors when doing UART boot on custom board

AM2434: sbl_opsi stuck at Sciclient_waitForBootNotfication() when booting from ospi

Hang Yang
Intellectual 2656 points
Part Number: AM2434
Other Parts Discussed in Thread: SYSCONFIG

Hi BU experts,

My customer have another issue after they used the work-around in the related thread. Customer is now trying to flash a hallow world example following the guide AM243x MCU+ SDK: Flashing Tools (ti.com)

The python script is successful, however the sbl stuck atSciclient_waitForBootNotfication() when they power-on the board (custom board) again.

Following are the spot where they stuck and the serial outputs:

And following is their cfg for the python script:

Note that they've change the sbl_ospi like they did to sbl_null for the reasons mentioned in the related thread, which includes removing EMMC adding UDMA.

Any idea what might be the cause?

Thanks,

Hang.

  • 0
    TI__Guru 69061 points

    Hi Hang,

    I see some inconsistency in the issue. This is because if the SBL is really stuck in `Sciclient_waitForBootNotfication()` then there will be no logs at all on the UART console since the function call `Sciclient_waitForBootNotfication()` is at the very start of the main function before any logs statements.

    So, I would like you to confirm once what really is the issue here?

    Regards,

    Prashant

  • 0 in reply to Prashant Shivhare
    TI__Intellectual 2656 points

    Hi Prashant,

    Sorry for the confusion I've caused.  The UART console is the latest status, customer has passed Sciclient_waitForBootNotfication().

    Regards,

    Hang.

  • +1 in reply to Hang Yang
    TI__Guru 69061 points

    Hi Hang,

    Thank you for the clarfication.

    So, the issue is about the "Some tests have failed!!" error. Can you please ask the customer if this error is coming on each POR or randomly?

    Additionally, can you also ask the customer to check the "Disable Auth For Application Image" option in the Sysconfig of SBL OSPI as shown below and see if that boots the application correctly.

    Regards,

    Prashant

  • 0 in reply to Prashant Shivhare
    TI__Intellectual 2656 points

    Hi Prashant,

    Checking this option solved the problem, many thanks?

    Additionally, Customer would like to know what exactly is disabled here. Can they do something to the image so that the Auth can success?

    Thanks,

    Hang.

  • 0 in reply to Hang Yang
    TI__Guru 69061 points

    Hi Hang,

    Hang Yang said:
    Additionally, Customer would like to know what exactly is disabled here. Can they do something to the image so that the Auth can success?

    Checking that option disables the Authentication of the appimage. If this option is checked, the SBL at runtime does not request for authentication of the appimage and directly boots it.

    Since, the error "Some tests have failed!!" goes away on checking that option, it means the error was due to the Authentication failure.

    The customer can continue the development with the authentication of the appimage disabled, it is however not recommeded to disable the authentication in production stage. In production, we would ideally want to first authenticate the appimage to make sure the appimage is legit & can be trusted before booting it. This is the primary purpose of using HS devices.

    Regards,

    Prashant

  • 0 in reply to Prashant Shivhare
    TI__Intellectual 2656 points

    Hi Prashant,

    Thanks for answering.

    Prashant Shivhare said:
    In production, we would ideally want to first authenticate the appimage to make sure the appimage is legit & can be trusted before booting it. This is the primary purpose of using HS devices.

    I think that's what customer wants too, is there any document on how to authenticate the appimage?

    Thanks,

    Hang.

  • 0 in reply to Hang Yang
    TI__Guru 69061 points

    Hi Hang,

    Hang Yang said:
    I think that's what customer wants too, is there any document on how to authenticate the appimage?

    For HS devices, the SBL by default authenticates the appimage before booting it. As I said earlier, the option "Disable Auth For Appimage Image" if checked results in the skipping of the authentication of the appimage. If kept unchecked, which is the default, the SBL authenticates the appimage before booting.

    Regards,

    Prashant

  • 0 in reply to Prashant Shivhare
    TI__Intellectual 2656 points

    Hi Prashant,

    Sorry for the confusion, I am asking what needs to be done to the appimage so that the authentication in the sbl can success and we don't need to disable it? 

    Thanks,

    Hang.

  • 0 in reply to Hang Yang
    TI__Guru 69061 points

    Hi Hang,

    That makes sense. Can you please ask the customer to run the OSPI at lower frequency 133333333 instead of the default 166666666 in SBL OSPI Sysconfig like shown below and see if that resolves the issue.

    Regards,

    Prashant