| Crates.io | defmt-rtt-target |
| lib.rs | defmt-rtt-target |
| version | 0.3.0 |
| created_at | 2022-01-10 13:17:05.263383+00 |
| updated_at | 2022-01-10 13:17:05.263383+00 |
| description | defmt logger implementation using the rtt-target crate |
| homepage | |
| repository | https://github.com/akiles/defmt-rtt-target |
| max_upload_size | |
| id | 511375 |
| size | 16,247 |
defmt-rtt-targetdefmt logger implementation using rtt-target.
The official defmt-rtt crate has its own RTT
implementation that is not externally exposed. This is done so that users can't corrupt the defmt log stream
by manually writing to the RTT channel. This library exists as an alternate option for when you do need
control over RTT, for example to log extra non-defmt data on other channels, or have a host->target "down channel".
If all you need is logging, you should use defmt-rtt instead of this.
rtt_target in your codedefmt_rtt_target::init() with the UpChannel you want to use for RTT printing. This should be channel 0, as that's the one all defmt tools use.Note that all log output before calling defmt_rtt_target::init() is discarded.
Licensed under either of
Apache License, Version 2.0 (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
MIT license (LICENSE-MIT or http://opensource.org/licenses/MIT)
at your option.