omap3530.cfg: use new "reset-assert" event

Replaces previous "reset-assert-pre" workaround.

Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
This commit is contained in:
David Brownell 2009-11-27 18:50:31 -08:00
parent e0cb27df6b
commit ddce517e3a
1 changed files with 2 additions and 2 deletions

View File

@ -65,10 +65,10 @@ proc omap3_dbginit {target} {
jtag_rclk 1000 jtag_rclk 1000
$_TARGETNAME configure -event "reset-start" { jtag_rclk 1000 } $_TARGETNAME configure -event "reset-start" { jtag_rclk 1000 }
# REVISIT This assumes that SRST is unavailable, so we must assert reset # Assume SRST is unavailable (e.g. TI-14 JTAG), so we must assert reset
# ourselves using PRM_RSTCTRL. RST_GS (2) is a warm reset, like ICEpick # ourselves using PRM_RSTCTRL. RST_GS (2) is a warm reset, like ICEpick
# would issue. RST_DPLL3 (4) is a cold reset. # would issue. RST_DPLL3 (4) is a cold reset.
set PRM_RSTCTRL 0x48307250 set PRM_RSTCTRL 0x48307250
$_TARGETNAME configure -event reset-assert-pre "$_TARGETNAME mww $PRM_RSTCTRL 2" $_TARGETNAME configure -event reset-assert "$_TARGETNAME mww $PRM_RSTCTRL 2"
$_TARGETNAME configure -event reset-assert-post "omap3_dbginit $_TARGETNAME" $_TARGETNAME configure -event reset-assert-post "omap3_dbginit $_TARGETNAME"