Re: [Openocd-development] Thoughts on JTAG code duplication

2008-12-24 Thread Dick Hollenbeck
Rick Altherr wrote: > Now that I've read through code for all the JTAG interface drivers > (including the 2 new ones), it seems that every single driver does > mass duplication of the JTAG state machine handling. The state > machine is defined as part of the JTAG standard (although it does > a

[Openocd-development] Thoughts on JTAG code duplication

2008-12-24 Thread Rick Altherr
Now that I've read through code for all the JTAG interface drivers (including the 2 new ones), it seems that every single driver does mass duplication of the JTAG state machine handling. The state machine is defined as part of the JTAG standard (although it does allow for extension) and al

[Openocd-development] RLink compiler warnings

2008-12-24 Thread Rick Altherr
Could one of you send a patch that fixes these compiler warnings? I made a few attempts at it but wasn't sure if changing the usb buffer to be a char * was appropriate, etc. gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src -I../../src/helper - I../../src/target -gstabs+ -I/opt/local/includ

Re: [Openocd-development] How to introduce new JTAG tool?

2008-12-24 Thread Rick Altherr
On Dec 24, 2008, at 10:36 AM, SimonQian wrote: Hi, > Look at one of the existing interfaces in src/jtag. Create a new .h/.c file and implement your interface. > Modify the Makefile.am in src/jtag and configure.in in src/ to add the option to enable your interface. > Then submit a patch wit

Re: [Openocd-development] Patch to svn code (STR configuration files)

2008-12-24 Thread Duane Ellis
Michel Catudal wrote: > According to the web site the patch was scrubbed off. It must not like > my extension .diff so I changed it to .patch and am trying again. I received your patch. - Most of the time attachments are *removed* from the archive page. > There seem to be a few different Olimex

[Openocd-development] Patch to svn code (STR configuration files)

2008-12-24 Thread Michel Catudal
According to the web site the patch was scrubbed off. It must not like my extension .diff so I changed it to .patch and am trying again. Here is a patch to fix a few bugs. They are minor bugs but got me stalled in my development for a couple days as I was looking at the wrong places for a solut

[Openocd-development] A small patch

2008-12-24 Thread Michel Catudal
I was not registered so I don't know if my patch went in the bit bucket or not so here it is again. Here is a patch to fix a few bugs. They are minor bugs but got me stalled in my development for a couple days as I was looking at the wrong places for a solution. There are basically a few typos

Re: [Openocd-development] How to introduce new JTAG tool?

2008-12-24 Thread SimonQian
Hi, > Look at one of the existing interfaces in src/jtag. Create a new .h/.c file > and implement your interface. > Modify the Makefile.am in src/jtag and configure.in in src/ to add the option > to enable your interface. > Then submit a patch with all the changes to this mailing list. There

Re: [Openocd-development] How to introduce new JTAG tool?

2008-12-24 Thread Rick Altherr
On Dec 24, 2008, at 9:11 AM, SimonQian wrote: Hi all, What should be done if I want to introduce a new JTAG tool? Look at one of the existing interfaces in src/jtag. Create a new .h/.c file and implement your interface. Modify the Makefile.am in src/jtag and configure.in in src/ to add

[Openocd-development] How to introduce new JTAG tool?

2008-12-24 Thread SimonQian
Hi all, What should be done if I want to introduce a new JTAG tool? My tool is vsllink(VerSaLoon LINK) at http://www.simonqian.com/en/Versaloon. This tool use 2 SPI interfaces to emulate a byte-wise JTAG interface. So in the OpenOCD driver of this tool, I insert clocks in the Pause-IR or Pause-DR