Skip to content

Releases: rtic-scope/cargo-rtic-scope

v0.3.3

14 Jun 17:07
Compare
Choose a tag to compare

[0.3.3] 2022-06-14

Added

  • cargo rtic-scope replay --list: print out a non-exhaustive header describing the index and trace file name, but not the comment (#140).

Changed

  • cortex-m-rtic-trace::trace: write watch variables using ptr::volatile_write instead, signaling that the write should not be optimized out.
  • rtic-scope-frontend-dummy: correctly report absolute timestamps as nanoseconds, not microseconds.
  • cargo rtic-scope replay --list: only print the trace comment if it exists (previously printed "None").

Fixed

  • cortex-m-rtic-trace::trace: correctly handle tasks/functions that exit prematurely or return a value.
  • /contrib: update lock file; cargo-rtic-scope now builds again inside a nix develop shell.
  • Builds of PACs with default features like device or rt during recovery stage, which previously resulted in fatal linker errors.

Full Changelog: v0.3.2...v0.3.3

v0.3.2

17 Mar 17:06
Compare
Choose a tag to compare

[0.3.2] 2022-03-17

Maintenance release.

Changed

  • Bump itm which improves the denotation of quality in the downstream api::Timestamp: a previous api::Timestamp { offset: 1, data_relation: TimestampDataRelation::Sync } is now represented as api::Timestamp::Sync(1).
  • rtic-scope-frontend-dummy: print qualities (good or bad, abstracted above the api::Timestamp enum) of timestamped events.

Full Changelog: v0.3.1...v0.3.2

v0.3.1

19 Jan 17:02
Compare
Choose a tag to compare

[0.3.1] 2022-01-19

Mostly a maintenance release with some quality-of-life changes. The largest change is that on trace --serial, the given device is not unconditionally configured for 115200bps.

Added

  • /docs/, a submodule that contains the overarching documentation of RTIC Scope, which is rendered at the organization profile.
  • /rtic-scope-frontend-dummy/, a submodule of the frontend reference implementation.
  • Crate documentation for cargo-rtic-scope, which is the same README.md used for the organization documentation.

Changed

  • On --serial /path/to/dev, dev will no longer unconditionally configure for 115200 B/s; the baud rate specified with tpiu_baud in the [package.metadata.rtic-scope] block in Cargo.toml will instead be applied. For example, tpiu_baud = 9600 will configure dev for 9600 B/s. Valid baud rates are listed in nix::sys::termios::BaudRate, with the exception of B0.
  • Improved the warning message when an overflow packet is decoded. It will now detail that non-timestamp packets have been dropped and/or that the local timestamp counter wrapped which means that timestamps from then on are potentially diverged.
  • Ignore enters and exits relating to the ThreadMode interrupt: RTIC always executes tasks in handler mode and then returns to ThreadMode on cortex_m::asm::wfi().
  • Bumped itm to v0.7.0 with its "serial" feature; the latter used to configure a TTY source.
  • Emit a warning if a DWT watch address used for software task tracing is read. Such an address should only ever be written to. This error would indicate that something has gone very wrong.
  • Crate documentation for rtic-scope-frontend-dummy, cortex-m-rtic-trace, and rtic-scope-api which is now the same as README.md used for the organization documentation but with a small header summarizing the crate.
  • Bumped cortex-m, ensuring additional target support verification during cortex_m_rtic_trace::configure.
  • Messages from frontends are now prefixed by a cyan "Frontend" instead of a red "Error".

Fixed

  • No longer prints "Target reset and flashed." or "preparing target" on trace --dont-touch-target.

Full Changelog: v0.3.0...v0.3.1

v0.3.0

05 Jan 15:08
Compare
Choose a tag to compare

RTIC Scope has finally reached a point that is close to production ready. With all features necessary for software and hardware task tracing, this release marks the end of the project work within the frame of my thesis. But the work continues at @GrepitAB.

From this release forward, a proper changelog will be enforced.

Overarching documentation can be found at the project root.

What's Changed

  • Create a test bench by @tmplt in #55
  • scope/build: improve error message, add relevant hints and CI by @tmplt in #59
  • Implement software task tracing by @tmplt in #57
  • run_loop: sync select next packet and halt condition by @tmplt in #68
  • Add a newline to separate JSON messages. by @Yatekii in #67
  • replay: add --trace-file option by @tmplt in #71
  • test --frontend from PATH, relative, and absolute path by @tmplt in #72
  • Don't build artifact on replay by @tmplt in #29
  • Refactor recovery module, record software task dispatchers by @tmplt in #65
  • Buffer packets from target by @tmplt in #78
  • Asynchronously print frontend stderrs by @tmplt in #80
  • Replace itm-decode with itm reimplementation by @tmplt in #85
  • print a final status message, summarizing the trace/replay by @tmplt in #87
  • add --dont-touch-target, which requires --serial by @tmplt in #93
  • Bump RTIC to v1.0.0 by @tmplt in #97
  • Finalize cortex-m-rtic-trace by @tmplt in #98
  • Finalize documentation by @tmplt in #99

New Contributors

Full Changelog: 0.2.0...v0.3.0