• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 303 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: RBL running from dmsc boot flow

Jun Tu
Expert 1640 points

Part Number: PROCESSOR-SDK-AM64X

Tool/software:

I am using a combined boot flow.  SBL is running from R5 single core.  the other core are not used.

Question,

1.In xSPI boot mode,  at which step DMSC  RBL copy the image to MSRAM vis SPI ?   I believe it happened before step  "DMSC Releases Reset to R5 CPU",  

2. since it is combined boot flow, SYSFW should be decrypted and load at above place.  after booted SYSFW and loaded board configuration it will send boot notification.

3.  then R5 start assebmly and boot to main, tjem ot wait for boot notification.


Please confirm

Thanks. 

  • 0
    TI__Genius 16900 points

    Hi Jun Tu,

    Jun Tu said:

    1.In xSPI boot mode,  at which step DMSC  RBL copy the image to MSRAM vis SPI ?   I believe it happened before step  "DMSC Releases Reset to R5 CPU",  

    The image is loaded to On-Chip RAM after DMSC ROM is done with the image verification:

    Jun Tu said:
    2. since it is combined boot flow, SYSFW should be decrypted and load at above place.  after booted SYSFW and loaded board configuration it will send boot notification.

    In the combined bootflow, SBL application loads the SYSFW, so this happens after SBL starts executing on R5, please refer to this link:  https://software-dl.ti.com/mcu-plus-sdk/esd/AM64X/latest/exports/docs/api_guide_am64x/BOOTFLOW_MIGRATION_GUIDE.html

    Jun Tu said:
    3.  then R5 start assebmly and boot to main, tjem ot wait for boot notification.

    Correct.

    Best Regads,

    Meet.

  • 0 in reply to Meet Thakar
    Expert 1640 points

    Where is the On-Chip RAM used by the DMSC? it is not MSRAM, right?

    if SYSFW loaded into MSRAM, what is the beginning location of SYSFW in MSRAM? 

  • 0 in reply to Jun Tu
    Expert 1640 points



    From this map, we found SYSFW is in reserved area of MSRAM.,  but in hs_fs mode, we should use  sysfw-hs-fs-enc.bin, it is more than 128 kb?



    then, I look at the raw image of sysfw in sysfw_hs_fs_signed.h  is   also /* 226964 bytes */

    It won't fit into 128kb, right?

  • 0 in reply to Jun Tu
    Expert 1640 points

    your second point is not right. 

    "in the combined bootflow, SBL application loads the SYSFW, so this happens after SBL starts executing on R5,"

    I believe,  in normal SBL, SBL application loads the SYSFW. 

    in combined bootload, SBL simply wait for boot notification. ROM bootloader loads SYSFW, as below.

    below should be combined boot flow looks like. 



    Thanks

  • +1 in reply to Jun Tu
    TI__Genius 16900 points

    Hi Jun Tu,

    Jun Tu said:
    in combined bootload, SBL simply wait for boot notification. ROM bootloader loads SYSFW, as below.

    Yes, you are correct. Apologies for any confusion caused by this.

    Jun Tu said:
    below should be combined boot flow looks like. 

    This looks correct.

    Jun Tu said:
    From this map, we found SYSFW is in reserved area of MSRAM

    DMSC might use this part of MSRAM during runtime for some tasks (like security handover), but this is not where the syswf binary is loaded. You can find SYSFW load address from the makefile of any sbl example, it is 0x44000.

    Best Regards,

    Meet.

  • 0 in reply to Meet Thakar
    Expert 1640 points

    For sure, how to interpret this start address 0x44000?

    so this address 0x44000 means m3 separate dedicated memory ? right.   it is not meaning address 0x44000 in R5

  • +1 in reply to Jun Tu
    TI__Genius 16900 points
    Jun Tu said:
    so this address 0x44000 means m3 separate dedicated memory

    That is correct, this is for DMSC's internal RAM.