In “Overview: From Snippets to Code Generation” I discussed several tools used in my development process. On tool which helps me a lot to get things done is Processor Expert. In this post I’ll give an overview about this tool and reasoning for the pros and cons of using it.
I think the biggest frustration point for any new or even seasoned engineer is the debugging phase: my application finally builds fine, but I’m not able to connect and download it to the target board :-(. In my view the debugging part is the most fragile part of the development process. I’m always very relieved if I can connect to a brand new board, because I know if it does not work, then the problem could be a very bad one, costing my several hours or even days to overcome it.
It took me a while to find the time to upgrade to FreeRTOS V7.4.2, but finally it is done :-). What caused me to move from V7.2 to V7.4 is a low power application on the FRDM-KL25Z board. V7.4 comes with two major new features: Queue Sets and Tickles Idle Mode (see this article). The last one if of interest here.
FreeRTOS runs an IDLE task. This one runs when there is no other active task. That task calls an optional Idle task hook which is a perfect place to put the microcontroller into low power mode:
One thing which is missing with the CodeWarrior for MCU10.2 announcement: MCU10.2 does not support the S12(X) from Freescale.
With this I still have several projects not ported to eclipse. So they are still implemented using the ‘classic’ (non-eclipse based) version of CodeWarrior for S12(X). And I’m using FreeRTOS in the eclipse based IDE with Processor Expert for S08, ColdFire and Kinetis, but not yet for the S12(X). What now? Continue reading →