Migrating from PIC18 to ARM: which MCU to choose?
in [Embedded]
|
From: Rich Webb on 11 Aug 2010 19:18 On Wed, 11 Aug 2010 19:27:28 +0200, Anton Erasmus <nobody(a)spam.prevent.net> wrote: >Go too >http://www.hitex.com/index.php?id=download-insiders-guides&L=1 > >And download the guides from Hitex. These guides are quite good and >gives a good overview of all these things. AFAICR the >older "The Insider's Guide To The Philips ARM7-Based Microcontrollers" >gives examples of how to do interrupt servers on these devices using >ARM7. They provide examples of typical assembly stubs as well as how >to handle nested interrupts using gcc. Got 'm. Thanks again! -- Rich Webb Norfolk, VA
From: David Brown on 12 Aug 2010 02:39
On 26/07/2010 22:57, Stimpy wrote: > On Jul 26, 8:46 am, rickman<gnu...(a)gmail.com> wrote: >> BTW, I don't see Atmel in this list. They are a major ARM vendor and >> should not be discounted. The SAM7 parts are still very viable >> devices and the SAM3 parts are the hot, new products in their ARM >> lineup. > > You're right, I completely forgot about Atmel. The SAM3 looks quite > good, it also has the DAC and DMA and SPI and probably the most > flexible timer / waveform generator that I've seen so far. The butilt- > in ROM bootloader is nice too, although not very useful for this > product. Now I've checked Digikey, Mouser, Arrow, Future, Farnell and > other than the development kit, no parts in stock anywhere. Are these > things actually available yet? If not, then I think I'll go with the > STM32. > > Now the question is which toolchain/JTAG to go with. I don't really > feel like mucking around with the DIY Eclipse/GCC/GDB/OpenOCD/Wiggler > solution and things like Keil, IAR, Greenhills, and Tasking are well > outside the budget. This leaves me with one of the "packaged" GCC > offerings like Rowley, Raisonance, Hitex, iSystem, Atollic, Aiji. > Does anybody have any experience with any of those? After reading a > few past discussions on here it looks like Rowley is a good choice, > Raisonance is OK but slow, and the Hitex IDE isn't all that great. The most popular "packaged gcc" suppliers are Code Sourcery and Code Red. Code Sourcery are the company that are responsible for gcc for the ARM (and MIPS, PPC, ColdFire, and a couple of others), and thus have the best knowledge and support for the compiler - when you ask them for help, you are talking to the people that wrote the tools. Most of the other "packaged gcc" companies base their tools directly on Code Sourcery's build rather than the official FSF tree. I don't know much about Code Red, except that they are popular in the USA. But TI/Luminary provides evaluation kits and software for four toolchains - Keil, IAR, Code Sourcery and Code Red - which should give you an idea of the popularity. I don't know how much the other "packaged gcc" suppliers actually contribute to gcc - they may be heavily involved, or may do very little. Some make their own libraries, others used pre-packaged libraries (such as newlib). Some make their own IDEs and/or debuggers, others use Eclipse and gdb (whether you call that a good thing or a bad thing is a matter of opinion). |