zcy
/
tinyriscv-openocd
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
tinyriscv-openocd/tcl/target/am437x.cfg

52 lines
1.4 KiB
INI
Raw Normal View History

cfg: add TI am43xx devices This adds support for the am43xx SoC and the AM437x GP EVM and AM438x ePOS EVM. Change-Id: I09cbb09072f38e0e08fdd520dedb6e67d45056be Signed-off-by: Felipe Balbi <balbi@ti.com> Signed-off-by: Tom Rini <trini@ti.com> Reviewed-on: http://openocd.zylin.com/2047 Tested-by: jenkins Reviewed-by: Paul Fertser <fercerpav@gmail.com>
2014-03-01 00:22:38 +00:00
source [find target/icepick.cfg]
if { [info exists CHIPNAME] } {
set _CHIPNAME $CHIPNAME
} else {
set _CHIPNAME am437x
}
#
# M3 DAP
#
if { [info exists M3_DAP_TAPID] } {
set _M3_DAP_TAPID $M3_DAP_TAPID
} else {
set _M3_DAP_TAPID 0x4b6b902f
}
jtag newtap $_CHIPNAME m3_dap -irlen 4 -ircapture 0x1 -irmask 0xf -expected-id $_M3_DAP_TAPID -disable
jtag configure $_CHIPNAME.m3_dap -event tap-enable "icepick_d_tapenable $_CHIPNAME.jrc 11"
#
# Cortex A9 DAP
#
if { [info exists DAP_TAPID] } {
set _DAP_TAPID $DAP_TAPID
} else {
set _DAP_TAPID 0x4b6b902f
}
jtag newtap $_CHIPNAME dap -irlen 4 -ircapture 0x1 -irmask 0xf -expected-id $_DAP_TAPID -disable
jtag configure $_CHIPNAME.dap -event tap-enable "icepick_d_tapenable $_CHIPNAME.jrc 12"
#
# ICEpick-D (JTAG route controller)
#
if { [info exists JRC_TAPID] } {
set _JRC_TAPID $JRC_TAPID
} else {
set _JRC_TAPID 0x0b98c02f
}
jtag newtap $_CHIPNAME jrc -irlen 6 -ircapture 0x1 -irmask 0x3f -expected-id $_JRC_TAPID -ignore-version
jtag configure $_CHIPNAME.jrc -event setup "jtag tapenable $_CHIPNAME.dap"
# some TCK tycles are required to activate the DEBUG power domain
jtag configure $_CHIPNAME.jrc -event post-reset "runtest 100"
#
# Cortex A9 target
#
set _TARGETNAME $_CHIPNAME.cpu
tcl: target: am437x.cfg: pass correct dbgbase Since commit ec9ccaa28849 (arm_adi_v5: make dap_lookup_cs_component() traverse subtables and handle multicore) AM437x devices can't be used with OpenOCD anymore. The reason is that dbgbase used to be set to zero before that commit and that just happens to work with AM437x devices. A more robust solution is to pass correct dbgbase when creating the target, which this commit does. Signed-off-by: Felipe Balbi <balbi@ti.com> Change-Id: Iaf2617804324de8094b25137943e08b84f14c75f Reviewed-on: http://openocd.zylin.com/2602 Tested-by: jenkins Reviewed-by: Paul Fertser <fercerpav@gmail.com> Reviewed-by: Tom Rini <trini@konsulko.com>
2015-03-13 22:10:42 +00:00
target create $_TARGETNAME cortex_a -chain-position $_CHIPNAME.dap -dbgbase 0x80000000
cfg: add TI am43xx devices This adds support for the am43xx SoC and the AM437x GP EVM and AM438x ePOS EVM. Change-Id: I09cbb09072f38e0e08fdd520dedb6e67d45056be Signed-off-by: Felipe Balbi <balbi@ti.com> Signed-off-by: Tom Rini <trini@ti.com> Reviewed-on: http://openocd.zylin.com/2047 Tested-by: jenkins Reviewed-by: Paul Fertser <fercerpav@gmail.com>
2014-03-01 00:22:38 +00:00
tcl: target: am437x: use entire SRAM area According to AM4379 TRM [1], table 2-1 L3 Memory Map, we have a total of 256KiB and there's no reason not to use it all. [1] http://www.ti.com/lit/ug/spruhl7b/spruhl7b.pdf Change-Id: I117f2afe721bc4e3f0df304d3542e1a91aa69d12 Signed-off-by: Felipe Balbi <balbi@ti.com> Reviewed-on: http://openocd.zylin.com/2611 Tested-by: jenkins Reviewed-by: Tom Rini <trini@konsulko.com> Reviewed-by: Paul Fertser <fercerpav@gmail.com>
2015-03-14 00:32:01 +00:00
# SRAM: 256K at 0x4030.0000
$_TARGETNAME configure -work-area-phys 0x40300000 -work-area-size 0x40000