Digi Errata NS9750B-A1 User manual

www.digi.com
1
NS9750B-A1
Errata
90000738, Rev F
Release date: September 2006
Use in conjunction with:
NS9750B-A1 Hardware
Reference, Rev. B
Part number: 90000737_B
Released: March 2006
Technical Support:
Phone: 1.877.912.3444
Web: [email protected]
• SPI slave data output high impedance control
•UARTgaptimer
• UART CTS-related transmit data errors
•USBOVRandUSBPWR
• PCI arbiter senses false request
• Ethernet receive data FIFO overflow (Ethernet
receiver stall)
• 1284 nibble ID negotiation
• Linked Ethernet TX buffer descriptors do not work with
late collisions

2
NS9750B-A1 Errata, Rev. F 09/2006
SPI slave data output high impedance control
SPI slave data output high impedance control
There is a problem that occurs in slave mode when there are other slaves on the SPI bus. When the
slave select signal is de-asserted, the data output pin fails to go into a high impedance state and
interferes with any other slave that is trying to drive the data signal.
Workaround: Do this for each SPI port. Externally buffer the data_out signal with a tri-state buffer
and connect the select signal to the active low tri-state control pin. There should be a pullup
resistor on the output of the buffer to prevent floating when no slaves are selected.
Example:
UART gap timer
The start bit of a new character may not be detected when the character or buffer gap timer
expires. Framing, parity, or data corruption occur when a start bit is missed.
Software workaround: Three conditions have been identified for this erratum:
Applications with a steady stream of receive data are not affected if the buffer gap timer is
disabled.
Applications where the gap between characters is fixed and the character gap timer period is
configured to be less than the fixed period. The buffer gap timer must be disabled.
Applications that have higher-level protocol error detection and recovery such as PPP can use
both the buffer and character gap timers.
Hardware workaround:
Note: The hardware workaround requires that you have installed the appropriate software patch
found in the NETOS SW Toolkit (on the Web).
A hardware workaround eliminates the possibility of receiving a start bit when a character or buffer
gap timer is expiring. The workaround drives the baud clock off-chip and synchronizes the incoming
data with this clock. As a result, the buffer and character gap timers and the next start bit have a
fixed and known relationship with each other.
slave_select_n
( from ASIC ) dout dout ( to bus )

www.digi.com
3
UART CTS-related transmit data errors
Limitations:
The TMODE bit in the Bit-rate register must be cleared.
Baud rates are limited to those available in x16 mode
Baud rates with a divisor of 0 are not possible for all CPU frequencies. This translates to a
maximum baud rate of 460k in x16 mode.
Baud rates with a divisor of 1 are not possible for CPU frequencies below 147MHz. This
translates to a baud rate of 230k in x16 mode.
The buffer and character gaps must be an even multiple of the sample clock period. For a
96000bps UART in x16 UART mode, the equation is:
Timer increment = ((1/9600) / 16) x 2 = 13.020us
One GPIO per UART is required to output the baud clock. The baud clock can be output on the
RI pin on each UART. This function is controlled by the RXEXT bit (27) in each Serial Bit-rate
register.
If multiple UARTs are running at the same baud rate, one baud clock can be used for the multiple
UARTs.
UART CTS-related transmit data errors
A problem occurs with the CTS flow control signal is de-asserted during the BCLK that begins
processing a new character. This problem causes the previous character to be resent instead of
getting the next character from the transmit FIFO.
Software workarounds:
Modify these bits in Serial Channel Control register A:
–Set the CTSTX bit (bit 23) to 0 to disable hardware-controlled CTSTX.
–Set the ERXCTS bit (bit 4) to enable the software CTS signal change interrupt.
–Update the serial transmit ISR to handle the CTS signal change.
RXD[n]
Add R1 instead of U1 to bypass this circuit
RXCLK[n] 3.3V 3.3V
RXD_mod[n]
74LV74
U1A
DQ
CLK
Q
PRCL
UART GAP Timer
workaround
RESET
RXD[n]
74LV74
U1B
DQ
CLK
Q
PRCL
0 OHMR1

4
NS9750B-A1 Errata, Rev. F 09/2006
USB OVR and USB PWR
The maximum bytes in each DMA buffer descriptor is limited to 16 bytes.
The maximum skid rate can be up to 16 characters.
The serial monitor thread is changed to handle the missing CTS interrupt.
See the appropriate (6.0 or 6.3) NET+OS SW toolkit (on the Web) for the required software
workarounds.
Hardware workaround: For each UART, externally clock the CTS signal with the Txd_n signal to
guarantee that CTS will not be seen de-asserting at the start of a character.
USB OVR and USB PWR
The USB OVR (over current) input on gpio[16] is not shown in the GPIO MUX pinout tables. The
polarity of this signal cannot be changed. It is true high, normally requiring an external inverter
and noise filter to prevent false indications of over current.
This table shows the corrections to GPIO[16] in the pinout table:
Updates are required to the BSP to change gpio[16] from mode 00 to mode 02. Timer 11 is
disabled, allowing USB OVR to be recognized by the USP IP. Even though Timer 11 is disabled, the
Timer clock select field must be set to 111-External pulse event to set GPIO[16] to an input.
If you are using USB Host, GPIO[16] must be reserved for the USB OVR function.
CTS[n]
74LV74
DQ
CLK
Q
PRCL
TXD[n]
UART CTSFlow
Control workaround
R2 0 OHM
CTS[n]
U2
RESET
TXD[n]
Add R2 instead of U2 to bypass this circuit
CTS_mod[n]
Signal Mode Description
00
01
02
03(default)
Reservedoutput
1284nFault(peripheraldriver,duplicate)
Timer11 (duplicate),USB OVR
GPIO 16
gpio[16]

www.digi.com
5
PCI arbiter senses false request
The USB PWR (power) control output requires additional external logic and GPIO to prevent USB
power from being enabled from the time power is valid until the code has set the USB registers and
selected gpio[17] to mode 00. The polarity of USB PWR is true high. Pulling down GPIO[17] to
disable the USB power control changes the CPU bus speed because this pin is also bootstrap — ND4.
Designs that add the additional GPIO to prevent USB power-on during startup would require the
BSP, as a final step, to set this GPIO to output a 1.
This figure shows a recommended logic workaround:
PCI arbiter senses false request
For complete information and workarounds for this issue, see the related application note at
http://www.digi.com/support/productdetl.jsp.
Ethernet receive data FIFO overflow (Ethernet receiver stall)
The Ethernet receiver intermittently locks up in 100 Mbps half-duplex applications due to an
overflow in the RX data FIFO.
Workaround: Reset the RX Ethernet logic when an RX_OVFL_DATA interrupt is generated. Go to
http://www.digi.com/support/productdetl.jsp to read the related application note for
instructions for doing this.
1284 nibble ID negotiation problem
The NS9750B-A1 should set the Xflag (Select) line low at event #6 (see the IEEE 1284 standards
specification). Instead, this signal is being driven high. The host uses this signal to determine
whether the requested mode is supported. Therefore, the host incorrectly concludes that the
NS9775 does not support nibble ID mode.
Workaround: None.
O
USB Power
Controller
2.4K
NS97xx
INV
GPIO[xy]
Rpull-up
RC filter = 500uS
Cfilter
Rfilter
NAND2
ENABLE_n
OVERCUR_n
3.3V
This circuit is required to prevent USB
power being enabled before code has set
GPIO[17] to mode 00. Pulling down
GPIO[17] effects CPU speed.
USB_PWR,
GPIO[17],
BOOTST_ND4
USB_OVR
GPIO[16]
O

6
NS9750B-A1 Errata, Rev. F 09/2006
Linked Ethernet TX buffer descriptors don’t work with late collisions
Linked Ethernet TX buffer descriptors don’t work with late collisions
If the Ethernet transmitter locks up when a late collision occurs while transmitting an Ethernet
package consisting of multiple linked buffer descriptors, one of these situations occurs:
The WRAP bit in the last entry of the embedded TXBD RAM is cleared.
The WRAP bit is set in both the first and last entries in the TXBD RAM.
Workaround: Software keeps a shadow copy of the TXBD RAM flags in main memory, and updates
the copy only when the CPU accesses the TXBD RAM. When the CPU receives an Ethernet TX ERROR
interrupt of any kind (that is, the TXERR bit is set in the Ethernet Interrupt Status register), which
includes a late collision, the CPU takes this action:
Reads the TX Error Buffer Descriptor Pointer register (TXERBD), which, in the case of the logic
error, points to the location that has the bad WRAP bit.
Copies the flags from the shadow TXBD RAM to the real TXBD RAM starting at the location
pointed to by the TXERBD and ending at the first shadow location that has the LAST bit set,
indicating the last buffer descriptor for the packet. This corrects the WRAP bit errors.


Digi International
11001 Bren Road East
Minnetonka, MN 55343 U.S.A.
United States: +1 877 912-3444
Other locations: +1 952 912-3444
Fax: +1 952 912-4960
www.digi.com/support
www.digi.com
Online problem reporting:
www.digi.com/support/eservice/eservicelogin.jsp
© Digi International Inc. 2005-2006 All rights reserved.
Digi and Digi International are trademarks or registered trademarks of Digi International Inc. in the United
States and other countries worldwide. NET+, NET+Works, and NET+OS are trademarks or registered
trademarks of Digi International Inc. in the United States and other countries worldwide. All other
trademarks are the property of their respective owners.
Information in this manual is subject to change without notice and does not represent a commitment on the
part of Digi International.
Digi provides this document “as is,” without warranty of any kind, either expressed or implied, including, but
not limited to, the implied warranties of fitness or merchantability for a particular purpose. Digi may make
improvements and/or changes in this manual or in the product(s) and/or the program(s) described in this
manual at any time.
This product could include technical inaccuracies or typographical errors. Changes are made periodically to
the information herein; these changes may be incorporated in new editions of the publication.
Table of contents
Other Digi Computer Hardware manuals

Digi
Digi Digi One EM Quick user guide

Digi
Digi NS9215 Application guide

Digi
Digi ConnectPort X3 H User manual

Digi
Digi Edgeport/1i User manual

Digi
Digi Digi JumpStart Kit User manual

Digi
Digi NS7520B-1-C36 Application guide

Digi
Digi ConnectCore 9P 9215 User manual

Digi
Digi ConnectCore 8X Quick user guide

Digi
Digi DataFire GO! PRO User manual

Digi
Digi Rabbit 5000 User manual
Popular Computer Hardware manuals by other brands

EMC2
EMC2 VNX Series Hardware Information Guide

Panasonic
Panasonic DV0PM20105 Operation manual

Mitsubishi Electric
Mitsubishi Electric Q81BD-J61BT11 user manual

Gigabyte
Gigabyte B660M DS3H AX DDR4 user manual

Raidon
Raidon iT2300 Quick installation guide

National Instruments
National Instruments PXI-8186 user manual

















