Hey Guys,
So to respond, r826 is the first point of failure I found (825 works
and flashes) 826 fails and does not flash.
Current SVN Head gives warning message and does not flash.
Currently rolling through 826-svn head and double checking.
version 1014 gives a different error message:
Hi Rick,
Thank you very much.
I will designate a work area in my configuration file.
And I found my JTAG interface has hardware issue, maybe this is reason
for failure. After I fix it, I will report the result.
Thanks.
On Thu, Nov 6, 2008 at 2:37 PM, Rick Altherr [EMAIL PROTECTED] wrote:
Be
Hi Oyvind,
I agree wholeheartedly. I'm looking into it... I'm going to probably
have to take blame for configuration file differences... I realized
that in my systematic testing at version 826 I started having to futz
with my configurations a bit to get things running (hmmh, so not
really so
Hi,
why does src/target/interface/parport.cfg use the
parport_port 0xc8b8
config? Shouldn't that be either 0 or 0x3f8 rather?
I've never seen that one used anywhere, and it definately doesn't
work on my (standard PC) parallel port (0 does work).
Thanks, Uwe.
--
http://www.hermann-uwe.de |
Hi,
I've updated the OpenOCD Debian package to r1130 yesterday, and the
Debian autobuild daemons found a compile problem with ep93xx on the
'armel' architecture, see
http://buildd.debian.org/fetch.cgi?pkg=openocd;ver=0.0%2Br1130-1;arch=armel;stamp=1225973025
The problem is how nanosleep() is
Fix a bunch of typos.
Uwe.
--
http://www.hermann-uwe.de | http://www.holsham-traders.de
http://www.crazy-hacks.org | http://www.unmaintained-free-software.org
Index: src/tcl/README_ABOUT_TCL.txt
===
---
