![](http://datasheet.mmic.net.cn/Maxim-Integrated-Products/DS34S132GN-_datasheet_97089/DS34S132GN-_44.png)
DS34S132 DATA SHEET
19-4750; Rev 1; 07/11
44 of 194
Each HDLC Engine can be programmed to use MSbit or LSbit first transmission (BCDR1.SCSNRE). This function
does not specify which bits of the Timeslot are used (previous paragraphs), but instead specifies whether the MSbit
or LSbit of each HDLC coded byte is transmitted first (the byte order is always MSByte first). For example, if LSbit
transmission and 8-bit coding are selected, then the LSbit of each byte is transmitted first (in the “bit 8” position of
the Timeslot). If instead MSbit transmission and 8-bit coding are selected then the MSbit of each byte is transmitted
first (in “bit 8”). Most T1/E1 applications use MSbit first.
Each HDLC Bundle can be programmed to include a 16-bit, 32-bit or “no” FCS (B.BCDR1SCRXBCSS and
SCTXBCSS).
In the TXP direction the HDLC Engine receives data from a TDM Port and removes the HDLC encoding (HDLC
Flags and HDLC Control Characters). The de-encoded packet data is buffered until a complete packet has been
received. After the HDLC FCS has been verified to be correct, the packet is queued for transmission as the payload
of a TXP HDLC Bundle packet.
TXP HDLC Bundles can optionally include RTP and Control Word Headers (enabled using the TXP Header
Descriptor). For RTP and/or Control Word headers can use Sequence Numbers that are always “zero”, or are
constantly incremented by one with each successive packet (B.BCDR4.SCTXCE and B.BCDR1.SCTXDFSE).
When incremented Sequence Numbers are used the S132 can be programmed to skip or include the Sequence
Number = “zero” value when the Sequence Number reaches roll-over.
In the RXP direction, when the RXP Classifier identifies an error-free packet for an HDLC Bundle, the PW packet
header and FCS are removed and the PW packet payload is stored for later processing by the RXP HDLC Engine.
The HDLC Engine inserts a Flag (Packet Delimiter = 0x7E) in between each successive RXP Packet to identify the
start and stop of each packet. The G.GCR.RXHMFIS register specifies the minimum number of Flags that are
inserted in between 2 HDLC packets where RXHMFIS + 1 = minimum number of flags (e.g. RXHMFIS = 0 for 1
flag). When the HDLC Engine no longer has a packet to forward and the minimum number of flags have been
transmitted the HDLC engine inserts “Inter-frame Fill” into the outgoing HDLC data stream. The Inter-frame Fill
value can be programmed to 0x7E or 0xFF (B.BCDR4.SCLVI).
In the RXP direction the S132 does not provide re-ordering of mis-ordered HDLC packets, so the optional RTP
and/or Control Word Sequence Numbers received in packets for RXP HDLC Bundles are ignored.
The B.BCDR1.PMS register is used to define the largest Ethernet packet that is accepted for an RXP HDLC
Bundle. Packets with a size greater than PMS are discarded.
Special Considerations
The S132 does not provide special handling for CAS Signaling when a T1/E1 Port includes an RXP HDLC Bundle.
If CAS Signaling is enabled for the T1/E1 Port and if the “overwrite CAS on TDAT” is enabled, CAS values will be
written in Timeslot positions assigned to HDLC Bundles. To prevent this, the HDLC 7-bit Sampling format can be
used, or else TSIG can be used to provide the CAS values (disable the “Overwrite CAS on TDAT”). In the TXP
direction, the RSIG value and the SW TXP CAS functions are ignored by TXP HDLC Bundles.
9.2.5.1.1 SAT/CES Engine
The S132 includes 256 SAT/CES Engines, one for each of the 256 possible SAT/CES Bundles.
Figure 9-15. SAT/CES Engine Environment
DS34S132
TXP
TSA
RXP
TSA
TXP SAT/CES Engine
RXP SAT/CES Engine
Buffer
Manager
TDM
Connection
In the RXP direction, B.BCDR1.PMS specifies the expected packet payload size for each RXP Bundle (not
including the optional CAS bytes). For SAT applications, PMS specifies how many bytes; for CES applications, how
many frames. In the TXP direction, the PMS setting determines the amount of data that is included in the payload
of each TXP Bundle packet.