TABLE 30 – FREEDM-32A256 THERMAL INFORMATION ............................220
PROPRIETARY AND CONFIDENTIAL vii
RELEASED
DATASHEET
PMC-2010336 ISSUE 1 FRAME ENGINE AND DATA LINK MANAGER 32A256
PM7383 FREEDM-32A256
1 FEATURES
· Single-chip multi-channel HDLC controller with a 50 MHz, 16 bit “Any-PHY”
Packet Interface (APPI) for transfer of packet data using an external
controller.
· Supports up to 256 bi-directional HDLC channels assigned to a maximum of
32 H-MVIP digital telephony buses at 2.048 Mbps per link. The links are
grouped into 4 logical groups of 8 links. A common clock and a type 0 frame
pulse is shared among links in each logical group. The number of time-slots
assigned to an HDLC channel is programmable from 1 to 32.
· Supports up to 256 bi-directional HDLC channels assigned to a maximum of 8
H-MVIP digital telephony buses at 8.192 Mbps per link. The links share a
common clock and a type 0 frame pulse. The number of time-slots assigned
to an HDLC channel is programmable from 1 to 128.
· Supports up to 256 bi-directional HDLC channels assigned to a maximum of
32 channelised T1/J1 or E1 links. The number of time-slots assigned to an
HDLC channel is programmable from 1 to 24 (for T1/J1) and from 1 to 31 (for
E1).
· Supports up to 32 bi-directional HDLC channels each assigned to an
unchannelised arbitrary rate link, subject to a maximum aggregate link clock
rate of 64 MHz in each direction. Channels assigned to links 0 to 2 support a
clock rate of up to 51.84 MHz. Channels assigned to links 3 to 31 support a
clock rate of up to 10 MHz.
· Supports three bi-directional HDLC channels each assigned to an
unchannelised arbitrary rate link of up to 51.84 MHz when SYSCLK is running
at 45 MHz.
· Supports a mix of up to 32 channelised, unchannelised and H-MVIP links,
subject to the constraint of a maximum of 256 channels and a maximum
aggregate link clock rate of 64 MHz in each direction.
· Links configured for channelised T1/J1/E1 or unchannelised operation
support the gapped-clock method for determining time-slots which is
backwards compatible with the FREEDM-8 and FREEDM-32 devices.
· For each channel, the HDLC receiver supports programmable flag sequence
detection, bit de-stuffing and frame check sequence validation. The receiver
PROPRIETARY AND CONFIDENTIAL 1
RELEASED
DATASHEET
PMC-2010336 ISSUE 1 FRAME ENGINE AND DATA LINK MANAGER 32A256
PM7383 FREEDM-32A256
supports the validation of both CRC-CCITT and CRC-32 frame check
sequences.
· For each channel, the receiver checks for packet abort sequences, octet
aligned packet length and for minimum and maximum packet length. The
receiver supports filtering of packets that are larger than a user specified
maximum value.
· Alternatively, for each channel, the receiver supports a transparent mode
where each octet is transferred transparently on the receive APPI. For
channelised links, the octets are aligned with the receive time-slots.
· For each channel, time-slots are selectable to be in 56 kbits/s format or 64
kbits/s clear channel format.
· For each channel, the HDLC transmitter supports programmable flag
sequence generation, bit stuffing and frame check sequence generation. The
transmitter supports the generation of both CRC-CCITT and CRC-32 frame
check sequences. The transmitter also aborts packets under the direction of
the external controller or automatically when the channel underflows.
· Alternatively, for each channel, the transmitter supports a transparent mode
where each octet is inserted transparently from the transmit APPI. For
channelised links, the octets are aligned with the transmit time-slots.
· Supports per-channel configurable APPI burst sizes of up to 256 bytes for
transfers of packet data.Provides 32 Kbytes of on-chip memory for partial
packet buffering in both the transmit and the receive directions. This memory
may be configured to support a variety of different channel configurations
from a single channel with 32 Kbytes of buffering to 256 channels, each with a
minimum of 48 bytes of buffering.
· Provides a 16 bit microprocessor interface for configuration and status
monitoring.
· Provides a standard 5 signal P1149.1 JTAG test port for boundary scan board
test purposes.
· Supports 5 Volt tolerant I/O (except APPI).
· Low power 2.5 Volt 0.25 mm CMOS technology.
PROPRIETARY AND CONFIDENTIAL 2
RELEASED
DATASHEET
PMC-2010336 ISSUE 1 FRAME ENGINE AND DATA LINK MANAGER 32A256
PM7383 FREEDM-32A256
· 329 pin plastic ball grid array (PBGA) package.
PROPRIETARY AND CONFIDENTIAL 3
RELEASED
DATASHEET
PMC-2010336 ISSUE 1 FRAME ENGINE AND DATA LINK MANAGER 32A256
PM7383 FREEDM-32A256
2 APPLICATIONS
· IETF PPP interfaces for routers
· TDM switches
· Frame Relay interfaces for ATM or Frame Relay switches and multiplexers
· FUNI or Frame Relay service inter-working interfaces for ATM switches and
multiplexers.
· Internet/Intranet access equipment.
· Packet-based DSLAM equipment.
· Packet over SONET.
PROPRIETARY AND CONFIDENTIAL 4
RELEASED
DATASHEET
PMC-2010336 ISSUE 1 FRAME ENGINE AND DATA LINK MANAGER 32A256
PM7383 FREEDM-32A256
3 REFERENCES
1. International Organization for Standardization, ISO Standard 3309-1993,
"Information Technology - Telecommunications and information exchange between
systems - High-level data link control (HDLC) procedures - Frame structure",
December 1993.
2. RFC-1662 – “PPP in HDLC-like Framing" Internet Engineering Task Force, July
1994.
3. GO-MVIP, “MVIP-90 Standard”, October 1994, release 1.1.
4. GO-MVIP, “H-MVIP Standard”, January 1997, release 1.1a.
PROPRIETARY AND CONFIDENTIAL 5
RELEASED
DATASHEET
PMC-2010336 ISSUE 1 FRAME ENGINE AND DATA LINK MANAGER 32A256
PMC-2010336 ISSUE 1 FRAME ENGINE AND DATA LINK MANAGER 32A256
PM7383 FREEDM-32A256
5 DESCRIPTION
The PM7383 FREEDM-32A256 Frame Engine and Datalink Manager device is a
monolithic integrated circuit that implements HDLC processing for a maximum of
256 bi-directional channels.
The FREEDM-32A256 may be configured to support H-MVIP, channelised
T1/J1/E1 or unchannelised traffic across 32 physical links.
The FREEDM-32A256 may be configured to interface with H-MVIP digital
telephony buses at 2.048 Mbps. For 2.048 Mbps H-MVIP links, the FREEDM32A256 allows up to 256 bi-directional HDLC channels to be assigned to
individual time-slots within a maximum of 32 H-MVIP links. The channel
assignment supports the concatenation of time-slots (N x DS0) up to a maximum
of 32 concatenated time-slots for each 2.048 Mbps H-MVIP link. Time-slots
assigned to any particular channel need not be contiguous within the H-MVIP
link. When configured for 2.048 Mbps H-MVIP operation, the FREEDM-32A256
partitions the 32 physical links into 4 logical groups of 8 links. Links 0 through 7, 8
through 15, 16 through 23 and 24 through 31 make up the 4 logical groups.
Links in each logical group share a common clock and a common type 0 frame
pulse in each direction.
The FREEDM-32A256 may be configured to interface with H-MVIP digital
telephony buses at 8.192 Mbps. For 8.192 Mbps H-MVIP links, the FREEDM32A256 allows up to 256 bi-directional HDLC channels to be assigned to
individual time-slots within a maximum of 8 H-MVIP links. The channel
assignment supports the concatenation of time-slots (N x DS0) up to a maximum
of 128 concatenated time-slots for each 8.192 H-MVIP link. Time-slots assigned
to any particular channel need not be contiguous within the H-MVIP link. When
configured for 8.192 Mbps H-MVIP operation, the FREEDM-32A256 partitions
the 32 physical links into 8 logical groups of 4 links. Only the first link, which
must be located at physical links numbered 4m (0£m£7), of each logical group
can be configured for 8.192 Mbps operation. The remaining 3 physical links in
the logical group (numbered 4m+1, 4m+2 and 4m+3) are unused. All links
configured for 8.192 Mbps H-MVIP operation will share a common type 0 frame
pulse, a common frame pulse clock and a common data clock.
For channelised T1/J1/E1 links, the FREEDM-32A256 allows up to 256 bidirectional HDLC channels to be assigned to individual time-slots within a
maximum of 32 independently timed T1/J1 or E1 links. The gapped clock
method to determine time-slot positions as per the FREEDM-8 and FREEDM-32
devices is retained. The channel assignment supports the concatenation of time-
PROPRIETARY AND CONFIDENTIAL 7
RELEASED
DATASHEET
PMC-2010336 ISSUE 1 FRAME ENGINE AND DATA LINK MANAGER 32A256
PM7383 FREEDM-32A256
slots (N x DS0) up to a maximum of 24 concatenated time-slots for a T1/J1 link
and 31 concatenated time-slots for an E1 link. Time-slots assigned to any
particular channel need not be contiguous within the T1/J1 or E1 link.
For unchannelised links, the FREEDM-32A256 processes up to 32 bi-directional
HDLC channels within 32 independently timed links. The links can be of arbitrary
frame format. When limited to three unchannelised links, each link can be rated
at up to 51.84 MHz provided SYSCLK is running at 45 MHz. For lower rate
unchannelised links, the FREEDM-32A256 processes up to 32 links each rated
at up to 10 MHz. In this case, the aggregate clock rate of all the links is limited to
64 MHz.
The FREEDM-32A256 supports mixing of up to 32 channelised T1/J1/E1,
unchannelised and H-MVIP links. The total number of channels in each direction
is limited to 256. The aggregate instantaneous clock rate over all 32 possible
links is limited to 64 MHz.
The FREEDM-32A256 provides a low latency “Any-PHY” packet interface (APPI)
to allow an external controller direct access into the 32 Kbyte partial packet
buffers. Up to seven FREEDM-32A256 devices may share a single APPI. For
each of the transmit and receive APPI, the external controller is the master of
each FREEDM-32A256 device sharing the APPI from the point of view of device
selection. The external controller is also the master for channel selection in the
transmit direction. In the receive direction, however, each FREEDM-32A256
device retains control over selection of its respective channels. The transmit and
receive APPI is made up of three groups of functional signals – polling, selection
and data transfer. The polling signals are used by the external controller to
interrogate the status of the transmit and receive 32 Kbyte partial packet buffers.
The selection signals are used by the external controller to select a FREEDM32A256 device, or a channel within a FREEDM-32A256 device, for data transfer.
The data transfer signals provide a means of transferring data across the APPI
between the external controller and a FREEDM-32A256 device.
In the receive direction, polling and selection are done at the device level.
Polling is not decoupled from selection, as the receive address pins serve as
both a device poll address and to select a FREEDM-32A256 device. In response
to a positive poll, the external controller may select that FREEDM-32A256 device
for data transfer. Once selected, the FREEDM-32A256 prepends an in-band
channel address to each partial packet transfer across the receive APPI to
associate the data with a channel. A FREEDM-32A256 must not be selected
after a negative poll response.
PROPRIETARY AND CONFIDENTIAL 8
RELEASED
DATASHEET
PMC-2010336 ISSUE 1 FRAME ENGINE AND DATA LINK MANAGER 32A256
PM7383 FREEDM-32A256
In the transmit direction, polling is done at the channel level. Polling is
completely decoupled from selection. To increase the polling bandwidth, up to
two channels may be polled simultaneously. The polling engine in the external
controller runs independently of other activity on the transmit APPI. In response
to a positive poll, the external controller may commence partial packet data
transfer across the transmit APPI for the successfully polled channel of a
FREEDM-32A256 device. The external controller must prepend an in-band
channel address to each partial packet transfer across the transmit APPI to
associate the data with a channel.
In the receive direction, the FREEDM-32A256 performs channel assignment and
packet extraction and validation. For each provisioned HDLC channel, the
FREEDM-32A256 delineates the packet boundaries using flag sequence
detection, and performs bit de-stuffing. Sharing of opening and closing flags, as
well as sharing of zeros between flags are supported. The resulting packet data
is placed into the internal 32 Kbyte partial packet buffer RAM. The partial packet
buffer acts as a logical FIFO for each of the assigned channels. An external
controller transfers partial packets out of the RAM, across the receive APPI bus,
into host packet memory. The FREEDM-32A256 validates the frame check
sequence for each packet, and verifies that the packet is an integral number of
octets in length and is within a programmable minimum and maximum lengths.
Receive APPI bus latency may cause one or more channels to overflow, in which
case, the packets are aborted. The FREEDM-32A256 reports the status of each
packet on the receive APPI at the end of each packet transfer.
Alternatively, in the receive direction, the FREEDM-32A256 supports a
transparent operating mode. For each provisioned transparent channel, the
FREEDM-32A256 directly transfers the received octets onto the receive APPI
verbatim. If the transparent channel is assigned to a channelised link, then the
octets are aligned to the received time-slots.
In the transmit direction, an external controller provides packets to transmit using
the transmit APPI. For each provisioned HDLC channel, an external controller
transfers partial packets, across the transmit APPI, into the internal 32 Kbyte
transmit partial packet buffer. The partial packets are read out of the partial
packet buffer by the FREEDM-32A256 and a frame check sequence is optionally
calculated and inserted at the end of each packet. Bit stuffing is performed
before being assigned to a particular link. The flag or idle sequence is
automatically inserted when there is no packet data for a particular channel.
Sequential packets are optionally separated by a single flag (combined opening
and closing flag) or up to 128 flags. Zeros between flags are not shared in the
transmit direction although, as stated previously, they are accepted in the receive
direction. Transmit APPI bus latency may cause one or more channels to
PROPRIETARY AND CONFIDENTIAL 9
RELEASED
DATASHEET
PMC-2010336 ISSUE 1 FRAME ENGINE AND DATA LINK MANAGER 32A256
PM7383 FREEDM-32A256
underflow, in which case, the packets are aborted. The FREEDM-32A256
generates an interrupt to notify the host of aborted packets. For normal traffic, an
abort sequence is generated, followed by inter-frame time fill characters (flags or
all-ones bytes) until a new packet is sourced on the transmit APPI. The
FREEDM-32A256 will not attempt to re-transmit aborted packets.
Alternatively, in the transmit direction, the FREEDM-32A256 supports a
transparent operating mode. For each provisioned transparent channel, the
FREEDM-32A256 directly inserts the transmitted octets provided on the transmit
APPI. If the transparent channel is assigned to a channelised link, then the
octets are aligned to the transmitted time-slots. If a channel underflows due to
excessive transmit APPI bus latency, an abort sequence is generated, followed
by inter-frame time fill characters (flags or all-ones bytes) to indicate idle channel.
Data resumes immediately when the FREEDM-32A256 receives new data on the
transmit APPI.
The FREEDM-32A256 is configured, controlled and monitored using the
microprocessor interface. The FREEDM-32A256 is implemented in low power2.5
Volt 0.25 mm CMOS technology. All FREEDM-32A256 I/O except those
belonging to the APPI are 5 volt tolerant. The APPI I/O are 3.3 volt tolerant. The
FREEDM-32A256 is packaged in a 329 pin plastic ball grid array (PBGA)
package.
PROPRIETARY AND CONFIDENTIAL 10
RELEASED
DATASHEET
PM7383 FREEDM-32A256
PMC-2010336 ISSUE 1 FRAME ENGINE AND DATA LINK MANAGER 32A256
6 PIN DIAGRAM
The FREEDM-32A256 is manufactured in a 329 pin plastic ball grid array
package.
The receive line clock signals (RCLK[31:0])
contain the recovered line clock for the 32
independently timed links. Processing of
the receive links are on a priority basis, in
descending order from RCLK[0] to
RCLK[31]. Therefore, the highest rate link
should be connected to RCLK[0] and the
lowest to RCLK[31].
For channelised T1/J1 or E1 links, RCLK[n]
must be gapped during the framing bit (for
T1/J1 interfaces) or during time-slot 0 (for
E1 interfaces) of the RD[n] stream. The
FREEDM-32A256 uses the gapping
information to determine the time-slot
alignment in the receive stream.
RCLK[31:0] is nominally a 50% duty cycle
clock of frequency 1.544 MHz for T1/J1 links
and 2.048 MHz for E1 links.
For unchannelised links, RCLK[n] must be
externally gapped during the bits or timeslots that are not part of the transmission
format payload (i.e. not part of the HDLC
packet). RCLK[2:0] is nominally a 50% duty
cycle clock between 0 and 51.84 MHz.
RCLK[31:3] is nominally a 50% duty cycle
clock between 0 and 10 MHz.
The RCLK[n] inputs are invalid and should
be forced to a low state when their
associated link is configured for operation in
H-MVIP mode.
PROPRIETARY AND CONFIDENTIAL 12
RELEASED
DATASHEET
PMC-2010336 ISSUE 1 FRAME ENGINE AND DATA LINK MANAGER 32A256
The receive data signals (RD[31:0]) contain
the recovered line data for the 32
independently timed links in normal mode
(PMCTEST set low). Processing of the
receive links is on a priority basis, in
descending order from RD[0] to RD[31].
Therefore, the highest rate link should be
connected to RD[0] and the lowest to
RD[31].
For H-MVIP links, RD[n] contains 32/128
time-slots, depending on the H-MVIP data
rate configured (2.048 or 8.192 Mbps).
When configured for 2.048 Mbps H-MVIP
operation, RD[31:24], RD[23:16], RD[15:8]
and RD[7:0] are sampled on every 2
nd
rising
edge of RMVCK[3], RMVCK[2], RMVCK[1]
and RMVCK[0] respectively (at the ¾ point
of the bit interval). When configured for
8.192 Mbps H-MVIP operation, RD[4m]
(0£m£7) are sampled on every 2nd rising
edge of RMV8DC (at the ¾ point of the bit
interval).
For channelised links, RD[n] contains the 24
(T1/J1) or 31 (E1) time-slots that comprise
the channelised link. RCLK[n] must be
gapped during the T1/J1 framing bit position
or the E1 frame alignment signal (time-slot
0). The FREEDM-32A256 uses the location
of the gap to determine the channel
alignment on RD[n]. RD[31:0] are sampled
on the rising edge of the corresponding
RCLK[31:0].
For unchannelised links, RD[n] contains the
HDLC packet data. For certain transmission
formats, RD[n] may contain place holder bits
or time-slots. RCLK[n] must be externally
gapped during the place holder positions in
the RD[n] stream. The FREEDM-32A256
supports a maximum data rate of 10 Mbit/s
PROPRIETARY AND CONFIDENTIAL 13
RELEASED
DATASHEET
PMC-2010336 ISSUE 1 FRAME ENGINE AND DATA LINK MANAGER 32A256
Pin Name Type Pin
Function
PM7383 FREEDM-32A256
No.
on an individual RD[31:3] link and a
maximum data rate of 51.84 Mbit/s on
RD[2:0]. RD[31:0] are sampled on the rising
edge of the corresponding RCLK[31:0].
RMVCK[0]
RMVCK[1]
RMVCK[2]
RMVCK[3]
Input P21
H22
A23
C17
The receive MVIP data clock signals
(RMVCK[3:0]) provide the receive data clock
for the 32 links when configured to operate
in 2.048 Mbps H-MVIP mode.
When configured for 2.048 Mbps H-MVIP
operation, the 32 links are partitioned into 4
groups of 8, and each group of 8 links share
a common data clock. RMVCK[0],
RMVCK[1], RMVCK[2] and RMVCK[3]
sample the data on links RD[7:0], RD[15:8],
RD[23:16] and RD[31:24] respectively.
Each RMVCK[n] is nominally a 50% duty
cycle clock with a frequency of 4.096 MHz.
RMVCK[n] is ignored and should be tied low
when no physical link within the associated
logical group of 8 links is configured for
operation in 2.048 Mbps H-MVIP mode.
PROPRIETARY AND CONFIDENTIAL 14
RELEASED
DATASHEET
PMC-2010336 ISSUE 1 FRAME ENGINE AND DATA LINK MANAGER 32A256
Pin Name Type Pin
Function
PM7383 FREEDM-32A256
No.
RFPB[0]
RFPB[1]
RFPB[2]
RFPB[3]
Input P22
H21
B23
B17
The receive frame pulse signals (RFPB[3:0])
reference the beginning of each frame for
the 32 links when configured for operation in
2.048 Mbps H-MVIP mode.
When configured for 2.048 Mbps H-MVIP
operation, the 32 links are partitioned into 4
groups of 8, and each group of 8 links share
a common frame pulse. RFPB[0], RFPB[1],
RFPB[2] and RFPB[3] reference the
beginning of a frame on links RD[7:0],
RD[15:8], RD[23:16] and RD[31:24]
respectively.
When configured for operation in 2.048
Mbps H-MVIP mode, RFPB[n] is sampled
on the falling edge of RMVCK[n].
Otherwise, RFPB[n] is ignored and should
be tied low.
RFP8B Input R21 The receive frame pulse for 8.192 Mbps H-
MVIP signal (RFP8B) references the
beginning of each frame for links configured
for operation in 8.192 Mbps H-MVIP mode.
RFP8B references the beginning of a frame
for any link configured for 8.192 Mbps HMVIP operation. Only links RD[4m] (0£m£7)
may be configured for 8.192 Mbps H-MVIP
operation.
When one or more links are configured for
8.192 Mbps H-MVIP operation, RFP8B is
sampled on the falling edge of RMV8FPC.
When no links are configured for 8.192
Mbps H-MVIP operation, RFP8B is ignored
and should be tied low.
PROPRIETARY AND CONFIDENTIAL 15
RELEASED
DATASHEET
PMC-2010336 ISSUE 1 FRAME ENGINE AND DATA LINK MANAGER 32A256
Pin Name Type Pin
Function
PM7383 FREEDM-32A256
No.
RMV8FPC Input P23 The receive 8.192 Mbps H-MVIP frame
pulse clock signal (RMV8FPC) provides the
receive frame pulse clock for links
configured for operation in 8.192 Mbps HMVIP mode.
RMV8FPC is used to sample RFP8B.
RMV8FPC is nominally a 50% duty cycle,
clock with a frequency of 4.096 MHz. The
falling edge of RMV8FPC must be aligned
with the falling edge of RMV8DC with no
more than ±10 ns skew.
RMV8FPC is ignored and should be tied low
when no physical links are configured for
operation in 8.192 Mbps H-MVIP mode.
RMV8DC Input R22 The receive 8.192 Mbps H-MVIP data clock
signal (RMV8DC) provides the receive data
clock for links configured to operate in 8.192
Mbps H-MVIP mode.
RMV8DC is used to sample data on RD[4m]
(0£m£7) when link 4m is configured for
8.192 Mbps H-MVIP operation. RMV8DC is
nominally a 50% duty cycle clock with a
frequency of 16.384 MHz.
RMV8DC is ignored and should be tied low
when no physical links are configured for
operation in 8.192 Mbps H-MVIP mode.
RBD Tristate
Output
R23 The receive BERT data signal (RBD)
contains the receive bit error rate test data.
RBD reports the data on the selected one of
the receive data signals (RD[31:0]) and is
updated on the falling edge of RBCLK.
RBD may be tristated by setting the RBEN
bit in the FREEDM-32A256 Master BERT
Control register low. BERT is not supported
for H-MVIP links.
PROPRIETARY AND CONFIDENTIAL 16
RELEASED
DATASHEET
PMC-2010336 ISSUE 1 FRAME ENGINE AND DATA LINK MANAGER 32A256
Pin Name Type Pin
Function
PM7383 FREEDM-32A256
No.
RBCLK Tristate
Output
R20 The receive BERT clock signal (RBCLK)
contains the receive bit error rate test clock.
RBCLK is a buffered version of the selected
one of the receive clock signals
(RCLK[31:0]). RBCLK may be tristated by
setting the RBEN bit in the FREEDM32A256 Master BERT Control register low.
BERT is not supported for H-MVIP links.
PROPRIETARY AND CONFIDENTIAL 17
RELEASED
DATASHEET
PMC-2010336 ISSUE 1 FRAME ENGINE AND DATA LINK MANAGER 32A256
The transmit line clock signals (TCLK[31:0])
contain the transmit clocks for the 32
independently timed links. Processing of
the transmit links is on a priority basis, in
descending order from TCLK[0] to
TCLK[31]. Therefore, the highest rate link
should be connected to TCLK[0] and the
lowest to TCLK[31].
For channelised T1/J1 or E1 links, TCLK[n]
must be gapped during the framing bit (for
T1/J1 interfaces) or during time-slot 0 (for
E1 interfaces) of the TD[n] stream. The
FREEDM-32A256 uses the gapping
information to determine the time-slot
alignment in the transmit stream.
For unchannelised links, TCLK[n] must be
externally gapped during the bits or timeslots that are not part of the transmission
format payload (i.e. not part of the HDLC
packet).
TCLK[2:0] is nominally a 50% duty cycle
clock between 0 and 51.84 MHz.
TCLK[31:3] is nominally a 50% duty cycle
clock between 0 and 10 MHz. Typical
values for TCLK[31:0] include 1.544 MHz
(for T1/J1 links) and 2.048 MHz (for E1
links).
AB6
AA6
AA5
AC4
The TCLK[n] inputs are invalid and should
be tied low when their associated link is
configured for operation in H-MVIP mode.
PROPRIETARY AND CONFIDENTIAL 18
RELEASED
DATASHEET
PMC-2010336 ISSUE 1 FRAME ENGINE AND DATA LINK MANAGER 32A256
The transmit data signals (TD[31:0]) contain
the transmit data for the 32 independently
timed links in normal mode (PMCTEST set
low). Processing of the transmit links is on
a priority basis, in descending order from
TD[0] to TD[31]. Therefore, the highest rate
link should be connected to TD[0] and the
lowest to TD[31].
For H-MVIP links, TD[n] contain 32/128
time-slots, depending on the H-MVIP data
rate configured (2.048 or 8.192 Mbps).
When configured for 2.048 Mbps H-MVIP
operation, TD[31:24], TD[23:16], TD[15:8]
and TD[7:0] are updated on every 2
nd
falling
edge of TMVCK[3], TMVCK[2], TMVCK[1]
and TMVCK[0] respectively. When
configured for 8.192 Mbps H-MVIP
operation, TD[4m] (0£m£7) are updated on
every 2nd falling edge of TMV8DC.
For channelised links, TD[n] contains the 24
(T1/J1) or 31 (E1) time-slots that comprise
the channelised link. TCLK[n] must be
gapped during the T1/J1 framing bit position
or during the E1 frame alignment signal
(time-slot 0). The FREEDM-32A256 uses
the location of the gap to determine the
channel alignment on TD[n]. TD[31:0] are
updated on the falling edge of the
corresponding TCLK[31:0].
For unchannelised links, TD[n] contains the
HDLC packet data. For certain transmission
formats, TD[n] may contain place holder bits
or time-slots. TCLK[n] must be externally
gapped during the place holder positions in
the TD[n] stream. The FREEDM-32A256
supports a maximum data rate of 10 Mbit/s
on an individual TD[31:3] link and a
maximum data rate of 51.84 Mbit/s on
TD[2:0].
PROPRIETARY AND CONFIDENTIAL 19
RELEASED
DATASHEET
PMC-2010336 ISSUE 1 FRAME ENGINE AND DATA LINK MANAGER 32A256
Pin Name Type Pin
Function
PM7383 FREEDM-32A256
No.
TD[31:0] are updated on the falling edge of
the corresponding TCLK[31:0] clock.
TMVCK[0]
TMVCK[1]
TMVCK[2]
TMVCK[3]
Input V21
Y19
AA15
AB9
The transmit MVIP data clock signals
(TMVCK[3:0]) provide the transmit data
clocks for the 32 links when configured to
operate in 2.048 Mbps H-MVIP mode.
When configured for 2.048 Mbps H-MVIP
operation, the 32 links are partitioned into 4
groups of 8, and each group of 8 links share
a common clock. TMVCK[0], TMVCK[1],
TMVCK[2] and TMVCK[3] update the data
on links TD[7:0], TD[15:8], TD[23:16] and
TD[31:24] respectively. Each TMVCK[n] is
nominally a 50% duty cycle clock with a
frequency of 4.096 MHz.
TFPB[0]
TFPB[1]
TFPB[2]
TFPB[3]
Input V23
AA20
AB15
AA9
TMVCK[n] is unused and should be tied low
when no physical links within the associated
group of 8 logical links is configured for
operation in 2.048 Mbps H-MVIP mode.
The transmit frame pulse signals
(TFPB[3:0]) reference the beginning of each
frame when configured for operation in
2.048 Mbps H-MVIP mode.
When configured for 2.048 Mbps H-MVIP
operation, the 32 links are partitioned into 4
groups of 8, and each group of 8 links share
a common frame pulse. TFPB[0], TFPB[1],
TFPB[2] and TFPB[3] reference the
beginning of a frame on links TD[7:0],
TD[15:8], TD[23:16] and TD[31:24]
respectively.
When configured for operation in 2.048
Mbps H-MVIP mode, TFPB[n] is sampled on
the falling edge of TMVCK[n]. Otherwise,
TFPB[n] is ignored and should be tied low.
PROPRIETARY AND CONFIDENTIAL 20
RELEASED
DATASHEET
PMC-2010336 ISSUE 1 FRAME ENGINE AND DATA LINK MANAGER 32A256
Pin Name Type Pin
Function
PM7383 FREEDM-32A256
No.
TFP8B Input U23 The transmit frame pulse for 8.192 Mbps H-
MVIP signal (TFP8B) references the
beginning of each frame for links configured
to operate in 8.192 Mbps H-MVIP mode.
TFP8B references the beginning of a frame
for any link configured for 8.192 Mbps HMVIP operation. Only links 4m (0£m£7)
may be configured for 8.192 Mbps H-MVIP
operation.
When one or more links are configured for
8.192 Mbps H-MVIP operation, TFP8B is
sampled on the falling edge of TMV8FPC.
When no links are configured for 8.192
Mbps H-MVIP operation, TFPB[n] is ignored
and should be tied low.
TMV8FPC Input V22 The transmit 8.192 Mbps H-MVIP frame
pulse clock signal (TMV8FPC) provides the
transmit frame pulse clock for links
configured for operation in 8.192 Mbps HMVIP mode.
TMV8FPC is used to sample TFP8B.
TMV8FPC is nominally a 50% duty cycle,
clock with a frequency of 4.096 MHz. The
falling edge of TMV8FPC must be aligned
with the falling edge of TMV8DC with no
more than ±10 ns skew.
TMV8FPC[n] is ignored and should be tied
low when no physical links are configured
for operation in 8.192 Mbps H-MVIP mode.
PROPRIETARY AND CONFIDENTIAL 21
RELEASED
DATASHEET
PMC-2010336 ISSUE 1 FRAME ENGINE AND DATA LINK MANAGER 32A256
Pin Name Type Pin
Function
PM7383 FREEDM-32A256
No.
TMV8DC Input U20 The transmit 8.192 Mbps H-MVIP data clock
signal (TMV8DC) provides the transmit data
clock for links configured to operate in 8.192
Mbps H-MVIP mode.
TMV8DC is used to update data on TD[4m]
(0£m£7) when link 4m is configured for
8.192 Mbps H-MVIP operation. TMV8DC is
nominally a 50% duty cycle clock with a
frequency of 16.384 MHz.
TMV8DC is unused and should be tied low
when no physical links are configured for
operation in 8.192 Mbps H-MVIP mode.
TBD Input Y5 The transmit BERT data signal (TBD)
contains the transmit bit error rate test data.
When the TBERTEN bit in the BERT Control
register is set high, the data on TBD is
transmitted on the selected one of the
transmit data signals (TD[31:0]). TBD is
sampled on the rising edge of TBCLK.
BERT is not supported for H-MVIP links.
TBCLK Tristate
Output
AA4 The transmit BERT clock signal (TBCLK)
contains the transmit bit error rate test clock.
TBCLK is a buffered version of the selected
one of the transmit clock signals
(TCLK[31:0]). TBCLK may be tristated by
setting the TBEN bit in the FREEDM32A256 Master BERT Control register low.
BERT is not supported for H-MVIP links.
PROPRIETARY AND CONFIDENTIAL 22
Loading...
+ 201 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.