[Openocd-development] OpenOCD 0.1.0 released

2009-01-20 Thread Rick Altherr
I just uploaded the source distribution of OpenOCD 0.1.0 to the BerliOS project site (http://developer.berlios.de/projects/openocd/). Thanks to everyone for their contributions and testing. The final version of 0.1.0 differs only by a few minor fixes to the autotools scripts and the inclus

Re: [Openocd-development] udev rules for openocd

2009-01-20 Thread Rick Altherr
On Jan 20, 2009, at 11:51 AM, Uwe Hermann wrote: On Tue, Jan 20, 2009 at 08:39:14PM +0100, Uwe Hermann wrote: On Tue, Jan 20, 2009 at 09:07:42AM -0800, Rick Altherr wrote: I await an updated file that includes all the additional device lines that have flown by on this list. Sure, attached

Re: [Openocd-development] udev rules for openocd

2009-01-20 Thread Michel Catudal
Rick Altherr a écrit : > > In terms of including this as part of OpenOCD, we suffer from > supporting multiple platforms and distrubtions. The preferred install > location for the udev script is likely to vary by distribution and it > only applies to the Linux platform. Many other projects han

Re: [Openocd-development] udev rules for openocd

2009-01-20 Thread Uwe Hermann
On Tue, Jan 20, 2009 at 10:15:42AM -0600, lou.openocd...@fixit.nospammail.net wrote: > Of course. Why not 0, then? Does it make sense to give everybody read > access to the node? Ah, I see. I don't know which one should be used, I don't mind either way. As far as I've seen in /etc/udev/ on my s

Re: [Openocd-development] udev rules for openocd

2009-01-20 Thread Uwe Hermann
On Tue, Jan 20, 2009 at 08:39:14PM +0100, Uwe Hermann wrote: > On Tue, Jan 20, 2009 at 09:07:42AM -0800, Rick Altherr wrote: > > I await an updated file that includes all the additional device lines > > that have flown by on this list. > > Sure, attached. Oops, forgot one. Updated patch attache

Re: [Openocd-development] udev rules for openocd

2009-01-20 Thread Uwe Hermann
On Tue, Jan 20, 2009 at 09:07:42AM -0800, Rick Altherr wrote: > I await an updated file that includes all the additional device lines > that have flown by on this list. Sure, attached. Uwe. -- http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.u

Re: [Openocd-development] AT91SAM9260 and Olimex Changes

2009-01-20 Thread Rick Altherr
svn up usually does the trick. The only case that can confuse things is if you have local changes. You can do 'svn revert -R .' to get back to the base versions and then 'svn up'. Rick On Jan 20, 2009, at 8:17 AM, Dean Glazeski wrote: For some reason, it appears the svn update isn't work

Re: [Openocd-development] udev rules for openocd

2009-01-20 Thread Rick Altherr
On Jan 20, 2009, at 7:41 AM, Uwe Hermann wrote: On Mon, Jan 19, 2009 at 07:21:39PM -0800, Rick Altherr wrote: As a platform-neutral project, I'd rather not call out any distribution by name and leave it up to the packager to figure out how best to include the contrib files. Yep, contrib/

Re: [Openocd-development] AT91SAM9260 and Olimex Changes

2009-01-20 Thread Dean Glazeski
For some reason, it appears the svn update isn't working. A fresh check out of the repository and everything looks good. I'm probably doing something wrong during the update. Is there a standard way to update my working copy once you commit changes that I made? Thanks. // Dean Rick Altherr

Re: [Openocd-development] udev rules for openocd

2009-01-20 Thread lou . openocd012
On Tue, Jan 20, 2009 at 04:39:52PM +0100, Uwe Hermann wrote: > On Tue, Jan 20, 2009 at 07:53:14AM -0600, lou.openocd...@fixit.nospammail.net > wrote: > > And another part for rlink: > > > > # Raisonance RLink > > SYSFS{idVendor}=="138e", SYSFS{idProduct}=="9000", MODE="664", > > GROUP="plugdev"

Re: [Openocd-development] AT91SAM9260 and Olimex Changes

2009-01-20 Thread Rick Altherr
In my copy of the repo, at91sam9260.cfg is what at91sam9260minimal.cfg was. In fact, the checkin shows that at91sam9260.cfg was replaced. The fix in unknown-board-atmel-at91sam9260.cfg is still necessary. Committed in r1353. Rick On Jan 19, 2009, at 11:52 PM, Dean Glazeski wrote: It loo

Re: [Openocd-development] udev rules for openocd

2009-01-20 Thread Uwe Hermann
On Mon, Jan 19, 2009 at 07:21:39PM -0800, Rick Altherr wrote: > As a platform-neutral project, I'd rather not call out any distribution by > name and leave it up to the packager to figure out how best to include > the contrib files. Yep, contrib/ sounds good. Uwe. -- http://www.hermann-uwe.de

Re: [Openocd-development] udev rules for openocd

2009-01-20 Thread Uwe Hermann
On Tue, Jan 20, 2009 at 07:53:14AM -0600, lou.openocd...@fixit.nospammail.net wrote: > And another part for rlink: > > # Raisonance RLink > SYSFS{idVendor}=="138e", SYSFS{idProduct}=="9000", MODE="664", GROUP="plugdev" > > Does the 4 in 664 make sense? Yes, you don't want _all_ users to have wr

[Openocd-development] udev rules for openocd

2009-01-20 Thread Laurent Gauch
Please already add Amontec JTAGkey-HiSpeed VID:0x0FBB PID:0x1000 # Amontec JTAGkey-HiSpeed SYSFS{idVendor}=="0x0FBB", SYSFS{idProduct}=="0x1000", MODE="664", GROUP="plugdev" Thanks, Laurent ___ Openocd-development mailing list Openocd-development@li

Re: [Openocd-development] Amontec USB JTAGkey configuration files

2009-01-20 Thread Kees Jongenburger
On Tue, Jan 20, 2009 at 3:01 PM, Kees Jongenburger wrote: > About this new interface >## interface reference: http://www.amontec.com/jtagkey-hispeed.shtml >## openocd location: ./src/target/interface/amontec-jtagkey-hispeed.cfg The link is broken or non existent yet I hit the send button to fast

Re: [Openocd-development] Amontec USB JTAGkey configuration files

2009-01-20 Thread Kees Jongenburger
About this new interface > ## interface reference: http://www.amontec.com/jtagkey.shtml > ## openocd location : ./src/target/interface/amontec-jtagkey.cfg The link is broken or non existent yet ___ Openocd-development mailing list Openocd-development@li

Re: [Openocd-development] udev rules for openocd

2009-01-20 Thread lou . openocd012
And another part for rlink: # Raisonance RLink SYSFS{idVendor}=="138e", SYSFS{idProduct}=="9000", MODE="664", GROUP="plugdev" Does the 4 in 664 make sense? On Mon, Jan 19, 2009 at 07:03:02PM -0800, Zach Welch wrote: > On Tue, 2009-01-20 at 03:43 +0100, Uwe Hermann wrote: > > here's a short udev

[Openocd-development] Amontec USB JTAGkey configuration files

2009-01-20 Thread Laurent Gauch
Please add these files instead the previous ones. The 'A' is still a trouble for ft2232 based emulators. Amontec Team is working on ft2232.c and the jtagkey layout. Also, we will resolve the specific ' A' on Windows in the same time. After resolving the ' A', the specific 'Windows OS' lines will

Re: [Openocd-development] Yet another 0.1.0 package

2009-01-20 Thread Spencer Oliver
> Due to the fixes for 'make maintainer-clean' and handling release > versioning better, I've spun yet another 0.1.0 source distribution. > I've placed it at > http://www.kc8apf.net/files/openocd-0.1.0.tar.gz per usual. > 'make distcheck' passes on OS X 10.5. Same request applies: > try

[Openocd-development] How to get rid of "BUG: keep_alive() was not invoked in the 1000ms timelimit. GDB alive packet not sent!"

2009-01-20 Thread Andreas Kuehn
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi out there! During execution of flash commands, somehow this "watchdog" is not triggered. The result are many of these lines: "BUG: keep_alive() was not invoked in the 1000ms timelimit. GDB alive packet not sent!" How can I switch them off,

[Openocd-development] Amontec USB JTAGkey configuration files

2009-01-20 Thread Laurent Gauch
Please add these .cfg as new interface configuration files. Thanks. Regards, Laurent Gauch http://www.amontec.com JTAGkey / JTAGkey-Tiny / JTAGkey-HiSpeed maker ## ## Amontec JTAGkey ## http://www.amontec.com ## ## interface reference: http://www.amontec.com/jtagkey.shtml ## openocd location