#nxp #imxrt

no-std imxrt-ral

Register access layer for all NXP i.MX RT microcontrollers

13 releases

0.5.3 Aug 21, 2023
0.5.1 Jul 3, 2023
0.5.0 Dec 27, 2022
0.4.4 Aug 21, 2022
0.1.0 Feb 11, 2020

#102 in Embedded development

Download history 285/week @ 2024-03-13 143/week @ 2024-03-20 128/week @ 2024-03-27 287/week @ 2024-04-03 229/week @ 2024-04-10 123/week @ 2024-04-17 382/week @ 2024-04-24 141/week @ 2024-05-01 894/week @ 2024-05-08 167/week @ 2024-05-15 820/week @ 2024-05-22 429/week @ 2024-05-29 656/week @ 2024-06-05 415/week @ 2024-06-12 726/week @ 2024-06-19 173/week @ 2024-06-26

1,987 downloads per month
Used in 11 crates (7 directly)


664K SLoC


A Rust register access layer (RAL), and SVD patches for NXP i.MX RT processors.

All Checks Crates.io

API Docs (main branch)


  • Simple but useful register level access. It compiles quickly, and it's intuitive for existing embedded developers.
  • RTIC support.

Getting Started

The imxrt-ral is a lower-level interface for i.MX RT processor registers with useful macros. The imxrt-ral is modeled after the stm32ral crate. It provides direct access to the processor's registers. Use the imxrt-ral if you'd like to create your own hardware abstraction layer, or a custom driver.

The imxrt-ral supports these i.MX RT processors:

  • "imxrt1011"
  • "imxrt1015"
  • "imxrt1021"
  • "imxrt1051"
  • "imxrt1052"
  • "imxrt1061"
  • "imxrt1062"
  • "imxrt1064"
  • "imxrt1176_cm4"
  • "imxrt1176_cm7"

The RAL also requires a feature flag to specify the processor variant. The RAL is on crates.io. The RAL provides the "rt" feature flag, and the interrupt table definition, that's used by the HAL.


Why not use svd2rust to generate a crate for register access?

See here and here. svd2rust generates a crate that's nearly 1 million lines of Rust code, and it takes a few minutes to compile. On the other hand, the RAL compiles in a few seconds. Additionally, svd2rust only supports one SVD input, but the RAL auto-generation script accepts multiple SVD inputs, sharing the common peripherals across processor families. This means that we can more easily support all i.MX RT processor variants from a single crate.

Contributing & Development

For contributions and development guidance, see CONTRIBUTING.md


Licensed under either of

at your option.