From a405fd158175e48682407eb6b8566c5182f00423 Mon Sep 17 00:00:00 2001 From: oharboe Date: Mon, 8 Jun 2009 06:16:43 +0000 Subject: David Brownell - Don't let disabled TAPs be set as the current target - Improve "targets" output: * Remove undesirable "chain position" number; we discourage using them * TAP and Target column updates: + make them long enough for current usage + improve labels, removing guesswork + "TapName" label patches scan_chain output * Highlight the "current" target * Display "tap disabled" as a new pseudo-state * Update docs accordingly git-svn-id: svn://svn.berlios.de/openocd/trunk@2107 b42882b7-edfa-0310-969c-e2dbd0fdcd60 --- doc/openocd.texi | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) (limited to 'doc') diff --git a/doc/openocd.texi b/doc/openocd.texi index 65075d77..cb340b4b 100644 --- a/doc/openocd.texi +++ b/doc/openocd.texi @@ -2117,14 +2117,15 @@ You can display the list with the @command{targets} This display often has only one CPU; here's what it might look like with more than one: @verbatim - CmdName Type Endian AbsChainPos Name State --- ---------- ---------- ---------- ----------- ------------- ---------- - 0: rm9200.cpu arm920t little 2 rm9200.cpu running - 1: MyTarget cortex_m3 little 0 mychip.cpu halted + TargetName Type Endian TapName State +-- ------------------ ---------- ------ ------------------ ------------ + 0* at91rm9200.cpu arm920t little at91rm9200.cpu running + 1 MyTarget cortex_m3 little mychip.foo tap-disabled @end verbatim One member of that list is the @dfn{current target}, which is implicitly referenced by many commands. +It's the one marked with a @code{*} near the target name. In particular, memory addresses often refer to the address space seen by that current target. Commands like @command{mdw} (memory display words) -- cgit v1.2.3