![](http://datasheet.mmic.net.cn/260000/PPSMMANUAL_datasheet_15946768/PPSMMANUAL_65.png)
12-6
UUART Communication Support
Programmer’s Manual
Data Transmit
APPLICATION
PPSM
H/W
Figure 12-2 UART Communication Architecture - Data Transmit
Request
Access
Check
Access
Permission
Release
Access &
Acknowledge
Send Data To
Hardware &
Acknowledge
Request
Transmit
Access Permission Request
(if not already)
Granted / Denied
Transmit Request & Data
Complete / Error
Release Access Request
Data Sent
Acknowledge
Release
Access
Personal Portable System Manager
Programmer’s Manual
12-3
Chapter 12 UART Communication Support
PPSM supports serial communication through the UART in both normal mode and
IrDA mode. A set of interface tools is provided for applications to send and receive
data through the UART.
12.1
UART Communication Architecture
The UART interface tools provide an easy-to-use API for applications to send and
receive data serially with or without hardware flow control. Refer to
and Figure 12-2 for an overview of the UART communication architecture
between a calling application and PPSM at system start up and during data
transmission.
PPSM monitors the use of the UART among applications through IrptRequest()
and IrptRelease() (refer to
tools will have effect only after the calling application has been granted permission
to access the UART. The data transmission is interrupt-driven.
). The UART interface
Once permission is granted, the calling application can configure the UART, send
or receive data through the UART, and be notified of the result of the send or
receive operation. The same set of API tools is used for IrDA communication if the
UART hardware is configured to run in IrDA mode.
12.1.1
UART hardware flow control
In PPSM v3.11, data communication between DragonBall and other
communication devices using UART supports RTS, CTS hardware flow control.
RTS is asserted automatically by calling UARTSend() and UARTReceive() when
hardware flow control is enabled. In null modem configuration, when Dragonball is
sender, receiver needs to acknowledge Dragonball ready to receive by asserting
it’s RTS pin. When Dragonball is receiver, it acknowledges the sender side by
asserting RTS pin. Thus, if both RTS pins of DragonBall and the other
communication device are asserted, data transfer can be full-duplex.
Three APIs are available for RTS, CTS hardware flow control. They are
UARTFlowCtrl(), UARTRcvCtrl() and UARTSendCtrl(). Hardware flow control can
be enabled or disabled by calling UARTFlowCtrl(). By calling UARTRcvCtrl() and
UARTSendCtrl(), PPSM can pause or continue data reception and data
transmission respectively.
An API, UARTSendAbort(), is used for returning the current position of software
send buffer and number of bytes have been transmitted by DragonBall. Also, this
API can abort the transmission with appropriate input flag.
F
Freescale Semiconductor, Inc.
For More Information On This Product,
Go to: www.freescale.com
n
.