Tracking changes in generated code

Processor Expert allows to track changes in generated modules. It is just necessary to enable the option Create code generation log in the Processor Expert Project options. Refer to the Processor Expert options topic for details. If this option is enabled, a file ProcessorExpert_CodeGeneration.txt is generated into Documentation folder.

The file contains a list of changes with details on purpose of each change. Refer to the example below:

Listing: Example - Tracking changes in generated code

###############################################################
Code generation 2010/10/22, 15:57; CodeGen: 1 by user:
by Processor Expert 5.00 for Freescale Microcontrollers; PE core 04.46
Configuration: Debug_S08GW64CLH
Target CPU: MC9S08GW64_64; CPUDB ver 3.00.000
# The following code generation options were changed:
> option Create code generation log: value changed from false to true
###############################################################

Code generation 2010/10/22, 16:01; CodeGen: 2 by user: User1 by Processor Expert 5.00 Beta for Freescale Microcontrollers; PE core 04.46
Configuration: Debug_S08GW64CLH
Target CPU: MC9S08GW64_64; CPUDB ver 3.00.000
# Component Cpu:MC9S08GW64_64, the following files modified due to 
internal interdependency:
- Generated_Code\Vectors.c - changed
- Generated_Code\Cpu.h - changed
- Generated_Code\Cpu.c - changed
# New component PWM1:PWM (ver: 02.231, driver ver. 01.28) added to the 
project, the following - 78 -
Processor Expert User Manual Application Design
- Generated_Code\PWM1.h - added
- Generated_Code\PWM1.c - added
# Documentation
- Documentation\ProcessorExpert.txt - regenerated
- Documentation\ProcessorExpert_Settings.xml - regenerated
# Other files have been modified due to internal interdependency:
- Generated_Code\PE_Timer.h - added
- Generated_Code\PE_Timer.c - added
# User modules
- Sources\ProcessorExpert.c - changed
> updated list of included header files
- Sources\Events.h - changed
> updated list of included header files
Totally 11 file(s) changed during code generation.

To view changes within the individual files, you can use a file pop-up menu command Compare with > Local history... available in Components view. It allows to compare files with the version before the code generation.