Loading...
 

Zephyr project on STM32

   Zephyr Workbench, a VSCode extension to manage Zephyr on STM32.
It enables users to easily create, develop, and debug Zephyr applications.
Main features:
  • Install host dependencies.
  • Import toolchain and SDK.
  • Create, configure, build and manage apps.
  • Debug STM32.
You can directly download it from the VSCode marketplace
For more details, visit the Zephyr Workbench

System Workbench for STM32


openocd binary not found

Dear all,

I have changed the directory architecture of my project, recreate a new one and now i get the message “openocd binary not found” when I launch the debugger. Before I did the change it worked fine. Where can I get the declaration of “openstm32_openocd_path” variable used by Debug Configuration.
I use version 1.1.0
Thanks

France

Hi Guy,

What do yo mean by changing the directory architecture of your project and create a new one? why creating a new project afetr changing the directory structure? What kind of project did you exactly create?

The openstm32_openocd_path is defined by the openocd plugin and does not depend on the project directory structure, so I don’t understand why changing it could break it.

Bernard


Hi Bernard,

I changed the directory tree with the Windows Explorer, because I have now 2 firmwares to design with 2 differents uC.
I used C++ project with Makefile project type.
During this moving may be I have lost or removed the settings.
I will redo from scratch.
Regards,


Hello,

I’ve updated my framework AC6 to last version 1.6.0 and now get the error message:

OpenOCD Binary not found
when starting a debug session.

I reinstalled my eclipse framework which is a terrible solution. And the issue remains.

Can you help about this ?

Thanks for your help,
Best regards,
Sylvain


If you go into your debug configuration, under the debugger tab, can you change the GDB command and OpenOCD command to point directly to the executable and avoid openstm32_openocd_path?

I had the same problem for a while, I believe pointing directly to the executable worked, but to really get the path variable correct I had to reinstall system workbench and OpenOCD. I don’t remember what order I used, it was not a fun time.


Recreating the workspace directory (especially workspace/.metadata) solved this issue.

Hi guys,

the solution would be going to “Debug configuration” and delete the selected configuration and recreate it.


 

Newest Forum Posts

  1. SPI on Nucleo_STMH533RE by royjamil, 2025-05-04 20:13
  2. SPI on Nucleo_STMH533RE by higginsa1, 2025-03-25 07:37
  3. SPI on Nucleo_STMH533RE by royjamil, 2025-03-23 11:31
  4. SPI on Nucleo_STMH533RE by higginsa1, 2025-03-23 09:33
  5. Configuring DMA for ADC in SW? by sam.hodgson, 2025-03-04 12:58
  6. Build a project in "release" mode by info@creosrl.it, 2025-02-20 18:12
  7. Build a project in "release" mode by info@creosrl.it, 2025-02-20 17:05
  8. Build a project in "release" mode by tang, 2025-02-20 10:36
  9. Build a project in "release" mode by info@creosrl.it, 2025-02-19 17:35
  10. Fail to debug in Win 11 C/C++ by mortenlund, 2024-12-26 20:27

Last-Modified Blogs