@@ekasusilo sorry i dint see in video how to download python3 , couldnt install it since doesnt exist pacman -S pythone3 file not found how do i download it and point it please let me know
Every thing perfect and debug and compile no errors thank you so much again for the clear instructions, I’m facing a code problem not sure if any experience it or maybe I’m doing some wrong since I’m only used to the Arduino environment, I am try to change modify the blink code just to see if will change and there is no changes at all still debug the prior original code ! I even comment out every thing in while loop and still running the old code and I can see still stepping in the comment out code this is insane and never seen this ! I google it and watch other videos and I asked no hope , thought I’ll post here so please help on this or any one know let me know what I’m doing wrong , I even modified the code from the blink original file and still running the old code. Thank you 🙏
I understand the STM32 chips support SWD (in addition to JTAG), and that STM32CubeIde+StLinkv3 allows you to stream trace data via the optional SWV(TDO) pin... but can the same be done with a J-Link-Edu/Mini debugger and Visual Studio Code + Openocd? Or via Eclipse?
Hi Ben, I haven't gotten my hands on ST-Linkv3 just yet. Once it is arrived in the mail I can take a look on how to get it working with my setup. From the quick look at ST-Linkv3 spec sheet, it includes VCOM. It may not be the one you are looking for, but I know JLink uses VCOM as well. Anyway, I'll let you know my finding with SWV setup. Thank you for bringing this up.
Hi, I changed the files and executed as shown in the video and its showing the error "Could not start GDB process, does the program exist in the filesystem? Error: spawn C/gcc-arm-none-eabi/bin/arm-none-eabi-gdb ENOENT" .Tried changing the armtoolchainpath in the cortex-debug but the error is still there.
Please make sure your toolchain is properly installed and is on the system path. This kind of error is mostly due to incorrect path, some typo in the path or something similar.
@@ekasusilo I had the same issue, I fixed the path for the armtoolchain which seemed to work but now I'm getting an OpenOCD error. "Failed to launch OpenOCD GBD Server: Error: spawn openocd.exe ENOENT". The filepath is definitely correct, I checked. So do you know how I can fix this? Thanks EDIT- Extra info: "openocd.exe -c "gdb_port 50000" -c "tcl_port 50001" -c "telnet_port 50002" -s "C:\\libopencm3-examples" -f "c:/Users/PC/.vscode/extensions/marus25.cortex-debug-1.12.0/support/openocd-helpers.tcl" -f "interface stlink.cfg" -f "target stm32f4x.cfg" [2023-06-26T16:38:54.575Z] SERVER CONSOLE DEBUG: GDBServerConsole: onBackendConnect: gdb-server program client error Error: read ECONNRESET [2023-06-26T16:38:54.576Z] SERVER CONSOLE DEBUG: onBackendConnect: gdb-server session closed" The terminal says this: "SERVER CONSOLE DEBUG: GDBServerConsole: onBackendConnect: gdb-server program client error Error: read ECONNRESET"
Thank you for this -- super helpful tutorial! Question: I noticed you installed the Makefile Tools extension, but it isn't able to invoke the MSYS2 make utility. Did I miss something?
@@ekasusilosorry, let me clarify. make installs in MSYS just fine using pacman, but the MS maketools extension isn't able to invoke it (that I've figured out) Instead, make has to be invoked from the MSYS terminal. It's not a big deal, just thought there might be a VS Code button or keystroke to invoke make.
@@ThomasHerron-f9u That, unfortunately, is not something that can work with MSYS2. The solution that works, and I have been using it for some time instead of MSYS2, is setting up the development environment with WSL2. The Makefile Tools is tested to work with Ubuntu 20.04.5 LTS WSL2 on both Windows 10 and 11.
Excuse me if you find my question stupid, but I'm not quite familiar with the subject matter: Why going thru all this process of installation to debug the STM32s when you can use the readily available STM32Cubeide? Isn't it much simpler/faster....or there is any drawback with using that software?
You could use STM32CubeIDE for sure. It really is a great tool to do everything in one place. But I find it intimidating to use with so many menu and options that I probably don't need. So, I find VSCode more suitable for my development environment with various extensions that I can install when I need it. It is just my preference, but I do use STM32CubeIDE as well sometimes, mostly for starting up new Makefile project generation.
hi i have problems like "GDB executable "arm-none-eabi-gdb.exe" was not found. Please configure "cortex-debug.armToolchainPath" or "cortex-debug.gdbPath" correctly." please help me thank a ton
You need to make sure that the path is correct, which I believe you did. Another thing to emphasize, GNU ARM Toolchain is 10.3. Please let me know if this helps to troubleshoot your issue.
hi i get a problem like this "File not found "executable": "C:/Users/hocla/libopencm3-examples/examples/stm32/f4/stm32-discovery/miniblink/miniblink.elf"" please help me. thanks a ton!
@@ekasusilo I have the same issue. Miniblink.elf was not built. What do I do? EDIT: I deleted the libopencm3 folder and re-did all the following steps, and for some reason only on the second attempt did the miniblink.elf get built. Success.
Great tutorial! Thank you for making this.
thank you for this, great tutorial
Made life so much easier
Dannnnnng you the man what the hell I was looking for this
Please make for window 11 step by step
Glad it helps! The steps are the same for Windows 11. At least I didn't see any issue when I tried it from my end.
@@ekasusilo sorry i dint see in video how to download python3 , couldnt install it since doesnt exist pacman -S pythone3 file not found how do i download it and point it please let me know
@@s.h7124 I notice you wrote `pythone3` instead of `python3`? That might explain why it does not exist?
@@ekasusilo you the man ! What an eye you have love you man if I see I’ll kiss you on your forehead peace ☮️
how we can configure stlink to flash from command line
Hi I have problems like "the editor could not be opened because the file was not found". How can this be solved? Thanks for the answer
Just wanted to know how exactly he gave the config files for the json (@24.00). Is there any tutorial / document to understand that?
Great tutorial! very helpful! Thanks!
Glad it was helpful!
Great manual! Thank you!
Glad it was helpful!
Every thing perfect and debug and compile no errors thank you so much again for the clear instructions, I’m facing a code problem not sure if any experience it or maybe I’m doing some wrong since I’m only used to the Arduino environment,
I am try to change modify the blink code just to see if will change and there is no changes at all still debug the prior original code ! I even comment out every thing in while loop and still running the old code and I can see still stepping in the comment out code this is insane and never seen this ! I google it and watch other videos and I asked no hope , thought I’ll post here so please help on this or any one know let me know what I’m doing wrong , I even modified the code from the blink original file and still running the old code.
Thank you 🙏
thank you a lot
Hi,
Does this cortex-debug extension work for cortex R connections as well?
Is there a reason you chose the zip file instead of running the executable for the GNU ARM Toolchain?
You could keep multiple compiler version and modify only the toolchain path when needed
I understand the STM32 chips support SWD (in addition to JTAG), and that STM32CubeIde+StLinkv3 allows you to stream trace data via the optional SWV(TDO) pin...
but can the same be done with a J-Link-Edu/Mini debugger and Visual Studio Code + Openocd? Or via Eclipse?
Hi Ben, I haven't gotten my hands on ST-Linkv3 just yet. Once it is arrived in the mail I can take a look on how to get it working with my setup. From the quick look at ST-Linkv3 spec sheet, it includes VCOM. It may not be the one you are looking for, but I know JLink uses VCOM as well. Anyway, I'll let you know my finding with SWV setup. Thank you for bringing this up.
Great Tutorial. Thank you, man. what if we add Google test to that? It would be great if you make a tutorial for that! :)
Hi, I changed the files and executed as shown in the video and its showing the error "Could not start GDB process, does the program exist in the filesystem? Error: spawn C/gcc-arm-none-eabi/bin/arm-none-eabi-gdb ENOENT" .Tried changing the armtoolchainpath in the cortex-debug but the error is still there.
Please make sure your toolchain is properly installed and is on the system path. This kind of error is mostly due to incorrect path, some typo in the path or something similar.
@@ekasusilo will try that. thank you
@@ekasusilo I had the same issue, I fixed the path for the armtoolchain which seemed to work but now I'm getting an OpenOCD error. "Failed to launch OpenOCD GBD Server: Error: spawn openocd.exe ENOENT". The filepath is definitely correct, I checked. So do you know how I can fix this? Thanks
EDIT- Extra info:
"openocd.exe -c "gdb_port 50000" -c "tcl_port 50001" -c "telnet_port 50002" -s "C:\\libopencm3-examples" -f "c:/Users/PC/.vscode/extensions/marus25.cortex-debug-1.12.0/support/openocd-helpers.tcl" -f "interface stlink.cfg" -f "target stm32f4x.cfg"
[2023-06-26T16:38:54.575Z] SERVER CONSOLE DEBUG: GDBServerConsole: onBackendConnect: gdb-server program client error Error: read ECONNRESET
[2023-06-26T16:38:54.576Z] SERVER CONSOLE DEBUG: onBackendConnect: gdb-server session closed"
The terminal says this:
"SERVER CONSOLE DEBUG: GDBServerConsole: onBackendConnect: gdb-server program client error Error: read ECONNRESET"
Thank you for this -- super helpful tutorial! Question: I noticed you installed the Makefile Tools extension, but it isn't able to invoke the MSYS2 make utility. Did I miss something?
MSYS2 sometimes may have trouble installing make. Have you installed it with pacman -S make?
@@ekasusilosorry, let me clarify. make installs in MSYS just fine using pacman, but the MS maketools extension isn't able to invoke it (that I've figured out) Instead, make has to be invoked from the MSYS terminal. It's not a big deal, just thought there might be a VS Code button or keystroke to invoke make.
@@ThomasHerron-f9u That, unfortunately, is not something that can work with MSYS2. The solution that works, and I have been using it for some time instead of MSYS2, is setting up the development environment with WSL2. The Makefile Tools is tested to work with Ubuntu 20.04.5 LTS WSL2 on both Windows 10 and 11.
Okay. Thank for the confirmation. Building through MSYS2 is adequate. Again, I really appreciate you putting together this video. It was super helpful
@@ThomasHerron-f9u You're very welcome! Take care!
Excuse me if you find my question stupid, but I'm not quite familiar with the subject matter: Why going thru all this process of installation to debug the STM32s when you can use the readily available STM32Cubeide? Isn't it much simpler/faster....or there is any drawback with using that software?
You could use STM32CubeIDE for sure. It really is a great tool to do everything in one place. But I find it intimidating to use with so many menu and options that I probably don't need. So, I find VSCode more suitable for my development environment with various extensions that I can install when I need it. It is just my preference, but I do use STM32CubeIDE as well sometimes, mostly for starting up new Makefile project generation.
@@ekasusilo Thank you for clarifiying my doubt. Now I understand your point. Great video by the way. Cheers.
STMCubeIDE is based on Eclipse. A lot of people, including me, hate it.
@keen2461 It is useful when you want to run a test (Like a Google test) besides running your application. You can't do this with stmIDE!
Man... Do you know powershell or wsl ??? What is the point to use windows if you preferd Linux shell ?
，very helpful. Please give a tutorial about the difference between using vsc and stm32ide. Or other ide tools.thanks.
Sure I will, please check back to my channel next week!
Awesome thank you can’t wait
Not sure as no GitHub of the result. …
hi i have problems like "GDB executable "arm-none-eabi-gdb.exe" was not found.
Please configure "cortex-debug.armToolchainPath" or "cortex-debug.gdbPath" correctly." please help me
thank a ton
You need to make sure that the path is correct, which I believe you did. Another thing to emphasize, GNU ARM Toolchain is 10.3. Please let me know if this helps to troubleshoot your issue.
hi i get a problem like this "File not found "executable": "C:/Users/hocla/libopencm3-examples/examples/stm32/f4/stm32-discovery/miniblink/miniblink.elf"" please help me. thanks a ton!
You gotta look if the miniblink.elf is in the path. It is either the path is incorrect, or it does not successfully build the binary.
@@ekasusilo I have the same issue. Miniblink.elf was not built. What do I do? EDIT: I deleted the libopencm3 folder and re-did all the following steps, and for some reason only on the second attempt did the miniblink.elf get built. Success.
@@dinobambino21 Check the build log and see if there is meaningful error or warning that can be used to debug your issue
@@ekasusilo Thank you. I was able to resolve that issue.