Note to myself squash before merge

Now that RP2350 support has been added to probe-rs (probe-rs/probe-rs#3005), I think we can simplify the rust integration to use the "Debugger for probe-rs" extension rather then Cortex-Debug for debugging rust code. This has full support for defmt, so should be easier to integrate.

Now that RP2350 support has been added to probe-rs (probe-rs/probe-rs#3005), I think we can simplify the rust integration to use the "Debugger for probe-rs" extension rather then Cortex-Debug for debugging rust code. This has full support for defmt, so should be easier to integrate.

I'll look into it. Im currently very busy, but I may find some time in a few weeks.

@will-v-pi Just updated the generator to use probe-rs but I can't get the defmt rtt (on RP2350) working again.
Any idea what the old config was that worked?

I think the config used by https://github.com/rp-rs/rp2040-project-template was working for me

I think the config used by https://github.com/rp-rs/rp2040-project-template was working for me

Also for the Pico 2?

I think the config used by https://github.com/rp-rs/rp2040-project-template was working for me

Also for the Pico 2?

I haven’t tried, but my hope is that with the probe-rs support it should just be a case of changing the chip name in the config?

@will-v-pi
The current version of this branch generates the config stuff for rp2350 but it doesn't work for me on macOS. I get pkg size could not be determined errors with the pico probe or it connected but no defmt.

It seems like the issue was the missing DEFMT_LOG flag.

Note that in the current state first rust project creation with fresh rustup install will take very long.
TODO: Add better progress indication during that time.
TODO: check that all requirements are checked on rust project opening.

Just wanted to note that I got an error when compiling a project, because I had an old Cargo version:

  The package requires the Cargo feature called `edition2024`, but that feature is not stabilized in this version of Cargo (1.84.1 (66221abde 2024-11-19)).
  Consider trying a newer version of Cargo (this may require the nightly release).
  See https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#edition-2024 for more information about the status of this feature.

The link in the error didn't help - the solution was to run rustup update to update the Cargo version

I'm hitting an error on a clean windows install where if I just use the automated rustup installer (rustup-init.exe), it doesn't install all the required MSVC stuff (it only install MSVC build tools, not the Windows 11 SDK), and then the extension throws an error when installing the flip-link crate that linker.exe is not found.

It might be good to filter for that specific flip-link error and instead of printing the generic failure message, direct users to https://rust-lang.github.io/rustup/installation/windows-msvc.html#manual-install to make sure their prerequisites are installed correctly.