Hi Andrija
You are correct in saying that porting to more powerful processors is not complicated and I am pleased that you could achieve the desired functionality without too much effort.
I think that the most important point is that the uTasker project is designed for single chip processors, which essentially means that it needs to be able to achieve a high level of functionality and user comfort without being able to rely on large amounts of memory. This means that it is certainly restrictive in its use of such resources, or put another way, it tried to use these as sparingly and as efficiently as possible.
When processors, like the larger Coldfires, have external memory it means that they tend to have large resources available (this also means that space requirements, power consumption and costs are generally higher too) and so some of the resource saving mechanisms in the project, which were optimised for the smaller processors - for example the single-chip V2 Coldfires - then become of less importance and may even be seen as a weakness. The project will of course be able to run on processors with high resource levels but may use a tiny footprint in comparison. The basic reason why it is probably not of great interest to support the larger chips is because this is then moving into territory dominated by solutions such as ucLinux, and others. These other solutions are on the other hand not practical when a larger design is to be shrunk to a smaller design - they would probably simply not be possible. To summarise, I don't want to say that the project is not of use or a bad choice for larger processors - I hope that it remains still a very good solution - but I don't think that generally the investment required to extend into this area and support it would be sensible since it is not such a good match and the competition is so great.
It is however worth noting that the uTasker project does make for a very good boot loader project for something like ucLinux on the larger platforms. It allows a full featured loader to be installed (essentially a uTasker project or a stripped down version with just the desired features - like a comfortable web browser for controlling uploads) which then controls loading of large applications.
But back to the CF card question: I still don't know the technical details about programming the cards but assume that there is a command mode which needs to be added. The FAT32 layer and most above it should be media independent. This means that it should not be a great amount of work to adapt the utFAT interface to work with the CF card. Are you interested in adding this interface specifically for your project?
Regards
Mark