This one applied fine.
Thanks!
--
Øyvind Harboe
PayBack incident management system
Reduce costs and increase quality, free Starter Edition
http://www.payback.no/index_en.html
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
h
2009/3/5 Øyvind Harboe :
> On Thu, Mar 5, 2009 at 8:15 AM, Audrius Urmanavičius
> wrote:
>> Re-created a patch against latest SVN version. Hope this will work.
>
> Nope.
>
> What tool are you using?
Sorry, that was my fault - I fiddled a bit the resulting diff with my
text editor (to remove some
On Thu, Mar 5, 2009 at 8:20 AM, Holger Schurig
wrote:
>> mailing list these days) as copy&pasting out of an email isn't
>> very robust.
>
> Than don't do this. Just save the whole mail. "patch will merely
> ignore all the e-mail headers and comments and notice by itself
> when the real patch start
On Thu, Mar 5, 2009 at 8:15 AM, Audrius Urmanavičius
wrote:
> Re-created a patch against latest SVN version. Hope this will work.
Nope.
What tool are you using?
--
Øyvind Harboe
PayBack incident management system
Reduce costs and increase quality, free Starter Edition
http://www.payback.no/i
> mailing list these days) as copy&pasting out of an email isn't
> very robust.
Than don't do this. Just save the whole mail. "patch will merely
ignore all the e-mail headers and comments and notice by itself
when the real patch starts.
___
Openocd-dev
Re-created a patch against latest SVN version. Hope this will work.
Kind Regards,
Audrius Urmanavicius
On Thu, Mar 5, 2009 at 9:07 AM, Øyvind Harboe wrote:
> Good find!
>
> The patch failed to apply. I don't know why.
>
> Can you try recreating it?
>
> - update to latest svn
> - use svn diff
Good find!
The patch failed to apply. I don't know why.
Can you try recreating it?
- update to latest svn
- use svn diff to create patch
- attach it
(It looks like you followed these steps, I don't understand why the patch failed
to apply).
--
Øyvind Harboe
PayBack incident management syste
committed.
Thanks!
Please attach the patches as a text file(the consensus in the mailing list
these days) as copy&pasting out of an email isn't very robust.
--
Øyvind Harboe
PayBack incident management system
Reduce costs and increase quality, free Starter Edition
http://www.payback.no/index_e
After months of hard work I am forced to abandon all work on the OpenOCD
support for the Micronas ARM7TDMI devices.
I had stopped it at one time but later restarted. Micronas was not very
helpfull but they have some nice devices.
They announced last week that following the layoffs and decision of
James a écrit :
> On Wed, 2009-03-04 at 09:41 +0100, Mag. Dr. Nikolaus Klepp wrote:
>
>> take this one: http://developers.stf12.net/eclipse-demo
>>
>
> Thanks.
>
> I've never looked at an Eclipse before, probably because people told me
> it would be bad for my eyes. They were right.
>
> I'
Hi all,
This is my first message to this list and my first patch to OpenOCD.
Excuse me if I do something wrong - I try to do my best.
Attached is a patch to fix flash fill* command when byte count to be
written exceeds 1024 - 1kb-sized gaps are made after each 1kb of data
due to incrementing loop
On Wed, 4 Mar 2009, Øyvind Harboe wrote:
> > Well, actually the documentation for "halt" says that an argument of 0
> > should skip waiting for the halted state. This patch brings the code in
> > agreement with the doc.
>
> Actually I find the documentation obtuse on this point.
>
> There is a
Committed.
It still needs fix for "halt 0" for doc + cleaner check on "0" ref
previous mail.
--
Øyvind Harboe
PayBack incident management system
Reduce costs and increase quality, free Starter Edition
http://www.payback.no/index_en.html
___
Openocd-dev
> Well, actually the documentation for "halt" says that an argument of 0
> should skip waiting for the halted state. This patch brings the code in
> agreement with the doc.
Actually I find the documentation obtuse on this point.
There is a difference between checking if the target was in the hal
On Wed, 4 Mar 2009, Nicolas Pitre wrote:
> Well, actually the documentation for "halt" says that an argument of 0
> should skip waiting for the halted state. This patch brings the code in
> agreement with the doc.
And on top of the patch above, here's a patch making reset+halt on the
SheevaPl
On Tue, 3 Mar 2009, Øyvind Harboe wrote:
> You could use "catch {halt 0}" or modify handle_wait_halt_command to
> be a silent no-op when ms=0
> if poll has side effects that you want to avoid.
Well, actually the documentation for "halt" says that an argument of 0
should skip waiting for the halt
Jonathan Dumaresq pisze:
> Thanx for the answer. SO from what I see, is no way to use openOCD with
> RIDE7 ?
>
> I have an Olimex ARM-USB-OCD device.
>
> This could be fun to have OpenOCD support in RIDE7.
Ride7 is a commercial toolchain, which supports only RLINK. Just as IAR
and Keil support
HI,
Thanx for the answer. SO from what I see, is no way to use openOCD with
RIDE7 ?
I have an Olimex ARM-USB-OCD device.
This could be fun to have OpenOCD support in RIDE7.
Jonathan
-Message d'origine-
De : openocd-development-boun...@lists.berlios.de
[mailto:openocd-development-boun.
On Wed, 2009-03-04 at 09:41 +0100, Mag. Dr. Nikolaus Klepp wrote:
> take this one: http://developers.stf12.net/eclipse-demo
Thanks.
I've never looked at an Eclipse before, probably because people told me
it would be bad for my eyes. They were right.
I'll stick to gedit, and a terminal ;-)
Che
take this one: http://developers.stf12.net/eclipse-demo
Am Mittwoch, 4. März 2009 schrieb James:
> On Wed, 2009-03-04 at 09:11 +0800, SimonQian wrote:
> > With some tweaks to OpenOCD, gdb in the latest Codesourcery G++ can
> > work.
> > For configuring Eclipse, you can also see
> > http://develope
On Wed, Mar 4, 2009 at 9:01 AM, Pieter Conradie
wrote:
> Hi everyone,
>
>
>
> I have noticed discrepancies in the names of the CFG files, which could
> confuse users of OpenOCD. Example: at91sam9260.cfg vs. sam7x256.cfg
>
>
>
> Maybe we need a naming convention.
Sounds good to me. If you are will
Hi everyone,
I have noticed discrepancies in the names of the CFG files, which could confuse
users of OpenOCD. Example: at91sam9260.cfg vs. sam7x256.cfg
Maybe we need a naming convention. There are a few things that could be
addressed:
1. Capitalization: Should we start to use capitalization t
22 matches
Mail list logo
