Hi Marcin
The uTasker project is based on a co-operative scheduler that takes up about 2k of code size (which is a fraction of the size required by FAT, for example).
If the scheduler is removed, different code, like a main super-loop, needs to be added that will eventually take up similar code size but lose features and make the project much more difficult to coordinate. Therefore the OS is not a disadvantage but instead allows modularity and reliability to be easily achieved with virtually no extra code overhead in the overall project.
The uTasker project is a single application that will run on most KEA, KE, KL, KV and K boards. It includes projects for the following IDEs/Compilers
and full source code so that it can be simply modified to suit the application in question.
CodeWarrior users can follow the simple guide linked by Freescale's CodeWarrior 10.x or follow the video: uTasker for Kinetis using CodeWarrior - YouTube
Regards
Mark
Kinetis: µTasker Kinetis support
K40: µTasker Kinetis KWIKSTIK support / µTasker Kinetis TWR-K40X256 support / µTasker Kinetis TWR-K40D100M support
ADC/DAC: http://www.utasker.com/docs/uTasker/uTaskerADC.pdf
USB User's Guide: http://www.utasker.com/docs/uTasker/USB_User_Guide.PDF
utFAT2.0: http://www.utasker.com/docs/uTasker/uTasker_utFAT.PDF
For the complete "out-of-the-box" Kinetis experience and faster time to market