Hi John
Just taking a stab in the dark, I tried
adding various CF_4I*MSL*.a files to the Support Files folder in the project with no luck
I think that this is the correct way to do it. The uTasker project is set up without any library support since there are non needed for the basic project to work.
If I need malloc()/free() I add C_4i_CF_SZ_MSL.a to the support file directory as you have done.
Since you are still getting linker errors it means that the library you are adding doesn't contain what is needed for the Floating Point work.
I suggest noting the routines (and/or const data) which are missing. Then do a serach in all files in the CW directory until you find them. They may be in C files but may also be in assembler files so best search with wild card (*.*) so that you don't miss anything. The missing routines must be there somewhere and once you have located the files you can probably work out which library they are actually used in. You may also find that the library sources also use defines and the routine you need is not actually being compiled into the library - in other words the actually library configuration is not available in the CW directory. In the worst case this may require settin the define in a header controlling the library build and rebuilding a library yourself. However it doesn't look as though the library support is quite rich and most flavours are already available precompiled.
I will also take a look later.
Regards
Mark
A little later...
I had a go at adding some floats and the linker complained about the routine f_add() being missing.
Now I couldn't find this anywhere at all!!
This makes me wonder whether the lite/special edition versions of CW perhaps really do not have any FP support at all.
If all else fails, it may be possible to add the GCC FP support (gcc/config/m68k/lb1sf68.asm in the GCC project) - see the following:
http://osdir.com/ml/hardware.motorola.microcontrollers.coldfire/2004-05/msg00063.htmlI haven't tried this (yet) so I don't know whether it really is as simple as that. Hopefully there will be a reply from one of the Freescale experts soon to clear up this case.