The C project that doesn't use Processor Expert can be converted to Processor Expert. This is useful when the user finds out additional features of Processor Expert.
Warning: Note that in most cases this conversion involves necessary manual changes in the application code, because for example the register interrupt vectors table definitions created by the user often conflicts with Processor Expert definitions. Don't forget to backup the whole project before the conversion. Some files will have to be removed from the project. The conversion to Processor Expert is recommended to experienced users only.
The conversion steps are as follows:
- Select the menu command File > New > Other...
- Within the "Select a wizard" dialog select Processor Expert/Enable Processor Expert for Existing C Project and click Next.
- Select the project that you would like to convert and the project type.
- Processor Expert can generate initialization code and drivers for on-chip peripherals and also drivers for selected external peripherals or software algorithms. See Features of Processor Expert topic for details.
- Select the microcontroller that the project is designed for.
- Select the microcontroller variant(s) and Processor Expert configurations that you would like to have available in the project.
Note: The functionality of the existing build configurations in the existing project (like Console_RAM) is not guaranteed. These build configurations need to be updated, typically a linker command file name has to be changed to the one generated by Processor Expert.
- Review the actions that Processor Expert is about to perform. You can deselect the checkboxes for items you would like not to be done. Ensure that you have backed-up your project before confirming before you confirm by clicking Finish button.
- Now it's necessary to move the application code from original main.c located in "Sources" folder into new ProcessorExpert.c generated by Processor Expert in previous step, consequently remove original main.c module from the project.
- For Kinetis family projects, it's necessary to remove the files kinetis_sysinit.c and kinetis_sysinit.h from Project_Settings/ Startup_Code. This module contains definitions that conflict with Processor Expert definitions.
- For Coldfire family projects, it is necessary to remove the cfm.c file in Sources folder. This module contains definitions that conflict with Processor Expert definitions.
If this module is changed, it is necessary to update the cpu component settings in Internal peripherals\FlashConfigurationField to match the changes in the cfm.c module.