On Tue, Jul 14, 2009 at 4:17 AM, Gene Smithg...@chartertn.net wrote:
Øyvind Harboe wrote, On 07/12/2009 10:12 AM:
This does look like a bug in Jim Tcl.
Can you provide a smaller test case?
Not sure what you mean by smaller test case? You just remove the
referenced closing } in str710.cfg.
On Tue, Jul 14, 2009 at 5:39 AM, Alain Mouetteala...@pobox.com wrote:
Did you try run as sudo?
After a good and restfull weekend, I found that the file had lost it's
suid bit during the tests, amongst a few other things.
It is much better to use udev rules than using setuid bit.
The contrib
Zach Welch wrote:
Since I changed that text, I clearly meant for it to be enabled by
default on x86; it always gets set on other hosts. When I factored that
configure code, I also changed the help text. I thought that I got the
logic right, but I just verified it to see if it was correct.
I seem unable to halt my LPC-2148 device, anyone knows what's
wrong/what I am doing wrong? Thanks a bunch in advance.
openocd using olimex arm-usb-ocd, openocd log:
Open On-Chip Debugger 1.0 (2008-10-04-10:00) svn:exported
$URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $
Also, you should try the builtin OpenOCD script rather than
the monolithic scripts you find on the web. Especially when
these scripts can contain obsolete commands and be out
of sync with the OpenOCD version you are using.
openocd -f interface/parport.cfg -f target/lpc2148.cfg
--
Øyvind
On Tuesday 14 July 2009, Xiaofan Chen wrote:
It is much better to use udev rules than using setuid bit.
Hmmm, right. I put together a quickie patch to the README so
that this gets mentioned as an install issue for Linux.
- Dave
___
Under Installing OpenOCD mention that Linux users likely need to
set up some /etc/udev file, maybe using contrib/udev.rules if that
works on their distro.
Say point-blank that the D2XX code is faster on Windows; but that
it's no faster on Linux.
---
README | 11 ++-
1 file changed, 10
On Tue, Jul 14, 2009 at 5:02 PM, David Brownelldavi...@pacbell.net wrote:
Under Installing OpenOCD mention that Linux users likely need to
set up some /etc/udev file, maybe using contrib/udev.rules if that
works on their distro.
Say point-blank that the D2XX code is faster on Windows; but
Modified:
trunk/configure.in
Log:
Make the parport-ppdev option enabled by default. This may
require giving --disable-parport-ppdev to configure on some
platform(s).
Any reason why as it breaks win32 build - why not leave as disabled by
default?
Cheers
Spen
On Tue, 2009-07-14 at 10:11 +0100, Spencer Oliver wrote:
Modified:
trunk/configure.in
Log:
Make the parport-ppdev option enabled by default. This may
require giving --disable-parport-ppdev to configure on some
platform(s).
Any reason why as it breaks win32 build - why
On Tue, 2009-07-14 at 10:11 +0100, Spencer Oliver wrote:
Modified:
trunk/configure.in
Log:
Make the parport-ppdev option enabled by default. This
may require
giving --disable-parport-ppdev to configure on some platform(s).
Any reason why as it breaks win32 build
Or do you mean to say that --disable-parport-ppdev does not work??
I had to specify --disable-parport-ppdev before my parport interface
would work under Ubuntu 9.04.
--
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.com
On Tue, 2009-07-14 at 10:24 +0100, Spencer Oliver wrote:
On Tue, 2009-07-14 at 10:11 +0100, Spencer Oliver wrote:
Modified:
trunk/configure.in
Log:
Make the parport-ppdev option enabled by default. This
may require
giving --disable-parport-ppdev to configure on some
Hi all,
The OpenOCD 0.2.0 source release should now be available from the
BerliOS download page:
https://developer.berlios.de/project/showfiles.php?group_id=4148release_id=16455
The trunk is now open for new development patches, and a branch is
available to take critical bug fixes in the
Output errno, very slightly useful when debugging problems with connecting
to parport.
Comments?
--
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.com
### Eclipse Workspace Patch 1.0
#P openocd
Index: src/jtag/parport.c
In this respect, I think all of the drivers should be enabled
by default. Developers could disable them by choice, but
their underlying libraries are being detected such that we
can add new checks to disable the drivers when their
dependencies are missing.
The goal is to allow our
Hi Xiaofan,
On 7/13/09, Xiaofan Chen xiaof...@gmail.com wrote:
On Tue, Jul 14, 2009 at 6:39 AM, Alan Carvalho de
Assisacas...@gmail.com wrote:
Then I think this issue just happen when using OpenOCD + JLink +
i.MX27ADS board.
I am not so sure if your problem have something to do with this
Hi Gary,
On 7/13/09, Gary Carlson gcarl...@carlson-minot.com wrote:
I think your board is being held in reset by something other then the J-link
dongle. If the board is in reset and the jlink device can't free it, your
will get the problem you described. You can prove that by taking your
Hi,
I think that I did not make myself clear. *my system is now WORKING*
BUT, I have to manualy insert the script to write the flash in the
TELNET terminal.
Back to my original question: How to I insert and execute that script
automaticaly, just like I did with the old scripts???
I read the
On Tuesday 14 July 2009, Freddie Chopin wrote:
Recently there was a build guide in the pdf manual. It had all the
--enable-xxx options and stuff like that. Now this section is not
present in the user guide and the doxygen manual without a search
functions is pretty much worthless IMHO...
On 7/14/09 7:55 AM, Alan Carvalho de Assis acas...@gmail.com wrote:
Hi Gary,
On 7/13/09, Gary Carlson gcarl...@carlson-minot.com wrote:
I think your board is being held in reset by something other then the J-link
dongle. If the board is in reset and the jlink device can't free it,
David Brownell escreveu:
On Tuesday 14 July 2009, Alain Mouette wrote:
Back to my original question: How to I insert and execute that script
automaticaly, just like I did with the old scripts???
openocd -f your_script_name.cfg
... where your_script_name.cfg sources files for the
Committed.
These are the Eclipse settings w/Cp1252 charset.
Perhaps the charset should be defined/documented otherwise, but it's nice to
have the these settings saved for those(me :-) that use Eclipse to check
out and work on OpenOCD
--
Øyvind Harboe
Embedded software and hardware
Committed.
These are the Eclipse settings w/Cp1252 charset.
Perhaps the charset should be defined/documented otherwise,
but it's nice to have the these settings saved for those(me
:-) that use Eclipse to check out and work on OpenOCD
This also changes my personal setting's when
On Tue, Jul 14, 2009 at 9:14 PM, Spencer Olivers...@spen-soft.co.uk wrote:
Committed.
These are the Eclipse settings w/Cp1252 charset.
Perhaps the charset should be defined/documented otherwise,
but it's nice to have the these settings saved for those(me
:-) that use Eclipse to check out
This also changes my personal setting's when using ecplise - can we
revert this patch?
Yes and no.
We should choose *one* charset that is the standard charset,
no matter which charset that is.
I don't care what charset it is, much.
Choosing a charset is not the issue - i use
On Tue, 2009-07-14 at 17:49 +0200, Freddie Chopin wrote:
0.2.0 release cannot be build on Windows (MinGW + MSYS) with parport support
./configure --enable-parport --enable-parport_giveio
make
Add --disable-parport-ppdev
___
Openocd-development
On Tue, Jul 14, 2009 at 9:22 PM, Spencer Olivers...@spen-soft.co.uk wrote:
This also changes my personal setting's when using ecplise - can we
revert this patch?
Yes and no.
We should choose *one* charset that is the standard charset,
no matter which charset that is.
I don't care what
On Tue, Jul 14, 2009 at 11:46:59AM +0200, Øyvind Harboe wrote:
Or do you mean to say that --disable-parport-ppdev does not work??
I had to specify --disable-parport-ppdev before my parport interface
would work under Ubuntu 9.04.
Hm, that would be strange. Did you do 'modprobe ppdev'?
On Wed, Jul 15, 2009 at 4:10 AM, Zach Welchz...@superlucidity.net wrote:
On Tue, 2009-07-14 at 17:49 +0200, Freddie Chopin wrote:
0.2.0 release cannot be build on Windows (MinGW + MSYS) with parport support
./configure --enable-parport --enable-parport_giveio
make
Add
On Tuesday 14 July 2009, Alain Mouette wrote:
David Brownell escreveu:
On Tuesday 14 July 2009, Alain Mouette wrote:
Back to my original question: How to I insert and execute that script
automaticaly, just like I did with the old scripts???
openocd -f your_script_name.cfg
...
On Tue, 2009-07-14 at 12:21 +0100, Spencer Oliver wrote:
In this respect, I think all of the drivers should be enabled
by default. Developers could disable them by choice, but
their underlying libraries are being detected such that we
can add new checks to disable the drivers when
On Wed, 2009-07-15 at 07:47 +0800, Xiaofan Chen wrote:
On Wed, Jul 15, 2009 at 4:10 AM, Zach Welchz...@superlucidity.net wrote:
On Tue, 2009-07-14 at 17:49 +0200, Freddie Chopin wrote:
0.2.0 release cannot be build on Windows (MinGW + MSYS) with parport
support
./configure
David Brownell escreveu:
... where your_script_name.cfg sources files for the interface
and board decls, says init, issues the commands you like,
then says shutdown.
See above about adding init first. That's important.
See the User's Guide about the configuration stage.
Before that
On Wed, Jul 15, 2009 at 8:37 AM, Zach Welchz...@superlucidity.net wrote:
By the way, I believe parport_giveio is not working for Vista 64bit.
This is similar to the issues of libusb-win32 (driver signing).
Maybe this can be added to the README file.
Yes, but I think the TODO is a better place
hello ,every one
Nice to meet you here.
I am studying the open-ocd and the JTAG also.
I know that this project use the FT2232 chip.
But I can not get the clear architecture about the open-ocd ,FT2232
and the target .
Can somebody tell me or give some document link.
Thank you very much.
best
36 matches
Mail list logo
