- 您现在的位置：买卖IC网 > PDF目录1916 > DS34S132GN+ (Maxim Integrated Products)IC TDM OVER PACKET 676-BGA PDF资料下载
参数资料
| 型号： | DS34S132GN+ |
| 厂商： | Maxim Integrated Products |
| 文件页数： | 159/194页 |
| 文件大小： | 0K |
| 描述： | IC TDM OVER PACKET 676-BGA |
| 产品培训模块： | Lead (SnPb) Finish for COTS Obsolescence Mitigation Program |
| 标准包装： | 40 |
| 功能： | TDM-over-Packet（TDMoP） |
| 接口： | TDMoP |
| 电路数： | 1 |
| 电源电压： | 1.8V, 3.3V |
| 工作温度： | -40°C ~ 85°C |
| 安装类型： | 表面贴装 |
| 封装/外壳： | 676-BGA |
| 供应商设备封装： | 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.
相关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 |
相关代理商/技术参数 |
参数描述 |
|---|---|
| DS34S132GN+ | 功能描述:通信集成电路 - 若干 32Port TDM-Over-Pack Transport Device RoHS:否 制造商:Maxim Integrated 类型:Transport Devices 封装 / 箱体:TECSBGA-256 数据速率: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 数据速率: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 |
发布紧急采购，3分钟左右您将得到回复。