Files produced by Processor Expert

The existence of the files can be conditional to project or Processor Expert environment settings and their usage by the components. See Project static modules topic for more details on files produced for project with static code support.

• Component module

  This module with its header file is generated for every component in the project with exception of some components that generate only an initialization code or special source code modules. Name of this file is the same as the name of the component.

  Header file (.h) contains definitions of all public symbols, which are implemented in the component module and can be used in the user modules.

  The module contains implementation of all enabled methods and may also contain some subroutines for internal usage only.

• Processor module

  The processor module is generated according to the currently active target processor component. The processor module additionally contains:

  • microcontroller initialization code
  • interrupt processing
• Main module

  The main module is generated only if it does not already exist (if it exists it is not changed). Name of this module is the same as the name of the project.

  The main module contains the main function, which is called after initialization of the microcontroller (from the processor module). By default, this function is generated empty (without any reasonable code). It is designed so that you can write code here.

• Event module

  The event module is generated only if it does not exist. If it exists, only new events are added into the module; user written code is not changed.

  The event module contains all events selected in the components. By default, these event handler routines are generated empty (without any meaningful code). It is considered that user will write code here.

  Event module can also contain the generated ISRs for the components that require a direct interrupt handling ( Peripheral Initialization Components). It is possible to configure the name of event module individually for each component in the ADVANCED view mode of the Component Inspector. However, note that the event module is not generated by Processor Expert if there is no event enabled in the component, except the processor component, for which the event module is always generated.

• Method list file with description of all components, methods and events generated from your project. The name of the file is {projectname}.txt or {projectname}.doc. This documentation can be found in the Documentation folder of the Project Panel.
• Signal names

  This is a simple text file {projectname}_SIGNALS.txt or {projectname}_SIGNALS.doc with a list of all used signal names. The signal name can be assigned to an allocated pin in the component properties (available in ADVANCED view mode). This documentation can be found in the Documentation folder of the Components view. See Signal names topic for details.

• Code generation log that contains information on changes since last code generation. See Tracking changes in generated code for details.
• XML documentation containing the project information and settings of all components in XML format. The generated file {projectname}_Settings.xml can be found in the Documentation folder of the Components view. It is updated after each successful code generation.
• Shared modules with shared code (the code which is called from several components). Complete list of generated shared modules depends on selected processor, language, compiler and on the current configuration of your project. Typical shared modules are:
  • IO_Map.h

    Control registers and bit structures names and types definitions in C language.

  • IO_Map.c

    Control registers variable declarations in C language. This file is generated only for the HC(S)08/HC(S)12 versions.

  • Vectors.c

    A source code of the interrupt vector table content.

  • PE_Const.h

    Definition of the constants, such as speed modes, reset reasons. This file is included in every driver of the component.

  • PE_Types.h

    Definition of the C types, such as bool, byte, word. This file is included in every driver of the component.

  • PE_Error.h

    Common error codes. This file contains definition of return error codes of component's methods. See the generated module for detailed description of the error codes. This file is included in every driver of the component.

  • PE_Timer

    This file contains shared procedures for runtime support of calculations of timing constants.

  • {startupfile}.c

    This external module, visible in the External Modules folder of the Components view, contains a platform specific startup code and is linked to the application. The name of the file is different for the Processor Expert versions. For details on the use of the startupfile during the reset, refer to the Reset scenario with PE for HC(S)08, RS08, and 56800/E topic.

  • "PESL".h

    PESL include file. This file can be included by the user in his/her application to use the PESL library. For more details, refer to the Processor Expert system library topic.

  • Static modules with static source code of Peripheral Initialization components, processor component methods including startup methods, IO map, Physical Device Driver macros and other Processor Expert modules. These modules are available only for projects with static code support. For more details, refer to the Project static modules topic.
  • Configuration header files containing parameterization constants which controls static source code. Configuration header file is generated for each component with static code support added to the project. These modules are generated only for projects with static code support. For more details, refer to the Peripheral initialization component files topic.

For more details, refer to the Predefined Types, Macros, and Constants topic.