Skip to content
Snippets Groups Projects
Select Git revision
  • dw-cmsisdap-path
  • max32xxx default protected
2 results
Search by author
  • Any Author
  • 9R 9R
  • Administrator root
  • Andreas Schildbach pink
  • Daniel Hoffend griffon
  • Definitely Not A Robot Doloo1ai
  • Dirk Jäckel Dirk Jäckel biafra
  • G G
  • Hauke Mehrtens hauke
  • Jan Morawek RFguy
  • Julian hdsjulian
  • Lila Fisch lilafisch
  • Martin Ling martinling
  • Mateusz Zalega msgctl
  • Michael Huebler mh
  • Ole Dreessen ole
  • Phileas Phileas pl
  • Philip Brechler Philip Brechler plaetzchen
  • Renze renze
  • Sabine Wolf Bine
  • Sec 42 sec
20 authors
  1. Oct 27, 2009
    • David Brownell's avatar
      omap3530: target reset/init improvements · 4a91b070
      David Brownell authored 
      
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: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
      4a91b070
  3. Oct 25, 2009
  5. Oct 21, 2009
  7. Oct 20, 2009
  9. Oct 14, 2009
  11. Oct 13, 2009
  13. Oct 12, 2009
  15. Oct 10, 2009
  17. Oct 09, 2009
    • David Brownell's avatar
      make PXA255 targets enumerate sort-of-OK · 60e24aa5
      David Brownell authored 
      
Startup now mostly works, except that the initial target state
is "unknown" ... previously, it refused to even start.

Getting that far required fixing the ircapture value (which
can never have been correct!) and the default JTAG clock rate,
then providing custom reset script.

The "reset" command is still iffy.  DCSR updates, and loading
the debug handler, report numerous DR/IR capture failures.
But once that's done, "poll" reports that the CPU is halted
(which it shouldn't be, this was "reset run"!), due to the
rather curious reason "target-not-halted".

Summary:  you still can't debug these parts, but it's closer.

Signed-off-by: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
      60e24aa5
  19. Oct 08, 2009
  21. Oct 06, 2009
  23. Oct 05, 2009
  25. Oct 02, 2009
  27. Sep 30, 2009
  29. Sep 27, 2009
  31. Sep 25, 2009
  33. Sep 21, 2009
  35. Sep 19, 2009
  37. Sep 18, 2009
  39. Sep 16, 2009
  41. Sep 13, 2009
  43. Sep 12, 2009
    • oharboe's avatar
      David Brownell <david-b@pacbell.net> · 40f361dd
      oharboe authored 
      Update the board config for the DaVinci DM355 EVM so the reset-init
event handler does the rest of the work it should do:

 - minor PLL setup bugfixes
 - initialize the DDR2 controller
 - probe both NAND banks
 - initialize UART0
 - enable the icache


git-svn-id: svn://svn.berlios.de/openocd/trunk@2699 b42882b7-edfa-0310-969c-e2dbd0fdcd60
      40f361dd
  45. Sep 11, 2009
  47. Sep 10, 2009
  49. Sep 04, 2009
  51. Sep 02, 2009
  53. Aug 25, 2009