Replies: 1 comment
-
Same here, did you ever find a solution @solunator ? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hardware: custom board, B-L072Z-LRWAN1 clone without ST-Link-V2-1, ST-Link/V2 ISOL connected to board. IAR is able to debug this setup with st software.
Source code: c:\loramac-node v4.6.0
OS: Windows 10
IDE: Visual Studio Code 1.64.0, 3 days old
Visual Studio Code Extensions:
Other software:
"c:/openocd/bin/openocd.exe": xPack OpenOCD x86_64 Open On-Chip Debugger 0.11.0+dev (2021-12-07-17:33)
"c:/arm/bin/arm-none-eabi-gcc.exe": gcc version 10.3.1 20210824 (release) (GNU Arm Embedded Toolchain 10.3-2021.10)
"c:/Program Files/CMake/bin/cmake.exe": version 3.22.2
"c:/msys64/mingw64/bin/mingw32-make.exe": GNU Make 4.3 Built for Windows32, from msys2-x86_64-20220118
I followed: https://github.com/Lora-net/LoRaMac-node/blob/master/doc/development-environment.md
c:/loramac-node/.vscode/settings.json
c:/loramac-node/.vscode/launch.json
Source code is configured, generated, compiled and linked successfully by VS Code.
When F5 if pushed in VS code (pretty format by hand):
Writing this post I've realized that there are 2 wrong paths.
Anyway VS Code shows this error: "Unable to start debugging. Debug server process failed to initialize."
When I run debug server from VS code terminal:
Note that I run:
C:/openocd/bin/openocd.exe -f interface/stlink.cfg -f target/stm32l0.cfg
but VS code runs:
"C:/openocd/bin/openocd.exe" -f interface/stlink.cfg -f target/stm32l0.cfg
If I add quotes it does not work:
When I run gdb from VS Code terminal:
How can I debug without any problem?
Regards
Beta Was this translation helpful? Give feedback.
All reactions