armada370: initial support for Marvell Armada 370 family

Initial support for using the jtag interface to the Marvell Armada 370
family of SoCs.

Change-Id: Id823a567e8805ac622c3c330bc111297c1dae37e
Signed-off-by: Greg Ungerer <gerg@uclinux.org>
Reviewed-on: http://openocd.zylin.com/1690
Tested-by: jenkins
Reviewed-by: Spencer Oliver <spen@spen-soft.co.uk>
This commit is contained in:
Greg Ungerer 2013-10-09 23:15:07 +10:00 committed by Spencer Oliver
parent 504f79a906
commit b3a3d8312e
1 changed files with 33 additions and 0 deletions

33
tcl/target/armada370.cfg Normal file
View File

@ -0,0 +1,33 @@
#
# armada370 -- support for the Marvell Armada/370 CPU family
#
# gerg@uclinux.org, OCT-2013
#
if { [info exists CHIPNAME] } {
set _CHIPNAME $CHIPNAME
} else {
set _CHIPNAME armada370
}
if { [info exists CPUTAPID] } {
set _CPUTAPID $CPUTAPID
} else {
set _CPUTAPID 0x4ba00477
}
jtag newtap $_CHIPNAME dap -irlen 4 -ircapture 0x1 -irmask 0xf -expected-id $_CPUTAPID
set _TARGETNAME $_CHIPNAME.cpu
target create $_TARGETNAME cortex_a8 -chain-position $_CHIPNAME.dap
proc armada370_dbginit {target} {
cortex_a dbginit
}
$_TARGETNAME configure -event reset-assert-post "armada370_dbginit $_TARGETNAME"
# We need to init now, so we can run the apsel command.
init
dap apsel 1