* doc: Document the project creation process
* fix: typo in readme.md introduced in the previous commit
Co-authored-by: 9names <60134748+9names@users.noreply.github.com>
---------
Co-authored-by: 9names <60134748+9names@users.noreply.github.com>
`probe-run` was recently announced as deprecated in favor of `probe-rs`. This changes the default
runner to `probe-rs run` and removes reference to the old `probe-run`.
* Update probe-rs tools to 0.19
* Restore rp2040_boot2 line
* Update runner to use probe-rs run 0.19 syntax
* Update vscode launch command for probe-rs debugger
* Add note about removing older installation of cargo-embed
If you had previously installed cargo-embed separately, it will conflict with the new way probe-rs installs multiple binaries at once.
* Update README.md
Co-authored-by: 9names <60134748+9names@users.noreply.github.com>
---------
Co-authored-by: Jan Niehusmann <jan@gondor.com>
* Add a basic VSCode configuration for probe-rs-debugger
* VSCode: have launch build first and use debug binary
* Got defmt working in vs-code-debugger
* Add VSCode debugger setup to README
The original comment "JLink probes sort of work" gave the impression that you could probably use a J-Link.
Support for this was never good, but it's currently completely broken.
I've replaced these parts with stronger language to discourage people from trying.
* Improve layout and formatting of readme
* Update comments around elf2uf2
* Update for DEFMT_LOG in config.toml
* Minor formatting fixes
* Use italics for 'environment variable'
In `README.md`, elf2uf2-rs has been misspelled as elf2usb2-rs in installation commands. In `.cargo/config.toml`, a quotation mark need to be added.
For users who use VS Code with Rust Analyzer, setting target architecture could help them to avoid warning like no tests module.
Since thejpster rebased our changes on upstream probe-run, probe-run-rp is now in the rp2040-support branch.
Updating the installation instructions to reflect that change.
