Menu
▾
▴
#238 Atmel at91saml21j18b board configuration error with Jtag connectivity Through Openocd Server.
new
None
Hello actually i'm trying to interface a saml21 board with Jtag through openocd server.But i'm facing some problem in configuration where it is throwing Invalid ACK (0) in DAP response Error...someone please help me to find a solution for this problem.
Saml21 board interface through JTag
high
2019-06-10
2019-05-24
No
------------Configuration Script used for interface-----------------
# samdXX devices only support SWD transports.
source [find target/swj-dp.tcl]
if { [info exists CHIPNAME] } {
set _CHIPNAME $CHIPNAME
} else {
set _CHIPNAME at91samd
}
if { [info exists ENDIAN] } {
set _ENDIAN $ENDIAN
} else {
set _ENDIAN little
}
# Work-area is a space in RAM used for flash programming
# By default use 2kB
if { [info exists WORKAREASIZE] } {
set _WORKAREASIZE $WORKAREASIZE
} else {
set _WORKAREASIZE 0x800
}
if { [info exists CPUTAPID] } {
set _CPUTAPID $CPUTAPID
} else {
set _CPUTAPID 0x4ba00477
}
adapter_khz 1500
#swj_newdap $_CHIPNAME cpu -irlen 4 -expected-id $_CPUTAPID
jtag newtap $_CHIPNAME cpu -irlen 4 -ircapture 0x1 -irmask 0xf -expected-id $_CPUTAPID -ignore-version
dap create $_CHIPNAME.dap -chain-position $_CHIPNAME.cpu
set _TARGETNAME $_CHIPNAME.cpu
target create $_TARGETNAME cortex_m -endian $_ENDIAN -dap $_CHIPNAME.dap
$_TARGETNAME configure -work-area-phys 0x20000000 -work-area-size $_WORKAREASIZE -work-area-backup 0
# dsu_reset_deassert configures whether we want to run or halt out of reset,
# then instruct the DSU to let us out of reset.
$_TARGETNAME configure -event reset-deassert-post {
at91samd dsu_reset_deassert
}
# SRST (wired to RESET_N) resets debug circuitry
# srst_pulls_trst is not configured here to avoid an error raised in reset halt
reset_config srst_gates_jtag
adapter_khz 400
# Atmel's EDBG (on-board cmsis-dap adapter of Xplained kits) works
# without problem at maximal clock speed. Atmel recommends
# adapter speed less than 10 * CPU clock.
# adapter_khz 5000
if {![using_hla]} {
# if srst is not fitted use SYSRESETREQ to
# perform a soft reset
cortex_m reset_config sysresetreq
}
set _FLASHNAME $_CHIPNAME.flash
flash bank $_FLASHNAME at91samd 0x00000000 0 1 1 $_TARGETNAME
--------check the below logs for error--------
Open On-Chip Debugger 0.10.0+dev-00738-gc3b90c0 (2019-03-12-12:23)
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 : auto-selecting first available session transport "jtag". To override use 'transport select <transport>'.
adapter speed: 1500 kHz
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
Info : clock speed 400 kHz
Error: JTAG scan chain interrogation failed: all zeroes
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway...
Error: at91samd.cpu: IR capture error; saw 0x00 not 0x01
Warn : Bypassing JTAG setup events due to errors
Error: Invalid ACK (0) in DAP response
Error: Invalid ACK (0) in DAP response
Related
The first line of target config says:
samdXX devices only support SWD transports.This is valid also for SAML, SAMR and SAMC series.
And your log says:
Info : auto-selecting first available session transport "jtag". To override use 'transport select <transport>'.You should add
transport select swdto your user config after adapter configuration or issue
openocd -f interface/your_adapter.cfg -c 'transport select swd' -f target/at91samdXX.cfgRecommended reading
http://openocd.org/doc/html/OpenOCD-Project-Setup.html#OpenOCD-Project-Setup
thanks for the quick response....
But still im getting the same error after using the below script
--> openocd -f interface/ftdi/ngxtech.cfg -c 'gdb_flash_program enable' -f
target/at91samdXX.cfg
On Fri, May 24, 2019 at 4:08 PM Tom tom_van@users.sourceforge.net wrote:
Related
Tickets: #238
But it is working with one of our other board sam5d36Xplained not with
samal21 board.
On Fri, May 24, 2019 at 4:51 PM ravi kiran ravikiran16218@gmail.com wrote:
Related
Tickets: #238
Hello Sir even after using this command -->"openocd -f
interface/ftdi/ngxtech.cfg -c 'gdb_flash_program enable' -f
target/at91samdXX.cfg" im getting the same error..
Error: JTAG scan chain interrogation failed: all zeroes
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway...
Error: at91samd.cpu: IR capture error; saw 0x00 not 0x01
Warn : Bypassing JTAG setup events due to errors
Error: Invalid ACK (0) in DAP response
Error: Invalid ACK (0) in DAP response
Error: Invalid ACK (0) in DAP response
Please tell me where im going wrong
On Fri, May 24, 2019 at 4:52 PM ravi ravikiran16218@users.sourceforge.net
wrote:
Related
Tickets: #238
Even we are using sysresetreq in place of srst.
please do check the below configuration file.
On Mon, May 27, 2019 at 11:29 AM ravi ravikiran16218@users.sourceforge.net
wrote:
Related
Tickets: #238
yeah --> "openocd -f interface/ftdi/ngxtech.cfg -c 'gdb_flash_program
enable' -f target/at91samdXX.cfg"
----------nd i tried this too--> "openocd -f interface/ftdi/ngxtech.cfg -f
target/at91samdXX.cfg "
On Mon, May 27, 2019 at 11:35 AM ravi ravikiran16218@users.sourceforge.net
wrote:
Related
Tickets: #238
Last edit: ravi 2019-05-28
Last edit: ravi 2019-05-28
hello please help me out to solve this problem sir.
On Mon, May 27, 2019 at 11:40 AM ravi ravikiran16218@users.sourceforge.net
wrote:
Related
Tickets: #238
Hello i haven't received any response from your side regarding my query
about openocd...please help me out get out of this issue.
On Tue, May 28, 2019 at 9:52 AM ravi via OpenOCD-devel openocd-devel@lists.sourceforge.net wrote:
Tom already gave you the answer above; you're trying to use JTAG to
communicate with a chip that only speaks SWD. Your debug adapter doesn't
even support SWD.
/Andreas
ok sir thank you for the information..Actually we are using Atmel ICE ,can
i use this for Hardware debugging..? If yes give me some idea how to do
hardware debugging.
On Tue, May 28, 2019 at 2:01 PM Andreas Fritiofson nattgris@users.sourceforge.net wrote:
Related
Tickets: #238
k sir thank you for the information..Actually we are using Atmel ICE ,can
i use this for Hardware debugging..? If yes give me some idea how to do
hardware debugging.
Below is the reply i got from Tom.where it is mentioned that it also valid
for SAML, SAMR and SAMC series.
"The first line of target config says:
samdXX devices only support SWD transports.
This is valid also for SAML, SAMR and SAMC series.
And your log says:
Info : auto-selecting first available session transport "jtag". To override
use 'transport select <transport>'.</transport>
You should add
transport select swd
to your user config after adapter configuration or issue
openocd -f interface/your_adapter.cfg -c 'transport select swd' -f
target/at91samdXX.cfg"
Hello Sir i have added
----->source [find board/atmel_saml21_xplained_pro.cfg]
in configuration file ( " at91samdXX.cfg " ) instead of
---->source [find target/swj-dp.tcl]
so that i can select the device directly from config file...but here im getting the below error
Warn : Interface already configured, ignoring
interface/cmsis-dap.cfg:7: Error:
in procedure 'script'
at file "embedded:startup.tcl", line 63
at file "target/at91samdXX.cfg", line 8
at file "board/atmel_saml21_xplained_pro.cfg", line 10
may i know the solution fo the above problem..
Hello Sir i havn't received any response from yourside regarding the above error ..so i thought of rebuilding the entire openocd 0.10.0 .after that i nhave ended up with make error as follows.
So im kindley requesting you to give me atleast some idea to get out of this Build error. Thanks in Advance