Hello AutoDevKit Support Team,
I’m setting up an AEK-MCU-C4MINI1 board and I’m unable to get a working debug session through the board’s mini-USB (P2). I’ve read the user manual, followed the bring-up steps, and tried several configurations, but OpenOCD never manages to see the device over JTAG.
Summary
- Expected: OpenOCD starts, identifies the SPC58 device, and GDB halts at main().
- Actual: OpenOCD starts but repeatedly reports JTAG scan/IDCODE errors (“all ones”; IR capture 0x3F). GDB then disconnects.
Hardware
- Board: AEK-MCU-C4MINI1 (power to J2 = 12 V, S1 ON; D10 LED on)
- Connection: single mini-USB to P2 (no external probe connected to J3)
- Windows Device Manager shows:
- Ports (COM & LPT): AEK-MCU-C4MINI1 (Interface 1) (COMx)
- USB devices: AEK-MCU-C4MINI1 (Interface 0)
- USB IDs seen via Zadig: 0483:049A for both interfaces
Host / Tools
- Windows 11 x64
- AutoDevKit Studio 2.6.1
- OpenOCD bundled with AutoDevKit: 0.12.0+dev-00318-g0e98d766e
- GDB: ppc-freevle-eabi-gdb.exe (AutoDevKit toolchain)
Project
- New SPC5 project (RLA bareboard / empty app for SPC58ECxx), minimal main.c that loops; builds fine to build/out.elf.
Current debug config (OpenOCD)
- Config options used most recently:
-s "C:\AutoDevKitStudio-2.6.1\openocd\scripts" -f board\spc58xc_dis.cfg -c "transport select jtag" -c "adapter speed 50" -c "reset_config srst_only srst_nogate connect_assert_srst"
Representative logs
Open On-Chip Debugger 0.12.0+dev-00318-g0e98d766eadapter srst pulse_width: 100adapter speed: 50 kHzInfo : Listening on port 3333 for gdb connectionsError: JTAG scan chain interrogation failed: all onesError: spc58xc.tap: IR capture error; saw 0x3f not 0x01Error: no IDCODE present on deviceWarn : target spc58xc.cpu examination failed...Error: Connect failed ... 'gdb' connection rejected
What I’ve already tried
Power-cycle, different USB ports and data-rated cable; ensured no terminal has COM open.
Held RESET during attach; used very low adapter speeds (4000 → 250 → 100 → 50 kHz).
Tested both spc58xc_dis.cfg and spc58ec.cfg.
Driver mapping via Zadig:
Confirmed only the P2 USB is used (nothing on J3).
Attempted UDE briefly, but I don’t have a PLS UAD probe, so I returned to OpenOCD.
Questions / Requests
Official, board-specific debug recipe for AEK-MCU-C4MINI1 using the onboard USB:
Exact driver mapping per interface (which driver for Interface 0 and Interface 1, and expected USB VID:PID values).
The correct OpenOCD .cfg file for this board (board vs. target), and any required reset_config / JTAG options.
Any jumpers/straps or special sequence needed to enable JTAG/OnCE on this board (beyond S1 and RESET).
A known-good sample project + debug configuration (or a screenshot of the Debug Configuration “Debugger” tab) that you recommend.
Please confirm whether UDE is required for this board, or if the onboard USB path with OpenOCD is the supported method.
If possible, please assign an expert or provide a step-by-step guide (driver install, expected Device Manager entries, OpenOCD line, and how to verify the chain/IDCODE).
I’m happy to provide additional logs or run any diagnostic commands you suggest. I’ve read the user manual but I’m still blocked at the debug-attach step.
Thank you for your help—please let me know the correct setup and any board-specific requirements, or schedule a short session with an expert to get this unblocked.
