--- In l..., Paul Curtis wrote:
>
> I am not sure that you can purchase this separately as it is an OEM product.
>
> You can purchase it with the FDI kits:
>
> http://www.teamfdi.com/support/touch-screen.php
>
> -- Paul.
>
Thanks Paul. That's exactly what it is !

Nope. I can't get these. It's also slowed down to about 33% of the full speed J-Link box. I suppose I could buy the FTI kit.
I was just thinking of using it for a backup if our J-Link goes
bad. We have several of those and once in a great while they
do break, but nothing has lately.

$300 is about the cheapest I can find the J-Link which will do.

boB

> On 17 Apr 2012, at 19:15, boB G wrote:
>
> >
> >
> > We use IAR EWARM and LPC1766 and LPC2366 parts with the J-Link...
> >
> > I just saw mentioned in the Segger catalog, this LPC Lite JTAG box.
> > Anybody know if it is actually available ?? I cannot seem to find it anywhere except in their PDF catalog...
> >
> >
> > 2.6.7 NXP: J-Link Lite LPC Edition
> >
> > J-Link Lite LPC Edition is an OEM version of J-Link, sold by NXP.
> > Limitations
> >
> > J-Link Lite LPC Edition only works with NXP devices. This limitation
> > can NOT be lifted; if you would like to use J-Link with a
> > device from an other manufacturer, you need to buy a separate
> > J-Link.
> >
> > Licenses
> > No licenses are included.
> >
> >
> >
> >
> >
> > --- In l..., richard neveau wrote:
> >>
> >>
> >>
> >>
> >>> Regarding Rowley
> >> I have used in last 7 years, at work, for ARM based product development, the following IDE's - Rowley Crossworks, IAR EWARM, TI CCS4, Freescale CodeWarrior 10, & Mentor Code Sourcery/Bench.
> >> The only 2 I will gladly use again are Rowley & IAR.
> >> ---------
> >> Rowley Crossworks also seemed the best tool for 'debug' of embedded devices as it wasn't as flaky as the eclipse based tools and IMO was a little better debug experience day to day than IAR. IAR seems to build a little better code in benchmarks I've seen but I have not needed to squeeze CPU cycles for a while so the debug experience is what I rate as most important. Also $1500 < $5000 so while both tools are good Rowley is less expensive.
> >> One thing with Eclipse based tools we have used is the whole 'sharing' of projects via SCM tool (SVN in our case) seems very hard to do smoothly. The .metadata directory has too big a mix between project and personal settings to be a good candidate for raw archiving and there was not a good rule of thumb we found to use across all Eclipse tools on what parts to save away. If you have more than a few developers on a project you might have some issues (or a lot of extra work) to make something that is bit for bit reproducible after changing PC's or several additional projects have occurred and you have to go back to do maintenance. If you can stick with one IDE and one product maybe you only have to learn the rules once so just a one time waste of resources but I'm betting figuring out this will cost you in some fashion close to $500 x N developers unless your N is large (or you force everyone to use exactly the same development environment).
> >> Have not used CodeRed but last time I did an IDE eval it seemed CodeRed didn't support the extended ARM family as well as Rowley and IAR did. If you go to an chip outside NXP/TI/ST products you would have to switch tools. You probably never HAVE to use a chip not available from one of those vendors for most embedded products but something to consider.
> >> If you are sure you will only use NXP chips then maybe the trace feature is enough to tip you to CodeRed even with the Eclipse issues. If it is as powerful as the Keil trace feature seems to be in demos it would catch my interest if I didn't have to support a wider range of chip vendors (and it wasn't Eclipse based ).
> >>
> >>
> >
> >
> >
> >
> >
> > Start a New Thread

Speaking of tools...

I sure with that Segger would FraCkinG fix there STUPID USB
drivers !!
I'm tired of getting these stoopid warnings like...

Warning: Write failed (target is running) at Memory address 0xE01FC08c when the damm USB cable is UNPLUGGED and it goes ON and ON and ON and I have to Ctrl-Alt-Delete and close IAR EWARM and the driver and sometimes reboot and re-install the USB drivers !

Why can't these guys (IAR/SEGGER) make their systems run on Mac OS X and then I could get away from Windoze completely !

Thanks
boB

--- In l..., Paul Curtis wrote:
>
> I am not sure that you can purchase this separately as it is an OEM product.
>
> You can purchase it with the FDI kits:
>
> http://www.teamfdi.com/support/touch-screen.php
>
> -- Paul.
>
> On 17 Apr 2012, at 19:15, boB G wrote:
>
> >
> >
> > We use IAR EWARM and LPC1766 and LPC2366 parts with the J-Link...
> >
> > I just saw mentioned in the Segger catalog, this LPC Lite JTAG box.
> > Anybody know if it is actually available ?? I cannot seem to find it anywhere except in their PDF catalog...
> >
> >
> > 2.6.7 NXP: J-Link Lite LPC Edition
> >
> > J-Link Lite LPC Edition is an OEM version of J-Link, sold by NXP.
> > Limitations
> >
> > J-Link Lite LPC Edition only works with NXP devices. This limitation
> > can NOT be lifted; if you would like to use J-Link with a
> > device from an other manufacturer, you need to buy a separate
> > J-Link.
> >
> > Licenses
> > No licenses are included.
> >
> >
> >
> >
> >
> > --- In l..., richard neveau wrote:
> >>
> >>
> >>
> >>
> >>> Regarding Rowley
> >> I have used in last 7 years, at work, for ARM based product development, the following IDE's - Rowley Crossworks, IAR EWARM, TI CCS4, Freescale CodeWarrior 10, & Mentor Code Sourcery/Bench.
> >> The only 2 I will gladly use again are Rowley & IAR.
> >> ---------
> >> Rowley Crossworks also seemed the best tool for 'debug' of embedded devices as it wasn't as flaky as the eclipse based tools and IMO was a little better debug experience day to day than IAR. IAR seems to build a little better code in benchmarks I've seen but I have not needed to squeeze CPU cycles for a while so the debug experience is what I rate as most important. Also $1500 < $5000 so while both tools are good Rowley is less expensive.
> >> One thing with Eclipse based tools we have used is the whole 'sharing' of projects via SCM tool (SVN in our case) seems very hard to do smoothly. The .metadata directory has too big a mix between project and personal settings to be a good candidate for raw archiving and there was not a good rule of thumb we found to use across all Eclipse tools on what parts to save away. If you have more than a few developers on a project you might have some issues (or a lot of extra work) to make something that is bit for bit reproducible after changing PC's or several additional projects have occurred and you have to go back to do maintenance. If you can stick with one IDE and one product maybe you only have to learn the rules once so just a one time waste of resources but I'm betting figuring out this will cost you in some fashion close to $500 x N developers unless your N is large (or you force everyone to use exactly the same development environment).
> >> Have not used CodeRed but last time I did an IDE eval it seemed CodeRed didn't support the extended ARM family as well as Rowley and IAR did. If you go to an chip outside NXP/TI/ST products you would have to switch tools. You probably never HAVE to use a chip not available from one of those vendors for most embedded products but something to consider.
> >> If you are sure you will only use NXP chips then maybe the trace feature is enough to tip you to CodeRed even with the Eclipse issues. If it is as powerful as the Keil trace feature seems to be in demos it would catch my interest if I didn't have to support a wider range of chip vendors (and it wasn't Eclipse based ).
> >>
> >>
> >
> >
> >
> >
> >
> > Start a New Thread

I evaluated all, chose IAR, using it for 4 years. Very pleased with software and support.

For professional use, I/we want to buy/use compiler/IDE tools, and NOT spend time building and debugging tools. Customer doesn't pay for that.
--- In l..., Steve Childress wrote:
>
> Did you consider IAR and Keil?
>
> And if your target is an Atmel ARM, Atmel Studio 6 (free)
>
>

Start a New Thread