#Keil 5 to makefile code

GCC CodeSourcery - GCC produces very good code for ARM (only a few % larger code size than the 'big-boys'). It is Eclipse base so people either love it or hate it - it is rather slow (due to Eclipse and Java script) and a bit quirky (again due to the Eclipse based operation and 'mentality') but useable with a bit of determination - but usually not as simple as the classical approach that IAR and Keil take. CW10.1 - Very interesting 128k limited version which is adequate for even quite large projects and is often the choice for low budget projects where Keil and IAR are too expensive.

#Keil 5 to makefile full

Note that Keil has a Freescale only version which costs about $600 but is otherwise full functional this is however a 1 year term license so expires after this period. Limited version is available but less useful than the IAR Kick start since it throws in extra code to limit use. For existing Keil users, Keil will probably be the preference. Personally I find its editor and project manager a little less capable than IAR. Instruction level debugger useful for testing configurations and start-up code. Keil is also easy to use - generates good code and has a fast and reliable debugger. For small projects, the 32k limited kick start version is useful. IAR is very easy to use - generates good code and has a fast and reliable debugger. However CodeWarrior is probabyl the best choice if you do like the Eclipse environment since it is freescale's own offering and so will always have the most up-to-date processor support for sure. K70) in their tool chain (if your preference is an Eclipse/GCC based solution). Also ATOLLIC now supports all Kinetis parts (incl. Best ask Mentor to be sure since it is their product. It may be that your freescale contact meant that the CodeSourcery Lite environment/debugger doesn't support the Kinetis (it may not have the necessary reset/download scripts or peripheral register mapping) but this doesn't mean that it won't build with its tool chain. CodeSourcery Lite is based on the GCC tool chain which will compile Kinetis projects as long as the code can be compiled by GCC (usually things like interrupt definitions, pragma use, code positioning can vary between compilers so a few 'minor' changes are often needed - although 'minor' changes can take a bit of tie to get right without some experience with the compilers in question).