Committed.
This patch is still problematic. There is a consensus to use native line endings
w/SVN and svn diff's handle this cleanly, your's will mess up the line
endings. Even
in 2009 line endings are causing grief. Geeez trying to fix line
endings is a bit
of a quixotic task...
I appreciate
> I tried to apply the patch, but it didn't apply cleanly.
The original patch applied, the attached one was broken. Don't
ask my why, it's not broken on my hard disk.
Personally, I like in-line patches more:
* easier to read in all mailing list clients
* easier to comment inline
* easier to inc
Yes, this should be changed. I mentioned this way back when. The
layout for the OS X d2xx library is similar to the linux layout but is
contained in a dmg rather than a tar.gz. The enable options for d2xx
should be consolidated into a single option that detects the layout
(windows vs lin
on the SparkFun OpenOCD board
http://forum.sparkfun.com/viewtopic.php?p=66305#66305
Should we change this somehow ?
Rob
Came across this thread and it helped me... but with the latest
release
of openocd (release "1.0"), if you try to configure with d2xx
drivers on OS-X, it will
On Feb 17, 2009, at 7:57 AM, Holger Schurig wrote:
On Tuesday 17 February 2009 14:34:02 Holger Schurig wrote:
jtag newtap $_CHIPNAME cpu \
-irlen 5 \
-ircapture 0x1 \
-irmask 0xf \
-expected-id $_CPUTAPID
I found the bsdl file: http://www.avr32.ru/AP7000.bsdl
In this file I find
On Feb 17, 2009, at 3:29 AM, Sergey Lapin wrote:
Hi, all!
Do anybody have proper pxa270 config to play with?
I try to use colibri board.
btw, target/pxa270.cfg soesn't work.
All the best,
S.
___
Openocd-development mailing list
Openocd-development@l
On Tue, Feb 17, 2009 at 3:17 PM, Holger Schurig
wrote:
>> Please use svn diff to create the patch and post it as an
>> attachment.
>
> I can do the attachment if you insist, but I won't use "svn
> diff".
I tried to apply the patch, but it didn't apply cleanly.
In this mailing list there is a con
On Tuesday 17 February 2009 14:34:02 Holger Schurig wrote:
> jtag newtap $_CHIPNAME cpu \
> -irlen 5 \
> -ircapture 0x1 \
> -irmask 0xf \
> -expected-id $_CPUTAPID
I found the bsdl file: http://www.avr32.ru/AP7000.bsdl
In this file I find "attribute INSTRUCTION_LENGTH of AP7000:
enti
> Info : JTAG tap: avr32ap7000.cpu tap/device found: 0x21e8203f
> (Manufacturer: 0x01f, Part: 0x1e82, Version: 0x2)
> Info : JTAG Tap/device matched
> Warn : Unexpected idcode after end of chain! 384 0x807f
> Warn : Unexpected idcode after end of chain! 416 0x00ff
> Warn : Unexpected idcode
> Please use svn diff to create the patch and post it as an
> attachment.
I can do the attachment if you insist, but I won't use "svn
diff". I have several, not related patches and use quilt to keep
them apart. That shouldn't be a problem for you, you can still
simply do an "patch -p1 < .pa
Please use svn diff to create the patch and post it as an attachment.
Thanks!
--
Øyvind Harboe
PayBack incident management system
Reduce costs and increase quality, free Starter Edition
http://www.payback.no/index_en.html
___
Openocd-development mai
This fixes some of the obvious warnings while compiling.
Even after this patch, some warnings stay. I think they
reveal programming errors:
xscale.c: In function 'xscale_step':
xscale.c:1464: warning: 'current_pc' is used uninitialized in this function
at91sam7.c: In function 'at91sam7_read_part
This script makes "svn st" be silent:
#!/bin/sh
{
echo Makefile
echo Makefile.in
echo openocd.aux
echo openocd.cp
echo openocd.fn
echo openocd.pg
echo openocd.pdf
echo openocd.log
echo openocd.tp
echo openocd.ky
echo openocd.cps
echo openocd.toc
echo openocd.vr
echo version.texi
echo texinfo.te
I've an ICnova / Grasshopper board that I'd like to get supported
via OpenOCD. As I'm willing to contribute this back, I'm using
OpenOCD from subversion, currently 1370.
My JTAG device is an Olimex USB-JTAG-TINY. I've started with a
bogus "target/avr32ap7000.cfg" file which basically contains
Hi Sergey,
On Tue, Feb 17, 2009 at 8:29 AM, Sergey Lapin wrote:
> Hi, all!
>
> Do anybody have proper pxa270 config to play with?
> I try to use colibri board.
> btw, target/pxa270.cfg soesn't work.
>
I'm not sure, but I think some people from OpenEZX project used
openocd to un-brick Motorola A1
Hi, all!
Do anybody have proper pxa270 config to play with?
I try to use colibri board.
btw, target/pxa270.cfg soesn't work.
All the best,
S.
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/list
16 matches
Mail list logo
