Hello, I just started to have error Failed to launch GDB: Error: write EPIPE on debugging start. [err2] I am using PlatformIO IDE plugin for VS Code on Windows 10. Yesterday and in the morning debugger was working. Then I turned off my laptop, turned it on back again hour later and now I cannot…

[versions] VS Code, PlatformIO versions

In vscode dev console are two errors. Debug start fail, Could not start debugger process > Error: spawn platformio ENOENT is second. First error (node:8584) [DEP0005]. [Error] It is C/C++ plugin thing ( Buffer() is deprecated due to security and usability issues. · Issue #4381 · microsoft/vscode-…

Can you please check if downgrading the PIO extension makes a difference. On the left sidebar -> Extensions -> PlatformIO -> Cogwheel -> Install other version -> 2.1.0 (2.0.1 also working).

I cannot help but can confirm that I have exactly the same issue. I’m debugging a Wio Terminal (ATSAMD 51P19 MCU). Up to yesterday all worked perfect. Today have the same error messages,

Downgrading the PIO extension to version 2.1.0 fixed the issue for me. Version 2.1.1 did not work. I didn’t even see the PIO Home screen.

[image] roschmi: Version 2.1.1 did not work. I didn’t even see the PIO Home screen. Yes that version is unstartable due to the bug described in PIO 2.1.1 does not work · Issue #2170 · platformio/platformio-vscode-ide · GitHub , that’s why it was fixed and re-released within one hour, too, as 2…

For me on plugin 2.1.0 debugging is working. 2.1.1 - nothing works, PlatformIO Home wont even open, no build, no upload. 2.1.2 - no debugging, but build + upload are working. Thanks for solution/workaround.