You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

146 lines
3.9KB

  1. Reporting Unknown JTAG TAP IDS
  2. ------------------------------
  3. If OpenOCD reports an UNKNOWN or Unexpected Tap ID please report it to
  4. the development mailing list - However - keep reading.
  5. openocd-devel@lists.sourceforge.net.
  6. ========================================
  7. About "UNEXPECTED" tap ids.
  8. Before reporting an "UNEXPECTED TAP ID" - take a closer look.
  9. Perhaps you have your OpenOCD configured the wrong way, maybe you
  10. have the tap configured the wrong way? Or something else is wrong.
  11. (Remember: OpenOCD does not stop if the tap is not present)
  12. This "tap id check" is there for a purpose.
  13. The goal is to help get the *right* configuration.
  14. The idea is this:
  15. Every JTAG tap is suppose to have "a unique 32bit tap id" number.
  16. They are suppose to be "sort of unique" but they are not. There are
  17. no guarantees.
  18. Version Number Changes:
  19. Sometimes, the tap ID only differs by VERSION number. If so - it's
  20. not a big deal. Please do report this information. We'd like to
  21. know about it.
  22. For example
  23. Error: ERROR: Tap: s3c4510.cpu - Expected id: 0x3f0f0f0f, Got: 0x1f0f0f0f
  24. Error: ERROR: expected: mfg: 0x787, part: 0xf0f0, ver: 0x3
  25. Error: ERROR: got: mfg: 0x787, part: 0xf0f0, ver: 0x1
  26. ========================================
  27. Updating the Tap ID number your self
  28. Why do this? You just want the warning to go away. And don't want
  29. to update your version/instance of OpenOCD.
  30. On simple systems, to fix this problem, in your "openocd.cfg" file,
  31. override the tap id. Depending on the tap, add one of these 3
  32. commands:
  33. set CPUTAPID newvalue
  34. or set BSTAPID newvalue
  35. or set FLASHTAPID newvalue
  36. or set ETMTAPID newvalue
  37. Where "newvalue" is the new value you are seeing.
  38. On complex systems, (with many taps and chips) you probably have a
  39. custom configuration file. Its is more complicated, you're going to
  40. have to read through the configuration files
  41. ========================================
  42. What to send:
  43. Cut & paste the output of OpenOCD that pointed you at this file.
  44. Please include the VERSION number of OpenOCD you are using.
  45. And please include the information below.
  46. ========================================
  47. A) The JTAG TAP ID code.
  48. This is always a 32bit hex number.
  49. Examples:
  50. 0x1f0f0f0f - is an old ARM7TDMI
  51. 0x3f0f0f0f - is a newer ARM7TDMI
  52. 0x3ba00477 - is an ARM Cortex-M3
  53. Some chips have multiple JTAG taps - be sure to list
  54. each one individually - ORDER is important!
  55. ========================================
  56. B) The maker of the part
  57. Examples:
  58. Xilinx, Atmel, ST Micro Systems, Freescale
  59. ========================================
  60. C) The family of parts it belongs to
  61. Examples:
  62. "NXP LPC Series"
  63. "Atmel SAM7 Series"
  64. ========================================
  65. D) The actual part number on the package
  66. For example: "S3C45101x01"
  67. ========================================
  68. E) What type of board it is.
  69. ie: a "commercial off the self eval board" that one can purchase (as
  70. opposed to your private internal custom board)
  71. For example: ST Micro systems has Eval boards, so does Analog Devices
  72. Or - if it is inside something "hackers like to hack" that information
  73. is helpful too.
  74. For example: A consumer GPS unit or a cellphone
  75. ========================================
  76. (F) The maker of the board
  77. ie: Olimex, LogicPD, Freescale(eval board)
  78. ========================================
  79. (G) Identifying information on the board.
  80. Not good: "iar red ST eval board"
  81. Really good: "IAR STR912-SK evaluation board"
  82. ========================================
  83. (H) Are there other interesting (JTAG) chips on the board?
  84. ie: An FPGA or CPLD ...
  85. ========================================
  86. (I) What target config files need updating?
  87. In fact it's best if you submit a patch with those
  88. updates. Most of the other information listed here
  89. is just to help create a good patch.
  90. ========================================