This template is not intended to be generic across multiple boards unless they have a BSP that conforms to the same layout as rp-pico - even then, you are expected to adapt it to your own needs after cloning/instantiating the template via github or cargo generate.
These choices were made by rp-rs developers to match what we thought was best, opinionated place to start from:
It uses the rp-pico as the target, because that is the cheapest and most common board and it exposes the debug interface
It uses a debugger with probe-run, as that is the best experience while developing embedded rust.
It needs to be super simple so someone new can understand what is going on.
Adding your specific board behind a cfg flag, changing to not use a debugger and adding a uf2 binary to this crate does not accomplish the goals of this crate. As such, I'm closing this PR.
@sndnvaps I recommend you maintain your own template if you think it this has value.
This template is not intended to be generic across multiple boards unless they have a BSP that conforms to the same layout as rp-pico - even then, you are expected to adapt it to your own needs after cloning/instantiating the template via github or cargo generate.
These choices were made by rp-rs developers to match what we thought was best, opinionated place to start from:
Adding your specific board behind a cfg flag, changing to not use a debugger and adding a uf2 binary to this crate does not accomplish the goals of this crate. As such, I'm closing this PR.
@sndnvaps I recommend you maintain your own template if you think it this has value.