Re: [Openocd-development] A little Git repo cleanup

2009-10-18 Thread Øyvind Harboe
On Mon, Oct 19, 2009 at 3:53 AM, Nicolas Pitre wrote: > On Sun, 18 Oct 2009, David Brownell wrote: > >> On Sunday 18 October 2009, Øyvind Harboe wrote: >> > I'm not quite up to speed on this graft stuff(first I heard of >> > it), but I trust you on how to execute this in the best manner. >> >> I d

Re: [Openocd-development] proc jtag_init {}

2009-10-18 Thread michal smulski
I attached telo.cfg that I used for testing with the dummy driver. 'hangs.log' is with the reset_init and nohang.log is with that procedure removed. It looks like the openocd does not hang but rather skips the initial scan when reset_init exits. The result is similar to the user as I can't access

Re: [Openocd-development] A little Git repo cleanup

2009-10-18 Thread Øyvind Harboe
> Yeah, plan on re-cloning ... that's why I wanted to see > some some discussion on this.  It's generally a consequence > of rebasing.  If I'd known about that issue, we could have > done that before the original switchover. I already planned on recloning. For this major improvement, I don't think

Re: [Openocd-development] A little Git repo cleanup

2009-10-18 Thread Nicolas Pitre
On Sun, 18 Oct 2009, David Brownell wrote: > On Sunday 18 October 2009, Øyvind Harboe wrote: > > I'm not quite up to speed on this graft stuff(first I heard of > > it), but I trust you on how to execute this in the best manner. > > I didn't know about "graft" (in the non-political sense!) > befor

Re: [Openocd-development] [PATCH] wsock32 & MinGW-W64

2009-10-18 Thread Redirect "Slash" NIL
> > Can't that "-D..." be automated? It will always be needed, > if I understand correctly. So requiring that it be specified > manually will just cause build errors when it's omitted. > Good thinking. Here's a patch that does just that. I tested it in both MinGW-W64 on Vista 64 and MinGW-W32 on

Re: [Openocd-development] A little Git repo cleanup

2009-10-18 Thread David Brownell
On Sunday 18 October 2009, Øyvind Harboe wrote: > I'm not quite up to speed on this graft stuff(first I heard of > it), but I trust you on how to execute this in the best manner. I didn't know about "graft" (in the non-political sense!) before I started exploring how to fix this either. ;) It's

Re: [Openocd-development] A little Git repo cleanup

2009-10-18 Thread Øyvind Harboe
On Sat, Oct 17, 2009 at 10:02 PM, David Brownell wrote: > On Friday 16 October 2009, Øyvind Harboe wrote: >> > I have a tree that removes those commits plus a few other bits >> > of noise that crept in.  Thing is, pushing it would NOT be enough >> > to achieve the full cleanup.  The existing clone

Re: [Openocd-development] Olimex SAM9-L9260 Update

2009-10-18 Thread Øyvind Harboe
Committed. Thanks! -- Øyvind Harboe http://www.zylin.com/zy1000.html ARM7 ARM9 ARM11 XScale Cortex JTAG debugger and flash programmer ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/o

Re: [Openocd-development] bin2char still slightly broken

2009-10-18 Thread Øyvind Harboe
On Sun, Oct 18, 2009 at 9:12 PM, David Brownell wrote: > On Sunday 18 October 2009, Øyvind Harboe wrote: >> To reproduce the problem: >> >> 1. use build != src dir >> >> 2. Create a dummy bin2char file(linux) under src/helper > > And if you don't start with a broken source tree ... ? Then it work

[Openocd-development] [PATCH] corrective fix for MinGW GNU C99 printf compliance

2009-10-18 Thread Redirect "Slash" NIL
Compilation on cygwin, using gcc v3 with option -mno-cygwin are currently producing a large number of the following warnings: warning: `gnu_printf' is an unrecognized format function type These have been introduced with the recent MinGW GNU C99 printf compliance patch, as gnu_printf was only i

Re: [Openocd-development] Sudden problem with Windows build and FT2232 driver

2009-10-18 Thread Dean Glazeski
This didn't work either. It must be a problem with my cygwin installation. A reinstallation of cygwin didn't help. As another note, the bootstrap script is also not working properly. It stems from the aclocal command about a problem loading perl DLLs. The problem might be that I'm on Windows 7,

Re: [Openocd-development] bin2char still slightly broken

2009-10-18 Thread David Brownell
On Sunday 18 October 2009, Øyvind Harboe wrote: > To reproduce the problem: > > 1. use build != src dir > > 2. Create a dummy bin2char file(linux) under src/helper And if you don't start with a broken source tree ... ? > touch openocd/src/helper/bin2char > > 3. configure & build as usual > >

Re: [Openocd-development] bin2char is now broken somehow when build!=src dir...

2009-10-18 Thread David Brownell
On Sunday 18 October 2009, Øyvind Harboe wrote: > Are you testing with build dir==src dir? > > In my case it works only when builddir==srcdir. I've done builds both ways. ___ Openocd-development mailing list Openocd-development@lists.berlios.de https:

Re: [Openocd-development] Sudden problem with Windows build and FT2232 driver

2009-10-18 Thread Redirect "Slash" NIL
I compiled the latest development tree on a fresh install of cygwin 1.7 + the FTDI driver on XP 32 bit, and I haven't seen I haven't seen the issue about the ftd2xx.h file: I used the following for configure: $ ./configure --enable-maintainer-mode --disable-werror --disable-shared --enable-ft2232_f

Re: [Openocd-development] bin2char still slightly broken

2009-10-18 Thread Øyvind Harboe
To reproduce the problem: 1. use build != src dir 2. Create a dummy bin2char file(linux) under src/helper touch openocd/src/helper/bin2char 3. configure & build as usual 4. failure => ./bin2char startup_tcl < ../../../zy1000/openocd/src/helper/startup.tcl > startup_tcl.c /bin/sh: ./bin2char:

Re: [Openocd-development] Sudden problem with Windows build and FT2232 driver

2009-10-18 Thread Dean Glazeski
As an addition to this, I can see the compile command output from libtool. Copying and pasting this command into the terminal works. I'm not entirely sure why this is failing in my case. It did work just earlier yesterday. // Dean Glazeski On Sun, Oct 18, 2009 at 1:08 PM, Dean Glazeski wrote:

Re: [Openocd-development] Sudden problem with Windows build and FT2232 driver

2009-10-18 Thread Dean Glazeski
Hi, I pulled down a fresh version of the repository and did a rebuild. I'm seeing the same problem. I'm building from inside of cygwin to run without cygwin, so it may be using mingw. I'm on a 32-bit system. I'm using the following configure command: $ ./configure --enable-maintainer-mode --d

Re: [Openocd-development] Sudden problem with Windows build and FT2232 driver

2009-10-18 Thread Redirect "Slash" NIL
Hi Dean, Considering that some of my patches for Windows were in the latest update, I'm willing to take a look. Are you building for MinGW or cygwin? And is your system 32 bit or 64 bit? Your configure parameters could probably help too... ___ Openocd-de

[Openocd-development] bin2char still slightly broken

2009-10-18 Thread Øyvind Harboe
there was a residual bin2char in the src/helper directory and that caused the problems below. Deleting src/helper/bin2char made things compile... I'll need to do a bit more testing, but we might not have heard the very last of this yet... It still doesn't compile here, some problems I see: - the

Re: [Openocd-development] bin2char is now broken somehow when build!=src dir...

2009-10-18 Thread Øyvind Harboe
On Sat, Oct 17, 2009 at 9:01 PM, David Brownell wrote: > On Saturday 17 October 2009, Øyvind Harboe wrote: > >> ./bin2char startup_tcl < >> ../../../zy1000/openocd/src/helper/startup.tcl > startup_tcl.c >> /bin/sh: ./bin2char: No such file or director > > Looking at the Makefile I can't see why th

Re: [Openocd-development] proc jtag_init {}

2009-10-18 Thread Øyvind Harboe
On Sat, Oct 17, 2009 at 8:37 PM, michal smulski wrote: > How do I add 'dummy' interface to openocd? configure --enable-dummy -- Øyvind Harboe http://www.zylin.com/zy1000.html ARM7 ARM9 ARM11 XScale Cortex JTAG debugger and flash programmer ___ Ope

[Openocd-development] Sudden problem with Windows build and FT2232 driver

2009-10-18 Thread Dean Glazeski
Hi list, After an update at some time yesterday, I can no longer build the ft2232 driver due to a missing include for ftd2xx.h. I am trying to build against FTD2XX libraries and the build process worked earlier yesterday. I don't understand the auto-magic that happens so I'm not able to trace wh