User Manual

Table Of Contents

  

        !"#$"$%

1.2. Driver service interface

BenQ provide complete specific driver API, which are:

 LCD driver API

 128*64 Black & White SPI control LCD.

 Keypad driver API

 Audio driver API

 Three sound types: key-beep, tone, melody.

 Two audio paths: hand-held, hand-free.

 GPIO driver API

 5 GPIO pins for customers.

 Real Time Clock API

 Flash File System driver API

 Power Management API

 Communication Channel API

 Communicate with external device via UART or USB port.

1.3. Dual image architecture

This platform provides one advanced code building policy which is “dual image”

architecture. Convention is compiling and link whole source files into one image file.

Hence, customer must maintain lots of library files and cost much time to download

the huge image file.

Dual image architecture is divide source code into two parts. The core proce-

dures which contain system, drivers and protocol are linked into one image file, and

MMI procedures of customer are built into another image file independently. By this

method, code management is more convenient. After module product leaving the

factory, the core image file is already downloaded into module and users only need to

download the MMI image. Hence, it costs users less time for proceeding download

procedure.

2. Console daemon

BenQ provides an MMI task prototype with development phase debug environ-

ment, which called “console daemon”. This software component simulates the MMI

task to communicate with module system core. Customers will know how to imple-

ment MMI task in this platform easily and conveniently via this task prototype. The

debug environment with command line interface is used to examine the correctness

of procedure and export the debug message via the serial port.