mcuinit

I am working on a project that I inherited. The project was originally developed with a much older version of Code Warrior. Since the older versions will not function on windows 7 (64), I needed to installed Code Warrior 10.6 (which has now down graded itself to the free special edition version).

Since there is no project import function, I created a new project specifying the correct chip (MC9S08QG8CPBE). Then via "add files" I added the source and header files. The original project included mcuinit.c and mcuinit.h. If I include these the build fails. Examining the contents of the orginal mcuinit.c file, the comments indicate the file is built by "the tool".

I want to use the supported currentversion of Code Warrior. Customers should not be tasked with finding methods for supporting their work with tricks and kludges to have existing projects work with new versions of software. This is like asking my customers to fix problems with my products sold to them. Sorry, but upgrade paths should always be provided so that existing software (projects) will continue to function with new versions of supplied by a vendor. If Freescale does not want to provide straight forward and easy to implement upgrade paths for existing projects, then it should continue support the versions of tools that do. In other words, Freescale should fix Code Warrior 6.x so that it installs and functions properly on Windows 7 (64 bit) and continue to support it.

So to answer your question " do you want to move the project on new version ?". Yes, I want my project to build and function properly using the latest supported version of Code Warrior. I do not want to be "stuck" on a version of the tools that are not supported.