Creating parts data base

Development Boards MicroMod
1

After spending a large amount of time looking for the manufacturers information on their JTAG setup

I wondered why there was no reference table built in to OpenOCD.

The server can already read the part ID from the chain, and now actually displays this information when it starts up.

A data base of part numbers and configurations for known devices could be set up with user supplied data.

This could give the instruction length and the other parameters needed for the config file of the known devices.

I am sure there are others out there who would supply this data form their many development boards.

To start the ball rolling here are 2 parts I am using

0x22230093 Xilinx XC3S1400A (jtag_device 6 0x11 0x3f 0x49)

0x19261013 Intel Xscale IXP432 (jtag_device 7 0x1 0x7f 0x09)

What do others think?

Dave

2

This is great idea.

I suggested before that the config be split into different sections.

A) The JTAG interface

B) The Port Numbers (GDP and Telnet)

C) The Target Chip

The reason for this is that non of these is actually related in any way.

I think your idea could be used to auto configure the Target chip. This could be done by using the hex value returned to open a configuration file say call JTAG_017F09.cfg for the Xscale IXP432 chip.

The application could search for known USB JTAG Interface’s at start-up. If there is only one then a configuration file maybe is not needed.

Most people use the default port numbers so a configuration file would not be required there either.

This seems to mean that for detectable chips and interfaces a configuration file is not required.

I must get round to doing some hacking on OpenOCD some time. I had a look at the source before. I prefer to program in C++ for the PC, so I found the code a little frustrating.