- 您現(xiàn)在的位置：買賣IC網(wǎng) > PDF目錄1916 > DS34S132GN+ (Maxim Integrated Products)IC TDM OVER PACKET 676-BGA PDF資料下載
參數(shù)資料
| 型號： | DS34S132GN+ |
| 廠商： | Maxim Integrated Products |
| 文件頁數(shù)： | 159/194頁 |
| 文件大?。?/td> | 0K |
| 描述： | IC TDM OVER PACKET 676-BGA |
| 產(chǎn)品培訓模塊： | Lead (SnPb) Finish for COTS Obsolescence Mitigation Program |
| 標準包裝： | 40 |
| 功能： | TDM-over-Packet（TDMoP） |
| 接口： | TDMoP |
| 電路數(shù)： | 1 |
| 電源電壓： | 1.8V, 3.3V |
| 工作溫度： | -40°C ~ 85°C |
| 安裝類型： | 表面貼裝 |
| 封裝/外殼： | 676-BGA |
| 供應商設(shè)備封裝： | 676-PBGA（27x27） |
| 包裝： | 管件 |
| 其它名稱： | 90-34S13+2N0 |
第1頁第2頁第3頁第4頁第5頁第6頁第7頁第8頁第9頁第10頁第11頁第12頁第13頁第14頁第15頁第16頁第17頁第18頁第19頁第20頁第21頁第22頁第23頁第24頁第25頁第26頁第27頁第28頁第29頁第30頁第31頁第32頁第33頁第34頁第35頁第36頁第37頁第38頁第39頁第40頁第41頁第42頁第43頁第44頁第45頁第46頁第47頁第48頁第49頁第50頁第51頁第52頁第53頁第54頁第55頁第56頁第57頁第58頁第59頁第60頁第61頁第62頁第63頁第64頁第65頁第66頁第67頁第68頁第69頁第70頁第71頁第72頁第73頁第74頁第75頁第76頁第77頁第78頁第79頁第80頁第81頁第82頁第83頁第84頁第85頁第86頁第87頁第88頁第89頁第90頁第91頁第92頁第93頁第94頁第95頁第96頁第97頁第98頁第99頁第100頁第101頁第102頁第103頁第104頁第105頁第106頁第107頁第108頁第109頁第110頁第111頁第112頁第113頁第114頁第115頁第116頁第117頁第118頁第119頁第120頁第121頁第122頁第123頁第124頁第125頁第126頁第127頁第128頁第129頁第130頁第131頁第132頁第133頁第134頁第135頁第136頁第137頁第138頁第139頁第140頁第141頁第142頁第143頁第144頁第145頁第146頁第147頁第148頁第149頁第150頁第151頁第152頁第153頁第154頁第155頁第156頁第157頁第158頁當前第159頁第160頁第161頁第162頁第163頁第164頁第165頁第166頁第167頁第168頁第169頁第170頁第171頁第172頁第173頁第174頁第175頁第176頁第177頁第178頁第179頁第180頁第181頁第182頁第183頁第184頁第185頁第186頁第187頁第188頁第189頁第190頁第191頁第192頁第193頁第194頁
DS34S132 DATA SHEET
19-4750; Rev 1; 07/11
67 of 194
When TXOTSE is enabled, TXOTSO identifies the OAM Timestamp Dword position in the packet. The CPU must
make the initial OAM Timestamp value 0x0000 in the packet stored in the TXP CPU FIFO. The S132 overwrites
that position with the current OAM Timestamp value as the packet is being transmitted at the Ethernet Port.
The S132 uses the ETHCLK signal to generate the TXP OAM Timestamps. The TXP OAM Timestamp Resolution
can be programmed for 1 us or 100 us using G.GCR.OTRS.
The OAM Timestamp can only be positioned on Dword boundaries within the Application Header. Because
Ethernet Headers do not commonly include an integer number of Dwords, the Application Header is commonly
offset by 2 bytes in the Ethernet packet, as depicted in Figure 9-25 (Ethernet packets do not include the “dummy”
bytes depicted in this figure). If the OAM Timestamp position is referenced instead to the beginning of the Ethernet
packet, some example OAM Timestamp byte positions are 46, 50, 54 (etc.), which would equate to TXOTSO
Dword = 11, 12 , 13 (etc.; respectively).
When a TXP CPU Packet uses the IPv4 protocol, the S132 can be programmed to assist with the generation of the
IPv4 Header FCS. The CPU must pre-calculate and include an IP FCS for all of the fields of the IP Header but the
IP Total Length field. The S132 modifies the IP FCS on-the-fly to include the IP Total Length. This allows the CPU
to store a “generic” pre-calculated IP FCS with each stored IP Header in CPU memory. The CPU pre-calculates the
IP FCS for the IP Header beginning with the IP Version field and ending with the IP Destination Address, but using
“0” values in the IP Total Length and IP Header FCS fields. The IPv6 Header does not include an FCS.
When a TXP CPU Packet uses the UDP/IP protocol, the S132 can be programmed to assist with the generation of
the FCS in the UDP Header. The CPU must include a UDP FCS for all but the IP length and UDP length fields. The
CPU pre-calculates the UDP FCS with a Pseudo IP Header that is added to the beginning of the UDP packet
(added only for this UDP FCS calculation) and including the entire UDP packet (from UDP Source Port to the end
of the UDP Payload; per RFC768), but calculates with “0” values in the “UDP Length” field of the Pseudo IP
Header, the ”Length” field of the UDP Header and the “Checksum” field of the UDP Header. The S132 modifies the
pre-calculated UDP FCS on-the-fly to include the lengths. This function can be used when the S132 is programmed
to add a TXP OAM Timestamp.
If the S132 FCS functions are not needed, then the CPU should not identify the packet as IPv4 or UDP (so that the
S132 does not modify the FCS values) and the CPU must include the IP and UDP FCS values for transmission.
All of these functions can be enabled at the same time or in various combinations as identified in Table 9-16. When
the CPU is ready the CPU writes the entire TXP CPU Packet including the pre-calculated FCS values, the “real”
packet length values and TXP OAM Timestamp = “0” (when applicable). For example, when TXOTSO = 1, TXUDP
= 1 and TXIPV4 = 1 (Add TXP OAM Timestamp & Re-calculate UDP FCS & IPv4 FCS), the CPU provides the
entire CPU packet (from Ethernet DA to the end of the Ethernet Payload) including the IP Total Length field (to
indicate the size of the IP packet), the pre-calculated IP FCS, the UDP Length field (to indicate the size of the UDP
packet), the pre-calculated UDP FCS and the “0” value in the TXP OAM Timestamp position. The S132 then
overwrites with the TXP OAM Timestamp and corrects the IP FCS and UDP FCS values.
Table 9-16. Modify FCS and Add TXP OAM Timestamp Functions
Application
TXOTSE TXUDP TXIPV6 TXIPV4
Re-calculate IPv4 FCS to include Length
0
1
For IPv4: Re-calculate UDP FCS & IPv4 FCS to include Length
0
1
0
1
For IPv6 packets: Re-calculate UDP FCS to include Length
0
1
0
Add TXP OAM Timestamp to any protocol (with no FCS modifications)
1
0
For IPv4: Add TXP OAM Timestamp & Re-calculate UDP FCS & IPv4 FCS
1
0
1
For IPv6: Add TXP OAM Timestamp & Re-calculate UDP FCS
1
0
The Write TXP CPU Packet process can be polling based using the EMA.WSR1.WFES status bit or interrupt driven
using the EMA.WSRL1.WFESL (latched status) and EMA.WSRIE1.WFEIE (Interrupt enable) register bits. When
the CPU is ready to Write a TXP CPU Packet into the TXP CPU FIFO, the CPU should begin by verifying that the
TXP CPU FIFO is empty (read the FIFO status at EMA.WSR1.WFES or flush the FIFO with EMA.WCR.TPCWC =
3). The CPU then Writes the Dwords for the packet at EMA.WDR.EMWD. Each successive Write at
EMA.WDR.EMWD fills the next Dword position in the FIFO. When the entire packet has been stored in the TXP
CPU FIFO the CPU must indicate the length of the packet (EMA.WCR.TL), how many packet bytes are included in
the last Dword (EMA.WCR.TLBE) and indicate that the packet should be transferred to the TXP CPU Queue in the
SDRAM (EMA.WCR.TPCWC = 6). When the complete packet has been transferred to the TXP CPU Queue,
EMA.WSR1.WFES will indicate that the FIFO is empty.
相關(guān)PDF資料 |
PDF描述 |
|---|---|
| DS34T102GN+ | IC TDM OVER PACKET 484TEBGA |
| DS3501U+H | IC POT NV 128POS HV 10-USOP |
| DS3502U+ | IC POT DGTL NV 128TAP 10-MSOP |
| DS3503U+ | IC POT DGTL NV 128TAP 10-MSOP |
| DS3897MX | IC TXRX BTL TRAPEZIODAL 20-SOIC |
相關(guān)代理商/技術(shù)參數(shù) |
參數(shù)描述 |
|---|---|
| DS34S132GN+ | 功能描述:通信集成電路 - 若干 32Port TDM-Over-Pack Transport Device RoHS:否 制造商:Maxim Integrated 類型:Transport Devices 封裝 / 箱體:TECSBGA-256 數(shù)據(jù)速率:100 Mbps 電源電壓-最大:1.89 V, 3.465 V 電源電壓-最小:1.71 V, 3.135 V 電源電流:50 mA, 225 mA 最大工作溫度:+ 85 C 最小工作溫度:- 40 C 封裝:Tube |
| DS34S132GNA2+ | 功能描述:通信集成電路 - 若干 32Port TDM-Over-Pack Transport Device RoHS:否 制造商:Maxim Integrated 類型:Transport Devices 封裝 / 箱體:TECSBGA-256 數(shù)據(jù)速率:100 Mbps 電源電壓-最大:1.89 V, 3.465 V 電源電壓-最小:1.71 V, 3.135 V 電源電流:50 mA, 225 mA 最大工作溫度:+ 85 C 最小工作溫度:- 40 C 封裝:Tube |
| DS34T101 | 制造商:MAXIM 制造商全稱:Maxim Integrated Products 功能描述:Single/Dual/Quad/Octal TDM-over-Packet Chip |
| DS34T101_08 | 制造商:MAXIM 制造商全稱:Maxim Integrated Products 功能描述:Single/Dual/Quad/Octal TDM-over-Packet Chip |
| DS34T101_09 | 制造商:MAXIM 制造商全稱:Maxim Integrated Products 功能描述:Single/Dual/Quad/Octal TDM-over-Packet Chip |
發(fā)布緊急采購，3分鐘左右您將得到回復。