Memory map and.. mapping on embedded
Posted: Tue Jun 13, 2017 8:19 am
Hi,
When a documentation gives a memory mapping, like this one:
Module Address (It is for Cluster CPU) Size
SRAM A1 0x0000 0000---0x0000 FFFF
SRAM A2 0x0004 4000---0x0004 BFFF
SRAM C 0x0001 0000---0x0001 AFFF
DE De-interlaced 0x0100 0000---0x013F FFFF
SMC
CCU
UART 1
...
DDR-III/LPDDR-II 0x4000 0000---0xBFFF FFFF (this is of interest)
Should I manually map all these or just the ddr3 (ram)?
Those other physical address link to memory mapped devices so they should not generate a page fault on kernel access, right? Because it is not RAM, the CPU automatically manage them (hmmm?)
Not sure on this one.
Please advise!
When a documentation gives a memory mapping, like this one:
Module Address (It is for Cluster CPU) Size
SRAM A1 0x0000 0000---0x0000 FFFF
SRAM A2 0x0004 4000---0x0004 BFFF
SRAM C 0x0001 0000---0x0001 AFFF
DE De-interlaced 0x0100 0000---0x013F FFFF
SMC
CCU
UART 1
...
DDR-III/LPDDR-II 0x4000 0000---0xBFFF FFFF (this is of interest)
Should I manually map all these or just the ddr3 (ram)?
Those other physical address link to memory mapped devices so they should not generate a page fault on kernel access, right? Because it is not RAM, the CPU automatically manage them (hmmm?)
Not sure on this one.
Please advise!