diff options
| author | David Brownell <dbrownell@users.sourceforge.net> | 2010-03-05 21:09:03 -0800 |
|---|---|---|
| committer | David Brownell <dbrownell@users.sourceforge.net> | 2010-03-05 21:09:03 -0800 |
| commit | c6e323b9838254b338310ec165a5345635c5d177 (patch) | |
| tree | ac70aa0b894f928e4fded3c42965ef8020d71ec8 /doc/manual/server.txt | |
| parent | 74113cf72570a20f5f2ff66f721284bd4228aee3 (diff) | |
| download | openocd+libswd-c6e323b9838254b338310ec165a5345635c5d177.tar.gz openocd+libswd-c6e323b9838254b338310ec165a5345635c5d177.tar.bz2 openocd+libswd-c6e323b9838254b338310ec165a5345635c5d177.tar.xz openocd+libswd-c6e323b9838254b338310ec165a5345635c5d177.zip | |
doc: not all debug adapters are "dongles"
Talk more about "debug adapters" instead of only "dongles". Not all
adapters are discrete widgets; some are integrated onto boards. If
we only talk about "dongles" we rule out many valid setups, and help
confuse some users (who may be using Dongle-free environments).
Also start bringing out the point that JTAG isn't the only transport
protocol, even though OpenOCD historically presumes "all is JTAG".
(Not all debug adapters are JTAG adapters, or JTAG-only adapters.)
Plus a few minor fixes (spelling etc) in the vicinity of those changes,
and updates about FT2232H clocking issues (they can go faster than the
older chips, and can support adaptive clocking).
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Diffstat (limited to 'doc/manual/server.txt')
| -rw-r--r-- | doc/manual/server.txt | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/manual/server.txt b/doc/manual/server.txt index 5250f7f1..f75f1d1d 100644 --- a/doc/manual/server.txt +++ b/doc/manual/server.txt @@ -207,7 +207,7 @@ upon it, sometimes that is the only scheme available. As a small group of developers, supporting all the platforms and targets in the debugger will be difficult, as there are enough problem -with the plethora of Dongles, Chips, and different target boards. +with the plethora of Adapters, Chips, and different target boards. Yes, the TCL interface might be suitable, but it has not received much love or attention. Perhaps it will after you read and understand this. @@ -235,7 +235,7 @@ different host-side GDB.. Sure - a <em>man on a mission</em> can make that work. The GUI might be libopenocd + Perl/TK, or maybe an Eclipse Plug-in. That is a development support nightmare for reasons described -above. We have enough support problems as it is with targets, dongles, +above. We have enough support problems as it is with targets, adapters, etc. @section serverdocshttpbg HTTP Server Background @@ -270,8 +270,8 @@ every peripheral register on the target platform. That also is transportable, regardless of the OpenOCD host platform: Linux/X86, Linux/ARM, FreeBSD, Cygwin, MingW, or MacOSX. -You could even port OpenOCD to an Google Android and use it as a -bit-bang dongle JTAG serving web pages. +You could even port OpenOCD to an Android system and use it as a +bit-banging JTAG Adapter serving web pages. @subsection serverdocshtmladv Advanced HTML Pages |