Post Go back to editing

EVAL-ADICUP360 & Crosscore Embedded Studio OpenOCD issue

Category: Software
Product Number: EVAL-ADICUP360
Software Version: CCES 2.11.1, ADuCM36x DFP CMSIS Pack version 1.0.4


I am trying to get an EVAL-ADICUP360 up and running with CCES 2.11.1. This was downloaded and installed today along with the ADuCM36x DFP CMSIS Pack version 1.0.4 per the guide in the Wiki here:

I also have the generic ARM CMSIS pack installed 5.9.0

After doing this I imported the example projects from Github per these instructions:

I am able to build the Blinky example project, however I am unable to download and debug on the hardware. The supplied Openocd aducm36x.cfg file appears to use deprecated config items. This is the output I get when I try and download:

Open On-Chip Debugger (Analog Devices CCES 2.11.1) OpenOCD 0.10.0 (2022-09-07-13:55)
Licensed under GNU GPL v2
Report bugs to <>
Info : auto-selecting first available session transport "swd". To override use 'transport select <transport>'.
DEPRECATED! use 'adapter speed' not 'adapter_khz'
C:/Analog Devices/CrossCore Embedded Studio 2.11.1/ARM/packs/AnalogDevices/ADuCM36x_DFP/1.0.4/openocd/scripts/target/aducm36x.cfg:38: Error: target requires -dap parameter instead of -chain-position!
in procedure 'script'
at file "embedded:startup.tcl", line 26
at file "C:/Analog Devices/CrossCore Embedded Studio 2.11.1/ARM/packs/AnalogDevices/ADuCM36x_DFP/1.0.4/openocd/scripts/target/aducm36x.cfg", line 38

I have modified the config file with what I think are the correct fixes and I can get a bit further but the device eventually times out waiting for the device to halt:

Open On-Chip Debugger (Analog Devices CCES 2.11.1) OpenOCD 0.10.0 (2022-09-07-13:55)
Licensed under GNU GPL v2
Report bugs to <>
Info : auto-selecting first available session transport "swd". To override use 'transport select <transport>'.
Info : CMSIS-DAP: SWD Supported
Info : CMSIS-DAP: FW Version = 1.0
Info : CMSIS-DAP: Interface Initialised (SWD)
Info : SWCLK/TCK = 0 SWDIO/TMS = 1 TDI = 0 TDO = 0 nTRST = 0 nRESET = 1
Info : CMSIS-DAP: Interface ready
Info : clock speed 1000 kHz
Info : SWD DPIDR 0x2ba01477
Info : DAP aducm360.cpu DPIDR indicates ADIv5 protocol is being used
Info : SWD DPIDR 0x2ba01477
Info : aducm360.cpu: hardware has 6 breakpoints, 4 watchpoints
Info : starting gdb server for aducm360.cpu on 3333
Info : Listening on port 3333 for gdb connections

Error: timed out while waiting for target halted
Warn : Flash driver of aducm360.flash does not support free_driver_priv()
Info : Halt timed out, wake up GDB.

For some reason it won't let me attach the modified file so here it is in line:

# Analog Devices ADuCM36x

source [find target/swj-dp.tcl]

if { [info exists CHIPNAME] } {
} else {
   set _CHIPNAME aducm360

if { [info exists ENDIAN] } {
} else {
   # This config file was defaulting to big endian..
   set _ENDIAN little

if { [info exists WORKAREASIZE] } {
} else {
   set _WORKAREASIZE 0x1000

if { [info exists CPUTAPID] } {
} else {
   set _CPUTAPID 0x2ba01477

swj_newdap $_CHIPNAME cpu -irlen 4 -ircapture 0x1 -irmask 0xf -expected-id $_CPUTAPID

adapter speed 1000

## Target configuration
dap create $_CHIPNAME.dap -chain-position $_CHIPNAME.cpu
target create $_TARGETNAME cortex_m -endian $_ENDIAN -dap $_CHIPNAME.dap
#target create $_TARGETNAME cortex_m -endian $_ENDIAN -chain-position $_TARGETNAME

$_TARGETNAME configure -work-area-phys 0x20000000 -work-area-size $_WORKAREASIZE -work-area-backup 0

# flash size will be probed
flash bank $_FLASHNAME aducm360 0x00 0 0 0 $_TARGETNAME

adapter srst delay 100
cortex_m reset_config vectreset

flash probe 0 
proc peek32 {address} {
	mem2array t 32 $address 1
	return $t(0)

arm semihosting enable

#implement ADI Halt after bootkernel
proc init_reset {mode} {
	echo "RESET: ADI halt after bootkernel"
	set rvec [peek32 0x4]
	set emcr [peek32 0xe000edfc]
	set hcsr [peek32 0xe000edf0]
	bp $rvec 2 hw
	mww 0xe000edf0 0xA05F0003
	mww 0xe000edfc 0x1000500
	mww 0xE000ED0C 0x05FA0004
	mww 0xe000edfc $emcr
	mww 0xe000edf0 $hcsr
	rbp $rvec

	if { $mode == "run" } {

The board does appear as an MBED flash drive in windows, and I can see activity on the SWDIO & SDCLK lines on the board whilst it is attempting to connect so most of the debug chain is working. 

I would appreciate guidance on how to proceed with this? 



  • I am facing a similar issue, just on the EVAL-ADICUP3029. Has anyone found a fix? 

  • Analog support offline eventually confirmed that this was a real issue, but have not provided a proper fix. They clearly updated OpenOCD in the Crosscore Embedded Studio but not all the CMSIS packs and didn't test everything. Not very impressive & a terrible out of the box experience.

    I ended up abandoning the onboard debugger and used an external J-Link probe together with the J-Link GDB server which works.

  • Hey Jonathan! 

    I managed to get mine to build the blinky project example from the CCES projects window and this is what I did:

    I hope this helps anyone out there with removing some of the errors/warnings.

    However, I'm still not getting an output on the board even after flashing the code in, so I'm not too sure if it's not giving the correct output due to unknown openocd errors, or if the code is incorrect. Can any Analog Devices support staff verify that the blinky code I included is still up and running, so I could pinpoint exactly why the LEDs on my board are not blinking?