Openocd and Arch Pro

Hi,

I’m running Ubuntu 20.04

I have just received my nice shiny new arch pro board.

I have managed to flash ‘blinky’, no big deal just copy a file.

Now what I want to do is debug blinky

I found a config file in /usr/share/openocd/scripts/board/mbed-lpc1768.cfg

So I run it:

$ openocd -f /usr/share/openocd/scripts/board/mbed-lpc1768.cfg

Open On-Chip Debugger 0.10.0+dev
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html
Info : auto-selecting first available session transport "swd". To override use 'transport select <transport>'.
cortex_m reset_config sysresetreq

Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
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 10 kHz
Info : SWD DPIDR 0x2ba01477
Info : lpc17xx.cpu: hardware has 6 breakpoints, 4 watchpoints
Info : Listening on port 3333 for gdb connections


All looks good.

I run up gdb and connect

$ /usr/local/gcc-arm-none-eabi-9-2019-q4-major/bin/arm-none-eabi-gdb ./BUILD/ARCH_PRO/GCC_ARM/mbed.elf

<licencs text deleted>

Reading symbols from ./BUILD/ARCH_PRO/GCC_ARM/mbed.elf...
(gdb) target remote localhost:3333
Remote debugging using localhost:3333
Remote communication error.  Target disconnected.: Connection reset by peer.
(gdb) target remote localhost:3333
Remote debugging using localhost:3333
Remote communication error.  Target disconnected.: Connection reset by peer.
(gdb) 

I can telnet to openocd and halt and reset the device. Anybody suggest how I can progress ?

Thanks.

I haven’t tried GCC-9. I used it on GCC-4.8 very early, no problem