From 99e828b7dc0ec8454bf82e6b2f14638bb3abfe81 Mon Sep 17 00:00:00 2001 From: Alex Touchet Date: Mon, 27 Mar 2023 13:24:50 -0700 Subject: [PATCH] Fix crates.io badges --- README.md | 2 +- panic-rtt-target/README.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 91da7c8..93bf872 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,6 @@ # rtt-target -[![crates.io](https://meritbadge.herokuapp.com/rtt-target)](https://crates.io/crates/rtt-target) [![documentation](https://docs.rs/rtt-target/badge.svg)](https://docs.rs/rtt-target) +[![crates.io](https://img.shields.io/crates/v/rtt-target.svg)](https://crates.io/crates/rtt-target) [![documentation](https://docs.rs/rtt-target/badge.svg)](https://docs.rs/rtt-target) 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. diff --git a/panic-rtt-target/README.md b/panic-rtt-target/README.md index b6bbf8f..a7f0b7e 100644 --- a/panic-rtt-target/README.md +++ b/panic-rtt-target/README.md @@ -1,6 +1,6 @@ # panic-rtt-target -[![crates.io](https://meritbadge.herokuapp.com/panic-rtt-target)](https://crates.io/crates/panic-rtt-target) [![documentation](https://docs.rs/panic-rtt-target/badge.svg)](https://docs.rs/panic-rtt-target) +[![crates.io](https://img.shields.io/crates/v/panic-rtt-target.svg)](https://crates.io/crates/panic-rtt-target) [![documentation](https://docs.rs/panic-rtt-target/badge.svg)](https://docs.rs/panic-rtt-target) Logs panic messages over RTT. A companion crate for rtt-target. @@ -10,7 +10,7 @@ RTT must have been initialized by using one of the `rtt_init` macros. Otherwise Panics are always logged on channel 0. Upon panicking the channel mode is also automatically set to `BlockIfFull`, so that the full message will always be logged. If the code somehow manages to panic at runtime before RTT is initialized (quite unlikely), or if channel 0 doesn't exist, nothing is logged. -The panic handler runs in a non-returning [critical_section](https://docs.rs/critical-section/latest/critical_section/) which implementation should be provided by the user. +The panic handler runs in a non-returning [critical_section](https://docs.rs/critical-section) which implementation should be provided by the user. # Usage