|
From: ravi k. <rav...@gm...> - 2019-06-26 13:15:36
|
Thank you for the clarification. but even i tried connection with swd adapter but still im facing the below problem. root@yash01-desktop:/home/yash01/Videos/code/tcl# openocd -f interface/ftdi/ngxtech.cfg -c "transport select swd" -f target/at91samdXX.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 WARNING! This file was not tested with real interface, but is assumed to work as this interface uses the same layout as configs that were verified. Please report your experience with this file to openocd-devel mailing list, so it could be marked as working or fixed. Info : FTDI SWD mode enabled swd none separate adapter speed: 400 kHz ---------- cortex_m reset_config sysresetreq Info : Listening on port 6666 for tcl connections Info : Listening on port 4444 for telnet connections Error: SWD mode is active but SWD_EN signal is not defined On Wed, Jun 26, 2019 at 6:09 PM Andreas Fritiofson < and...@gm...> wrote: > > > On Wed, Jun 26, 2019 at 2:16 PM ravi kiran <rav...@gm...> > wrote: > >> # script for Atmel SAMD, SAMR, SAML or SAMC, a Cortex-M0 chip >> # >> # >> # samdXX devices only support SWD transports. >> > > The config file says it. The chip doesn't support JTAG. So you'll need to > have an adapter that can speak SWD (the NGX one doesn't), and you'll need > to specify SWD as the transport *before* sourcing the target config file. > > For example: > > openocd -f interface/your-swd-capable-adapter.cfg -c "transport select > swd" -f target/at91samdXX.cfg > > Note that you have an additional problem in your command line; you're > sourcing a board file for a board that has an integrated debug adapter, but > you have already sourced an adapter file. If you don't have that exact > board, source the target file directly, as above. If you do have that > Xplained board, then why do you use an external debug adapter? > > /Andreas > |