reduce size of XIP region

in practice, we're not putting a 128M part out there, but merely
saving space for that amount of memory chews up 32k of page tracking
for something we will never use.

Tune that down to 64M, reducing the overhead to 16k. This also
matches the largest available HyperRam / FLASH part that we might
put into the XIP memory range.
This commit is contained in:
bunnie 2024-05-21 15:59:17 +08:00
parent 8b487361b2
commit 9c90994bd5
3 changed files with 3 additions and 3 deletions

View file

@ -16360,7 +16360,7 @@ soc/candidate/mbox_v0.1.sv]]></description>
<memoryRegion>
<name>XIP</name>
<baseAddress>0x70000000</baseAddress>
<size>0x08000000</size>
<size>0x04000000</size>
</memoryRegion>
<memoryRegion>
<name>PL230</name>

View file

@ -687,7 +687,7 @@ register to disable individual events.]]></description>
<memoryRegion>
<name>XIP</name>
<baseAddress>0x70000000</baseAddress>
<size>0x08000000</size>
<size>0x04000000</size>
</memoryRegion>
<memoryRegion>
<name>VEXRISCV_DEBUG</name>

View file

@ -311,7 +311,7 @@ pub const HW_SRAM_MEM_LEN: usize = 2097152;
pub const HW_RERAM_MEM: usize = 0x60000000;
pub const HW_RERAM_MEM_LEN: usize = 4194304;
pub const HW_XIP_MEM: usize = 0x70000000;
pub const HW_XIP_MEM_LEN: usize = 134217728;
pub const HW_XIP_MEM_LEN: usize = 67108864;
pub const HW_PL230_MEM: usize = 0x40011000;
pub const HW_PL230_MEM_LEN: usize = 4096;
pub const HW_MDMA_MEM: usize = 0x40012000;