List of Figures.........................................................................................................................................4
2.0 Features ...........................................................................................................................................6
This document is intended to help hardware designers integrate the CobraNetTM interface
into an audio system design. It covers the CS18100x, CS18101x, CS18102x, CS49610x,
CS49611x, and CS49612x members of the CobraNet
“x” is the ROM version (ROM ID). This document also describes the CM-2 module with
schematics, mechanical drawings, etc.
CobraNet is a combination of hardware (the CobraNet interface), network protocol, and
firmware. CobraNet operates on a switched Ethernet network and provides the following
additional communications services.
• Isochronous (Audio) Data Transport
• Sample Clock Distribution
• Control and Monitoring Data Transport
The CobraNet interface performs synchronous-to-isochronous and isochronous-tosynchronous conversions as well as the data formatting required for transporting real-time
digital audio over the network.
The CobraNet interface has provisions for carrying and utilizing control and monitoring
data such as Simple Network Management Protocol (SNMP) through the same network
connection as the audio. Standard data transport capabilities of Ethernet are shown here
as unregulated traffic. Since CobraNet is Ethernet based, in most cases, data
communications and CobraNet applications can coexist on the same physical network.
Figure 1 illustrates the different data services available through the CobraNet system.
Flash memory holds the CobraNet firmware and management interface variable settings.
The CS1810xx or CS4961xx network processor is the heart of the CobraNet interface. It
implements the network protocol stacks and performs the synchronous-to-isochronous
and isochronous-to-synchronous conversions. The network processor has a role in
sample clock regeneration and performs all interactions with the host system.
The sample clock is generated by a voltage-controlled crystal oscillator (VCXO)
controlled by the network processor. The VCXO frequency is carefully adjusted to achieve
lock with the network clock.
The Ethernet controller is a standard interface chip that implements the 100-Mbit Fast
Ethernet standard. As per Ethernet requirements the interface is transformer isolated.
The host port is used to manage and monitor the CobraNet interface. Electrical operation
and protocol is detailed in the "Host Management Interface (HMI)" on page 23 of this
Manual.
The host port can operate in two modes in order to accomodate Motorola
interfaces. The default mode is Motorola. Intel mode is set via a firmware modification.
Table 2-1: Host Port Signals
SignalDescriptionDirection
HDATA[7:0] Host DataIn/Out
HADDR[3:0] Host AddressIn
HRW
HRDHost ReadInJ1:A4 107 Host Read (Intel mode).
Host RequestOutJ1:A6 140Host port data request.
HREQ
Host AlertOutJ1:A3 102Host port interrupt request.
HACK
HDS
Host StrobeInJ1:A5 103Host port strobe (Motorola mode).
HWR
Host EnableInJ1:A7 104Host Port Enable.
HEN
Host
Direction
Host WriteInJ1:A5 103Host Write (Intel mode).
InJ1:A4 107 Host port transfer direction (Motorola mode).
CM-2
Pin #
J1:A19,
A[17:11]
J1:A20,
A[10:8]
CS1810xx/
CS4961xx Pin #
111, 112, 114,
115, 117, 118,
102, 121
105, 106, 109,110 Host port address.
Host port data.
Notes
®
or Intel® style
HCS
SelectInJ1:A7 104Select (Intel mode).
4.2.2 Asynchronous Serial Port (UART Bridge) Signals
Level-shifting drive circuits are typically required between these signals and any external
connections.
Enable transmit (active high) drive for
two wire multi-drop interface.
Version 2.3
4.2.3 Synchronous Serial (Audio) Signals
The synchronous serial interfaces are used to bring digital audio into and out of the
system. Typically the synchronous serial is wired to ADCs and/or DACs. Detailed timing
and format is described in "Digital Audio Interface" on page 19.
CobraNet Hardware User’s Manual
Pinout and Signal Descriptions
SignalDescriptionDirection
DAO1_SCLKAudio Bit ClockOutJ3:A720
DAO1_DATA[3:0]
DAI1_DATA[3:0]Audio Input DataIn
DAI1_SCLKAudio Bit ClockInJ4:A7137
Audio Output
Data
Out
CM-2
Pin #
J3:A18,
B18
J3:
A[15:12]
CS1810xx/
CS4961xx Pin #
15-17, 19
131, 132, 134, 135
4.2.4 Audio Clock Signals
See "Synchronization" on page 17 for an overview of synchronization modes and issues.
Notes
Synchronous serial bit clock.
64 FS for CS18100x & CS49610x (2x1 channel)
64 FS for CS18101x & CS49611x (2x4
channels)
128 FS for CS18102x & CS49612x (4x4
channels)
Typically tied to DAI1_SCLK.
Output synchronous serial audio data
DAO1_DATA[3:1] not used for CS18100x &
CS49610x.
Input synchronous serial audio data
DAI1_DATA[3:1] not used for CS18100x &
CS49610x.
Should be tied to DAO1_SCLK.
Synchronous serial bit clock.
SignalDescriptionDirection
DAI1_LRCLK
DAO1_LRCLK
(FS1)
DAO2_LRCLK
(FS1)
REFCLK_INReference clockInJ3:A6 97
MCLK_IN
MCLK_OUT
Sample clock
input
Sample clock
output
Sample clock
output
Master audio
clock input
Master audio
clock output
In138Should be tied to DAO1_LRCLK for all devices.
OutJ3:A322
OutJ3:A314FS1 (word clock) for CS18102x & CS49612x.
*An external multiplexor controlled by this pin is required for full MCLK_IN and MCLK out
implementation.
Notes
FS1 (word clock) for CS18100x/CS49610x and
CS18101x/CS49611x.
Clock input for synchronizing network to an
external clock source, for redundancy control
and synchronization of FS divider chain to
external source. See "Synchronization" on
page 17 for more detail.
For systems featuring multiple CobraNet
interfaces operating off a common master
clock. See "Synchronization" on page 17 for
more detail.
System reset (active low).
10 ns max rise time. 1 ms min assertion time.
Toggles at 750 Hz nominal rate to indicate proper
operation. Period duration in excess of 200 ms
indicates hardware or software failure has occurred
and the interface should be reset. Note that
improper operation can also be indicated by short
pulses (<100 ns).
Asserts (active low) during initialization and when a
fault is detected or connection to the network is lost.
Use these CS1810xx/CS4961xx signals stricktly in the manner described in CM-2
Schematics (Section 9.2 on page 44). Each signal is briefly described below.
CobraNet Hardware User’s Manual
Pinout and Signal Descriptions
Signal Description
VCXO_CTRLA Delta-sigma DAC Output for Controlling the On-board VCXO1
MCLK_SELControl Signal for Selecting MCLK Sources2
DBDA, DBCKI2C Debugger Interface3, 4
TEST
DATA[15:0]Data Bus for Flash & Ethernet Controller(s)
ADDR[19:0]Address Bus for Flash & Ethernet Controller(s)
WE
CS1
CS2
OE
IOWAITWait State Signal from Ethernet Controller(s)96
Figure 3 shows clock related circuits for the CS1810xx/CS4961xx and board design
(CM-2). This circuitry allows the synchronization modes documented below to be
achieved. Modes are distinguished by different settings of the multiplexors and software
elements.
CobraNet Hardware User’s Manual
Synchronization
MCLK_OUT
DAC
MCLK_IN
MCLK_SEL
RefClkEnable
RefClkPolarity
REFCLK_IN
BeatReceived
VCXO
24.576 MHz
Edge
Detect
AClkConfig
Sample
Phase
Counter
Legend:
Detector
External
Hardware
Component
(CM2)
Audio
Clock
Generator
Phase
Hardware
Component
(CS1810xx, CS4961xx)
CS1810xx/CS4961xx
FS1
SLCK
Loop
Filter
Internal
Software
Component
Figure 3. Audio Clock Sub-system
5.1Synchronization Modes
Clock synchronization mode for conductor and performer roles is independently
selectable via management interface variables syncConductorClock and syncPerformerClock. The role (conductor or performer) is determined by the network
environment including the conductor priority setting of the device and the other devices on
the network. It is possible to ensure you will never assume the conductor role by selecting
a conductor priority of zero. However, it is not reasonable to assume that by setting a high
conductor priority, you will always assume the conductor role. For more information, refer
to CobraNet Programmer’s Reference Manual.
The following synchronization modes are further described below:
• "Internal Mode" on page 18
• "External Word Clock Mode" on page 18
• "External Master Clock Mode" on page 18
5.1.1 Internal Mode
All CobraNet clocks are derived from the onboard VCXO. The master clock generated by
the VCXO is available to external circuits via the master clock output.
Conductor—The VCXO is “parked” according to the syncClockTrim setting.
Performer—The VCXO is “steered” to match the clock transmitted by the Conductor.
5.1.2 External Word Clock Mode
All CobraNet clocks are derived from the onboard VCXO. The VCXO is steered from an
external clock supplied to the reference clock input. The clock supplied can be any
integral division of the sample clock in the range of 750Hz to 48kHz.
External synchronization lock range: ±5 µs. This specification indicates drift or wander
between the supplied clock and the generated network clock at the conductor. Absolute
phase difference between the supplied reference clock and generated sample clock is
dependant on network topology.
Conductor—This mode gives a means for synchronizing an entire CobraNet network to
an external clock.
Performer—The interface disregards the fine timing information delivered over the
network from the conductor. Coarse timing information from the conductor is still used;
fine timing information is instead supplied by the reference clock. The external clock
source must be synchronous with the network conductor. This mode is useful in
installations where a house sync source is readily available.
5.1.3 External Master Clock Mode
The VCXO is disabled and MCLK_IN is used as the master clock for the node. This is a
“hard” synchronization mode. The supplied clock is used directly by the CobraNet
interface for all timing. This mode is primarily useful for devices with multiple CobraNet
interfaces sharing a common master audio clock. The supplied clock must be
24.576 MHz. The supplied clock must have a ±37 ppm precision.
Conductor—The entire network is synchronized to the supplied master clock.
Performer—The node will initially lock to the network clock and will “jam sync” via the
supplied master clock. The external clock source must be synchronous with the network
conductor.
The CS18101x/CS49611x, CS18102x/CS49612x, and CM-2 support four bi-directional
synchronous serial interfaces. The CS18100x & CS49610x support one bi-directional
synchronous serial interface. All interfaces operate in master mode with DAO1_SCLK as
the bit clock and FS1 as the frame clock. A sample period worth of synchronous serial
data includes two (or four) audio channels. CobraNet supports two synchronous serial bit
rates: 48 Khz and 96 KHz. However, 96 kHz sample rate is not available when using
CS18102x/CS49612x with 16X16 channels. Bit rate is selected by the modeRateControl
variable. All synchronous serial interfaces operate from a common clock at the same bit
rate.
CobraNet Hardware User’s Manual
Digital Audio Interface
DAO1_D A TA0 / D A I1_D A T A0
DAO1_D A TA1 / D A I1_D A T A1
DAO1_D A TA2 / D A I1_D A T A2
DAO1_D A TA3 / D A I1_D A T A3
* Not
Figure 4. Channel Structure for Synchronous Serial Audio at 64FS (One Sample Period) - CS18100x/CS49610x &
resent in CS18100x or CS49610x.
DAO1_DATA0 / DAI1_DATA0
DAO1_DATA1 / DAI1_DATA1
FS1
FS1
12
34
56
78
CS18101x/CS49611x
12
56
34
78
DAO1_DATA2 / DAI1_DATA2
DAO1_DATA3 / DAI1_DATA3
Figure 5. Channel Structure for Synchronous Serial Audio at 128FS (One Sample Period) - CS18102x/CS49612x
910
1314
1112
1516
Default channel ordering is shown above. Note that the first channel always begins after
the rising or falling edge of FS1 (depending on the mode).
DAI1_SCLK period depends on the sample rate selected. Up to 32 significant bits are
received and buffered by the DSP for synchronous inputs. Up to 32 significant bits are
transmitted by the DSP for synchronous outputs. Bit 31 is always the most significant
(sign) bit. A 16-bit audio source must drive to bit periods 31-16 with audio data and bits
15-0 should be actively driven with either a dither signal or zeros. Cirrus Logic
recommends driving unused LS bits to zero.
Although data is always transmitted and received with a 32-bit resolution by the
synchronous serial ports, the resolution of the data transferred to/from the Ethernet may
be less. Incoming audio data is truncated to the selected resolution. Unused least
significant bits on outgoing data is zero filled.
6.1Digital Audio Interface Timing
MCLK_OUT
DAO1_SCLK
FS1
0 –5ns
0 –10ns
Figure 6. Timing Relationship between FS512_OUT, DAO1_SCLK and FS1
An DAO1_SCLK edge follows an MCLK_OUT edge by 0.0 to 5.0ns. An FS1 edge follows
a MCLK_OUT edge by 0.0 to 10.0ns.
Note: The DAO1_SCLK and FS1 might be synchronized with the either the falling edge or
the rising edge of MCLK_OUT. Which edge is impossible to predict since it depends
on power up timing.
≥5ns≥0ns
DAO1_SCLK
DAI1_DATAx
DAO1_DATAx
0 –12ns
Figure 7. Serial Port Data Timing Overview
Setup times for DAI1_DATAx and FS1 are 5.0 ns with a hold time of 0.0 ns with respect to
the DAI1_SCLK edge. Clock to output times for DAO1_DATAx is 0.0 to 12.0 ns from the
edge of DAO1_SCLK.
Each audio channel is comprised of 32 bits of data, regardless of audio sample size. The
figure above shows 24-bit audio data.
The MSB is left justified and arrives one bit period following FS1. Data is sampled on the
rising edge of DAI_SCLK and data changes on the falling edge.
The host port is 8 bits wide with 4 bits of addressing. Ten of the 16 addressable registers
are implemented. The upper two registers can be used to configure and retrieve the
status on the host port hardware. However, only the first 8 are essential for normal HMI
communications. It is therefore feasible, in most applications, to utilize only the first 3
address bits and tie the most significant bit (A3) low.
CobraNet Hardware User’s Manual
Host Management Interface (HMI)
Host port hardware supports Intel
®
(little-endian), Motorola®, and Motorola multiplexed
bus (big-endian) protocols. Standard CobraNet firmware configures the port in the
Motorola, big-endian mode.
The host port memory map is shown in Tabl e 3 . Refer also to "HMI Definitions" on
page 33 and "HMI Access Code" on page 34.
Host AddressRegister
0Message A (MS)
1Message B
2Message C
3Message D (LS)
4Data A (MS)
5Data B
6Data C
7Data D (LS)
8Control
9Status
Table 3. Host port memory map
The message and data registers provide separate bi-directional data conduits between
the host processor and the CS1810xx/CS4961xx. A 32-bit word of data is transferred to
the CS1810xx/CS4961xx when the host writes the D message or data register after
presumably previously writing the A, B, and C registers with valid data. Data is transferred
from the CS1810xx/CS4961xx following a read of the D message or data register. Again,
presumably the A, B, and C registers are read previously.
Two additional hardware signals are associated with the host port: HACK
and HREQ.
Both are outputs to the host.
HACK
may be wired to an interrupt request input on the host. HACK can be made to
assert (logic 0) on specific events as specified by the hackEnable MI variable. HACK
is
deasserted (logic 1) by issuance of the Acknowledge Interrupt message (see “Messages”
below).
HREQ may be wired to a host interrupt or DMA request input. HREQ is used to signal the
host that data is available (read case, logic 0) or space is available in the host port data
channel (write case, logic 1).
The read and write case are distinguished by the HMI based on the preceding message.
Identify, Goto Translation (read), Goto Packet (read) and Goto Counters cause HREQ
represent read status. Goto Translation (write) and Goto Packet (write) switch HREQ
write mode. All other commands have no effect on HREQ
to
to
operation.
In general, the host can read from the CS1810xx/CS4961xx when HREQ
write data to CS1810xx/CS4961xx when HREQ
7.2 Host Port Timing - Motorola® Mode
(CL = 20 pF)
ParameterSymbolMinMaxUnit
Address setup before HEN
Address hold time after HEN
Delay between HDS
Data valid after HEN
HEN
and HDS low for readt
Data hold time after HEN
Data high-Z after HEN
HEN
or HDS high to HEN and HDS low for next readt
HEN
or HDS high to HEN and HDS low for next writet
HR/W
rising to HREQ falling
Delay between HDS
Data setup before HEN
HEN
and HDS low for writet
HRW
setup before HEN and HDS lowt
HRW
hold time after HEN or HDS hight
Data hold after HEN
HEN
or HDS high to HEN and HDS low with HRW high for
next read
and HDS lowt
and HDS lowt
Read
then HEN low or HEN then HDS lowt
and HDS low with HRW hight
or HDS high after readt
or HDS high after readt
Write
then HEN low or HEN then HDS lowt
or HDS hight
or HDS hight
mas
mah
mcdr
mdd
mrpw
mdhr
mdis
mrd
mrdtw
t
mrwirqh
mcdw
mdsu
mwpw
mrwsu
mrwhld
mdhw
t
mwtrd
is low and can
is high.
5-ns
5-ns
0-ns
-19ns
24-ns
8-ns
-18ns
30-ns
30-ns
-12ns
0-ns
8-ns
24-ns
24-ns
8-ns
8-ns
30-ns
or HDS high to HEN and HDS low for next writet
HEN
HRW
rising to HREQ falling
mwd
t
mrwbsyl
30-ns
-12ns
NOTES:1. The system designer should be aware that the actual maximum speed of the communication port may
be limited by the firmware application. Hardware handshaking on the HREQ
The message conduit is used to issue commands to the CS1810xx/CS4961xx and
retrieve HMI status. The data conduit is used to transfer data dependent on the HMI state
as determined by commands issued by the host via the message conduit.
7.4.1 Messages
Messages are used to efficiently invoke action in the CS1810xx/CS4961xx. To send a
message, the host optionally writes to the A, B, and C registers. Writing to the D register
transmits the message to the CS1810xx/CS4961xx. A listing of all HMI messages is
shown in Ta bl e 4 . Refer also to "HMI Definitions" on page 33 and "HMI Access Code" on
Translate Address does not actually update the address pointers but initiates the
processing required to eventually move them. The host can accomplish other tasks,
including HMI Reads and Writes while the address translation is being processed. A
logical description of Translate Address is given below. A contextual use of the Translate Address operation is shown in the reference implementations. Refer also to "HMI
Definitions" on page 33 and "HMI Access Code" on page 34.
Moves HMI data pointers to the results of the most recently completed translate address
operation. The write parameter dictates the operation of the HREQ
signal and only needs
to be supplied for applications using hardware data handshaking via this signal.
Sets bridgeTxPkt = bridgeTxPktDone+1 thus initiating transmission of the contents of
bridgeTxPktBuffer. Presumably bridgeTxPktBuffer has been previously written with valid
packet data.
HMI status can always be retrieved by reading the message conduit. Status is updated in
a pipelined manner whenever the Message D register is read. Reading the message
conduit gives the current status as of the last time the conduit was read. Bitfields in the
HMI Status Register are outlined in Tabl e 5 below. Refer also to "HMI Definitions" on
Before accessing data, address setup must be performed. Address setup consists of
issuing a Translate Address request, waiting for the request to complete, then issuing a Goto Translation.
Pipelining requires that a “garbage read” be performed following an address change. The
second word read contains the data for the address requested. No similar pipelining issue
exists with respect to write operations.
7.4.3.1.Region length
Distance from the original pointer position (as per Translate Address) to the end of the
instantiated region. A value of 0 indicates an invalid pointer.
7.4.3.2.Writable Region
When set, this bit indicates the address pointer is positioned within a writable region. MI
variables may be modified in a writable region by writing data to the data conduit.
7.4.3.3.Translation Complete
When set, this bit indicates that the address translator is available (translation results are
available and a new translation request may be submitted). This bit is cleared when a
Translate Address message is issued and is set when the translation completes.
7.4.3.4.Packet Transmission Complete
This bit is cleared when transmission is initiated by issuance of the Transmit Packet
message. The bit is set when the packet has been transmitted and the transmit buffer is
ready to accept a new packet.
7.4.3.5.Received Packet Available
This bit is set when a packet is received into the packet bridge. It is cleared when the
packet data is read and receipt is acknowledged by issuance of an Acknowledge Packet Receipt message. Note that Received Packet Available only goes low when there are no
longer any pending received packets for the packet bridge. The packet bridge has the
capacity to queue multiple packets in the receive direction.
7.4.3.6.Message Togglebit
This bit toggles on completion of processing of each message. A safe means for the host
to acknowledge processing of messages is as follows:
void WaitToggle( void )
{
int msgack = MSG_D; /* clean pipeline */
msgack = MSG_D; /* record current state of togglebit */
GPIO[0..1] is not used elsewhere.
These pulldowns ar e used for test points and
to keep these signa ls at valid levels.
GPIO1
R1GP IO0
R2
10K Ohm
GND
VCC_+3.3
This linear regulator is used to assure that the +1.8v rail quickly passes
the 0.5v threshold at powerup, thus minimizing power sequencing issues
and making sure that the DSP does not draw excessive power as the
power rails ramp up. This linear regulator is set with Vout=1.22v, so it
is effectively shut off once the switching regulator comes up. Further
testing and characterization of the DSP is require to determine if this
linear regulator is in fact required.
U9
1
IN
2
GND
LTC1761
U1
LTC3406-1.8
4
VIN
1
RUN
Vout/FB
C1
10 uF, X5R, 6.3 Volts
This is a simple switching regulator. It produces
1.8V at >500 mA at about 90% efficency. A simple low drop
out linear regulator would be a cheaper alternative at the
expense of power. A linear regulator would dissapate
about 0.75 watts max, This switching regulator dissapates
about 0.10 watts max.
CS181002-CQ/A12x2 Channels0°C to +70°C144-pin LQFP
CS181012-CQ/A18x8 Channels0°C to +70°C144-pin LQFP
CS181022-CQ/A116x16 Channels0°C to +70°C144-pin LQFP
CS181002-CQZ/A12x2 Channels0 °C to +70°C144-pin LQFP Lead Free
CS181012-CQZ/A18x8 Channels0 °C to +70°C144-pin LQFP Lead Free
CS181022-CQZ/A116x16 Channels0 °C to +70°C144-pin LQFP Lead Free
CS496102-CQZ/A12x2 Channels + DSP0 °C to +70°C144-pin LQFP Lead Free
CS496112-CQZ/A18x8 Channels + DSP0 °C to +70°C144-pin LQFP Lead Free
CS496122-CQZ/A116x16 Channels + DSP0 °C to +70°C144-pin LQFP Lead Free
10.2 Device Part Numbering Scheme
CobraNet Hardware User’s Manual
Ordering Information
CS1810x2 — CQZ/A1
Base Part Number
Channel Count Designator:
0 = 2x2
1 = 8x8
2 = 16x16
ROM Version
(ROM ID)
CS4961x2 — CQZ/A1
Base Part Number
Channel Count Designator:
0 = 2x2
1 = 8x8
2 = 16x16
ROM Version
(ROM ID)
Die Revision
Lead-free Designator:
Z = Lead-free Device Packaging
(not present if device contains lead)
Package Type:
Q = LQFP (144-pin)
Temperature Grade Designator:
C = Commercial (0°C to +70 °C)
Die Revision
Lead-free Designator:
Z = Lead-free Device Packaging
(not present if device contains lead)
Package Type:
Q = LQFP (144-pin)
Temperature Grade Designator:
C = Commercial (0°C to +70 °C)
Note: Go to the Cirrus Logic Internet site at http://www.cirrus.com to find contact information for your local sales representative.
For all product questions and inquiries contact a Cirrus Logic Sales Representative.
o find the one nearest to you go to www.cirrus.com
IMPORTANT NOTICE
irrus Logic, Inc. and its subsidiaries ("Cirrus") believe that the information contained in this document is accurate and reliable. However, the informatio
s subject to change without notice and is provided "AS IS" without warranty of any kind (express or implied). Customers are advised to obtain the lates
ersion of relevant information to verify, before placing orders, that information being relied on is current and complete. All products are sold subject to th
erms and conditions of sale supplied at the time of order acknowledgment, including those pertaining to warranty, indemnification, and limitation of liability
o responsibility is assumed by Cirrus for the use of this information, including use of this information as the basis for manufacture or sale of any items, o
or infringement of patents or other rights of third parties. This document is the property of Cirrus and by furnishing this information, Cirrus grants no license
xpress or implied under any patents, mask work rights, copyrights, trademarks, trade secrets or other intellectual property rights. Cirrus owns the copy
ights associated with the information contained herein and gives consent for copies to be made of the information only for use within your organizatio
ith respect to Cirrus integrated circuits or other products of Cirrus. This consent does not extend to other copying such as copying for general distribution
dvertising or promotional purposes, or for creating any work for resale.
ERTAIN APPLICATIONS USING SEMICONDUCTOR PRODUCTS MAY INVOLVE POTENTIAL RISKS OF DEATH, PERSONAL INJURY, OR SEVER
PROPERTY OR ENVIRONMENTAL DAMAGE ("CRITICAL APPLICATIONS"). CIRRUS PRODUCTS ARE NOT DESIGNED, AUTHORIZED OR WAR
RANTED FOR USE IN AIRCRAFT SYSTEMS, MILITARY APPLICATIONS, PRODUCTS SURGICALLY IMPLANTED INTO THE BODY, AUTOMOTIV
AFETY OR SECURITY DEVICES, LIFE SUPPORT PRODUCTS OR OTHER CRITICAL APPLICATIONS. INCLUSION OF CIRRUS PRODUCTS I
UCH APPLICATIONS IS UNDERSTOOD TO BE FULLY AT THE CUSTOMER'S RISK AND CIRRUS DISCLAIMS AND MAKES NO WARRANTY, EX
PRESS, STATUTORY OR IMPLIED, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR PARTICULAR PURPOSE
ITH REGARD TO ANY CIRRUS PRODUCT THAT IS USED IN SUCH A MANNER. IF THE CUSTOMER OR CUSTOMER'S CUSTOMER USES O
PERMITS THE USE OF CIRRUS PRODUCTS IN CRITICAL APPLICATIONS, CUSTOMER AGREES, BY SUCH USE, TO FULLY INDEMNIFY CIRRUS
ITS OFFICERS, DIRECTORS, EMPLOYEES, DISTRIBUTORS AND OTHER AGENTS FROM ANY AND ALL LIABILITY, INCLUDING ATTORNEYS
FEES AND COSTS, THAT MAY RESULT FROM OR ARISE IN CONNECTION WITH THESE USES.
irrus Logic, Cirrus, and the Cirrus Logic logo designs are trademarks of Cirrus Logic, Inc. All other brand and product names in this document may b
rademarks or service marks of their respective owners.
otorola is a registered trademark of Motorola, Inc.