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.
========================================
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
========================================
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.
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
Examples:
"NXP LPC Series"
"Atmel SAM7 Series"
-
+
========================================
D) The actual part number on the package
ie: Olimex, LogicPD, Freescale(eval board)
========================================
-
+
(G) Identifying information on the board.
Not good: "iar red ST eval board"
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.
+
+========================================