Re: [Openocd-development] New branch for flash access through generic boundary scans

2010-11-03 Thread Rick van Rein
Hi, > Over the past weeks, I've been working on and off to get BSDL-based flash > access > incorporated in OpenOCD. In its current state it isn't worth publishing, but > some of you might be interested in trying it anyway. So I setup a branch, as > 0yvind suggested to me. It is located at: >

[Openocd-development] New branch for flash access through generic boundary scans

2010-11-03 Thread Rick van Rein
Hello, Over the past weeks, I've been working on and off to get BSDL-based flash access incorporated in OpenOCD. In its current state it isn't worth publishing, but some of you might be interested in trying it anyway. So I setup a branch, as 0yvind suggested to me. It is located at: gi

Re: [Openocd-development] OpenOCD master now uses Jim Tcl 0.63

2010-11-03 Thread Peter Stuge
Laurent Gauch wrote: >> >/ we have to make sure the compile step stays as easy as possible on >> />/ Windows as on Linux and Mac ! >> / >> I don't agree. Windows is pretty much a useless development >> environment as-is, > > That's your point of view ... but, for me, this is a user point of > vie

Re: [Openocd-development] U Boot ethernet problem

2010-11-03 Thread Marek Vasut
On Wednesday 03 November 2010 14:59:55 Moshe Artzi wrote: > Hi Marek, > > > > I finally running u boot on my PXA320 but, > > I don't know why but, > > > > When I'm sending ping from the u boot to the host it pings ok. > > But when I'm trying to ping from the host to the u boot it lost. > >

Re: [Openocd-development] OpenOCD master now uses Jim Tcl 0.63

2010-11-03 Thread Laurent Gauch
Laurent Gauch wrote: >/ Having external Jim TCL is not so bad, / I think it's an important improvement. >/ we have to make sure the compile step stays as easy as possible on />/ Windows as on Linux and Mac ! / I don't agree. Windows is pretty much a useless development environment as-is, That'

Re: [Openocd-development] OpenOCD master now uses Jim Tcl 0.63

2010-11-03 Thread Peter Stuge
Laurent Gauch wrote: > Having external Jim TCL is not so bad, I think it's an important improvement. > we have to make sure the compile step stays as easy as possible on > Windows as on Linux and Mac ! I don't agree. Windows is pretty much a useless development environment as-is, and it's not r

Re: [Openocd-development] OpenOCD master now uses Jim Tcl 0.63

2010-11-03 Thread Peter Stuge
Spencer Oliver wrote: > The issue is caused because jim will install into /usr/local/lib. > cygwin and mingw will only look in /usr/lib - quick solution is to > manually move the various files. Quick but note that it is also a dirty solution, since you are not only circumventing the packaging syst

Re: [Openocd-development] OpenOCD master now uses Jim Tcl 0.63

2010-11-03 Thread Laurent Gauch
Øyvind Harboe wrote: Yes, but having jim as standalone make a new dependency for openocd project :-( ! With new version control of jim TCL ... The current thinking is to have the choice of whether to use installed Jim Tcl or have OpenOCD just build the Jim Tcl that ships with(submodule) Op

Re: [Openocd-development] OpenOCD master now uses Jim Tcl 0.63

2010-11-03 Thread Øyvind Harboe
> Yes, but having jim as standalone make a new dependency for openocd project > :-( ! With new version control of jim TCL ... The current thinking is to have the choice of whether to use installed Jim Tcl or have OpenOCD just build the Jim Tcl that ships with(submodule) OpenOCD. Release builds ar

Re: [Openocd-development] OpenOCD master now uses Jim Tcl 0.63

2010-11-03 Thread Laurent Gauch
>/ I think we do not need to have any 'make install' for JIM TCL, />/ since we want JIM TCL embedded in the openocd project. / As you may already know, if a project uses autotools then the build is not completed without make install. I would suggest to set --prefix for jim to a subdir of the ope

Re: [Openocd-development] OpenOCD master now uses Jim Tcl 0.63

2010-11-03 Thread Spencer Oliver
On 02/11/2010 12:55, Laurent Gauch wrote: >/ won't it be better compile both jimtcl and openocd with single />/ ./configure and make, without needing to install that stuff />/ separatelly ? / It doesn't need to be installed, that's part of the point. Although I'm thinking about if it might make

Re: [Openocd-development] OpenOCD master now uses Jim Tcl 0.63

2010-11-03 Thread Anders Montonen
On Nov 3, 2010, at 11:13, Peter Stuge wrote: > It could assume that jim was built and installed into some default > prefix, but really, since jim is standalone, it would make sense to > me to have it installed separately in the system even if it is linked > statically into openocd. Look at how GC

Re: [Openocd-development] OpenOCD master now uses Jim Tcl 0.63

2010-11-03 Thread Peter Stuge
Laurent Gauch wrote: > I think we do not need to have any 'make install' for JIM TCL, > since we want JIM TCL embedded in the openocd project. As you may already know, if a project uses autotools then the build is not completed without make install. I would suggest to set --prefix for jim to a su

Re: [Openocd-development] OpenOCD master now uses Jim Tcl 0.63

2010-11-03 Thread Laurent Gauch
Hi Steve, Yes, you're right. I think we do not need to have any 'make install' for JIM TCL, since we want JIM TCL embedded in the openocd project. The jim include paths and jim lib paths directly should be added in the 'configure' of openocd. Regards, Laurent http://www.amontec.com USB J

Re: [Openocd-development] STM32 core debug reset problem

2010-11-03 Thread Chris Jones
On 31/10/2010 13:40, Michel Catudal wrote: Le 2010-10-30 04:20, Chris Jones a écrit : I'd like to work out whether the debug unit really does break, or whether there's just a misunderstanding about state between it and OpenOCD. Wouldn't pulling the boot pin and send the reset core work? I w