M28529G-12 Mindspeed Technologies, M28529G-12 Datasheet - Page 298

• Manufacturer Part Number: M28529G-12
• Description: ATM IMA 8.192Mbps 1.8V/3.3V 484-Pin BGA
• Manufacturer: Mindspeed Technologies

Specifications of M28529G-12

• Package: 484BGA
• Utopia Type: Level 2
• Typical Operating Supply Voltage: 1.8|3.3 V
• Minimum Operating Supply Voltage: 1.71|3.135 V
• Maximum Operating Supply Voltage: 1.89|3.465 V
• Maximum Output Rate: 8.192 Mbps

Table 4-6.
28529-DSH-001-K
IIO.10
IIO.11
IIO.12
IIO.13
IIO.14
IIO.15
IIO.16
IIO.17
IIO.18
IIO.19
IIO.20
IIO.21
Item
IIO.4
IIO.5
IIO.6
IIO.7
IIO.8
IIO.9
sub-states?
the events listed in Table 8 on page 52?
the Tx LSM, although the order of treatment is implementation specific if
these events appear simultaneously?
IMA unit via the ICP cells?
Does the implementation perform the actions corresponding to the Rx LSM
sub-states?
the events listed in Table 9 on page 53?
Does the implementation treat sequentially the incoming events that trigger
the Rx LSM, although the order of treatment is implementation specific if
these events appear simultaneously?
Does the implementation report any change of the Tx and Rx LSMs within
the next 2*M (where M is the M used by the IMA transmitter) cells on that
link over the “Tx State” and “Rx State” fields of the Link Information field
(refer to Table 3 on page 32)?
Does the implementation use one of the Unusable encodings when reporting
the Unusable state?
Does the implementation use “Inhibited”, “Failed”, “Fault” or “Mis-
connected” as a reason when reporting the Unusable state?
Does the implementation re-evaluate the TX and Rx LSMs state upon each
incoming ICP cell with new state indication?
Does the implementation allow the valid combinations of Tx and Rx LSM
states and disallow the invalid combinations when running in the
Symmetrical Configuration and Operation mode?
Does the implementation allow the valid combinations of Tx and Rx LSM
states and disallow the invalid combinations when running in the
Symmetrical Configuration and Asymmetrical Operation mode?
Does the implementation allow all combinations of Tx and Rx LSM states
when running in the Asymmetrical Configuration and Operation mode?
Does the implementation report any GSM states, with the exception of the
Not Configured state, to the FE group using the corresponding value defined
in the “Group Status and Control” field?
Does the implementation always send over each link the same value in the
“Group Status and Control” field for at least 2 consecutive IMA frames?
Does the implementation validate the Rx OAM Label, Rx M, and Rx IMA ID
over at least one link before moving into the Start-up-Ack state?
Does the implementation use the validated Rx OAM Label, Rx M, and Rx
IMA ID to achieve IMA frame synchronization as defined in Section 11 on
page 68?
Does the implementation perform the actions corresponding to the Tx LSM
Does the implementation update the Tx LSM according the occurrence of
Does the implementation treat sequentially the incoming events that trigger
Does the implementation signal the current state of the Rx LSM to the FE
Does the implementation update the Rx LSM according the occurrence of
IMA Interface Operation (IIO) Functions (2 of 4)
Protocol feature
Mindspeed Proprietary and Confidential
Mindspeed Technologies
®
Cond. for
Status
Status
Pred.
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
O
(R-78)
(R-78)
(R-78)
(R-78)
(R-78)
(R-78)
(R-78)
(R-79)
(R-80)
(O-14)
(R-81)
(R-82)
(R-82)
(R-82)
(R-83)
(R-84)
(R-85)
(R-86)
Ref.
Yes X No__
Yes X No__
Yes X No__
Yes X No__
Yes X No__
Yes X No__
Yes X No__
Yes X No__
Yes X No__
Yes X No__
Yes X No__
Yes X No__
Yes X No__
Yes X No__
Yes X No__
Yes X No__
Yes X No__
Yes X No__
Appendices
Support
283