ETC PM73122?

PM
AAL1gator-32 Revision C Device Errata
Released
rsd
ay
,1
9S
ep
tem
be
r,
20
02
10
:40
:44
PM73122
ett
io
nT
hu
AAL1gator-32 Revision C
Device Errata
Do
wn
loa
de
db
yV
inv
ef
uo
fo
liv
32 Link CES AAL1 SAR
Released
Issue 3: July 2002
Proprietary and Confidential to PMC-Sierra, Inc., and for its Customers’ Internal Use
Document ID: PMC-2011072, Issue 3
AAL1gator-32 Revision C Device Errata
Released
PM
Legal Information
:40
:44
Copyright
10
© 2002 PMC-Sierra, Inc.
20
02
The information is proprietary and confidential to PMC-Sierra, Inc., and for its customers’
internal use. In any event, you cannot reproduce any part of this document, in any form, without
the express written consent of PMC-Sierra, Inc.
tem
be
r,
PMC-2011072 (R3)
ep
Disclaimer
nT
hu
rsd
ay
,1
9S
None of the information contained in this document constitutes an express or implied warranty by
PMC-Sierra, Inc. as to the sufficiency, fitness or suitability for a particular purpose of any such
information or the fitness, or suitability for a particular purpose, merchantability, performance,
compatibility with other parts or systems, of any of the products of PMC-Sierra, Inc., or any
portion thereof, referred to in this document. PMC-Sierra, Inc. expressly disclaims all
representations and warranties of any kind regarding the contents or use of the information,
including, but not limited to, express and implied warranties of accuracy, completeness,
merchantability, fitness for a particular use, or non-infringement.
Do
wn
loa
de
db
yV
inv
ef
uo
fo
liv
ett
io
In no event will PMC-Sierra, Inc. be liable for any direct, indirect, special, incidental or
consequential damages, including, but not limited to, lost profits, lost business or lost data
resulting from any use of or reliance upon the information, whether or not PMC-Sierra, Inc. has
been advised of the possibility of such damage.
Proprietary and Confidential to PMC-Sierra, Inc., and for its Customers’ Internal Use
Document ID: PMC-2011072, Issue 3
2
AAL1gator-32 Revision C Device Errata
Released
PM
Contacting PMC-Sierra
10
:40
:44
PMC-Sierra
8555 Baxter Place Burnaby, BC
Canada V5A 4V7
20
02
Tel: (604) 415-6000
Fax: (604) 415-6200
9S
ep
tem
be
r,
Document Information: [email protected]
Corporate Information: [email protected]
Technical Support: [email protected]
Web Site: http://www.pmc-sierra.com
,1
Revision History
Issue Date
Details of Change
1
June 2001
Document created.
2
May 2002
DBCES feature is no longer supported in the PM73122
AAL1gator-32 device. All DBCES & non-DBCES Idle Detection
related errata items are removed.
nT
hu
rsd
ay
Issue No.
Updated Section 3.3 with additional information.
liv
July 2002
fo
3
ett
io
Added erratum “Changes in Ingress Multi-frame Alignment are
not reported in the A1SPn Receive Status FIFOs
(A1SPn_RSTAT_FIFO) via the R_LINE_RESYNC bits” See
Section 3.3
Do
wn
loa
de
db
yV
inv
ef
uo
Added erratum “With LOW_CDV Enabled, Changing a T1/E1
link from Structured Mode (SDF-FR or SDF-MF) to
Unstructured Mode (UDF-ML) Causes Data Corruption” See
Section 3.4.
Proprietary and Confidential to PMC-Sierra, Inc., and for its Customers’ Internal Use
Document ID: PMC-2011072, Issue 3
3
AAL1gator-32 Revision C Device Errata
Released
PM
Table of Contents
:44
Legal Information ................................................................................................................ 2
:40
Contacting PMC-Sierra ....................................................................................................... 3
Introduction.................................................................................................................. 5
Device Identification............................................................................................ 5
1.2
References ......................................................................................................... 6
02
1.1
20
1
10
Table of Contents ................................................................................................................ 4
AAL1gator-32 Revision C Status................................................................................. 7
3
PM73122 AAL1gator-32 Revision C Functional Deficiency List ............................... 10
tem
be
r,
2
Reporting of Misaligned H-MVIP Sync Pulse Can Be Missed in a Certain Condition
.......................................................................................................................... 10
3.2
The First Pointer Received After an Underrun Condition is Not Verified for an Out of
Range Condition ............................................................................................... 10
3.3
Changes in Ingress Multi-frame Alignment are not reported in the A1SPn Receive
Status FIFOs (A1SPn_RSTAT_FIFO) via the R_LINE_RESYNC bits. ............ 11
3.4
With LOW_CDV Enabled, Changing a T1/E1 link from Structured Mode (SDF-FR or
SDF-MF) to Unstructured Mode (UDF-ML) Causes Data Corruption .............. 13
hu
nT
Documentation Deficiency List .................................................................................. 16
Do
wn
loa
de
db
yV
inv
ef
uo
fo
liv
ett
io
4
rsd
ay
,1
9S
ep
3.1
Proprietary and Confidential to PMC-Sierra, Inc., and for its Customers’ Internal Use
Document ID: PMC-2011072, Issue 3
4
AAL1gator-32 Revision C Device Errata
Released
Introduction
PM
1
:40
Section 2 summarizes Revision C status including functionality with respect to
the Revision A errata
·
Section 3 lists the known functional errata for Revision C of the PM73122
Device.
·
Section 4 refers to documentation deficiencies found, if any, in Issue 8 of the
PM73122 AAL1gator-32 Data Sheet (PMC-1981419) and any other document
that is covered by this errata.
tem
be
r,
20
02
10
·
ep
Device Identification
9S
1.1
:44
In this document:
rsd
ay
,1
The information contained in this section relates to Revision C of the PM73122
AAL1gator-32 only. The device revision code is marked at the end of the Wafer
Batch Code on the face of the device.
hu
Figure 1. PM73122 AAL1gator-32 Branding Format.
ef
uo
fo
liv
ett
io
nT
Pin A1
Reference Mark
Do
wn
loa
de
db
yV
inv
PMC Logo
AAL1gator-32
TM
PM73122-Bl
C_______C
Myyww
PHILIPPINES
Proprietary and Confidential to PMC-Sierra, Inc., and for its Customers’ Internal Use
Document ID: PMC-2011072, Issue 3
Part Number
Wafer Batch Code
Assembly Date Code
Country of Origin
5
References
Issue 8 of the PM73122 AAL1gator-32 Data Sheet (PMC-1981419)
Do
wn
loa
de
db
yV
inv
ef
uo
fo
liv
ett
io
nT
hu
rsd
ay
,1
9S
ep
tem
be
r,
20
02
10
:40
·
:44
1.2
PM
AAL1gator-32 Revision C Device Errata
Released
Proprietary and Confidential to PMC-Sierra, Inc., and for its Customers’ Internal Use
Document ID: PMC-2011072, Issue 3
6
AAL1gator-32 Revision C Device Errata
Released
PM
AAL1gator-32 Revision C Status
:44
2
02
10
:40
The PM73122 AAL1gator-32 Revision C is currently production released, but a
notice was sent last year informing customers that we plan to do an in-production
Revision D of the device to rectify deficiencies in the DBCES functionality.
Recently the situation has changed significantly and we no longer plan to perform
this in-production revision.
9S
ep
tem
be
r,
20
The PM73122 AAL1gator-32 Revision C device has been fully qualified,
characterized, and functionally tested to production-grade status. The primary
CES features are fully functional with only minor errata as stated in this
document. Dynamic Bandwidth Circuit Emulation Service (DBCES) functionality
will not be supported in the production release Revision C PM73122 AAL1gator32. Table 1 summarizes all the AAL1gator-32 Revision C errata into 2 groupings.
rsd
ay
,1
1. The first portion of Table 1 summarizes the PM73122 AAL1gator-32 Revision
A deficiencies and the status of these deficiencies in the PM73122
AAL1gator-32 Revision C device.
nT
hu
2. The second grouping summarizes any new deficiencies in the PM73122
AAL1gator-32 Revision C device.
ett
io
Table 1. Summary of PM73122 AAL1gator-32 Revision C Deficiencies.
Comment
fo
uo
inv
ef
Robust SNP Feature
Fixed in
PM73122
Revision C
liv
PM73122 Revision A
Deficiency
yV
Runt Cells Can Cause Cell Errors
a
a
db
when in Multi-Port Mode
Adaptive Clock Recovery Mode -
a
Do
wn
loa
de
Underrun Status Could Be Missed
LOW_CDV Queue Does Not
a
Activate/Deactivate Correctly
RATM_CLK Must be Present even
a
when Debugging Hardware
SRTS Queue Underrun Impacts
a
Other Lines in A1SP
Proprietary and Confidential to PMC-Sierra, Inc., and for its Customers’ Internal Use
Document ID: PMC-2011072, Issue 3
7
Comment
:44
Fixed in
PM73122
Revision C
:40
PM73122 Revision A
Deficiency
PM
AAL1gator-32 Revision C Device Errata
Released
10
a
When RDB/CSB is Asserted 15 ns
Beyond ACKB Certain SBI Interrupt
02
Register Read Cycles Result in
20
Corrupt Data
r,
a
When a Significant Number of
tem
be
Queues are Configured in TDM-toTDM Loopback Cells May be
REF_VAL_ENABLE in E1 SDF-MF
a
9S
a
,1
MVIP-90 Mode is Not Functional
ep
Dropped
rsd
ay
Mode is not Functional
a
UTOPIA Registers - Read Timing
a
Setting HS_GEN_DS3_AIS Does
uo
Underrun Feature is Not Functional
fo
Maintain Bit-Count-Integrity Through
ef
Proper SBI Initialization Sequence
liv
ett
Increment
io
Not Cause T_COND_CELL_CNT to
nT
hu
Violation
a
a
inv
is Required to Prevent CAS from
yV
Corruption
db
Reporting of Misaligned H-MVIP
Sync Pulse Can Be Missed in a
See Section
Do
wn
loa
de
Certain Condition
3.1
Only After an Underrun Condition,
the Value of the First Pointer
See Section
Received is Not Verified for an Out
3.2
of Range Condition or a Dummy
Pointer Value
Erroneous Depth Check Interrupts
a
Occur on Floating (Asynchronous)
Proprietary and Confidential to PMC-Sierra, Inc., and for its Customers’ Internal Use
Document ID: PMC-2011072, Issue 3
8
Fixed in
PM73122
Revision C
Comment
:44
PM73122 Revision A
Deficiency
PM
AAL1gator-32 Revision C Device Errata
Released
10
:40
SBI Tributaries when DC_EN=0
a
C1FP_ADD Pin Not Available on
02
AAL1gator-32 Revision A
20
a
SHIFT_CAS Feature Not Available
tem
be
r,
on AAL1gator-32 Revision A
a
BUSMASTER Feature Not Available
Comment
Changes in Ingress Multi-frame
See Section
ay
,1
9S
PM73122 Revision C
Deficiency
ep
on AAL1gator-32 Revision A or B
3.3
rsd
Alignment are not reported in the
A1SPn Receive Status FIFOs
hu
(A1SPn_RSTAT_FIFO) via the
nT
R_LINE_RESYNC bits.
ett
a T1/E1 link from Structured Mode
io
With LOW_CDV Enabled, Changing
3.4
liv
(SDF-FR or SDF-MF) to
See Section
fo
Unstructured Mode (UDF-ML)
Do
wn
loa
de
db
yV
inv
ef
uo
Causes Data Corruption
Proprietary and Confidential to PMC-Sierra, Inc., and for its Customers’ Internal Use
Document ID: PMC-2011072, Issue 3
9
PM73122 AAL1gator-32 Revision C Functional
Deficiency List
:44
3
PM
AAL1gator-32 Revision C Device Errata
Released
20
02
10
:40
This section lists the known functional deficiencies for Revision C of the
PM73122 AAL1gator-32 as of the publication date of this document. For each
deficiency, the known workaround and the operating constraints, with and without
the workaround, are also described.
Reporting of Misaligned H-MVIP Sync Pulse Can Be Missed in a
Certain Condition
3.1.1
Description
ep
tem
be
r,
3.1
hu
Workaround:
nT
3.1.2
rsd
ay
,1
9S
The AAL1gator-32 automatically resynchronizes when a misaligned sync pulse
(F0B) is encountered on the H-MVIP interface. This functions normally.
However if the F0B pulse advances by exactly one 4 MHz clock cycle (1 chance
in 256) then the reporting of this misaligned sync pulse will not cause the
R_LINE_RESYNC or T_LINE_RESYNC bit to be set in the A1SPn RSTAT_FIFO.
Performance with workaround:
liv
3.1.3
ett
io
The F0B pulse is usually generated by external board logic. Any movement in
this signal could be detected in the external frame generation logic.
Performance without workaround:
ef
3.1.4
uo
fo
All movements of the F0B pulse will be reported by external logic.
Do
wn
loa
de
db
yV
inv
There is a 1 out of 256 chance that a misaligned F0B pulse will not be reported
as such. In all cases, however, the AAL1gator-32 device will automatically
realign with the new F0B position.
3.2
The First Pointer Received After an Underrun Condition is Not
Verified for an Out of Range Condition
3.2.1
Description
After a receive buffer underruns, the AAL1gator-32 RALP automatically accepts
the first structure pointer received as valid without actually checking for validity.
All other structure pointers are checked for validity. An invalid pointer is defined
as Out of Range or a Dummy Pointer Value.
Proprietary and Confidential to PMC-Sierra, Inc., and for its Customers’ Internal Use
Document ID: PMC-2011072, Issue 3
10
AAL1gator-32 Revision C Device Errata
Released
Workaround:
PM
3.2.2
Performance with workaround:
:40
3.2.3
:44
There is no workaround. See Section 3.2.4.
02
Performance without workaround:
20
3.2.4
10
There is no workaround. See Section 3.2.4.
,1
9S
ep
tem
be
r,
If the first AAL1 structure pointer received after an underrun condition is out-ofrange (i.e. > 93) or is a dummy pointer value (0xFF), then this out-of-range
structure pointer will be detected when the next two structure pointers are
received which will result in a pointer reframe to the correct structure. The only
noticeable effect will be a two-pointer delay in achieving synchronization to the
AAL1 structure.
Changes in Ingress Multi-frame Alignment are not reported in
the A1SPn Receive Status FIFOs (A1SPn_RSTAT_FIFO) via the
R_LINE_RESYNC bits.
3.3.1
Description
io
nT
hu
rsd
ay
3.3
yV
inv
ef
uo
fo
liv
ett
Changes in the ingress multiframe alignment, which are not accompanied by
changes in basic frame (125 us) alignment, are not reported in the
R_LINE_RESYNC bits of the A1SPn Receive Status FIFOs. However, these
changes in the ingress multiframe alignment do initiate the ingress frame
resynchronization process, which results in the suppression of generated cells.
Two Line Interface modes are affected: SBI mode and Direct Low Speed mode
with MF_SYNC_MODE=1. It is not possible to disable this ingress multiframe
alignment resynchronization process.
Do
wn
loa
de
db
There are three scenarios to consider:
1) If the ingress multiframe alignment changes, but the ingress basic frame
alignment does not change, the device will resynchronize to the new multiframe
alignment, including suppressing cell generation for 12-32 ms, but will not report
the change of multiframe alignment in the R_LINE_RESYNC bit of the A1SPn
RSTAT_FIFO.
2) If a basic frame slip occurs in the T1/E1 Framer receive elastic store, then the
AAL1gator-32’s ingress basic frame alignment will not change, but its ingress
multiframe alignment will change, which will trigger the device to resynchronize to
the new multiframe alignment, including suppressing cell generation for 12-32
Proprietary and Confidential to PMC-Sierra, Inc., and for its Customers’ Internal Use
Document ID: PMC-2011072, Issue 3
11
AAL1gator-32 Revision C Device Errata
Released
:44
PM
ms; but the device will not report the change of multiframe alignment in the
R_LINE_RESYNC bit of the A1SPn RSTAT_FIFO.
20
02
10
:40
3) If the ingress basic frame alignment changes, then the device will
resynchronize to the new basic frame alignment, including suppressing cell
generation for 12-32 ms, and will report the change of basic frame alignment in
the R_LINE_RESYNC bit of the A1SPn RSTAT_FIFO. This is the proper
operation, but the device will not report the change of multiframe alignment in the
R_LINE_SYNC bit of the AISPn_RSTAT_FIFO.
Workarounds:
9S
3.3.2
ep
tem
be
r,
Internally, the device always detects changes in the ingress multiframe alignment
and handles them properly by activating its frame resynchronization mechanism,
but the device does not report the changes in ingress multiframe alignment in
cases 1 and 2 above.
ay
,1
Workaround # 1: SBI & Direct Low Speed Modes
io
nT
hu
rsd
While the device does not report this event in the A1SPn RSTAT_FIFO, it will still
increment the T_SUPPRESS_CNT counter. Monitoring this counter is an
alternate way of detecting the change in ingress multiframe alignment. In
summary, the T_SUPRESS_CNT increments for the following reasons:
fo
liv
ett
1. Change in T1/E1 basic frame alignment detected. This change of basic frame
alignment is also reported in the R_LINE_RESYNC bit of the
A1SPn_RSTAT_FIFO.
inv
ef
uo
2. Change in T1/E1 multiframe alignment detected. This change of basic frame
alignment is not reported in the R_LINE_RESYNC bit of the
A1SPn_RSTAT_FIFO.
yV
3. The SUPPRESS_XMT bit is set.
Do
wn
loa
de
db
4. In UDF-HS mode, the queue has been added but the TX_ACTIVE bit is not
set.
Workaround # 2: Direct Low Speed Mode Only
LINE_MODE=00: Set MF_SYNC_MODE=0 in registers 0x80200-F. This setting
configures the RL_SYNC input and the TL_SYNC input/output pin for basic
frame (125 us) operation. Multi-frame resynchronizations are not possible in this
mode.
Proprietary and Confidential to PMC-Sierra, Inc., and for its Customers’ Internal Use
Document ID: PMC-2011072, Issue 3
12
AAL1gator-32 Revision C Device Errata
Released
Performance with workaround:
PM
3.3.3
:44
Workaround # 1: SBI & Direct Low Speed Modes
10
:40
The additional task of monitoring the T_SUPPRESS_CNT cell counter has to be
performed in order to detect changes in ingress multiframe alignment.
20
02
Workaround # 2: Direct Low Speed Mode Only
Performance without workaround:
,1
3.3.4
9S
ep
tem
be
r,
Device operates normally, and multiframe resyncs will not occur. If the
application uses T1/E1 CAS, then the T1/E1 framer device must drive the CAS
onto the RL_SIG pin during all 16/24 (E1/T1) frames of the 16 or 24 frame
multiframe.
rsd
ay
Workaround # 1: SBI & Direct Low Speed Modes
nT
hu
The device will not report changes in ingress multiframe alignment via the A1SPn
RSTAT_FIFO, but the device will resynchronize to the new alignment properly.
io
Workaround # 2: Direct Low Speed Mode Only
uo
fo
liv
ett
If MF_SYNC_MODE=1, it is possible that a multiframe resync will occur, and it
will not be reported in the RSTAT_FIFO. In this case, workaround #1 should be
used.
yV
inv
ef
If neither workaround is used, then the user will not know when multiframe
resyncs have occurred, and cells might be suppressed for no apparent reason.
With LOW_CDV Enabled, Changing a T1/E1 link from Structured
Mode (SDF-FR or SDF-MF) to Unstructured Mode (UDF-ML)
Causes Data Corruption
3.4.1
Description
Do
wn
loa
de
db
3.4
The PM73122 AAL1gator-32 device has a feature called LOW_CDV mode which,
when enabled, causes cells to be scheduled every 47 bytes instead of every
frame in Unstructured Data Format (UDF-ML). This mode reduces the Cell Delay
Variation (CDV) introduced by the internal scheduler from 125 us in E1 mode, or
167 us in T1 mode to a nominal 10 us. Note that the LOW_CDV mode only
applies to Unstructured Data Format (UDF-ML).
Proprietary and Confidential to PMC-Sierra, Inc., and for its Customers’ Internal Use
Document ID: PMC-2011072, Issue 3
13
AAL1gator-32 Revision C Device Errata
Released
:44
PM
The LOW_CDV mode in the AAL1gator-32 only controls CDV caused by the cellscheduling algorithm. The other factors impacting the overall CDV are
:40
1. Cell Clumping (+30 us) where multiple cells are scheduled at the same time.
10
2. Queuing Delays (+5 us) at any point in the system such as the Utopia bus.
20
02
3. CDV introduced in the network, which is network dependent. This component
of CDV is not tied to the AAL1gator-32 device.
ep
tem
be
r,
If a T1/E1 link is currently running in Structured mode (SDF-FR or SDF-MF), and
the T1/E1 link is then changed to Unstructured mode (UDF-ML) with
LOW_CDV=1, the AAL1gator-32 generates cells with corrupted T1/E1 payload
data.
Workarounds:
io
3.4.2
nT
hu
rsd
ay
,1
9S
If a T1/E1 link is configured to start (i.e. after A1SP reset) and remain in
Unstructured mode (UDF-ML) with LOW_CDV=1, the AAL1gator-32 operates
normally (generates cells without errors and the low CDV is achieved). Also, the
AAL1gator-32 operates normally in these scenarios 1. With LOW_CDV=0, when
links change between Structured mode and Unstructured mode, 2. Only
Structured mode connections are used (since LOW_CDV mode applies only to
Unstructured mode connections).
ett
Workaround # 1
ef
uo
fo
liv
If it is required to dynamically change a T1/E1 link between Structured and
Unstructured modes and 125 us (E1) or 167 us (T1) of CDV is acceptable, then
set LOW_CDV=0 at all times.
inv
Workaround # 2
Do
wn
loa
de
db
yV
If it is required to reduce CDV to 10 us (nominally), configure the link to start (i.e.
after A1SP reset) and remain in Unstructured Data Format (UDF-ML). Note that
it is possible to change from the Unstructured mode to Structured mode without
data corruption, but not return to Unstructured mode.
Workaround # 3
If it is required to change a T1/E1 link from Structured to Unstructured mode and
reduce CDV to 10 us, then reset the A1SPn before changing modes.
Proprietary and Confidential to PMC-Sierra, Inc., and for its Customers’ Internal Use
Document ID: PMC-2011072, Issue 3
14
AAL1gator-32 Revision C Device Errata
Released
Performance with workaround:
PM
3.4.3
:44
Workaround # 1
10
:40
Operates normally - switching between Structured and Unstructured data formats
is achieved without data corruption. The scheduler generated CDV is at least
125 us (E1) or 167 us (T1) on Unstructured links.
20
02
Workaround # 2
tem
be
r,
Operates normally - reduction in scheduler generated CDV can be achieved to a
nominal 10 us.
Workaround # 3
rsd
Performance without workaround:
hu
3.4.4
ay
,1
9S
ep
As many as seven other T1/E1 links will be reset, along with the link whose mode
was changed. This will cause cell generation to stop on all queues built from the
seven other T1/E1 links, disrupting service on these queues. After the reset, the
device operates normally - low CDV is achieved in Unstructured mode.
Do
wn
loa
de
db
yV
inv
ef
uo
fo
liv
ett
io
nT
Generated cells will contain data errors after changing a T1/E1 link from
Structured mode (SDF-FR or SDF-MF) to Unstructured mode (UDF-ML) with
LOW_CDV=1.
Proprietary and Confidential to PMC-Sierra, Inc., and for its Customers’ Internal Use
Document ID: PMC-2011072, Issue 3
15
AAL1gator-32 Revision C Device Errata
Released
Documentation Deficiency List
PM
4
Do
wn
loa
de
db
yV
inv
ef
uo
fo
liv
ett
io
nT
hu
rsd
ay
,1
9S
ep
tem
be
r,
20
02
10
:40
:44
As of the publication date of this document, there are no known document
deficiencies in Issue 8 of the PM73122 AAL1gator-32 Datasheet
(PMC-1981419).
Proprietary and Confidential to PMC-Sierra, Inc., and for its Customers’ Internal Use
Document ID: PMC-2011072, Issue 3
16