On Fri, Apr 30, 2010 at 12:30 AM, Peter Stuge wrote:
> Hi Øyvind,
>
> Øyvind Harboe wrote:
>> There is no SWD support in OpenOCD currently, but it has been
>> discussed on and off. I know David Brownell has some work in
>> progress, but he'll probably post something more on that when
>> it is time
Hi Øyvind,
Øyvind Harboe wrote:
> There is no SWD support in OpenOCD currently, but it has been
> discussed on and off. I know David Brownell has some work in
> progress, but he'll probably post something more on that when
> it is time.
Right. Might there be some way to help him with it?
I under
There is no SWD support in OpenOCD currently, but it has been discussed
on and off. I know David Brownell has some work in progress, but he'll
probably post something more on that when it is time.
--
Meet Zylin at ESC 2010 San Jose
April 26 - 30. 2010
http://www.zylin.com/events_esc2010.html
Freddie Chopin wrote:
>> it seems that NXP gave up JTAG for their ARM controllers and are
>> now using SWD for everything new.
>
> Actually there is no JTAG for LPC13xx and (I think) LPC11xx, but
> the bigger Cortex-M3 cores - LPC17xx - have "normal" JTAG.
Yea, that's quite right. It's the smaller
On 2010-04-29 20:38, Peter Stuge wrote:
LPC-2000 is getting old, ARM7 and all, so I'm looking at the newer
products. LPC-1343 seems to hit the sweet spot, and that LPCxpresso
board is nice and all, but it seems that NXP gave up JTAG for their
ARM controllers and are now using SWD for everything n
Hi all,
I've been using OpenOCD for a while with the NXP LPC-2148 controller
and it is working tremendously well. I'm very happy, and want to say
thanks for the great software!
LPC-2000 is getting old, ARM7 and all, so I'm looking at the newer
products. LPC-1343 seems to hit the sweet spot, and t
The flash write_image was known to be broken for the case of
sections not being in ascending order.
This has was fixed for gdb load a long time ago by sorting the
sections. Do the same for flash write_image.
--
Meet Zylin at ESC 2010 San Jose
April 26 - 30. 2010
http://www.zylin.com/events_es
It's not every subject that seems to generate such interest
I know gdb prints out something about loading speed for the "load" command.
Worth having a look at?
--
Meet Zylin at ESC 2010 San Jose
April 26 - 30. 2010
http://www.zylin.com/events_esc2010.html
Øyvind Harboe
US toll free 1-866-
Michael Schwingen wrote:
> Jon Povey wrote:
>> My 2 pence:
>>
>> "KB/s" is "correct" as far as I understand, but obviously there is
>> still ambiguity. Some poor souls might still confuse KiB/s to be
>> bits instead of bytes.
>>
> Nope. The SI prefix for kilo("1000") is a lower-case "k", so kB/s,
>
Jon Povey wrote:
> My 2 pence:
>
> "KB/s" is "correct" as far as I understand, but obviously there is still
> ambiguity. Some poor souls might still confuse KiB/s to be bits instead of
> bytes.
>
Nope. The SI prefix for kilo("1000") is a lower-case "k", so kB/s, would
be correkt - let's use co
Signal rise time troubles are related to the IO port current ! Amontec
JTAGkey Tiny uses VREF to power his JTAG IO port ( TCK, TMS, TDI, SRST_N
and TRST_N signals ).
How did you connect the VREF pin1 and the GND pin20 of the Amontec
JTAGkey Tiny ? follow these rules :
1. The VREF pin1 of the
Sergey Lapin wrote:
kilograms is Kg not kg
That's wrong - kilogram is kg. IIRC data rate units are special category.
Also openocd target audience will never have problems with
kilobyte/kibibyte mess,
so familiar KBps or KB/s should be used, IMHO.
Yes Yes Yes, you're right AND I was wrong
freddie_cho...@op.pl wrote:
> I'm for using the binary prefixes (
> http://en.wikipedia.org/wiki/Binary_prefix ) in the form of x/s so
> e.g. KiB/s
My 2 pence:
"KB/s" is "correct" as far as I understand, but obviously there is still
ambiguity. Some poor souls might still confuse KiB/s to be bits
Jon Povey wrote:
> Since then I have also tested the latest GIT version under (virtual)
> linux, and also the latest git version build with FTDI's drivers
> instead of libftdi. All combinations show the same random errors.
> Also tried at a range of different JTAG clock speeds, makes no
> differenc
>
> kilograms is Kg not kg
That's wrong - kilogram is kg. IIRC data rate units are special category.
Also openocd target audience will never have problems with
kilobyte/kibibyte mess,
so familiar KBps or KB/s should be used, IMHO.
___
Openocd-development
Użytkownik Laurent Gauch napisał:
>kilograms is Kg not kg
You're wrong - kilogram is definetely "kg" -
http://en.wikipedia.org/wiki/Kilogram http://en.wikipedia.org/wiki/SI_prefix ,
just the same as km or kV. Capital K actually stands for kelvin in SI, so using
it as "binary kilo" is somewhat
16 matches
Mail list logo
