• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 100 subscribers
  • Views 232 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.

SK-AM64B: How Memory mapping is done in AM64x

shraddha naik
Intellectual 290 points
Part Number: SK-AM64B

Dear team,

I need to understand the memory mapping done on AM64x series. As i understood, ROM code expects SBL/SPL bootloader at offset 0x0 of eMMC/OSPI, and application image at offset 0x80000 for OSPI & at offset 0x800000 for eMMC.

But for eMMC/OSPI/GPMC memories how memory mapping is done?

  • 0
    TI__Guru** 101030 points

    Hello Shraddha,

    Just to make sure we understand your question. Are you asking specifically about where the ROM code looks for the next boot media for eMMC/OSPI/GPMC? Or are you asking about memory maps later in the boot process, or during runtime?

    For questions about where the ROM code expects code to be, please reference the AM64x Technical Reference Manual (TRM), Section Initialization > Boot Modes > read the sections about the boot modes that you want to learn more about.

    Regards,

    Nick

  • 0 in reply to Nick Saulnier
    Intellectual 290 points

    Hello Nick,

    Actually I wanted to know the memory address assignment for OSPI or eMMC/GPMC. On TRM, its mentioned ROM expects bootloader to be at offset =0x0, & app image at offset 0x80000, so are there any default memory addresses reserved for OSPI or eMMC memory? 

    Regards,

    Shraddha

  • 0 in reply to shraddha naik
    TI__Guru** 101030 points

    Hello Shraddha,

    I am reassigning your thread to another team member to comment. Feel free to ping the thread if you have not received a response within several business days.

    Regards,

    Nick

  • +1 in reply to Nick Saulnier
    TI__Guru* 86180 points

    Section 4.8 in the TRM has more information about the ROM memory map.  eMMC is not memory mapped per se.  This is a block addressable memory which is accessed via a controller which move its contents block by block to another memory (internal or external), so that it can be accesses by one of the processors in the device.  The OSPI is similar, but its controller also has a direct access mode which presents a memory map to the processor and translates that to OSPI commands to access the data on the memory

    Regards,

    James