<feed xmlns='http://www.w3.org/2005/Atom'>
<title>imxrt-rt/board/src, 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>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>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>Address clippy transmute warnings</title>
<updated>2024-10-16T12:51:14Z</updated>
<author>
<name>Ian McIntyre</name>
<email>me@mciantyre.dev</email>
</author>
<published>2024-10-16T12:51:03Z</published>
<link rel='alternate' type='text/html' href='https://git.mciantyre.dev/imxrt-rs/imxrt-rt/commit/?id=cb3af5ba736443adbf3dbf305f7a95aa23f3d26b'/>
<id>urn:sha1:cb3af5ba736443adbf3dbf305f7a95aa23f3d26b</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Add optional DCD section in linker script</title>
<updated>2023-09-08T23:18:34Z</updated>
<author>
<name>summivox</name>
<email>summivox@gmail.com</email>
</author>
<published>2023-08-21T06:13:59Z</published>
<link rel='alternate' type='text/html' href='https://git.mciantyre.dev/imxrt-rs/imxrt-rt/commit/?id=c6d3bcfb11800c58339037be58fa9935f816f1bb'/>
<id>urn:sha1:c6d3bcfb11800c58339037be58fa9935f816f1bb</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>First commit</title>
<updated>2022-12-02T01:21:05Z</updated>
<author>
<name>Ian McIntyre</name>
<email>ianpmcintyre@gmail.com</email>
</author>
<published>2022-08-02T10:21:12Z</published>
<link rel='alternate' type='text/html' href='https://git.mciantyre.dev/imxrt-rs/imxrt-rt/commit/?id=c7a9b9f3d4b9e71303c7b988d2bd916c2e4df9bc'/>
<id>urn:sha1:c7a9b9f3d4b9e71303c7b988d2bd916c2e4df9bc</id>
<content type='text'>
</content>
</entry>
</feed>
