On Tue, Jul 26, 2011 at 4:12 PM, Andreas Fritiofson
wrote:
>
>
> On Wed, Jul 27, 2011 at 12:22 AM, Steve Franks
> wrote:
>>
>> On Tue, Jul 26, 2011 at 3:06 PM, Andreas Fritiofson
>> wrote:
>> > 0.4.0 is rather old, you may be seeing a bug that has already been
>> > fixed.
>> > Grab the latest ve
On Wed, Jul 27, 2011 at 12:22 AM, Steve Franks wrote:
> On Tue, Jul 26, 2011 at 3:06 PM, Andreas Fritiofson
> wrote:
> > 0.4.0 is rather old, you may be seeing a bug that has already been fixed.
> > Grab the latest version from the repo and give it a try. I don't think
> > anyone will bother with
On Tue, Jul 26, 2011 at 3:06 PM, Andreas Fritiofson
wrote:
> On Tue, Jul 26, 2011 at 11:25 PM, Steve Franks
> wrote:
>>
>> Every year or so I try openocd, and still no joy. Actually, seems the
>> script and config stuff has all finally matured/stabilized, so I'll
>> assume I can make it work w/o
On Tue, Jul 26, 2011 at 11:25 PM, Steve Franks wrote:
> Every year or so I try openocd, and still no joy. Actually, seems the
> script and config stuff has all finally matured/stabilized, so I'll
> assume I can make it work w/o too much pain, after I fix this hang:
>
> I have a vanilla lpc2138 on
Every year or so I try openocd, and still no joy. Actually, seems the
script and config stuff has all finally matured/stabilized, so I'll
assume I can make it work w/o too much pain, after I fix this hang:
I have a vanilla lpc2138 on an ARM-USB-OCD, that seems to fire up ok
using the built-in conf
