![](http://datasheet.mmic.net.cn/260000/PPSMMANUAL_datasheet_15946768/PPSMMANUAL_17.png)
3-2
PPSM PPSM Programming
Programmer’s Manual
handler assignment. It must be called before any other PPSM tool. As an optioterminated, the sub-task will be swapped out or terminated too. Sub-task inherits
can also perform the pen to screen calibration. This should only be done oncthe input pad and panning screen properties from the parent task at creation.
system start-up.
3.1.2
Task Registration
An application is treated as a task in PPSM. After PPSM is initialized, each
application task on the system must be registered with PPSM before the
application can make use of the PPSM tools.
When integrating the individual applications onto the system, the system
integrator must first call one of the task creation tools for each application. There
are two types of tasks, main task or sub task (refer to Section 13.1 - Main Task
and Section 13.2 - Sub-task). This registration of tasks ensures that the run time
memory and stack required for each application are allocated within PPSM’s
memory system.
Associated with each main application task is an optional application launch icon.
This launch icon’s position on the touch panel can be specified in the task creation
tool. The application is put to the foreground whenever this application icon is
selected by the pen input device.
When writing an application task, the developer can treat each task as a stand
alone procedure as PPSM resources are individually allocated. This
implementation of tasks allow a number of applications to be written
independently and linked together at the end to form a single system.
For details of the task creation tools, please refer to
Section 13.7 - Creating a
Task
,
Section 13.8 - Creating a Task with Specific Task Parameters
and
Section
13.9 - Creating a Sub Task
.
After all applications have been registered, the first application task can be started
by calling the tool TaskStart(). This tool never returns and other applications within
the system will be started when the corresponding application launch icon is
pressed.
3.2
PPSM Application Programming
This section describes the general flow for most applications operating under during active state execution. The interrupt service routine, running in supervisor
PPSM environment. The typical flow for most PPSM applications is shown in
Figure 3-2
. After the application initializes itself and registers icons and draw
areas with PPSM, it would continuously call IrptGetData() to check for incoming
events. When an event occurs, the application would process the event and tThe suspended task will return to active state if no other application is selected,
loop back to IrptGetData() to wait for more events.
Personal Portable System Manager
Programmer’s Manual
2-7
2.8.2
Application State Transition
Application tasks have three states.
application.
shows the three states of an
Active
Suspended
Stopped
This is the state when an application is actively being accessed by the user. All
hardware resources are available to an active task.
2.8.2.2 Suspended State
An application task is put into suspended state when the kernel is interrupted
mode, will become the active task. During the active-to-suspended transition, only
the registers that are used by the interrupt handler are saved.
otherwise it will be put into stopped state.
2.8.2.3 Stopped State
An application changes from suspended state to stopped state when another
application is selected. In this execution state, all registers and application display
bitmap image are stored by the kernel.
A task will exit from the stopped state to active state when the application is re-
Figure 2-4 Application State Transitions
Active
Suspended
Stopped
Interrupt
Application Selected
Interrupt
Return
from
Return
from Interrupt
F
Freescale Semiconductor, Inc.
For More Information On This Product,
Go to: www.freescale.com
n
.