• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 31 subscribers
  • Views 94 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.

AM6422: SBL boot A53, and then A53 app boot another A53 app.

Jun Tu
Expert 1720 points

Part Number: AM6422

Hi, 

From the SBL running on R5F, I can boot an R5F application. I also understand that an R5F application can boot another R5F application, as described in the TI E2E thread 
AM2432: How to boot another appimage from RAM - Arm-based microcontrollers forum - Arm-based microcontrollers - TI E2E support forums 

My question is about a different boot chain:

  1. SBL running on R5F

  2. R5F boots an A53 application

  3. The A53 application then boots another A53 image

Do you think step 3 is feasible/supported on AM64x? Are there any limitations or special considerations for an A53 application booting another A53 image in a no-OS environment?

Thanks. 






  • +1
    TI__Mastermind 22315 points

    Hi,

    This should be possible but there are a few things you need to take care of.

    It is not supported in the default SDK, so this is something that you would need to implement yourself, also bootloader driver on A53 core is not supported in SDK, but you can port it for A53.

    In SBL OSPI example for R5F0-0 we call Bootloader_socCpuResetReleaseSelf at the end to reset and start R5F0-0 application, when using A53 core as the next stage bootloader, you will have to implement this for a53 if you plan to run an application on a53 after the bootloader.

    Best Regards,

    Meet.