How can I obtain the latest source code for OpenOCD that comes with STM32CubeIDE?

ZYong.2 · ‎2025-12-08

The open source code on GitHub hasn't been updated for a long time, and many devices are unsupported. How can I get the latest OpenOCD source code? Should I contact technical support? Is there a contact email?

Aimen1 · ‎2025-12-24

Hello ZYong.2,

I am sharing with you the link to the dedicated GitHub repository:https://github.com/STMicroelectronics/OpenOCD

Please let me know if this meets your needs or if there is any specific missing device you would like us to include

Regards.

In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.

ZYong.2 · ‎2025-12-24

I am currently testing the STM32H563VIT6, but I noticed that the number of new devices added to STM32Cube since the last GitHub commit is far greater than what is available. I develop development boards based on STM32, so I hope to gain support for new devices rather than having to ask you for patches every time I find one missing. Moreover, it seems that even when I reach out to you, the response is quite slow.

Aimen1 · ‎2025-12-25

Hello ZYong.2,

The OpenOCD included with STM32CubeIDE is already up to date.

I understand that you are looking for the open-source version, is that correct ? If so, could you please clarify why you prefer to use it as a standalone tool? This will help me coordinate with the dedicated team to update the GitHub repository accordingly.

Regards.

In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.

ZYong.2 · ‎2025-12-25

I have a need for debugging multiple devices on a local network. I do not want to dedicate a computer to run STM32CubeIDE for each development board just for remote debugging. I hope to have source code that can be cross-compiled to ARM64, so I can use a Raspberry Pi or a cheaper ARM processor to accomplish remote debugging of multiple devices on the local network.

ZYong.2 · ‎2025-12-25

I'm not sure if your OpenOCD code involves any confidentiality, but I believe open-sourcing it would give users more options. I personally don’t like using STM32CubeIDE—I write code mostly in VS Code and debug with CubeIDE. I know ST released a VS Code plugin now, but if the open-source repository code could be updated synchronously, it would greatly improve the experience. Users could either dive deeper into the code or freely choose their development tools. I came here to inquire because I’ve noticed multiple unanswered update requests in issues on GitHub, and that’s why I'm reaching out.

AScha.3 · ‎2025-12-26

To have open OCD on a Pi , see:

https://cdn-learn.adafruit.com/downloads/pdf/programming-microcontrollers-using-openocd-on-raspberry-pi.pdf

https://github.com/raspberrypi/openocd

If you feel a post has answered your question, please click "Accept as Solution".

ZYong.2 · ‎2025-12-26

Thank you. I can cross-compile and run OpenOCD on a Raspberry Pi. The ST version is customized, and the upstream OpenOCD has incomplete support for ST chips. ST has also added its own validations, so the upstream OpenOCD cannot use STCube for debugging. That’s why I’m here, hoping to obtain the latest official customized source code.

DietWall · ‎2025-12-29

I would like to have STs openocd version as a standalone tool as well.

For me it makes no difference whether its compiled, or as source code. If I can use it on a raspberry pi, I would do it, even if I need to compile it and create a debian package.

I would like to use it in a CI/CD pipeline for testing and for remote debugging and development applications for multiple STM32 Boards.

ZYong.2 · ‎2025-12-29

Yes, releasing the latest ARM version binary would also work. It doesn’t necessarily have to be source code, though having the source code would of course be even better.