To open this view, click
Window > Show View > Other...
and select
Processor Expert > Components.
Components view shows the tree with the following items:
- Generator_Configurations - Configurations of the project.
- Operating System - contains special components that provide operating system interface and configuration if there are any used.
- Processors - contains Processor Components included in the project.
- Components - it is included in the project. Every component inserted in the project is displayed in the Component Inspector view and may have a sub tree showing items available for the component (note that components can offer only some or even none of these items):
- Methods - Methods allow runtime control of the component's functionality.
- Events routines - Events allow handling of the hardware or software events related to the component. If the event is disabled, the name of the event is shown. For enabled events, the name of the handling function is shown.
- ISRs - Represent component-related interrupt routines that is created by you for low-level interrupt processing. For items, whose ISR names have been specified within component settings, a user-specified name of an ISR and name of the interrupt vector is shown. If an ISR name is not specified (interrupt has to be disabled in this case), only the interrupt vector name is present. You can specify an ISR in the component and generate the code. If the Generate ISRs project option is selected, empty ISR templates are generated into an event module. If you disable an ISR and select the Delete unused events and ISRs project option, empty ISR templates are removed automatically.
- PESL commands - low-level PESL commands related to the peripheral configured by this component. This folder is available only for Peripheral Initialization components.
- PDD Macros - low-level PDD macros for peripherals allocated by the component. Macros can be dragged and dropped into the source code. If the PDD macro is dragged, the base address parameter is automatically filled with the macro-value which uses the peripheral selected in the component.
- PDD -The global list of all PDD macros for all available peripherals are grouped by peripheral name. This folder is available only if PDD is available for the currently active CPU. PDD commands are low level peripheral access macros and they
are the replacement of PESL macros. PDD commands are available on all platforms
supported by Logical Device Drivers (LDD). Macros can be dragged and dropped into the source code. For details on PDD, see Low-level access to peripherals topic.
Note: PESL and PDD folders are available only for Peripheral Initialization components and only if PDD library or PESL library is supported for the selected processor. Either PESL or PDD folder is displayed and not both.
Figure 1. List of PDD macros 
All component's items have status icons that signify the enabled or disabled state. If this state cannot be changed directly, the background of the icon is gray. For more details, see
Embedded components topic.
This table explains the various states of a component.
Table 1. Description of component states | Component Status Icon |
Description |
|
|
Signifies that component is enabled. It can be configured and code can be generated from this component. |
|
|
Signifies that component is disabled. It can be configured, but the configuration validation/ generation is disabled. No code is generated from this component. |
|
|
Signifies error in the component. For example, Components folder contains component with error. |
|
|
Signifies that component is frozen and will not be re-generated. When the user generates the code again, files of this component are not modified and the generated code is frozen. |
Shared components are automatically placed into a dedicated subfolder Referenced_Components. You can move the component from this folder to anywhere.
Figure 2. Referenced components 
When you have more than one Processor Expert project in your workspace and you are working with those projects, the last project shown in Components view is recorded in the workspace history. When you restart the Eclipse IDE, the last session project is opened automatically.