# rtic-rs/rtic

Real-Time Interrupt-driven Concurrency (RTIC) framework for ARM Cortex-M microcontrollers

Repository: https://github.com/rtic-rs/rtic
Canonical: https://ross.abutalabs.com/products/rtic
Homepage: https://rtic.rs
Language: Rust
License: Apache-2.0
License Family: permissive
Topics: rust, no-std, arm, cortex-m, microcontroller, bare-metal, scheduler, concurrency
Last push: 2026-08-25T18:51:09+00:00

## Health v2 (maintenance only)
Score: 77/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 99, release rhythm 35, longevity 100
- inputs: {"age_days": 3468, "days_push": 8, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: no_releases
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 2389, forks 262 (observed 2026-08-28T04:06:43.287081+00:00)

## What it is
RTIC is a hardware-accelerated concurrency framework for building real-time systems on ARM Cortex-M and most RISC-V microcontrollers in Rust. It provides event- and software-triggered tasks, message passing, a timer queue, and compile-time-guaranteed deadlock-free, data-race-free resource sharing with minimal scheduling overhead.

## Use cases
- build a real-time embedded application in Rust on a Cortex-M microcontroller
- implement periodic tasks with a timer queue on bare-metal hardware
- share data between interrupt handlers without data races
- schedule preemptive priority-based tasks with no dynamic allocation
- replace an RTOS with a lightweight no-std task scheduler
- run WCET-analyzable task scheduling on embedded firmware

## When to choose
- you are writing no-std Rust firmware for ARM Cortex-M or supported RISC-V devices
- you need compile-time guarantees against deadlocks and data races
- you want minimal scheduling overhead by leveraging hardware interrupts
- you need a single-stack, allocator-free concurrency model

## When to avoid
- you target non-embedded platforms like Linux or Windows
- you need full RTOS features such as filesystems or networking stacks
- your MCU architecture is not Cortex-M or a supported RISC-V backend
- you prefer async executors like Embassy with async peripheral drivers

## Facets
- artifact type: framework
- maturity: active
- function: concurrency, scheduling, embedded
- domain: embedded-systems, developer-tools
- platform: rust, embedded, cross-platform
- tags: rtos, no-std, cortex-m, bare-metal, interrupt-driven, preemptive-multitasking, risc-v, real-time

## Member repositories
- rtic-rs/rtic (main) score 77

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:06:43.287081+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T02:34:32.535264+00:00, confidence not recorded.
  - readme: https://github.com/rtic-rs/rtic (fetched 2026-08-28T04:06:43.287081+00:00, sha 9a27d6c1cb22)
  - homepage: https://rtic.rs (fetched 2026-08-29T10:15:14.019573+00:00, sha 60c3ee0c41bf)
  - registry_crates: https://crates.io/api/v1/crates/rtic (fetched 2026-08-29T10:15:14.029678+00:00, sha df2f0333f656)
- Data as of 2026-08-30T08:39:29.467469+00:00.