Hi,

> > Because from my understanding an N-Link is a U-Link
> > So, there's no possibility to integrate into OpenOCD.
>
> I don't understand this. With wiggler it was no problem too, why
> schould it be for N/U-LINK?

Because it uses a proprietary comms mechanism and Keil only provide an RDI
interface IIRC. Hence, there is zero possibility of hooking it into
OpenOCD.

> > You pays your money...
>
> much more of our money :-(
>
> As I understood JTAG was made to make one standard interface but
> there isn't really one available. Even TCP/IP-based OCD isn't
> compatible with all the tools.
> But as I read you go ahead with the support of Olimex-Tool. I think
> this is the right way to do.

4-wire JTAG is standard except that when implemented by CPU vendors
non-standard features creep in (e.g. RTCK). There is no standard JTAG
connector because each and every JTAG header features extra pins for other
fluff. Hence there's a good reason to make a single-function device which
reduces production costs.

However, I have written a STAPL interpreter (i.e. it parses and runs STAPL
files) which runs with a CrossConnect or FTDI devices. You can use this to
program things other than ARMs.

-- Paul.

An Engineer's Guide to the LPC2100 Series

Hi Alex,

> > Can anyone tell me, why there is no USB-JTAG that is useable for
all?
> > As Hardware developper you have FPGA, CPLD, C-JTAGs from several
> > tools and not one is compatible with the others.
> > Why must everyone create there own dongle. It's awful!
>
> Guess why no one of the vendors really wants to be interoperable...

a few hundred years ago evey manufactor uses his own standards. few
years later nearly all gains from stadardisized tools and parts. Even
cars uses them over the borders of factories. And if you needs a
screw you mostly don't have to have panic.

Martin

Hi Dominic,

> The BDI2000 has, as has the Peedi.
> They're offering a GDB remote interface and a telnet interface.

Unterstzte Typen:
- BDM support for CPU16/32/32+, PowerPC 5xx/8xx, ColdFire
- JTAG support for ARM, M-CORE, PowerPC 4xx/6xx/7xx/74xx, PowerPC
82xx/83xx/85xx, XScale, MIPS32, MIPS64

Seems not to be a universal JTAG-Tool. Do you know whether it is
useable with all relevant tool(chain)s like keil, IAR, Crossworks...?

> The OpenOCD has IP connectivity, too,

OK, but USB woul be enoug for me. IP would have the advantage having
an isolated device.

> There are endeavours to
> create a uC+FPGA combination capable of running the OpenOCD,

Well this is the way to go ahead.

Martin
> details will
> follow once I know more.
>
> Regards,
>
> Dominic
>

--- In l..., "Paul Curtis" wrote:
Hi, Paul,

> > May I ask why? A driver to use it with crossworks may be useful,
too
> > ;-)
>
> Because from my understanding an N-Link is a U-Link
> So, there's no possibility to integrate into OpenOCD.

I don't understand this. With wiggler it was no problem too, why
schould it be for N/U-LINK?

> > Can anyone tell me, why there is no USB-JTAG that is useable for
all?

I mean at least just like wiggler.

> > As Hardware developper you have FPGA, CPLD, C-JTAGs from several
> > tools and not one is compatible with the others. Why must everyone
> > create there own dongle. It's awful!
>
> Each device has its own capabilities and limitations.

Limitation you mean. Because everyone implements only that
functionalities they needs we have to buy lot of devices with ...

> You pays your money...

much more of our money :-(

As I understood JTAG was made to make one standard interface but
there isn't really one available. Even TCP/IP-based OCD isn't
compatible with all the tools.
But as I read you go ahead with the support of Olimex-Tool. I think
this is the right way to do.

Martin

Marte

--- In l..., "Alexander Stohr"
wrote:
>
> > Can anyone tell me, why there is no USB-JTAG that is useable for all?
> > As Hardware developper you have FPGA, CPLD, C-JTAGs from several
> > tools and not one is compatible with the others.
> > Why must everyone create there own dongle. It's awful!
>
> Guess why no one of the vendors really wants to be inter operable...
> Think about something valuable...
> How about money?
>
> -Alex.
>
Hi guys,

I might be wrong but afaik there is one USB->JTAG that works with IAR,
Keil, Rowleys, GNU, and that would be Segger's J-Link. It also happens
to be the fastest download option I know of.
http://www.segger.com

As I said, to my best knowledge, no guarantees.

Bob

Hi,

> Hi Paul,
> > > OK, how about to deliver a driver to use n-Link with openOCD
> instead
> > > of supporting only keil? This would be really helpful.
>
> > That made me chuckle. :-)
>
> May I ask why? A driver to use it with crossworks may be useful, too
> ;-)

Because from my understanding an N-Link is a U-Link--the hardware is to all
intents and purposes identical and the firmware is downloaded into the
device's RAM (it uses a Cypress chipset IIRC). Hence there is no IP in
software from the N-Link provider, it hitches a lift on the back of Keil's
software. So, there's no possibility to integrate into OpenOCD.

> Can anyone tell me, why there is no USB-JTAG that is useable for all?
> As Hardware developper you have FPGA, CPLD, C-JTAGs from several
> tools and not one is compatible with the others. Why must everyone
> create there own dongle. It's awful!

Each device has its own capabilities and limitations. You pays your
money...

-- Paul.

On Wednesday 08 August 2007 15:00:27 Baldur Gislason wrote:
> What sort of JTAG has IP connectivity?
>
> Baldur

The BDI2000 has, as has the Peedi.
They're offering a GDB remote interface and a telnet interface.

The OpenOCD has IP connectivity, too, it just needs to run on a Linux powered
host, for example an ARM based SBC.
I've successfully used OpenOCD on a Cirrus EP9301 based board using a FT2232
based dongle connected to the EP9301's USB host. There are endeavours to
create a uC+FPGA combination capable of running the OpenOCD, details will
follow once I know more.

Regards,

Dominic

What sort of JTAG has IP connectivity?

Baldur

On Mon, Aug 06, 2007 at 11:00:06PM -0400, Tom Walsh wrote:
> Alexander Stohr wrote:
> >> Why ARM co,ltd. not develop free IDE Software for interface with ARM GCC
> >> same ( AVRStudio + AVR GCC (Atmel) , MPLAB (Microchip) ). I think the ARM
> >> Developers' will grow more than this time.
> >>
> >
> > Why dont you do such software by yourselves
> > or just use whats out for free already?
> >
> >
> Hmmm, IDE == Integrated Development Environment. Hey! I've got one of
> those!
>
> Console #1: telnet session into JTAG
> Console #2: Insight debug session
> Console #3: run vi + make to build source
> ..
>
> Oh, you meant put all those big windows (sic) into tiny little ones for
> one screen??
>
> Regards,
>
> TomW
>
> --
> Tom Walsh - WN3L - Embedded Systems Consultant
> http://openhardware.net http://cyberiansoftware.com http://openzipit.org
> "Windows? No thanks, I have work to do..."
> ----------------

> Can anyone tell me, why there is no USB-JTAG that is useable for all?
> As Hardware developper you have FPGA, CPLD, C-JTAGs from several
> tools and not one is compatible with the others.
> Why must everyone create there own dongle. It's awful!

Guess why no one of the vendors really wants to be interoperable...
Think about something valueable...
How about money?

-Alex.

Hi Paul,
> > OK, how about to deliver a driver to use n-Link with openOCD
instead
> > of supporting only keil? This would be really helpful.

> That made me chuckle. :-)

May I ask why? A driver to use it with crossworks may be useful, too
;-)
Can anyone tell me, why there is no USB-JTAG that is useable for all?
As Hardware developper you have FPGA, CPLD, C-JTAGs from several
tools and not one is compatible with the others. Why must everyone
create there own dongle. It's awful!

Martin