Seeing the same for a Nucleo STM32F303K8: ```bash openocd -d2 -s C:\Users\vkais\.platformio\packages\tool-openocd/openocd/scripts -f board/st_nucleo_f3.cfg -c "program {.pio\build\nucleo_f303k8\firmware.elf} verify reset; shutdown;" xPack Open On-Chip Debugger 0.12.0-01004-g9ea7f3d64-dirty (2023-01-30-15:04) Licensed under GNU GPL v2 For bug reports, read http://openocd.org/doc/doxygen/bugs.html debug_level: 2
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD srst_only separate srst_nogate srst_open_drain connect_deassert_srst Info : clock speed 1000 kHz Info : STLINK V2J43M28 (API v2) VID:PID 0483:374B Info : Target voltage: 3.257369 Info : [stm32f3x.cpu] Cortex-M4 r0p1 processor detected Info : [stm32f3x.cpu] target has 6 breakpoints, 4 watchpoints Info : starting gdb server for stm32f3x.cpu on 3333 Info : Listening on port 3333 for gdb connections [stm32f3x.cpu] halted due to breakpoint, current mode: Thread xPSR: 0x61000000 pc: 0x2000003a msp: 0xfffffffc Info : Unable to match requested speed 1000 kHz, using 950 kHz Info : Unable to match requested speed 1000 kHz, using 950 kHz [stm32f3x.cpu] halted due to debug-request, current mode: Thread xPSR: 0x01000000 pc: 0xfffffffe msp: 0xfffffffc Info : Unable to match requested speed 8000 kHz, using 4000 kHz Info : Unable to match requested speed 8000 kHz, using 4000 kHz ** Programming Started ** Info : device id = 0x10016438 Info : flash size = 64 KiB Warn : Adding extra erase range, 0x0800325c .. 0x080037ff Error: error writing to flash at address 0x08000000 at offset 0x00000000 embedded:startup.tcl:1516: Error: ** Programming Failed ** in procedure 'program' in procedure 'program_error' called at file "embedded:startup.tcl", line 1581 at file "embedded:startup.tcl", line 1516 *** [upload] Error 1 ``` --- **[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:** Tue Feb 06, 2024 09:47 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 openocd-devel@lists.sourceforge.net 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.