| Electronic Components Datasheet Search |
|
DP83924 Datasheet(PDF) 29 Page - National Semiconductor (TI) |
|
|
|
|||||||||||||||||||||||||||||
DP83924 Datasheet(HTML) 29 Page - National Semiconductor (TI) |
|
29 / 42 page ![]() 29 www.national.com 6.0 User Information 6.1 CRS Assertion Connected to a 100M Node Issue: CRS may be asserted when connected to a non-AutoNe- gotiating, 100Mb/s node and the DP83924B is also in the non-AutoNegotiating mode. The 4TPHY could also estab- lish link as a result of 100 Mb/s scrambled IDLEs. The LED could also indicate receive activity. (All of the above are IEEE 802.3 compliant and included in the User Info Sheet for clarification purposes.) Description: When connected to a 100M node that is configured into non Auto Negotiation mode, the scrambled Idles transmit- ted by this 100M node may cause the DP83924B to assert CRS. Since 100 Mbps scrambled idles can have waveforms passing the smart squelch levels and frequency require- ments, this is to be expected. Also IEEE 802.3 Clause 14, Figure 14.6 shows that it’s permissible to indicate “link test pass” based on receive data activity even in the absence of link pulses. In Auto-negotiation mode, activity on the receive line will not cause “link test pass” state to be entered. Compatibility: This behavior is consistent with the DP83924A, which is a non-Auto Negotiating device. Impact: Problem can be resolved by enabling Auto-Negotiation via the BMCSR or through the strap option during reset. Die Revision Plan: The non Auto-negotiation behavior of the 4TPHY is consis- tent with IEEE 802.3 and doesn’t require any fix. 6.2 Link Fail Inhibit Timer Problem: The DP83924B's Link Fail Inhibit Timer within the Auto_Negotiation block can time-out after 650ms rather than the 750ms minimum specified in 802.3u, Clause 28. (Based on simulation results) Description: The Link Fail Inhibit Timer, which monitors whether a valid link has been established at the end of either an FLP exchanger a parallel detection, may expire after 650 ms in DP83924B. Impact: There is no current solution to this problem, however, there should be no decrease in performance due to this anom- aly.The 10 Mb negotiation will resolve within ~250 ms max for a parallel detection, and within ~440 ms max based on FLP detection. In both cases, it is well within the 650 ms allowed by the Link Fail Inhibit Timer. Die Revision Plan: There are currently no plans. Although the DP83924B does not meet the 750 ms minimum specified in IEEE 802.3u, this should not affect functionality in an otherwise compli- ant system environment. 6.3 Lockup during duplex mode change: Problem: The 4TPHY can lock up during change of the duplex mode from half duplex to full duplex. Description: If a port is transmitting and receiving while the duplex mode of that port is changed from half duplex to full duplex then the receive logic of the port will lock up. (The duplex mode can be changed by writing to the port register or by direct control of the duplex mode by using the FDX_n pins while in enhanced full duplex mode. In either method the lockup problem is seen) While locked up, CRS will stay high even if the cable is disconnected. A hard reset will resume regu- lar operation. Impact: The users should disable transmit before changing the duplex status. Die Revision Plan: None. 6.4 Start of TP_IDL, 45 Bit Times to 50 mV: Problem: TP_IDL output should settle to a value between ±50 mV within 45 BT of the last bit transmitted. The level is typically +/- 80 mV. Description: The IEEE 802.3 specification defines that the output wave- form should settle to +50mV, 45 bit times after the last low to high transition of a transmitted packet. This parameter is typically +/- 80mV. Impact: We expect no customer impact. Die Revision Plan: None. 6.5 Polarity detection: Issue: The 924B polarity detection is based onNLPs only. It will not detect polarity inversion based on packet data. Description: The 4TPHY will automatically detect and correct wiring polarity reversal on the UTP receive pins. To be able to do this it has to see seven consecutive NLPs with the wrong polarity. It would not detect polarity errors based on data. Impact: If the link partner starts sending packets before the 4TPHY receives 7 consecutive inverted polarity NLPs then the 4TPHY will not be able to detect/correct polarity errors until there is a gap between packets such that 7 consecutive NLPs are received. Die Revision Plan: None. |
|
Link URL |
| Does ALLDATASHEET help your business so far? [ DONATE ] |
About Alldatasheet | Advertisement | Contact us | Privacy Policy | Link to Datasheet | Link Exchange | Manufacturer List All Rights Reserved©Alldatasheet.com |
| Russian : Alldatasheetru.com | Korean : Alldatasheet.co.kr | Spanish : Alldatasheet.es | French : Alldatasheet.fr | Italian : Alldatasheetit.com Portuguese : Alldatasheetpt.com | Polish : Alldatasheet.pl | Vietnamese : Alldatasheet.vn Indian : Alldatasheet.in | Mexican : Alldatasheet.com.mx | British : Alldatasheet.co.uk | New Zealand : Alldatasheet.co.nz |
|
Family Site : ic2ic.com |
icmetro.com |