Table of Contents
Advertisement
Note: In boot and hold mode,
HIP is only available over
endpoints 2-IN and 2-OUT.
Rev 1.9 Sep.08
Note: On endpoints 4-IN and 4-OUT, the default non-MUX data
service for AC59X, C59X, and MC572X is HIP (carrying CnS and
DM).
If required, the default configuration for these devices can be changed
to DM, HIP (carrying CnS), or HIP (carrying CnS and DM). Contact
Sierra Wireless for details.
AC8XX, MC8775, MC8775V, MC8780, MC8781
•
mode, these modules use endpoints 4‐IN and 4‐OUT to
transport the data, and endpoint 1‐IN for flow control of the
host. In MUX mode, they use DLCI‐3 to transport the data.
C8XX, MC8785V, MC8790, MC8790V, MC8791V, MC8792V
•
non‐MUX mode, these modules are configured to transport
HIP (carrying CnS) messages using endpoints 1‐IN and
1‐OUT. In MUX mode, they use DLCI‐3 to transport the
data.
For details on the HIP protocol, refer to CDMA 1xEV‐DO CnS
Reference (Document 2130754), "HIP Basics" chapter, or MC87xx
Modem CnS Reference (Document 2130602), Chapter 3: "HIP
Basics".
CnS (Control and Status)
CnS objects (commands) are used to manage the module's
configuration, and to provide status reporting and monitoring
of the device.
These objects are transported between the host and module by
embedding them in HIP messages (see
Protocol)
, page 34).
For details on available CnS objects, refer to CDMA 1xEV‐DO
CnS Reference (Document 2130754) or MC87xx Modem CnS
Reference (Document 2130602).
DM (QUALCOMM Diagnostic
Monitoring)
The DM data channel is implemented as follows:
AC59X
C59X
•
,
can be configured to transport DM using endpoints 4‐IN
and 4‐OUT. In MUX mode, they use DLCI‐2 to transport the
data.
Proprietary and Confidential
MC572X
,
— In non‐MUX mode, these modules
Services
—In non‐MUX
— I n
HIP (Host Interface
35
Advertisement
Table of Contents
