omap3530: target reset/init improvements
commit4a91b070ffd7890c5a0b6381997787136d797bd5
authorDavid Brownell <dbrownell@users.sourceforge.net>
Tue, 27 Oct 2009 05:53:18 +0000 (26 22:53 -0700)
committerDavid Brownell <dbrownell@users.sourceforge.net>
Tue, 27 Oct 2009 05:53:18 +0000 (26 22:53 -0700)
treeca70e5f1d1a615c9bc0696bd5deafa7bd73ebe05
parentddade10d4a9309ea252b0a03cde9f757b5c71778
omap3530: target reset/init improvements

Now I can issue "reset halt" and have everything act smoothly;
the vector_catch hardware is obviously not kicking in, but the
rest of the reset sequence acts sanely.

 - TAP "setup" event enables the DAP, not omap3_dbginit
   (resolving a chicken/egg bug I noted a while back)
 - Remove stuff from omap3_dbginit which should never be
   used in event handlers
 - Cope better with slow clocking during reset

Also, stop hard-wiring the target name: use the input params in
the standard way, and set up $_TARGETNAME as an output param.

Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
tcl/target/omap3530.cfg