#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

#55 in Embedded development

Download history 4546/week @ 2024-02-26 5308/week @ 2024-03-04 4031/week @ 2024-03-11 3704/week @ 2024-03-18 3316/week @ 2024-03-25 3277/week @ 2024-04-01 3730/week @ 2024-04-08 3396/week @ 2024-04-15 3045/week @ 2024-04-22 3011/week @ 2024-04-29 2754/week @ 2024-05-06 3444/week @ 2024-05-13 3008/week @ 2024-05-20 3442/week @ 2024-05-27 2825/week @ 2024-06-03 3846/week @ 2024-06-10

13,312 downloads per month
Used in 71 crates (55 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