The format is based on Keep a Changelog and this project adheres to Semantic Versioning.
- Updated probe-rs to 0.13.0.
- Fixed the probe-setup URLs in the helptexts (#208).
- Updated probe-rs to 0.12.0.
- Improved erroring a lot with additional hints for the user on how to fix a certain problem.
- Updated probe-rs to 0.11.0.
- Disable sentry by default as an intermediate measure to fix the subpar user experience due to its introduction.
Note: This release was yanked.
- 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)!
- FTDI support is now optional. To enable FTDI support, please use the
ftdi
feature (#124).
- Support for cargo workspaces was added with the integration of
cargo-metadata
instead ofcargo-project
(in #39 by @Tiwalun) - Show the compiler output in
cargo flash
if the calledcargo build
command fails (in #53 by @Tiwalun).
- 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
- Added
Cargo.toml
metadata parsing for specifying the chip (see #31). - Probes can now be selected via the VID:PID:[SerialNo] triplet.
- 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.
- 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.
- 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.
- 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.
- Some chips do not reset automatically after flashing
- The STM32L0 cores have issues with flashing.
- A basic GDB server was added \o/ You can either use the provided
gdb-server
binary or usecargo flash --gdb
to first flash the target and then open a GDB session. There is many more new options which you can list withcargo flash --help
. - A flag to disable progressbars was added. Error reporting was broken because of progressbar overdraw. Now one can disable progress bars to see errors. In the long run this has to be fixed.
Improved flashing for cargo-flash
considering speed and useability.
- Added CMSIS-Pack powered flashing. This feature essentially enables to flash any ARM core which can also be flashed by ARM Keil.
- Added progress bars for flash progress indication.
- Added
nrf-recover
feature that unlocks nRF52 chips through Nordic's customAP
- Various bugfixes
- Introduce cargo-flash which can automatically build & flash the target elf file.