Skip to content
This repository has been archived by the owner on Jan 14, 2023. It is now read-only.

Releases: probe-rs/cargo-flash

0.13.0

12 Jul 10:56
cc15d22
Compare
Choose a tag to compare

0.13.0

Changed

  • Updated probe-rs to 0.13.0.

0.12.1

01 Apr 16:18
v0.12.1
95efa29
Compare
Choose a tag to compare

Fixed

  • Fixed the probe-setup URLs in the helptexts (#208).

0.12.0

25 Nov 14:44
5bd462e
Compare
Choose a tag to compare

Changed

  • Updated probe-rs to 0.12.0.

0.11.0

23 Jun 21:25
1d07cb2
Compare
Choose a tag to compare

Added

  • Improved erroring a lot with additional hints for the user on how to fix a certain problem.

Changed

  • Updated probe-rs to 0.11.0.

0.10.1

19 Nov 19:06
5610605
Compare
Choose a tag to compare

Added

  • Updated to probe-rs 0.10.0. Please consult its own changelog for new features and fixes.
  • Added logging to sentry.io. This is 100% OPT-IN! You will be asked only if an unhandled error or panic occurs, and only if you give consent, data is transmitted. If you do not trust us either way, you can disable the sentry feature when you install the crate. The completely anonymous data can be investigated on sentry.io by anyone who likes to see it. Unfortunately sentry.io does not feature public orgs yet, so please reach out to @Yatekii to be added.
    Sentry helps us track down tricky issues that only occur in very specific cases. It is very much appreciated if you log upcoming errors this way (#121)!

Changed

  • FTDI support is now optional. To enable FTDI support, please use the ftdi feature (#124).

0.9.0

02 Sep 21:09
73f5b93
Compare
Choose a tag to compare

Added

  • Support for cargo workspaces was added with the integration of cargo-metadata instead of cargo-project (in #39 by @Tiwalun)
  • Show the compiler output in cargo flash if the called cargo build command fails (in #53 by @Tiwalun).

Removed

  • The option to start a GDB server after flashing is removed. It is recommended to use cargo-embed to start a GDB server. The following options are removed:
    • --gdb
    • --no-download
    • `--gdb-connection-string

0.8.0

29 Jun 22:24
Compare
Choose a tag to compare

[0.8.0]

Added

  • Added Cargo.toml metadata parsing for specifying the chip (see #31).
  • Probes can now be selected via the VID:PID:[SerialNo] triplet.

Changed

  • Improved error logging by a large margin! Errors are now displayed properly in stacked fashion and are easier to read.
  • Cleaned up some of the logging output. Mostly beauty stuff.

0.7.0

04 Jun 20:17
Compare
Choose a tag to compare

Added

  • Added Cargo.toml metadata parsing for specifying the chip (see #31).

Changed

  • Improved error logging by a large margin!
  • Cleaned up some of the logging output. Mostly beauty stuff.

0.6.0

30 Mar 23:25
Compare
Choose a tag to compare

Added

  • Add a --speed setting to configure protocol speed in kHz.
  • Upgrade to probe-rs 0.6.0 which fixes some bugs that appeared within cargo-flash (see CHANGELOG)
  • Add a --restore-unwritten flag which makes the flashing procedure restore all bytes that have been erased in the sectore erase but are not actually in the writeable sections of the ELF data.
  • Add an --elf setting to point to a specific ELF binary instead of a cargo one.
  • Add a --work-dir for cargo flash to operate in.

0.5.0

03 Mar 22:07
Compare
Choose a tag to compare

Added

  • Adds support for JLink and JTag based flashing.
  • Add the possibility to select the debug protocol (SWD/JTAG) with --protocol.
  • Added the possibility to set the log level via the --log argument.

Changed

Fixed

  • Fix a bug where --probe-index would be handed to cargo build accidentially.
  • Logs are now always shown, even with progressbars enabled.
    Before progressbars would behave weirdly and errors would not be shown.
    Now this is handled properly and any output is shown above the progress bars.

Known issues

  • Some chips do not reset automatically after flashing
  • The STM32L0 cores have issues with flashing.