Don't be fooled by this simplified diagram found in ARM documentation: it's so simplified that it's wrong. SWDIO correctly changes on failing SWCLK edge when the adapter transmits and on rising SWCLK edge when SWDP transmits. See 8690: target/arm_adi: add URLs of latest ARM ADI spec | https://review.openocd.org/c/openocd/+/8690 https://documentation-service.arm.com/static/5ea6eaba9931941038df04ff?token=
--- **[tickets:#456] aducm360 swd could not find MEM-AP** **Status:** new **Milestone:** 0.10.0 **Labels:** aducm360_swd **Created:** Tue Jul 01, 2025 01:58 PM UTC by Den **Last Updated:** Wed Jul 02, 2025 11:48 AM UTC **Owner:** nobody **Attachments:** - [attach.zip](https://sourceforge.net/p/openocd/tickets/456/attachment/attach.zip) (751.5 kB; application/x-zip-compressed) aducm360 not connect to openocd via jtag-swd. adapter based on ftdi2232 used original config aducm360.cfg used my config ftdi_swd.cfg tested in openocd v10 & v12 command: openocd.exe -d0 -f \interface\ftdi\ftdi_swd.cfg -f target\aducm360.cfg -c init -c targets -c "reset halt" -c "flash erase 0" -c shutdown log: debug_level: 0 cortex_m reset_config vectreset Error: [aducm360.cpu] Could not find MEM-AP to control the core TargetName Type Endian TapName State -- ------------------ ---------- ------ ------------------ ------------ 0* aducm360.cpu cortex_m little aducm360.cpu unknown Error: [aducm360.cpu] Could not find MEM-AP to control the core Error: [aducm360.cpu] Debug AP not available, reset NOT asserted! in attach log from debug level 3 ftdi_swd.cfg log saleae logic 1.2.18 --- 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.
