Im running into this exact problem too but have noticed this only happens for
"larger" programs. A simple "Blink an LED" program flashes just fine.
Activating more and more perihperals via CubeMX - which consequently includes
the appropriate HAL drivers - causes the flashing to stop working. I can
reproduce this perfectly by enabling and disabling a single peripheral (I2C in
my example), rebuilding and flashing. With I2C enabled, i observe the exact
behavior described above. With it disabled, the program flashes just fine. I
dont know if its allowed to attache .elf files here. If so, i would gladly
provide a working and non-working .elf.
---
**[tickets:#421] OpenOCD v12 - STLink-v3Minie & STM32 f334 Not Working**
**Status:** new
**Milestone:** 0.10.0
**Labels:** bug v12.0
**Created:** Tue Jan 30, 2024 12:46 AM UTC by Taylor Lineman
**Last Updated:** Sat Feb 03, 2024 03:52 PM UTC
**Owner:** nobody
Hi all! I am a member of the RIT EVT Team and we often use OpenOCD to debug our
boards. These boards use a range of STM32 chips, specifically the f334, f302,
and f446. We have been struggling recently with OpenOCD on the f334 chips that
some of our boards use. We assumed this was a board issue so tested with
STM32CubeProgrammer, which worked flawlessly. However that program does not
allow for debugging and we have already built OpenOCD into our workflow, so we
wanted to get it working.
## Issue
The issue that we are seeing is that OpenOCD v12.0 fails with an STLinkv3 Minie
on only f334 boards. We have tested on an STM32 Nucleo as well as a custom
board to verify if there is a difference, and there is not. The following chart
shows our findings:
| Open OCD Version | STLink Version | Board | STM Name | Open
OCD |
|------------------|-------------------|-------------|-------------------|-------------|
| 0.12.0 | STLink v3 - Mini | IMU v1 | STM32 F334 C8 U6 | Not
Working |
| 0.12.0 | STLink v3 - Mini | HUDL v1.2 | STM32 F302 R8 T6 |
Working |
| | | | |
|
| 0.12.0 | Nucleo STlLink v3 | Nucleo F302 | STM32 F302 R8 AU1 |
Working |
| 0.12.0 | Nucleo STlLink v3 | Nucleo F334 | STM32 F334 R8 | Not
Working |
| 0.12.0 | Nucleo STlLink v3 | Nucleo F446 | STM32 F446 RE |
Working |
| | | | |
|
| 0.11.0 | STLink v3 - Mini | IMU v1 | STM32 F334 C8 U6 | Not
Working |
| 0.11.0 | STLink v3 - Mini | HUDL v1.2 | STM32 F302 R8 T6 | Not
Working |
| | | | |
|
| 0.11.0 | Nucleo STlLink v3 | Nucleo F302 | STM32 F302 R8 AU1 |
Working |
| 0.11.0 | Nucleo STlLink v3 | Nucleo F334 | STM32 F334 R8 |
Working |
| 0.11.0 | Nucleo STlLink v3 | Nucleo F446 | STM32 F446 RE |
Working |
As the chart shows, STM32 F334 support was working in OpenOCD v11.0, however
after updating to OpenOCD v12.0 we see it beging failing on Nucleo F334. The
above information was all tested and verified multiple times to ensure we got
our data correct.
-----
If the maintainers beelive we need to provide more information please let us
know! We will gladly help out in any way we can!
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/openocd/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/openocd/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
