Parts Discussed in Thread: AM62x, AM62Ax, AM62Dx, AM62Px
The primary role of the Device Management (DM) R5F core is to run the DM task. However, there may be other non-DM code running on the DM R5F, alongside the DM task. The firmware running on the DM R5F core is initialized during boot time, either during SPL boot or SBL boot.
For more information about SPL boot and SBL boot, refer to the processor academy > Multicore > Boot flows: SBL vs SBL
AM62x || AM62Ax || AM62Px || AM64x
When using the SBL boot flow, the DM R5F initializes critical parts of the system, including the DM task. The SBL code may either close itself at that point, or it may load a runtime application into the DM R5F. The runtime application is selected based on address instead of being selected by filename. That means that if a runtime application is loaded, then you need to verify what application is flashed to the memory at that address.
Other FAQs
- This FAQ focuses on looking at the SBL build flow and program flow. For more information about how to test the binary that is running on the DM R5F, refer to [FAQ] Linux: How to check what binary is running on the DM R5F
- For information about the SPL bootflow, refer to [FAQ] SPL Boot: How to find the DM R5F binary that is built into tispl.bin
This is a helper FAQ for RE: [FAQ] DM R5F can crash in certain conditions: AM62x, AM62Ax, AM62Dx, AM62Px, AM67, AM67A question "SBL boot: How to find the DM R5F firmware that is loaded by SBL".