Rich
I generally still use CW6.3 but just did a couple of tests also with CW7.0
Base = standard uTasker project V1.3 + SP7 (no libraries)
The values are those displayed for code and RAM sizes in CW (assuming they are accurate):
CW6.3 maximum optimisation for size: 72k FLASH 7k RAM
CW6.3 no optimisation: 117k FLASH 7k RAM
CW7.0 - note that register coloring was automatically activated after converting CW6.3 project to CW7.0. CW6.3 has neither settings for register coloring, instruction scheduling, nor peepholeCW7.0 maximum optimisation for size: 78k FLASH 8k RAM
CW7.0 maximum optimisation for size - no register coloring: 108k FLASH 8k RAM
CW7.0 maximum optimisation for size - no register coloring, no instruction scheduling, no peephole: 115k FLASH 8k RAM
CW7.0 no optimisation: 80k FLASH 8k RAM
CW7.0 no optimisation - no register coloring: 112k FLASH 8k RAM
CW7.0 no optimisation - no register coloring, no instruction scheduling, no peephole: 120k FLASH 8k RAM
This shows that these new settings (register coloring, instruction scheduling and peephole) do indeed have a major effect on program size. The optimiser level setting much less.
Also it shows that the program size that CW6.3 achieves is about 8% smaller than CW7.0.
I have started using CW7.0 to debug 5222X and 5221X boards since CW6.3 doesn't seem to work with the demo boards - with the EVBs and external P&E BDM I can still debug with the CW6.3. However we have never had any problems with CW6.3 based project code, so the smaller build size suggests staying with it for the moment. Note that we avoid any library code - malloc() in CW6.3/CW6.4 has major problems and in CW7.0 there seem to be various difficulties (http://forums.freescale.com/freescale/board/message?board.id=CFCOMM&thread.id=4528).
Despite the few known problems I do however find the CW solution great - especially due to the fact that most people are using it for free as
special edition. It makes the choice for a Coldfire processor much easier for a lot of customers who are otherwise worried about having to make new investments in development tools. The debugger is not bad at all and of course the Coldfires themselves are a dream to work with...
Regards
Mark