User Manual

  
        !"#$"$%
3
1. M25 software architecture
This Module platform provides dual channels for MMI task to control protocol
stack and hardware device respectively. These service interfaces are Internal AT
command interface and driver service interface, as shown in Figure 1.
MMI task sends message which carries string based AT command to protocol
stack. By this way, MMI task must register AT command call back function for han-
dling occurred event. Hence, MMI task controls communication procedure via this
“Internal AT command” directly without extra hardware device support. Moreover,
previous BenQ module platform uses AT command to control hardware device. This
platform provides simply and uniform specific driver API for operating hardware de-
vice.
Figure 1 Service interfaces for MMI task
1.1. Internal AT command API
MMI task sends AT command string via internal AT command interface, and re-
ceives response message from registered callback function. The follow APIs are used
to handle those procedures.
 If_at_init() : This function is used to register callback function.
 If_at_cmd() : This function is used to send internal AT command.
MMI
AT command
Interface
Driver Service
Interface
Internal
AT command
Response
Callback
Driver API
Event
Callback