I would suggests doing the paperwork and ordering a new Pico - ideally more than one, as soon as possible. Trying to identify the failure mode and resolve that - if that's even possible, may take longer than getting a new Pico.
If the new Pico doesn't work that would suggest an issue with your development setup, software or configuration.
If it works you can carry on developing while investigating whatever the issue is at leisure without delaying your work.
In the meantime I would suggest going back to the Pico SDK you had before 2.0.0 and seeing if things still work with that.
I would also suggest getting the recommended GCC toolchain to see if whatever you are using is the issue. It's just an 'apt install' on a Pi and Linux, and I don't recall it being difficult under Windows.
If the new Pico doesn't work that would suggest an issue with your development setup, software or configuration.
If it works you can carry on developing while investigating whatever the issue is at leisure without delaying your work.
In the meantime I would suggest going back to the Pico SDK you had before 2.0.0 and seeing if things still work with that.
I would also suggest getting the recommended GCC toolchain to see if whatever you are using is the issue. It's just an 'apt install' on a Pi and Linux, and I don't recall it being difficult under Windows.
Statistics: Posted by hippy — Fri Oct 25, 2024 12:31 pm