On Tue, Jul 14, 2009 at 4:17 AM, Gene Smith 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. See
On 7/13/09 3:39 PM, "Alan Carvalho de Assis" wrote:
>>
>> OK that helps. Here are some additional questions:
>>
>> What is the host-operating system you are using (Windows, Mac OS X, Linux,
>> etc)?
>>
>
> I am running Linux Ubuntu 9.04, gcc 4.3.3, etc :-)
>
>> Does this error show up 10
Ø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. Seems pretty small. :)
Actually, I don't have the str712 board
On Tue, Jul 14, 2009 at 6:39 AM, Alan Carvalho de
Assis 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
thread and maybe you want to try that fix as well.
https://lists.berlios.de/pipermail
On Mon, 13 Jul 2009, Zach Welch wrote:
> On Wed, 2009-07-08 at 01:02 -0400, Nicolas Pitre wrote:
> > Before, the ./configure --help used to list --enable-parport-ppdev
> > instead of the current --disable-parport-ppdev. The later suggests that
> > parport-ppdev is now set by default when using
On Wed, 2009-07-08 at 01:02 -0400, Nicolas Pitre wrote:
> Before, the ./configure --help used to list --enable-parport-ppdev
> instead of the current --disable-parport-ppdev. The later suggests that
> parport-ppdev is now set by default when using --enable-parport (which
> would be a good thing
Hello Gary,
On 7/13/09, Gary Carlson wrote:
>
>
>
> On 7/13/09 3:06 PM, "Alan Carvalho de Assis" wrote:
>
>> Hi Gary,
>>
>> On 7/10/09, Gary Carlson wrote:
>>>
>>> Try the V4 patch.
>>>
>>
>> Same behavior:
>>
>> # openocd -f interface/jlink.cfg -f board/imx27ads.cfg
>> Open On-Chip Debugger 0.
On 7/13/09 3:06 PM, "Alan Carvalho de Assis" wrote:
> Hi Gary,
>
> On 7/10/09, Gary Carlson wrote:
>>
>> Try the V4 patch.
>>
>
> Same behavior:
>
> # openocd -f interface/jlink.cfg -f board/imx27ads.cfg
> Open On-Chip Debugger 0.2.0-in-development (2009-07-13-18:53) svn:2513
> $URL: htt
Hi Gary,
On 7/10/09, Gary Carlson wrote:
>
> Try the V4 patch.
>
Same behavior:
# openocd -f interface/jlink.cfg -f board/imx27ads.cfg
Open On-Chip Debugger 0.2.0-in-development (2009-07-13-18:53) svn:2513
$URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $
For bug reports,
Hi all,
Last week, I had a conference call with Dan Ravicher, Legal Director of
the Software Freedom Law Center, and two of his colleagues. He helped
answer some questions that came up for me during the licensing debate.
Further, he has generously offered to take questions from the community
rega
Xiaofan Chen escreveu:
>
> 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.
Ok, now aI can write the flash with these commands via telnet:
halt
wait_halt
flash info 0
flash erase_sector 0 0 25
Some cleanup of the ARMv7-M support:
- Reference the relevant ARMv7-M ARM doc (DDI 0405C to non-Vendors), and
update the Cortex-M3 doc refs (DDI 0337C is no longer available).
- Those registers aren't actually general, and some are incorrect (per all
public docs anyway). Update comments
On Mon, 2009-07-13 at 07:37 +0100, Spencer Oliver wrote:
> >
> > Still Spen could commit Gary's V3 J-Link patch to fix the
> > problem for Windows users.
> > https://lists.berlios.de/pipermail/openocd-development/2009-Ju
> > ly/009438.html
> >
>
> commited as rev2513
Thanks. FWIW, I had to re
2009/7/13 David Brownell :
> On Monday 13 July 2009, Audrius Urmanavičius wrote:
>> Has anybody played with LPC17xx (CM3 core) using OpenOCD? We are going
>> to have a project based on LPC1758 soon, I wonder how much hassle will
>> be to debug it with OpenOCD - I grep'ed through latest SVN source a
On Monday 13 July 2009, Audrius Urmanavičius wrote:
> Has anybody played with LPC17xx (CM3 core) using OpenOCD? We are going
> to have a project based on LPC1758 soon, I wonder how much hassle will
> be to debug it with OpenOCD - I grep'ed through latest SVN source and
> found not a single LPC17* r
Hi,
I have just spotted that we use a block size of 560bytes for the dump_image
cmd.
This cmd as such has not been changed since the original svn import.
I will look into speeding this up unless anyone know's a reason why 560bytes
are used?
Cheers
Spen
___
Hello list,
Has anybody played with LPC17xx (CM3 core) using OpenOCD? We are going
to have a project based on LPC1758 soon, I wonder how much hassle will
be to debug it with OpenOCD - I grep'ed through latest SVN source and
found not a single LPC17* reference.
The eval board we are going to start
*Very* last chance if there is anything else that should in.
Otherwise I hope that 0.2 will be cut in the next 12 hours.
--
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.com
___
Openocd-development mailing list
Ope
On Mon, Jul 13, 2009 at 2:07 PM, Øyvind Harboe wrote:
I think Gary's J-Link patch should be in. If not,
J-Link is broken under Windows as per Spen.
https://lists.berlios.de/pipermail/openocd-development/2009-July/009438.html
>>>
>>> I don't know anything about j-link stuff so I could
19 matches
Mail list logo
