User Tools

Site Tools


reverse_engineering:ghidra:memory_map

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
reverse_engineering:ghidra:memory_map [2022/03/13 15:58]
kitor
reverse_engineering:ghidra:memory_map [2022/03/13 19:47] (current)
kitor [QEMU]
Line 14: Line 14:
  
 Visual explanation may make more sense. Image below contains a complete memory map for EOS R 1.8.0 (7.3.9) ROM. Visual explanation may make more sense. Image below contains a complete memory map for EOS R 1.8.0 (7.3.9) ROM.
-Cacheable RAM mirror on this model is available between ''0x40000000'' and ''0xBFFFFFFF''.+Uncacheable RAM mirror on this model is available between ''0x40000000'' and ''0xBFFFFFFF''.
  
 Because DryOS loads some chunks into locations inside that region (see ''0x40100000'' and ''40700000''), those were added to a memory map first. Because DryOS loads some chunks into locations inside that region (see ''0x40100000'' and ''40700000''), those were added to a memory map first.
Line 54: Line 54:
   * ''count='' is the length of copied data ''0x400''   * ''count='' is the length of copied data ''0x400''
  
-Thus in this example, data from ''0x400'' bytes from ''0xE00088F0'' (''0xE0000000 + 0x88F0'') was copied to ''0xDF001000''+Thus in this example, ''0x400'' data bytes from ''0xE00088F0'' (''0xE0000000 + 0x88F0'') was copied to ''0xDF001000''
  
 === Extracting chunks === === Extracting chunks ===
reverse_engineering/ghidra/memory_map.1647183489.txt.gz ยท Last modified: 2022/03/13 15:58 by kitor