Hi
I have struggled “a bit” with debug RP2040
Now i hav install VS code and PlatformIO on a new installation of WIN 10
and tried first with a BluePill “stm”
i can Download firmware to the chip use J-LINK EDU
but when Debugging the terminal ends with
Linking .pio\build\bluepill_f103c8\firmware.elf
Checking size .pio\build\bluepill_f103c8\firmware.elf
Advanced Memory Usage is available via “PlatformIO Home > Project Inspect”
RAM: [ ] 3.7% (used 764 bytes from 20480 bytes)
Flash: [= ] 12.4% (used 8136 bytes from 65536 bytes)
Building .pio\build\bluepill_f103c8\firmware.bin
======================================== [SUCCESS] Took 18.68 seconds ========================================
and does not start Debug Consule the “icon” Debug close (cant put in picture)
and nothing in debug console (not starting debugger) can some come up with an input
Hi and thanks for you reply
On my old WIN7 PC with an old Platformio and upgraded after install VS code 2022 (had VD code 2015 upgraded to 2022) it works
the problem with this came after I removed all VS code and Platformio because I had weird things in debug RP2040 then I could not debug so I thought format C: and completely fresh WIN10 and VS code and Platformio
maybe I should try with a VS code 2015?
can well see I’m not the only one
On the working WIN7 PC with upgradet VS code and Platformio
About is
Version: 1.64.0 (user setup)
Commit: 5554b12acf27056905806867f251c859323ff7e9
Date: 2022-02-03T04:22:20.678Z
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows_NT x64 6.1.7601
It currently looks like it’s a problem with fresh PlatformIO installations and those using the builtin Python interpreter. Best to wait for an official solution as linked above.
In the meantime, I’ve modified my PlatformIO extension settings to not use the builtin Core and not use the portable Python interpreter, did a pip install platformio in my PC-global Python 3.8.6 installation, added the Scripts folder of my Python3 installation to my PATH and restarted VSCode; The PlatformIO extension will pick up this global PIO installation now and debugging works properly.
Hi Ivan
i think i have the newest (i have not used platformio for 2 years and just startet again)
the only old is i testet PY 3.9 and same problem with 3.10
Please tell me wath to upgrade you can see my extension list above
Hi Ivan
Thanks it is now working on the STM 10 * to you for fast support
now I can try with RP2040 which was the one that started my uninstallation
because it behaved strangely with unknown stack.
Tests tomorrow and creates a new thread if teasing otherwise I write an ok here