Re: [OpenOCD-user] Error: JTAG scan chain interrogation failed: all zeroes

[ravi k. <rav...@gm...>]

No, it doesn't.
Actually it is telling that interface is required to debug
--terminal log after executing ->openocd -f
board/atmel_saml21_xplained_pro.cfg

root@yash01-desktop:/home/yash01/Videos/code/tcl# openocd -f
board/atmel_saml21_xplained_pro.cfg
Open On-Chip Debugger 0.10.0+dev-00735-g56568b7-dirty (2019-06-10-18:27)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Error: The specified debug interface was not found (cmsis-dap)
The following debug interfaces are available:
1: ftdi
2: usb_blaster
3: ft232r
4: presto
5: usbprog
6: openjtag
7: jlink
8: vsllink
9: rlink
10: ulink
11: arm-jtag-ew
12: hla
13: osbdm
14: opendous
15: aice
16: xds110

root@yash01-desktop:/home/yash01/Videos/code/tcl#




On Thu, Jun 27, 2019 at 6:54 PM Andreas Fritiofson <
and...@gm...> wrote:

>
>
> On Thu, Jun 27, 2019 at 2:51 PM ravi kiran <rav...@gm...>
> wrote:
>
>> Hello Sir actually we are not using this setup for flashing the code
>> instead we are using this for hardware diagnostic through java gui. We are
>> sending testing commands from the gui through jtag for all the hardware
>> components via telnet server.
>>
>>
> Ok, but that's not what I asked. I wanted to know if the built-in debugger
> works, before potentially trying to see what the problem is with the ngx
> setup. Connect only USB to the debug port on the Xplained board (and
> separate power if needed) and run OpenOCD with the following command:
>
> openocd -f board/atmel_saml21_xplained_pro.cfg
>
> Does it work? Otherwise it's pointless to find any problems with your
> other setup.
>
> If it does work, what do you need the ngx for?
>
> /Andreas
>