Hi folks, Thanks for the help. I assumed no-one had replied and this was a dead list as I had no reply, then realised I'd joined the old shadow group, not the proper one! Sheesh, if I can't get that right, what chance do I stand programming ARMs?! ;-) Cheers, Rob --- In lpc2000@yahoogroups.com, "Hugh O'Keeffe" <hugh.okeeffe@a...> wrote: > Hi Curt, > Thanks for your feedback. FYI, we now offer a range of adapters with the > devices all ready soldered/tested. Details on our page at > www.ashling.com/support/LPC2000. > > I'd appreciate if you send me some details (directly) on the "quirks" you > mention below. We're working on our next release and will incorporate good > suggestions time/schedules permitting. > > > > > Hugh @ http://www.ashling.com/support/lpc2100/ > > -----Original Message----- > From: Curt Powell [mailto:curt.powell@s...] > Sent: 13 April 2004 15:29 > To: lpc2000@yahoogroups.com > Subject: RE: [lpc2000] Thinking of using LPC2294 > > > Rob, > > I've about five months experience with the Ashling EVBA7 LPC2106 board. > It is part of a complete development system including gcc compiler, > source-level debugger, etc. Full license, including board, is about > 1500USD. It's has its many quirks, but its big advantage is that it > does work right out of the box. However, it is windows-centric. Also, > I seem to recall that for the non-210x LPC chips, you need to buy a bare > board and solder the LPC chip on yourself. > > Others on this list are developing on Linux, they might be able to point > you to other tools that might better fit your needs in that environment. > > Curt > > -----Original Message----- > From: dibosco [mailto:robert.wood@a...] > Sent: Tuesday, April 13, 2004 6:42 AM > To: lpc2000@yahoogroups.com > Subject: [lpc2000] Thinking of using LPC2294 > > > Hi folks, > > I have a project coming up for which I need some CAN ports and a > reasonable amount of power (in MIPS, not in mA!). The LPC2294 looks > perfect from what I can see, but I've never used ARM devices before and > would very much appreciate a little input. > > It looks to me like the Ashling LPC2000 dev board would be good for > getting me familiar with ARM, and the Crossworks compiler runs under > Linux which is what I want. Does anyone have any experience with Ashling > in general? Are they good products? Would Crosswork's kit work with it? > > My experince includes 68k, Infineon (X)C166, Fujitsu 16 bit devices and > lots of eight bit stuff, so I have a good amount of experice including a > large amout of 16 and some 32 bit micros. A few of the micros I've > worked with have JTAG interfaces and I like the fact that these Phillips > devices have them too. Are the ARM devices reasonably easy to get to > grips with for someone with the above experience? > > Finally, I would need to hang a couple of mega bytes of RAM on the > external address and data bus, how do ARM devices with internal RAM cope > with that? It might seem like a daft question, but, for example, the > Infineon XC16x devcies with internal flash aren't so great for hanging > stuff off the external bus because of memory segmentation. > > Many thanks, > > Rob > > > > > > Yahoo! Groups Links > > > > > > > > > Yahoo! Groups Sponsor > > ADVERTISEMENT > > <http://rd.yahoo.com/SIG=12cthcfcm/M=281792.4727319.5879690.1261774/D=egroup > web/S=1706554205:HM/EXP=1081953046/A=2058224/R=0/SIG=116652qbq/*http://my.ya > hoo.com/promo/ppets.html> click here > > <http://us.adserver.yahoo.com/l?M=281792.4727319.5879690.1261774/D=egroupweb > /S=:HM/A=2058224/rand=647486673> > > > _____ > > Yahoo! Groups Links > > > * To visit your group on the web, go to: > http://groups.yahoo.com/group/lpc2000/ > > > * To unsubscribe from this group, send an email to: > lpc2000-unsubscribe@yahoogroups.com > <mailto:lpc2000-unsubscribe@yahoogroups.com?subject=Unsubscribe> > > > * Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service > <http://docs.yahoo.com/info/terms/> .
Message
Re: Thinking of using LPC2294
2004-04-21 by robert.wood@apostrophe.co.uk
Attachments
- No local attachments were found for this message.