diff -r 578be2adaf3e -r 307f4279f433 Adaptation/GUID-6060F138-CEB6-482A-B0E9-BBBE261568B0.dita --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/Adaptation/GUID-6060F138-CEB6-482A-B0E9-BBBE261568B0.dita Fri Oct 15 14:32:18 2010 +0100 @@ -0,0 +1,99 @@ + + + + + +Baseport Template OverviewThis section provides a summary of the Baseport Template +platform service. +
What +is the Baseport Template

The Baseport Template is a reference +board template, which provides a basic framework consisting of base +parts of the Symbian platform. This framework can be modified to suit +your hardware configurations.

The Baseport Template code is +categorized into Application Specific Standard Product (ASSP) layer +and variant layer. The ASSP layer provides the source code for hardware-specific +functions (for example, GPIO, DMA, IIC, USB Client Controller) that +are used by the kernel. This layer is implemented by the TemplateAssp class. The variant layer provides common peripheral +control functions such as power, bootstrap, keymap, keyboard and sound +that other extensions and device drivers can use. This layer is implemented +by the Template class.

ASSP and variant layers +provide control functions for hardware which is used by multiple devices. +This is done by placing Baseport Template code in a single DLL, called +the Variant DLL (ecust.dll). For hardware architectures +based on an ASSP, you can allow multiple phone types that use the +same ASSP to share the common code. To achieve this, implement the +common ASSP code in a kernel extension, and ecust.dll implements the code that is specific to each variant.

+
Purpose +of the Baseport Template

The Baseport Template is mostly +useful in creating a baseport and testing the software. The following +is a list of some of the key uses of the Baseport Template.

The Baseport Template is useful in handling:

    +
  • data exchange between devices connected to the bus

  • +
  • data copy between memory locations or between memory location +and peripheral

  • +
  • communication interface between the microprocessor components

  • +
  • hardware events and registers

  • +
  • USB functions of the device

  • +
  • power resources

  • +
  • phone restart after a hardware reset

  • +
  • shared chunks of camera and sound physical device driver

  • +
  • CPU idle operations

  • +
  • HAL, interrupt and keyboard functions

  • +
  • data storage based on NOR type flash memory

  • +
  • variant specific initialization (not the same as ASSP specific +initialization).

  • +
+
Users +of Baseport TemplateThe Baseport Template documentation cover +users who:
    +
  • manufacture devices and want to develop software and get an +early debug output.

  • +
  • develop baseport. See Base Porting Guide for base porting details

  • +
+
Baseport +Template details

The following table lists the Baseport +Template details:

+ + + +

DLL

+

Library

+

Description

+
+ + + +

katemplate.dll

+

None

+

ASSP DLL. This DLL is made up of the following template +files and can be found under ...template\asspandvariant\template_assp\ directory:

    +
  • template_assp.cpp

  • +
  • interrupts.cpp

  • +
  • assp.cpp

  • +
  • register.cpp

  • +
  • template_assp.cia

  • +
  • interrupts.cia

  • +
  • assp.cia

  • +

+
+ +

ecust.dll

+

None

+

Variant DLL. This DLL is made up of the following template +files and can be found in ...template\asspandvariant\template_variant\ directory:

    +
  • variant.cpp

  • +
  • variant.cia

  • +

+
+ + +
+
+Base +Porting Guide +
\ No newline at end of file