Post AXD1Yo2S9hSVuh6nWy by fff@pouet.chapril.org
(DIR) More posts by fff@pouet.chapril.org
(DIR) Post #AXD05wKO9oBJGoAZI8 by lore@berserker.town
2023-06-30T06:34:24Z
0 likes, 0 repeats
hmm... but i have that debugger installed already through the STM32CubeCLT package, and i'm compiling my #STM32 #embedded project just fine with it the other GNU compiler tools. this was working on macOS but something's not working on Ubuntu...
(DIR) Post #AXD1Yo2S9hSVuh6nWy by fff@pouet.chapril.org
2023-06-30T06:50:47Z
0 likes, 0 repeats
@lore The message is clear, the path to the ARM debugger is not found. Problem with permissions on linux or environment variable?
(DIR) Post #AXD2Q87kD23hYT0hlY by lore@berserker.town
2023-06-30T07:00:28Z
0 likes, 0 repeats
@fff the funny thing is that it's compiling just fine... with tools that are in the same folder... it's just not finding the path to the debugger...
(DIR) Post #AXD2XSJ7Z8uyBDpCWu by lore@berserker.town
2023-06-30T07:01:47Z
0 likes, 0 repeats
@fff it uses a variable but it's not an environment variable. it's something in the IDE but i don't know where that setting is.
(DIR) Post #AXD2dgZnQXbwAiay6y by lore@berserker.town
2023-06-30T07:02:55Z
0 likes, 0 repeats
@fff the variable it uses is ${command:vscode-embedded.st.gdb} which is obviously a config value from the VS Code Embedded Tools extension. but i don't know where, and Google's being unhelpful. i need an answer from someone who's done this before.
(DIR) Post #AXD2jrhqxWcyQcJJLM by lore@berserker.town
2023-06-30T07:04:02Z
0 likes, 0 repeats
@fff what appears to be happening is that CMake is finding the tools at the default expected path for STM32CubeCLT for Linux but somehow, the Embedded Tools extension isn't.
(DIR) Post #AXD2qb5L9eBmuDVSLY by lore@berserker.town
2023-06-30T07:05:15Z
0 likes, 0 repeats
@fff this was previously a macOS project that i was building/running in VS Code for macOS and i'm trying to get it up and running on Linux now.