<feed xmlns='http://www.w3.org/2005/Atom'>
<title>imxrt-rt/board, branch main</title>
<subtitle>Runtime support for i.MX RT MCUs
</subtitle>
<id>https://git.mciantyre.dev/imxrt-rs/imxrt-rt/atom?h=main</id>
<link rel='self' href='https://git.mciantyre.dev/imxrt-rs/imxrt-rt/atom?h=main'/>
<link rel='alternate' type='text/html' href='https://git.mciantyre.dev/imxrt-rs/imxrt-rt/'/>
<updated>2026-11-22T15:47:30Z</updated>
<entry>
<title>Prototype secondary core support</title>
<updated>2026-11-22T15:47:30Z</updated>
<author>
<name>Ian McIntyre</name>
<email>me@mciantyre.dev</email>
</author>
<published>2026-11-21T18:39:55Z</published>
<link rel='alternate' type='text/html' href='https://git.mciantyre.dev/imxrt-rs/imxrt-rt/commit/?id=ea60b60f3ff579cd175abecde49d2d9397420dc0'/>
<id>urn:sha1:ea60b60f3ff579cd175abecde49d2d9397420dc0</id>
<content type='text'>
Haven't tested the included examples on hardware. It's just here so I
can define an inspect_elf test. Out of tree, there's a basic example
on an 1170EVK.
</content>
</entry>
<entry>
<title>Add ECC stress test for 1170EVK testing</title>
<updated>2026-10-27T15:35:22Z</updated>
<author>
<name>Ian McIntyre</name>
<email>me@mciantyre.dev</email>
</author>
<published>2026-10-26T21:53:21Z</published>
<link rel='alternate' type='text/html' href='https://git.mciantyre.dev/imxrt-rs/imxrt-rt/commit/?id=f0ef2b86cee6b44e801eb80ba301888a608fdd76'/>
<id>urn:sha1:f0ef2b86cee6b44e801eb80ba301888a608fdd76</id>
<content type='text'>
A little firmware that you can run on your 11xx with ECC RAM active.
If I'm doing the preloading correctly and considering speculative reads
into unused memory, this test should pass. Right now, it definitely does
not pass, since the __pre_init only (maybe) zeros the program sections.
</content>
</entry>
<entry>
<title>Change how board supports RAM-only programs</title>
<updated>2026-10-27T15:35:22Z</updated>
<author>
<name>Ian McIntyre</name>
<email>me@mciantyre.dev</email>
</author>
<published>2026-10-26T21:10:19Z</published>
<link rel='alternate' type='text/html' href='https://git.mciantyre.dev/imxrt-rs/imxrt-rt/commit/?id=efe328a7bd17df1962a1db2a517c79f1e76a7b05'/>
<id>urn:sha1:efe328a7bd17df1962a1db2a517c79f1e76a7b05</id>
<content type='text'>
Just a refactor inside board. Activate the "ram" feature to target a
RAM-only for your given bord. I'm adding the 1170EVK RAM support.
</content>
</entry>
<entry>
<title>Preload RAM for ECC ciphers</title>
<updated>2026-03-08T18:14:31Z</updated>
<author>
<name>Ian McIntyre</name>
<email>me@mciantyre.dev</email>
</author>
<published>2026-02-11T21:29:27Z</published>
<link rel='alternate' type='text/html' href='https://git.mciantyre.dev/imxrt-rs/imxrt-rt/commit/?id=a9bb416c822d20c1b94fb7b2bfab282d25e11125'/>
<id>urn:sha1:a9bb416c822d20c1b94fb7b2bfab282d25e11125</id>
<content type='text'>
Testing shows that we must blow fuses in order to activate either ECC
engine.  Once the fuse is blown, NXP's boot ROM will enable the ECC
engine. So by the time the reset handler is running, ECC may already
be enabled.

The 32-bit copy loops won't work for initializing ITCM and OCRAM.
Since these bus widths are 64-bit and the ECC is computed over 64
bits, these 32 bit accesses result in a read-modify-write (RMW) on the
underlying interface. If these RAM regions aren't already initialized,
we'll fail an ECC check; the read in RMW compares bogus RAM contents
against a bogus ECC. This seems to dramatically slow down
initialization, or stall it (I've seen the CPU spinning in the boot
ROM).

If we listen to NXP and use 64-bit writes to preload ECC-protected RAM
regions, the 32-bit copy loops will work as expected. Note that we can
still issue 64-bit accesses towards DTCM; they're scattered across the
two 32-bit interfaces. There's an NXP whitepaper [1] describing that.

Once TCM ECC is enabled, we need to tell the TCM interfaces to RMW
smaller accesses. Otherwise, we won't generate correct ciphers. We
also might need to retry operations if there was a correction by the
RAM controller. We can perform these with predicated instructions.
Tested on an 1010EVK, where I used the debugger to show the control
registers weren't touched; and tested on the 1170EVK, with the same
approach showing the expected set bits.

[1]: https://www.nxp.com/docs/en/white-paper/CORTEXM7WP.pdf
[2]: https://www.nxp.com/docs/en/application-note/AN13204.pdf
</content>
</entry>
<entry>
<title>Add section for boot ROM reservations</title>
<updated>2026-03-08T14:59:30Z</updated>
<author>
<name>Ian McIntyre</name>
<email>me@mciantyre.dev</email>
</author>
<published>2025-04-03T20:44:15Z</published>
<link rel='alternate' type='text/html' href='https://git.mciantyre.dev/imxrt-rs/imxrt-rt/commit/?id=a0dd354bdc299d7d089bd4ed143f6a213852a905'/>
<id>urn:sha1:a0dd354bdc299d7d089bd4ed143f6a213852a905</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>Add builder config for boot_header inclusion</title>
<updated>2026-02-15T12:38:37Z</updated>
<author>
<name>Ian McIntyre</name>
<email>me@mciantyre.dev</email>
</author>
<published>2026-02-15T12:38:37Z</published>
<link rel='alternate' type='text/html' href='https://git.mciantyre.dev/imxrt-rs/imxrt-rt/commit/?id=66f3fb862c88ada3fd35e00186376b90fe37154a'/>
<id>urn:sha1:66f3fb862c88ada3fd35e00186376b90fe37154a</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>Allow smaller vector tables in tests</title>
<updated>2025-11-26T15:49:04Z</updated>
<author>
<name>Ian McIntyre</name>
<email>me@mciantyre.dev</email>
</author>
<published>2025-11-26T15:17:14Z</published>
<link rel='alternate' type='text/html' href='https://git.mciantyre.dev/imxrt-rs/imxrt-rt/commit/?id=8b0d5278b0de5254a242f8a356f061949a896161'/>
<id>urn:sha1:8b0d5278b0de5254a242f8a356f061949a896161</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>Prototype API to build runtime in RAM</title>
<updated>2025-11-11T13:24:38Z</updated>
<author>
<name>Ian McIntyre</name>
<email>ianpmcintyre@gmail.com</email>
</author>
<published>2023-03-13T10:50:57Z</published>
<link rel='alternate' type='text/html' href='https://git.mciantyre.dev/imxrt-rs/imxrt-rt/commit/?id=6f5633761528e484e8d0963c7ac59403f7210093'/>
<id>urn:sha1:6f5633761528e484e8d0963c7ac59403f7210093</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>Adopt Rust 2024 edition</title>
<updated>2025-09-16T11:47:23Z</updated>
<author>
<name>Ian McIntyre</name>
<email>me@mciantyre.dev</email>
</author>
<published>2025-06-14T14:16:12Z</published>
<link rel='alternate' type='text/html' href='https://git.mciantyre.dev/imxrt-rs/imxrt-rt/commit/?id=9728ac5305cfe259115858f0bc49985a0ad7cec4'/>
<id>urn:sha1:9728ac5305cfe259115858f0bc49985a0ad7cec4</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>Added in_flash RuntimeBuilder constructor</title>
<updated>2025-03-22T00:04:24Z</updated>
<author>
<name>Sherif A Abdou</name>
<email>sherif_abdou@outlook.com</email>
</author>
<published>2025-02-03T15:22:32Z</published>
<link rel='alternate' type='text/html' href='https://git.mciantyre.dev/imxrt-rs/imxrt-rt/commit/?id=b319d62052d6b553b135837ff8c35ee0c8d475bf'/>
<id>urn:sha1:b319d62052d6b553b135837ff8c35ee0c8d475bf</id>
<content type='text'>
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.
</content>
</entry>
</feed>
