<feed xmlns='http://www.w3.org/2005/Atom'>
<title>imxrt-rt/CHANGELOG.md, 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>Align all sections to 8 bytes minimum</title>
<updated>2026-10-27T15:18:02Z</updated>
<author>
<name>Ian McIntyre</name>
<email>me@mciantyre.dev</email>
</author>
<published>2026-10-24T10:38:12Z</published>
<link rel='alternate' type='text/html' href='https://git.mciantyre.dev/imxrt-rs/imxrt-rt/commit/?id=5ad4b42b4bd810eecf47d3a13853658ffb263a16'/>
<id>urn:sha1:5ad4b42b4bd810eecf47d3a13853658ffb263a16</id>
<content type='text'>
8 byte alignment means we can perform per-section ECC RAM preloading,
usually requiring 64-bit accesses.
</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>Restrict RAM if ECC is enabled</title>
<updated>2026-03-08T18:12:21Z</updated>
<author>
<name>Ian McIntyre</name>
<email>me@mciantyre.dev</email>
</author>
<published>2026-02-09T22:04:50Z</published>
<link rel='alternate' type='text/html' href='https://git.mciantyre.dev/imxrt-rs/imxrt-rt/commit/?id=57978b04a7e141e0f34bc24088771a6fedea634e'/>
<id>urn:sha1:57978b04a7e141e0f34bc24088771a6fedea634e</id>
<content type='text'>
As of this commit, the RuntimeBuilder only limits the available OCRAM
if either ECC controller is enabled. It's misleading; however, it gives
users a chance to evaluate their firmware builds with the restricted
RAM regions. I'll add and test the controller setups in a later commit.

Existing tests still pass. New unit tests demonstrate the restricted
RAM behavior.
</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>Relax cortex-m-rt version specification</title>
<updated>2026-02-19T11:34:37Z</updated>
<author>
<name>Rock Boynton</name>
<email>rboynton@anduril.com</email>
</author>
<published>2026-02-17T19:46:34Z</published>
<link rel='alternate' type='text/html' href='https://git.mciantyre.dev/imxrt-rs/imxrt-rt/commit/?id=d3fdd76d504622c2e63a8d38b1306fa1abfc86de'/>
<id>urn:sha1:d3fdd76d504622c2e63a8d38b1306fa1abfc86de</id>
<content type='text'>
cortex-m-rt v0.7.3 and earlier didn't document support for custom linker
scripts. Without that, I figured we were relying on an implementation
detail, and a patch version bump could break dependents. Pinning the
version avoided that possibility.

Now that there's documented support for custom scripts, we can relax
that.
</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>Let users change name of included device.x file</title>
<updated>2025-11-26T15:49:04Z</updated>
<author>
<name>Ian McIntyre</name>
<email>me@mciantyre.dev</email>
</author>
<published>2025-11-26T14:22:06Z</published>
<link rel='alternate' type='text/html' href='https://git.mciantyre.dev/imxrt-rs/imxrt-rt/commit/?id=eb47674359ea27cc5e7824a234067491ff01ab13'/>
<id>urn:sha1:eb47674359ea27cc5e7824a234067491ff01ab13</id>
<content type='text'>
Alternate PAC designs might describe the device file with a custom / chip
specific name. This change lets users specify which linker script they're
using.
</content>
</entry>
<entry>
<title>Add builder API for FlexRAM bank layout</title>
<updated>2025-11-22T16:20:32Z</updated>
<author>
<name>Ian McIntyre</name>
<email>me@mciantyre.dev</email>
</author>
<published>2025-11-09T16:53:17Z</published>
<link rel='alternate' type='text/html' href='https://git.mciantyre.dev/imxrt-rs/imxrt-rt/commit/?id=c4ee315a20e41c234d2d0f7ca3ed7e37a09b9d32'/>
<id>urn:sha1:c4ee315a20e41c234d2d0f7ca3ed7e37a09b9d32</id>
<content type='text'>
The layout, or assignment of FlexRAM banks to memory regions, is more
precise than the count. When a user specifies the count, we still apply
the same layout as we always have. But now, by default, we prefer the
fuse layout for users who have made no choice.

This commit supports RAM loading with probe-rs. After probe-rs resets
the MCU and uses the fuse FlexRAM layout, firmware can perfectly match
that layout without disrupting the data already copied into RAM by the
debugger.
</content>
</entry>
<entry>
<title>Reserve address 0 by shifting ITCM start address</title>
<updated>2025-09-09T12:55:06Z</updated>
<author>
<name>Ian McIntyre</name>
<email>me@mciantyre.dev</email>
</author>
<published>2025-09-09T12:29:25Z</published>
<link rel='alternate' type='text/html' href='https://git.mciantyre.dev/imxrt-rs/imxrt-rt/commit/?id=ce97696bcd4515b5b2556163aa50c1b4723e7c0f'/>
<id>urn:sha1:ce97696bcd4515b5b2556163aa50c1b4723e7c0f</id>
<content type='text'>
The runtime previously allowed function placement at address 0 in ITCM.
However, if you ever formed a pointer to the function placed there, it
would look like a null pointer. And you would never be able to call that
function if you relied on null pointer optimization. Also, most MCU
reference manuals (RM) recommend against this placement.

This commit reduces the total capacity of ITCM by 32 bytes, the smallest
possible size of a MPU region. Note that this is greater than the RM's
recommendation of a four byte reservation. It affects all supported
MCUs, except the 1180. If you're so inclined, your MPU could disallow
loads, stores, and execution from this reservation.

Revised unit tests should cover this change. Additionally, you can
manually verify that the ITCM region lengths are reduced by 32 bytes by
opening the linker scripts generated by the ELF test suite.
</content>
</entry>
</feed>
