|
Bean - An Embedded Bean is a component that can
be used in Processor Expert. Embedded Beans
encapsulate the functionality of basic elements of embedded systems like
CPU core, CPU on-chip peripherals, standalone peripherals, virtual devices
and pure software algorithms and wrap these facilities to properties,
methods, and events (like objects in OOP). Beans can support several
languages (ASM, ANSI C, Modula and others) and the code is generated for
the selected language. Bean Inspector - window with all parameters of a selected bean:
properties, methods, events. CPU Bean - bean which encapsulates the CPU core initialization
and control. This bean also holds a group of settings related to the
compilation and linking (Stack size, Memory mapping, linker settings etc..).
Only one CPU bean can be set active as the target CPU. See chapter CPU
Beans for details. Bean Driver - Bean drivers are the core of
Processor Expert code generation process. Processor Expert uses drivers to
generate the source code modules for driving an internal or external
peripheral according to the bean settings. A Bean can use one or more
drivers. Events - are used for processing events related
to the bean's function (errors, interrupts, buffer overflow etc.) by
user-written code. See chapter Embedded Beans
for details. External user module - external source code attached to the PE
project. The external user module may consist of two files: implementation
and interface (*.C and *.H). Internal peripherals - internal devices of the
CPU (ports, timers, A/D converters, etc. usually controlled by the CPU
core using special registers). ISR - Interrupt Service Routine - code which is called when an
interrupt occurs. Methods - user callable functions or
sub-routines. The user can select which of them will be generated and
which not. Selected methods will be generated during the code generation
process into the bean modules. Module - source code module. Could be generated
by Processor Expert (Bean modules, CPU Module, events.c) or created by the
user and included in the project (user module). OOP - Object-oriented programming (OOP) was invented to solve
certain problems of modularity and reusability that occur when traditional
programming languages such as C are used to write applications. PE - Abbreviation of Processor Expert which is often used within
this documentation. PESL (Processor Expert System Library) is
dedicated to power programmers, who are familiar with CPU architecture -
each bit and each register. PESL provides the macros to access the
peripherals directly, so PESL should be used only in some special cases.
See chapter PESL for details. Peripheral Initialization bean - encapsulates
the whole initialization of the appropriate peripheral. Beans that have
the lowest levels of abstraction and usage comfort. See chapter Bean
categories for details. They usually do not support any methods or
events except the initialization method. The rest of the device driver
code needs to be written by hand using either PESL or direct control of
the peripheral registers. See chapter Low-level Access
for details. Popup menu - this menu is displayed when the right mouse button
is pressed on some graphical object. Properties - parameters of the bean. Property
settings define which internal peripherals will be used by the bean and
also initialization and behavior of the bean at runtime. Target CPU - the CPU derivative used in a given
project. Template - Bean Template is a bean with preset
parameters. User-defined Bean Template - User-defined bean template is a
bean with preset parameters saved under a selected name. Also the name of
the author and short description can be added to the template. User module - a source code module created or
modified by the user. (Main module, event module or external user module).
|