diff options
| author | Ian McIntyre <me@mciantyre.dev> | 2025-04-03 16:44:15 -0400 |
|---|---|---|
| committer | Ian McIntyre <me@mciantyre.dev> | 2026-03-08 10:59:30 -0400 |
| commit | a0dd354bdc299d7d089bd4ed143f6a213852a905 (patch) | |
| tree | 692aa05e756289d5c12638c558f959763615fbff /cmds.gdb | |
| parent | d3fdd76d504622c2e63a8d38b1306fa1abfc86de (diff) | |
Add section for boot ROM reservations
The boot ROM is allowed to use allocations of OCRAM as scratch space. If
you interact with the boot ROM -- using it to interact with FlexSPI, for
instance -- then you cannot also use these OCRAM regions. See the system
boot chapter in the reference manual for more info.
The boot ROM typically reserves the start of OCRAM. The size varies by
chip. This commit describes a new section, .bootrom_reservation, at the
start of OCRAM. Users are encouraged to place a MaybeUninit buffer
that's sized for your ROM's requirements.
If users don't place anything in this section, then the new directive is
a no-op. On the other hand, the section is defined before other RAM
regions, so that it takes precedence over other sections users might
want to place in OCRAM.
Tested using the runtime's test suite. I'm testing with the Teensy 4
binary, since the test suite can support features in this build. The
updated test suite shows that the linker will place the boot ROM
reservation before placing the stack, suggesting that we're respecting
section priority.
Diffstat (limited to 'cmds.gdb')
0 files changed, 0 insertions, 0 deletions
