tcl/target: ti_tms570.cfg restructure dap support

[openocd] / NEWTAPS

diff --git a/NEWTAPS b/NEWTAPS
index c92308201a22deb3ad1b509dc803456e1879d2bf..10f300632945428eb72e0afde54f36a73ff43e99 100644 (file)
--- a/NEWTAPS
+++ b/NEWTAPS
@@ -4,7 +4,7 @@ Reporting Unknown JTAG TAP IDS
 If OpenOCD reports an UNKNOWN or Unexpected Tap ID please report it to
 the development mailing list - However - keep reading.
 
-openocd-development@lists.berlios.de.
+openocd-devel@lists.sourceforge.net.
 
 ========================================
 
@@ -30,7 +30,7 @@ Version Number Changes:
   not a big deal.  Please do report this information.  We'd like to
   know about it.
 
-  For example 
+  For example
 
 Error:  ERROR: Tap: s3c4510.cpu - Expected id: 0x3f0f0f0f, Got: 0x1f0f0f0f
 Error:  ERROR: expected: mfg: 0x787, part: 0xf0f0, ver: 0x3
@@ -39,7 +39,7 @@ Error:  ERROR:      got: mfg: 0x787, part: 0xf0f0, ver: 0x1
 ========================================
 
 Updating the Tap ID number your self
- 
+
   Why do this? You just want the warning to go away.  And don't want
   to update your version/instance of OpenOCD.
 
@@ -77,13 +77,13 @@ This is always a 32bit hex number.
 Examples:
     0x1f0f0f0f - is an old ARM7TDMI
     0x3f0f0f0f - is a newer ARM7TDMI
-    0x3ba00477 - is an ARM cortex M3
+    0x3ba00477 - is an ARM Cortex-M3
 
-Some chips have multiple JTAG taps - be sure to list 
+Some chips have multiple JTAG taps - be sure to list
 each one individually - ORDER is important!
 
 ========================================
-B) The maker of the part 
+B) The maker of the part
 
 Examples:
     Xilinx, Atmel, ST Micro Systems, Freescale
@@ -94,7 +94,7 @@ C) The family of parts it belongs to
 Examples:
    "NXP LPC Series"
    "Atmel SAM7 Series"
-   
+
 ========================================
 
 D) The actual part number on the package
@@ -121,7 +121,7 @@ For example: A consumer GPS unit or a cellphone
         ie: Olimex, LogicPD, Freescale(eval board)
 
 ========================================
-        
+
 (G)   Identifying information on the board.
 
       Not good:   "iar red ST eval board"
@@ -135,3 +135,11 @@ For example: A consumer GPS unit or a cellphone
     ie: An FPGA or CPLD ...
 
 ========================================
+
+(I) What target config files need updating?
+
+    In fact it's best if you submit a patch with those
+    updates.  Most of the other information listed here
+    is just to help create a good patch.
+
+========================================