helper/log: Fix build issue on MSYS2 and Cygwin
flash/nor/fm4: Fix build on MSYS2 with Clang
Fix build issue on MSYS2 and Cygwin
configure: Rework HAVE_CAPSTONE #define
jtag: adapter: move adapter_driver extern declaration to header file
target/dsp5680xx: cleanup retval usage
target/dsp5680xx: add missing retval assignment
target/dsp5680xx: declare vars at first use
target/dsp5680xx: remove err_check()
target/dsp5680xx: remove check_halt_and_debug()
target/dsp5680xx: remove err_check_propagate()
target/dsp5680xx: cleanup code confusing cppcheck
target/semihosting_common: remove redundant NULL check
target/arm_simulator: fix undefined behaviour
rtos/hwthread: move pointer deref after NULL check
pld/gowin: move pointer deref after NULL check
pld/gatemate: move pointer deref after NULL check
jtag/drivers/presto: fix potential divide by 0
flash/nor/str7x: fix undefined behaviour
flash/nand/core: remove redundant NULL check
ARM: VFP register offset shift and GDB crash on cores without MON/HYP extensions
I've tested this with an ESP32-WROVER-E WCH JTAG DevKit which has a CH347 chip with firmware version 5.44 and found that's working. It's the current version that's delivered with ESP-IDF 6.0-beta2. Tested on Ubuntu Linux. Here is the log output: Open On-Chip Debugger v0.12.0-esp32-20251215 (2025-12-15-18:17) Licensed under GNU GPL v2 For bug reports, read http://openocd.org/doc/doxygen/bugs.html Warn : DEPRECATED: auto-selecting transport "jtag". Use 'transport select jtag' to suppress this message....
bug with J-Link debug
J-Link sees zero target voltage, that likely means your reference voltage input is not connected to target's Vcc so J-Link can't communicate not knowing what voltage to use.
server/server: Fix build on FreeBSD
target/smp: reply to unknown packets in gdb_read_smp_packet
tools/checkpatch: Add Markdown linter support
log: simplify handling of mallinfo()
target: stm32mpxxx: fix return to SWD after reset
flash: nor: improve check on memory allocations
server: Make "exit" command behave consistently
Issue can be closed. This works with the master branch, the issue was w/o specifying CMSIS-DAP support the strange error as above appeared: for anyone interested: sudo apt-get install libhidapi-dev libusb-1.0-0-dev git clone https://sourceforge.net/p/openocd/code/ci/master/tree/ git submodule update --init --recursive git checkout master ./bootstrap export CFLAGS="-Wno-error=calloc-transposed-args" ./configure --enable-internal-jimtcl --enable-cmsis-dap make sudo make install flash with sudo openocd...
Issue can be closed. This works with the master branch, the issue was w/o specifying CMSIS-DAP support the strange error as above appeared: for anyone interested: sudo apt-get install libhidapi-dev libusb-1.0-0-dev git clone https://sourceforge.net/p/openocd/code/ci/master/tree/ git submodule update --init --recursive git checkout master ./bootstrap export CFLAGS="-Wno-error=calloc-transposed-args" ./configure --enable-internal-jimtcl --enable-cmsis-dap make sudo make install
Tested with RP2040 and latest openocd and fails, Distro openocd works for RP2040,. See video.
it seem that for many apt applications on ubuntu are years behind. I tried those two options as well with the same DAP. The Raspberry seems not support CMIS-SAP and the latest openocd fails as well. Bus 001 Device 029: ID 2e8a:000c Raspberry Pi Debug Probe (CMSIS-DAP) RP2350 below all run after build fresh from source and sudo make install: openocd: Open On-Chip Debugger 0.12.0+dev-02422-g5b3db97c4 (2026-03-06-14:15) Licensed under GNU GPL v2 For bug reports, read http://openocd.org/doc/doxygen/bugs.html...
it seem that for many apt applications on ubuntu are years behind. I tried those two options as well with the same DAP. The Raspberry seems not support CMIS-SAP and the latest openocd fails as well. Bus 001 Device 029: ID 2e8a:000c Raspberry Pi Debug Probe (CMSIS-DAP) RP2350 openocd: Open On-Chip Debugger 0.12.0+dev-02422-g5b3db97c4 (2026-03-06-14:15) Licensed under GNU GPL v2 For bug reports, read http://openocd.org/doc/doxygen/bugs.html Info : [rp2350.cm0] Hardware thread awareness created Info...
it seem that for many apt applications on ubuntu are years behind. I tried those two options as well with the same DAP. The Raspberry seems not support CMIS-SAP and the latest openocd fails as well. openocd: Open On-Chip Debugger 0.12.0+dev-02422-g5b3db97c4 (2026-03-06-14:15) Licensed under GNU GPL v2 For bug reports, read http://openocd.org/doc/doxygen/bugs.html Info : [rp2350.cm0] Hardware thread awareness created Info : [rp2350.cm1] Hardware thread awareness created _rv_reset_init adapter speed:...
No wonder as you're using the latest but too old release (0.12 from January 2023) and RP2350 flash support was merged in April 2025. Don't combine config files downloaded from untrustworthy sources with different OpenOCD binary. Either use fresh upstream git master (build from source or a prebuild pack) - it will support rp2350 except RISC-V cores, or use RPi fork https://github.com/raspberrypi/openocd for complete rp2350 support
RP2350 flash fails with Incorrect RP2040 BOOT ROM version
tcl/target/nordic/nrf53: fix empty event handler
target/arm_adi_v5: search for multiple AP types much more effective way
server/gdb: Add support for NVM banks without sectors
The issue with versions of CH347 5.44 and 4.41
Comparing the Samsung K9F1G08U0D (2048 + 64 page size) datasheet with that of K9F1G08U0C (512 + 16 page size), you can realize the significant difference of spare data handling. For the 2048 page size NAND flash, the spare area is selected by the highest column address. For the 512 page size NAND, there's no such a bit in the address sequence, but the spare area can be read by the NAND_CMD_READOOB command. The page program command supports loading 512 + 16 bytes at once, writing the page data with...
configure.ac: Replace --enable-malloc-logging with a new runtime log level.
configure: silent MacOS clang warning gnu-folding-constant
transport: don't warn when a transport is selected twice
target: stm32u0x: add transport swd
target: stm32l0x: drop swj on swd only target
target: stm32g0x: drop swj on swd only target
target: stm32f0x: drop swj on swd only target
target: stm32c0x: drop swj on swd only target
tcl/target/numicro*: drop swj on swd only target
tcl/target/lpc8nxx: drop swj on swd only target
tcl/target/psoc4: drop swj on swd only targets
tcl/target/nordic: drop swj on swd only targets
tcl/target/klx, ke0x: drop swj on swd only targets
tcl/target/at91samd, atsame5x: drop swj on swd only targets
tcl/target/rp2040, rp2350: use swd newdap instead of swj_newdap
flash: read only alias
flash: ROM support
target: clean up return value of target_type::blank_check_memory()
flash: virtual: simplify error checking
I cannot see the connections in the pictures nor the pinout of the DAPLINK, but the removed jumpers are ok. You need to connect the GND between the boards, for sure, and VDD 3.3V as you said required by your DAPLINK. The SWDIO goes to PA13, that is on pin 13 of CN7 The SWCLK goes to PA14, that is on pin 15 of CN7 Probably you have simply swapped SWDIO and SWCLK. Or, the firmware in the STM32F446 is blocking the SWD interface. Without a NRST driven by the DAPLINK, you can try to keep pressed the black...
tcl/target/ti/mspm0.cfg: drop swj on swd only target
flash/nor/mspm0.c: support new parts
flash/nor/mspm0.c: add parts.
flash/nor/mspm0.c: remove MSPM0G3505TDGS28R
flash/nor/mspm0.c: organize parts
meta: Add editor configuration
I have done still same issue :
On the Nucleo board there are two jumpers, just above the crystal of the on-board ST-Link. You need to remove them to isolate the SWD port of the ST-Link from the F446. With the jumpers in place, the on-board ST-Link will prevent using the external CMSIS-DAP. Please reply if this fixes the issue, so we can close the ticket
CMSIS-DAP SWD: "SWD ack not OK @ 0 JUNK" and "Error connecting DP: cannot read IDR"
Unexpected behavior of writing 512 page size NAND with `oob_only` mode
flash/nor/spi: Add Boya-Micro BY25Q128AS and Byte-Semi BY25Q16ES flash
target: arm_dap: Fix crash in 'dap info' command
log: change line counter to unsigned
target: cortex-m: defer cache identification on Cortex-M85 under reset
configure.ac: Detect mallinfo automatically
README.md: Fix Markdown linter errors
README.macOS: Align structure and fix linter errors
README.Windows: Avoid multiple top-level headings
README: Rework installation section
README.macOS: Use Markdown syntax
README.Windows: Use Markdown syntax
README: Use Markdown extension
server: close the TCP socket while stopping a service
target: openrisc: jsp_server: check for out of memory, fix memory leak
server: gdb_server: check for out of memory and fix a memory leak
target: arm_tpiu_swo: fix memory leak on add_service() failure
server: fix double free() on add_service() early return
flash/stm32l4x: Fix flash size address for STM32WBA5
doc: add STM32WBA as supported by flash driver 'stm32l4x'
flash: nor: keep Windows backslashes in flash list output
log: avoid incrementing 'count' for discarded log lines
tcl/target: Move GigaDevice configs into vendor directory
tcl/target: Fix include paths and standardise max32 configs
tcl/target: Add max32662.cfg
tcl/target: Add max32660.cfg
tcl/target: Stop setting adapter speed in max32680.cfg