--- In lpc2000@lpc2..., "Stephen Pelc" <stephen@m...> wrote: > MPE's JTAG Widget has a completely open and documented API. It > will work for any O/S (including Linux) that supports the FTDI > chips. See: > http://www.mpeforth.com/jtagwidget.htm This looks like overkill if we just want a USB JTAG device? Is there any open source JTAG-specific drivers, for gdb or any other debugger? I am impressed by any open JTAG API, and especially those for USB devices, and your support for Forth on Arm is also attractive. I used to be into Forth years ago but I would be dating myself if I told you any more than that :-) Eric

An Engineer's Guide to the LPC2100 Series

> >I don't think people purchase CrossWorks because they chose a >CrossConnect. I might be wrong. You'd know more than me about this, but in my recent research of these devices your CrossConnect keeps coming up. And you're the only USB and commercial suite vendor that can support linux. Even if your number of linux users isn't that great, I think linux support makes people think well of your company. You've got an understanding of cross platform tools, and people like to know that they aren't required to use Microsoft Windows forever. I personally like Microsoft because they've been very good to me. The company has changed a lot, but they still have a negative impression in many people's minds... Eric

Eric, > > We are currently in two (or maybe three) minds as to > whether to open > > up the CrossConnect API. There's good reasons to keep it > closed and > > good reasons to open it up. > > I'm sure you understand the pros and cons of opening the interface. > > In favor of opening the API: > > 1. If the interface is open you may sell more CrossConnect parts. Yes, this is true. One other question is how much we provide in the API. > 2. You would foster "good will" by having an open interface. I find that doesn't cut much ice when paying for groceries at the local Tesco store. > Reasons not to open the API: > > 1. You might lose a competitive advantage because there would > be less need for people to buy CrossWorks. I don't think people purchase CrossWorks because they chose a CrossConnect. I might be wrong. > 2. Further, your competitors might even take advantage of > your own device. They wouldn't make a clone, but rather, if > they support your devices you'd make a small amount on the > devices themselves, but they would get the higher profit > margin on selling their software tools to people who buy your parts. Certainly true, but I wonder how many competitors would go to all this trouble? > Obviously #1 on the "in favor" list is mitigated by the fact > that you are not really in business to sell CrossConnect > parts. Rather, it's likely being done specifically as a > "value added" addition to help CrossWorks users. In fact, I > am guessing that you're probably making very little profit > selling CrossConnect. Correct, we are not making much profit on the CrossConnect--but then there's a big investment in developing CrossWorks too. The fact we have our own software from top to bottom and in the JTAG interface means that we can't lay the blame with anybody else when things go wrong. (That's not 100% true as we use the FTDI USB to FIFO device, but that will probably be engineered out in the next revision.) > I'm definitely in favor of open source tools (I write some of > my own for the hc11/hc12), but I understand that businesses > have to pay attention to all of the items mentioned above. > > We all love to hate the "bean counters", but we also need to eat :-) Yep. :-) In fact, there is another axis to this discussion. You'll see what I mean when we announce something. -- Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk CrossWorks for MSP430, ARM, AVR and now MAXQ processors

> I don't know much about CrossConnect/CrossWorks but I understand > it works on both Windows and linux. I think this is the only USB > JTAG device that works on linux. But I don't think this provides > an open API? MPE's JTAG Widget has a completely open and documented API. It will work for any O/S (including Linux) that supports the FTDI chips. See: http://www.mpeforth.com/jtagwidget.htm Stephen -- Stephen Pelc, stephen@step... MicroProcessor Engineering Ltd - More Real, Less Time 133 Hill Lane, Southampton SO15 5AF, England tel: +44 23 80 631441, fax: +44 23 80 339691 web: http://www.mpeforth.com - free VFX Forth downloads

--- In lpc2000@lpc2..., "Paul Curtis" <plc@r...> wrote: > We are currently in two (or maybe three) minds as to whether to open up > the CrossConnect API. There's good reasons to keep it closed and good > reasons to open it up. I'm sure you understand the pros and cons of opening the interface. In favor of opening the API: 1. If the interface is open you may sell more CrossConnect parts. 2. You would foster "good will" by having an open interface. Reasons not to open the API: 1. You might lose a competitive advantage because there would be less need for people to buy CrossWorks. 2. Further, your competitors might even take advantage of your own device. They wouldn't make a clone, but rather, if they support your devices you'd make a small amount on the devices themselves, but they would get the higher profit margin on selling their software tools to people who buy your parts. Obviously #1 on the "in favor" list is mitigated by the fact that you are not really in business to sell CrossConnect parts. Rather, it's likely being done specifically as a "value added" addition to help CrossWorks users. In fact, I am guessing that you're probably making very little profit selling CrossConnect. I'm definitely in favor of open source tools (I write some of my own for the hc11/hc12), but I understand that businesses have to pay attention to all of the items mentioned above. We all love to hate the "bean counters", but we also need to eat :-) Eric

Eric, > > I have a question about Rowley's CrossConnect: does it only > work with > > CrossWorks, or can it be used with my own GNU toolchain and > GDB? I am > > also wondering the same about the Segger J-Link. > > The J-Link comes with a Windows DLL that provides a proprietary > (closed) implementation of the RDI debug commands. They also > make a J-link server that surfaces a TCP/IP interface to the > RDI commands and that API is open and supported by gdb. Gdb > is a commandline debugger that has GUI wrappers in the form > of Insight and Eclipse. > > The J-link currently cannot be used on any host OS other than Windows. > > I don't know much about CrossConnect/CrossWorks but I > understand it works on both Windows and linux. I think this > is the only USB JTAG device that works on linux. But I don't > think this provides an open API? We are currently in two (or maybe three) minds as to whether to open up the CrossConnect API. There's good reasons to keep it closed and good reasons to open it up. I'm prepared to hear arguments to open up the CrossConnect. -- Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk CrossWorks for MSP430, ARM, AVR and now MAXQ processors

--- In lpc2000@lpc2..., Doug Sutherland <doug@p...> wrote: > I have a question about Rowley's CrossConnect: does it only work with > CrossWorks, or can it be used with my own GNU toolchain and GDB? I am > also wondering the same about the Segger J-Link. The J-Link comes with a Windows DLL that provides a proprietary (closed) implementation of the RDI debug commands. They also make a J-link server that surfaces a TCP/IP interface to the RDI commands and that API is open and supported by gdb. Gdb is a commandline debugger that has GUI wrappers in the form of Insight and Eclipse. The J-link currently cannot be used on any host OS other than Windows. I don't know much about CrossConnect/CrossWorks but I understand it works on both Windows and linux. I think this is the only USB JTAG device that works on linux. But I don't think this provides an open API? Eric

--- In lpc2000@lpc2..., "Isamoung" <isamoung@h...> wrote: > > Hi there, > > I was used in using Olimex ARM-JTAG (Wiggler) on my laptop. > I now got a new laptop with no parallel port only usb. > > Are there any solutions to have a "lowcost" to programm LPC2138 chip. > > is it better to use usb equipment , and what is availible ? > > regards, > > gerrit You can probably use something like this for the least expense. It claims to be aimed at your particular problem. http://www.transdigital.net/info.htm --Dave

Doug Sutherland wrote: >Isamoung wrote: > >>I was used in using Olimex ARM-JTAG (Wiggler) on my laptop. >>I now got a new laptop with no parallel port only usb. >> >>Are there any solutions to have a "lowcost" to programm LPC2138 chip. >>is it better to use usb equipment , and what is availible ? >> >> > >I have a list of JTAG adapters here >http://www.proficio.ca/#JTAG-Resources > >If anyone is aware of others not on that list, please let me know. > >I have a question about Rowley's CrossConnect: does it only work with >CrossWorks, or can it be used with my own GNU toolchain and GDB? I am Hi Doug, CrossConnect works only with CrossWorks. Regards Michael >also wondering the same about the Segger J-Link. > > -- Doug > > >Yahoo! Groups Links

Isamoung wrote: > I was used in using Olimex ARM-JTAG (Wiggler) on my laptop. > I now got a new laptop with no parallel port only usb. > > Are there any solutions to have a "lowcost" to programm LPC2138 chip. > is it better to use usb equipment , and what is availible ? I have a list of JTAG adapters here http://www.proficio.ca/#JTAG-Resources If anyone is aware of others not on that list, please let me know. I have a question about Rowley's CrossConnect: does it only work with CrossWorks, or can it be used with my own GNU toolchain and GDB? I am also wondering the same about the Segger J-Link. -- Doug