| Age | Commit message (Collapse) | Author |
|
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.
|
|
To form a secondary image, use in_flash to position it in flash, then
override the default setting that disables the boot header.
With proper configuration, NXP's boot ROM can load a backup image. This
commit reconfigures the 1170EVK board for the experiment.
|
|
The vector tables exported by imxrt-ral are smaller than the default
cortex-m-rt vector table. The tests fail once we enable the rt / device
features. With this change, we expect the MCU-dependent vector table sizes.
|
|
Just a proof-of-concept. The new inspect_elf test seems to show that
we're building the correct image. We need another commit in order to
help the program run in FlexRAM.
|
|
I'm considering this a breaking change. I'll try to introduce new
sections that rely on the user's `unsafe` keyword for linker placement.
Rust 2024 has different opinions on format, and clippy has new thoughts.
Let's adopt them.
|
|
Applications linked through this builder can be placed in a flash
reservation. You'll need some other software to launch these programs,
since they lack the boot header required by the NXP boot ROM.
|
|
|
|
If you define a runtime, you can call `stack_size_env_override` to
define an optional environment variable checked by the runtime builder.
Same goes for the heap. A user can set these environment variables to
override the runtime's stack / heap size. You can use this package's
examples to try it out; see the updated build script.
There's no default environment variable for either memory region. The
package that defines the runtime needs to opt-in to this feature.
|
|
Users can define their device configuration data (DCD), and place the
data in the .dcd section. If the .dcd section has content, the entry in
the IVT points at the user's DCD. This plays well with imxrt-dcd.
|
|
|