We are evaluating an ADuCM362 evaluation board using CrossCore 2.8 and testing applications such as Blinky fails to download using the jlink and CrossCore debugger. The code builds without errors. The Seggar jlink commander v6.3 finds the Seggar ADI lite jlink device and talks to the ADuCM362 processor if the device is set to use the SWD option. I do not think the OpenOCD script in aducm36x from the new Analog DAP 1.0.3 is setting the jlink to SWD but we do not know how to do it or even if this assumption is the real problem. We are new to this type of programming but did get a ADuCM360 board with the CMSIS DAP to work fine. The problem appears to be communication with the ADI Lite Seggar Jlink from CrossCore/OpenOCD. I hope somebody can tell us how to fix.
Debugger Console gives: for the RTX_Blinky, the Blinky_362 did the same- using GDB and OpenOCD [emulator] option:
Please find attached an updated ADuCM362 Blinky example for the EVAL-ADuCM362-ADuCM363 Evaluation Board | Analog Devices.
I have also added a section on our ADuCM360 Wiki about How to debug an programs using an ADuCM362 and ADuCM363 Evaluation Board.
Apologies for the inconvenience.