diff options
| author | Ian McIntyre <me@mciantyre.dev> | 2026-10-26 10:52:57 -0400 |
|---|---|---|
| committer | Ian McIntyre <me@mciantyre.dev> | 2026-11-07 10:20:33 -0500 |
| commit | 1087e9bb7cd31e6fd88532ead08a927168e36de7 (patch) | |
| tree | ea487e5dc1758f959e0ef9859e89b8196678e8ac /.gitignore | |
| parent | f0ef2b86cee6b44e801eb80ba301888a608fdd76 (diff) | |
Zero unallocated memory, too
If the CPU speculates into the RAM we haven't initialized, we can fault
when the ECC controller reports bad data. Didn't have that problem when
blasting all of RAM...
We can use the linker to help us figure out the range of these unused
regions. If we don't need to zero anything, the host emits 0 for the
start and end, skipping the zeroing.
I'm also zeroing the 32 byte reservation at the start of ITCM, along
with any padding introduced before the vector table. With this in place,
the rip_through_ram firmware does not report any exceptions.
Diffstat (limited to '.gitignore')
0 files changed, 0 insertions, 0 deletions
