#rtt #debugging #no-std

no-std rtt-target

Target side implementation of the RTT (Real-Time Transfer) I/O protocol

9 unstable releases

0.5.0 Jan 4, 2024
0.4.0 Mar 3, 2023
0.3.1 Apr 27, 2021
0.3.0 Nov 24, 2020
0.1.1 Apr 19, 2020

#36 in Embedded development

Download history 3382/week @ 2024-03-14 3932/week @ 2024-03-21 3136/week @ 2024-03-28 3408/week @ 2024-04-04 3529/week @ 2024-04-11 3401/week @ 2024-04-18 2722/week @ 2024-04-25 2966/week @ 2024-05-02 3352/week @ 2024-05-09 2875/week @ 2024-05-16 3147/week @ 2024-05-23 3355/week @ 2024-05-30 3207/week @ 2024-06-06 4044/week @ 2024-06-13 3473/week @ 2024-06-20 3141/week @ 2024-06-27

14,246 downloads per month
Used in 72 crates (56 directly)

MIT license

39KB
598 lines

rtt-target

crates.io documentation

Target side implementation of the RTT (Real-Time Transfer) I/O protocol. RTT implements input and output via a debug probe using in-memory ring buffers and polling. This enables debug logging from the microcontroller with minimal delays and no blocking, making it usable even in real-time applications where e.g. semihosting delays cannot be tolerated.

Documentation

Platform support

To use the global rprintln! macro, a platform-specific critical-section implementation is needed for locking.

Output directly to a channel object with write! or the binary write method does not require locking and therefore does not need any platform-specific critical section.

Usage

With a platform-specific critical section in use, printing is as simple as:

use rtt_target::{rtt_init_print, rprintln};

fn main() {
    rtt_init_print!();
    loop {
        rprintln!("Hello, world!");
    }
}

Development

The examples-cortex-m and panic-test crates come with build files for the venerable STM32F103C8xx by default, but can be easily adapted for any chip as they contain only minimal platform-specific runtime code to get fn main to run.

Dependencies

~35KB