<feed xmlns='http://www.w3.org/2005/Atom'>
<title>imxrt-rt/board/src, branch main</title>
<subtitle>i.MX RT Runtime Support
</subtitle>
<id>https://git.mciantyre.dev/imxrt-rt/atom?h=main</id>
<link rel='self' href='https://git.mciantyre.dev/imxrt-rt/atom?h=main'/>
<link rel='alternate' type='text/html' href='https://git.mciantyre.dev/imxrt-rt/'/>
<updated>2025-11-11T13:24:38+00:00</updated>
<entry>
<title>Prototype API to build runtime in RAM</title>
<updated>2025-11-11T13:24:38+00:00</updated>
<author>
<name>Ian McIntyre</name>
<email>ianpmcintyre@gmail.com</email>
</author>
<published>2023-03-13T10:50:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.mciantyre.dev/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:23+00:00</updated>
<author>
<name>Ian McIntyre</name>
<email>me@mciantyre.dev</email>
</author>
<published>2025-06-14T14:16:12+00:00</published>
<link rel='alternate' type='text/html' href='https://git.mciantyre.dev/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:14+00:00</updated>
<author>
<name>Ian McIntyre</name>
<email>me@mciantyre.dev</email>
</author>
<published>2024-10-16T12:51:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.mciantyre.dev/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:34+00:00</updated>
<author>
<name>summivox</name>
<email>summivox@gmail.com</email>
</author>
<published>2023-08-21T06:13:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.mciantyre.dev/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:05+00:00</updated>
<author>
<name>Ian McIntyre</name>
<email>ianpmcintyre@gmail.com</email>
</author>
<published>2022-08-02T10:21:12+00:00</published>
<link rel='alternate' type='text/html' href='https://git.mciantyre.dev/imxrt-rt/commit/?id=c7a9b9f3d4b9e71303c7b988d2bd916c2e4df9bc'/>
<id>urn:sha1:c7a9b9f3d4b9e71303c7b988d2bd916c2e4df9bc</id>
<content type='text'>
</content>
</entry>
</feed>
