Pin Name | Type | Type | Usage | COB C08 Notes |
---|---|---|---|---|
DTACK_INV/GPIO[0] | In/Out | LVTTL, 6mA | Defines polarity of DTACK_N. If connected to ground, then
| DTACK_INV is pulled down to GND by a 4.7kOhm resistor. The PLX doesn't connect to the DTACK_INV pin. Conclusion: Statically pulled down. So this is probably not related to the issue we are dealing with. |
RW_INV/GPIO[1] | In/Out | LVTTL, 6mA | Defines polarity of RW_N pin when in EBI mode. When On FM2000, this pin is permanently used for this function On FM3000/FM4000, this pin is sampled at reset and can | RW_INV is pulled up to VDD by a 4.7kOhm resistor. The PLX doesn't connect to the RW_INV pin. Conclusion: Statically pulled up. So this is probably not related to the issue we are dealing with. |
IGNORE_PARITY/GPIO[2] | In/Out | LVTTL, 6mA | Setting this pin to VDD33 will disable parity checking on On FM2000, this pin is permanently used for this function. On FFM3000/FM4000, this pin is sampled at reset and can | A.K.A. IGN_PAR
IGN_PAR is pulled down to GND by a 4.7kOhm resistor.
The PLX doesn't connect to the IGN_PAR pin.
Conclusion: Statically pulled down. So this is probably not related to the issue we are dealing with. |
SPI_CLK/GPIO[3] SPI_CS_N/GPIO[4] SPI_MOSI/GPIO[5] SPI_MISO/GPIO[6] | In/Out In/Out In/Out In/Out | LVTTL, 2mA | Used for either SPI or general purpose I/O pins. These pins are used as SPI when the switch retrieves its
Note: The pin SPI_MOSI was previously called SPI_SO in | At bootup, these pins are GPIO inputs by default (see page 70 of FM4000 datasheet). The PLX doesn't connect to the any of these pins. They are accessible via the debug J8 connector. Conclusion: This is only a name change. Pinout has not changed. So this is probably not related to the issue we are dealing with. |
PARITY_EVEN/GPIO[10] | In/Out | LVTTL, 6mA | General purpose I/O pin.
| PARITY_EVEN is pulled up to VDD by a 4.7kOhm resistor. However, the loading options for this resistor is NL (no load). From the data sheet "This pin must be pulled up or pulled down and cannot be left unconnected" Conclusion: This could be causing our problem. We should install the 4.7kOhm resistor and see if it solve our problem.
|
DATA_HOLD/GPIO[14] | In/out | LVTTL, 6mA | General purpose I/O pin.
| DATA_HOLD is pulled up to VDD by a 4.7kOhm resistor. However, the loading options for this resistor is NL (no load).
From the data sheet "It should not be left unconnected"
Conclusion: This could be causing our problem. We should install the 4.7kOhm resistor and see if it solve our problem. |
Multi-chip systems using both Tahoe and Bali devices may, depending on the hardware learning configuration,
require consistent frame hashing across the two generations of switches. For example, in a fat tree with
learning enabled in the spine chips, it is important that (a) the hash function be symmetric and (b) all edge
switches use the same hash function. The following table summarizes the configuration requirements that
are necessary in order to achieve consistent hashing between Bali and Tahoe devices.
Table 25: Summary of Hash Configuration Requirements for Tahoe Compatibility"
Bali Requirement | Tahoe Requirement | Motivation |
---|---|---|
TahoeCompatible == 1 UseSMAC == 0, UseDMAC == 0 | - | Select Tahoe Compatibility mode. |
UseType == 0 | IncludeTypeAndSource == 0 | See note above about differences between Bali & Tahoe in their handling of EtherType. |
Page 351:
Name | Bit | Description | Type | Default |
---|---|---|---|---|
FloodGlort (was GlortFlood) | 15: 0 | Defines the glort to use when flooding. | RW | 0x0 |
XcastGlort (was GlortBroadcast) | 31: 16 | Defines the glort used for broadcast and multicast. Note that multicast in this case is defined as MAC addresses that resolve to a destination mask instead of a glort, which is how multicast is implemented in FM2000, but is deprecated in FM4000 | RW | 0x0 |