Potential problem here:
Pretty sure in Windows and elsewhere if you don't put paths in quotes, bad things will happen because the app has no way of determining properly what is what. Try again with a project folder using a path with no space in it and see if things get better.
[Edit] Then again, picotool said it loaded something into flash... beats me![:D]( "Very Happy")
I'm not a VS Code user, but a space in the path is a big red flag for me. Others here who are actual VS Code users might be more familiar with the output messages, so I won't try to dabble into that. But picotool has a lot of options that you can use to investigate this issue, for example:
To check the UF2 and see if it matches the board type you have.
Space in the path:Executing task: C:\Users\martin/.pico-sdk/picotool/2.2.0-a4/picotool/picotool.exe load e:/Documents/1a_VS Code/blink/build/blink.elf -fx
Code:
e:/Documents/1a_VS Code/blink/build/blink.elf[Edit] Then again, picotool said it loaded something into flash... beats me
I'm not a VS Code user, but a space in the path is a big red flag for me. Others here who are actual VS Code users might be more familiar with the output messages, so I won't try to dabble into that. But picotool has a lot of options that you can use to investigate this issue, for example:
Code:
$ picotool info blink.uf2File blink.uf2 family ID 'rp2040':Program Information name: blinker_simple binary start: 0x10000000 binary end: 0x10001ba4Statistics: Posted by katak255 — Mon Jan 26, 2026 3:42 am