NSLU2-Linux
view · edit · print · history

Info.GPIOConnections History

Hide minor edits - Show changes to markup

January 02, 2008, at 01:30 AM by rwhitby --
Deleted lines 2-9:

GPIO(8) should actually be assigned as INTD on the PCI bus but it's been set as an output instead of tristate. It is connected to the power circuitry and is used to power down the NSLU2.

GPIO(15) is GPIO_CLK1 and is running at 33MHz. It is required to access the Flash memory on the expansion bus. After power-up the IXP420 is configured to provide a clock on this GPIO pin. If the clock output on this pin is disabled, access to the Flash is impossible.

The USB 2.0 controller can be configured to only use INTA which would free up GPIO(9) and GPIO(10). If the USB 2.0 controller tristates the INTB0 and INTC0 pins when they are disabled then we may reuse the GPIOs without cutting traces. If the USB 2.0 controller however actively pulls the pin high or low even when disabled then we must cut traces to allow reuse of the GPIOs.

A much safer and easier option to add extra IO pins is to use a I²C IO extender. Please see PinoutOfI2CPort for more details on the I²C connection.

Added lines 22-29:

GPIO(8) should actually be assigned as INTD on the PCI bus but it's been set as an output instead of tristate. It is connected to the power circuitry and is used to power down the NSLU2.

GPIO(15) is GPIO_CLK1 and is running at 33MHz. It is required to access the Flash memory on the expansion bus. After power-up the IXP420 is configured to provide a clock on this GPIO pin. If the clock output on this pin is disabled, access to the Flash is impossible.

The USB 2.0 controller can be configured to only use INTA which would free up GPIO(9) and GPIO(10). If the USB 2.0 controller tristates the INTB0 and INTC0 pins when they are disabled then we may reuse the GPIOs without cutting traces. If the USB 2.0 controller however actively pulls the pin high or low even when disabled then we must cut traces to allow reuse of the GPIOs.

A much safer and easier option to add extra IO pins is to use a I²C IO extender. Please see PinoutOfI2CPort for more details on the I²C connection.

Restore
October 01, 2006, at 07:13 PM by Petr Jakes -- corrected the name for the RTC (Real Time Clock). Not XC1205 but X1205
Changed lines 19-20 from:
GPIO[6]V21I²C SCLXC1205 RTC - SCL - Pin 6Output
GPIO[7]AA26I²C SDAXC1205 RTC - SDA - Pin 5Tristate
to:
GPIO[6]V21I²C SCLX1205 RTC - SCL - Pin 6Output
GPIO[7]AA26I²C SDAX1205 RTC - SDA - Pin 5Tristate
Restore
June 29, 2005, at 07:32 AM by ep1220 -- GPIO14 == pin U22 (was U21 here before)
Changed line 27 from:
GPIO[14]U21PCI Clock (33MHz)uPD720101 USB - PCLK - Pin 42Output
to:
GPIO[14]U22PCI Clock (33MHz)uPD720101 USB - PCLK - Pin 42Output
Restore
June 21, 2005, at 01:28 AM by tman --
Changed line 19 from:
GPIO[6]V21I²C SCLXC1205 RTC - SCL - Pin 6Input
to:
GPIO[6]V21I²C SCLXC1205 RTC - SCL - Pin 6Output
Restore
February 17, 2005, at 02:57 AM by tman --
Changed line 5 from:

GPIO(15) is GPIO_CLK1 and is probably running at 33MHz. It is required to access the Flash memory on the expansion bus. After power-up the IXP420 is configured to provide a clock on this GPIO pin. If the clock output on this pin is disabled access to the Flash is impossible.

to:

GPIO(15) is GPIO_CLK1 and is running at 33MHz. It is required to access the Flash memory on the expansion bus. After power-up the IXP420 is configured to provide a clock on this GPIO pin. If the clock output on this pin is disabled, access to the Flash is impossible.

Changed line 28 from:
GPIO[15]U25Expansion Bus Clock (33MHz?)IXP420 - EX_CLK - Ball M32Output
to:
GPIO[15]U25Expansion Bus Clock (33MHz)IXP420 - EX_CLK - Ball M32Output
Restore
January 21, 2005, at 07:54 PM by tman --
Changed line 9 from:

A much safer and easier option to add extra IO pins is to use a I2C IO extender. Please see PinoutOfI2CPort for more details on the I2C connection.

to:

A much safer and easier option to add extra IO pins is to use a I²C IO extender. Please see PinoutOfI2CPort for more details on the I²C connection.

Changed lines 12-28 from:
BallGPIO(X)FunctionConnected to:Configured as:
Y22GPIO(0)Red Status LEDStatus LEDOutput
W21GPIO(1)Green Ready LED (1 = On)Ready LEDOutput
AC26GPIO(2)Disk 2 LED (0 = On)Disk 2 LEDOutput
AA24GPIO(3)Disk 1 LED (0 = On)Disk 1 LEDOutput
AB26GPIO(4)BuzzerBuzzerOutput
Y25GPIO(5)Power Button (Pulse when state change)Power Button via flipflopTristate/input
V21GPIO(6)I2C SCLXC1205 RTC - SCL - Pin 6Tristate/input
AA26GPIO(7)I2C SDAXC1205 RTC - SDA - Pin 5Tristate/input
W23GPIO(8)Power Off (1 = Turn Off)R10Output
V22GPIO(9)PCI INTCuPD720101 USB (EHCI) - INTC0 - Pin 43Tristate/input
Y26GPIO(10)PCI INTBuPD720101 USB (OHCI #2) - INTB0 - Pin 88Tristate/input
W25GPIO(11)PCI INTAuPD720101 USB (OHCI #1) - INTA0 - Pin 125Tristate/input
W26GPIO(12)Reset Button (0 = Pressed)Reset ButtonTristate/input
V24GPIO(13)PCI ResetuPD720101 USB - VBBRST0 - Pin 87Output
U21GPIO(14)PCI Clock (33MHz)uPD720101 USB - PCLK - Pin 42Output
U25GPIO(15)Expansion Bus ClockIXP420 - EX_CLK - Ball M32Output
to:
GPIOIXP BallFunctionConnected to:Configured as:
GPIO[0]Y22Red Status LED (1 = On)Status LEDOutput
GPIO[1]W21Green Ready LED (1 = On)Ready LEDOutput
GPIO[2]AC26Disk 2 LED (0 = On)Disk 2 LEDOutput
GPIO[3]AA24Disk 1 LED (0 = On)Disk 1 LEDOutput
GPIO[4]AB26BuzzerBuzzerOutput
GPIO[5]Y25Power Button (Pulse when state change)Power Button via flipflopInput
GPIO[6]V21I²C SCLXC1205 RTC - SCL - Pin 6Input
GPIO[7]AA26I²C SDAXC1205 RTC - SDA - Pin 5Tristate
GPIO[8]W23Power Off (1 = Turn Off)R10Output
GPIO[9]V22PCI INTCuPD720101 USB (EHCI) - INTC0 - Pin 43Input
GPIO[10]Y26PCI INTBuPD720101 USB (OHCI #2) - INTB0 - Pin 88Input
GPIO[11]W25PCI INTAuPD720101 USB (OHCI #1) - INTA0 - Pin 125Input
GPIO[12]W26Reset Button (0 = Pressed)Reset ButtonInput
GPIO[13]V24PCI ResetuPD720101 USB - VBBRST0 - Pin 87Output
GPIO[14]U21PCI Clock (33MHz)uPD720101 USB - PCLK - Pin 42Output
GPIO[15]U25Expansion Bus Clock (33MHz?)IXP420 - EX_CLK - Ball M32Output
Restore
October 18, 2004, at 03:14 PM by tman --
Changed line 21 from:
W23GPIO(8)Power Off Signal?FlipflopOutput
to:
W23GPIO(8)Power Off (1 = Turn Off)R10Output
Restore
October 15, 2004, at 04:57 PM by tman --
Changed line 1 from:

The IXP420 CPU has 16 General Purpose Input/Output (GPIO) pins which are used to interface to external hardware. In the case of the NSLU2, the GPIO pins are used to monitor the buttons, control the LEDs, connect to the RTC and USB 2.0 controller. The only pin for which the usage remains uncertain is GPIO(8).

to:

The IXP420 CPU has 16 General Purpose Input/Output (GPIO) pins which are used to interface to external hardware. In the case of the NSLU2, the GPIO pins are used to monitor the buttons, control the LEDs, connect to the RTC and USB 2.0 controller.

Changed line 3 from:

GPIO(8) is assigned as INTD on the PCI bus which only has the NEC USB 2.0 controller on. The USB 2.0 controller however does not connect to INTD at all so it appears to be unused. A possible bug in the stock kernel sets the pin type to be an output when it should be tristate/input for it to operate correctly as a interrupt pin. This may be a bug or it may be an intentional kludge to reuse the pin.

to:

GPIO(8) should actually be assigned as INTD on the PCI bus but it's been set as an output instead of tristate. It is connected to the power circuitry and is used to power down the NSLU2.

Changed line 21 from:
W23GPIO(8)PCI INTDUnused?Output (Bug in stock kernel?)
to:
W23GPIO(8)Power Off Signal?FlipflopOutput
Restore
September 24, 2004, at 12:16 AM by tman --
Changed line 27 from:
U21GPIO(14)PCI ClockuPD720101 USB - PCLK - Pin 42Output
to:
U21GPIO(14)PCI Clock (33MHz)uPD720101 USB - PCLK - Pin 42Output
Restore
September 24, 2004, at 12:15 AM by tman --
Changed line 1 from:

The IXP420 CPU has 16 General Purpose Input/Output (GPIO) pins which are used to interface to external hardware. In the case of the NSLU2, the GPIO pins are used to monitor the buttons, control the LEDs, connect to the RTC and USB 2.0 controller. The only pins for which the connections & usage remain uncertain are GPIO(8) and GPIO(15).

to:

The IXP420 CPU has 16 General Purpose Input/Output (GPIO) pins which are used to interface to external hardware. In the case of the NSLU2, the GPIO pins are used to monitor the buttons, control the LEDs, connect to the RTC and USB 2.0 controller. The only pin for which the usage remains uncertain is GPIO(8).

Restore
September 24, 2004, at 12:13 AM by tman --
Changed line 5 from:

GPIO(15) is GPIO_CLK1 and is probably running at 33MHz. It is required to access the Flash memory on the expansion bus. After power-up the IXP4xx? is configured to provide a clock on this GPIO pin. If the clock output on this pin is disabled access to the Flash is impossible.

to:

GPIO(15) is GPIO_CLK1 and is probably running at 33MHz. It is required to access the Flash memory on the expansion bus. After power-up the IXP420 is configured to provide a clock on this GPIO pin. If the clock output on this pin is disabled access to the Flash is impossible.

Changed line 28 from:
U25GPIO(15)Expansion Bus ClockIXP420 EX_CLK Pin (Ball M32)Output
to:
U25GPIO(15)Expansion Bus ClockIXP420 - EX_CLK - Ball M32Output
Restore
September 24, 2004, at 12:11 AM by tman --
Changed line 28 from:
U25GPIO(15)Expansion Bus ClockIXP420 EX_CLK Pin (Ball M32)Output
to:
U25GPIO(15)Expansion Bus ClockIXP420 EX_CLK Pin (Ball M32)Output
Restore
September 22, 2004, at 09:24 PM by tman --
Changed line 1 from:

The IXP425 CPU has 16 General Purpose Input/Output (GPIO) pins which are used to interface to external hardware. In the case of the NSLU2, the GPIO pins are used to monitor the buttons, control the LEDs, connect to the RTC and USB 2.0 controller. The only pins for which the connections & usage remain uncertain are GPIO(8) and GPIO(15).

to:

The IXP420 CPU has 16 General Purpose Input/Output (GPIO) pins which are used to interface to external hardware. In the case of the NSLU2, the GPIO pins are used to monitor the buttons, control the LEDs, connect to the RTC and USB 2.0 controller. The only pins for which the connections & usage remain uncertain are GPIO(8) and GPIO(15).

Restore
September 22, 2004, at 08:47 PM by quantin --
Changed line 5 from:

GPIO(15) is GPIO_CLK1 and is probably running at 33MHz. It is not known at this time whether anything is actually connected to this pin or not.

to:

GPIO(15) is GPIO_CLK1 and is probably running at 33MHz. It is required to access the Flash memory on the expansion bus. After power-up the IXP4xx? is configured to provide a clock on this GPIO pin. If the clock output on this pin is disabled access to the Flash is impossible.

Changed line 28 from:
U25GPIO(15)Clock of some kind???Output
to:
U25GPIO(15)Expansion Bus ClockIXP420 EX_CLK Pin (Ball M32)Output
Restore
September 21, 2004, at 10:05 PM by ka6sox --
Changed line 7 from:

The USB 2.0 controller can be configured to only use INTA which would free up GPIO(9) and GPIO(10). If the USB 2.0 controller tristates the INTB0 and INTC0 pins when they are disabled then we may reuse the GPIOs? without cutting traces. If the USB 2.0 controller however actively pulls the pin high or low even when disabled then we must cut traces to allow reuse of the GPIOs.

to:

The USB 2.0 controller can be configured to only use INTA which would free up GPIO(9) and GPIO(10). If the USB 2.0 controller tristates the INTB0 and INTC0 pins when they are disabled then we may reuse the GPIOs without cutting traces. If the USB 2.0 controller however actively pulls the pin high or low even when disabled then we must cut traces to allow reuse of the GPIOs.

Changed line 9 from:

A much safer and easier option to add extra IO pins is to use a I2C IO extender. Please see PinoutOfI2CPort for more details on the I2C? connection.

to:

A much safer and easier option to add extra IO pins is to use a I2C IO extender. Please see PinoutOfI2CPort for more details on the I2C connection.

Restore
September 21, 2004, at 03:05 AM by tman --
Changed line 3 from:

GPIO(8) is assigned as INTD on the PCI bus which only has the NEC USB 2.0 controller on. The USB 2.0 controller however does not connect to INTD at all so it appears to be unused. A possible bug in the stock kernel sets the pin type to be an output which it should be tristate/input for it to operate correctly as a interrupt pin. This may be a bug or it may be an intentional kludge to reuse the pin.

to:

GPIO(8) is assigned as INTD on the PCI bus which only has the NEC USB 2.0 controller on. The USB 2.0 controller however does not connect to INTD at all so it appears to be unused. A possible bug in the stock kernel sets the pin type to be an output when it should be tristate/input for it to operate correctly as a interrupt pin. This may be a bug or it may be an intentional kludge to reuse the pin.

Changed line 30 from:
 -- tman
to:

--tman

Restore
September 21, 2004, at 03:01 AM by tman --
Changed lines 1-9 from:

These are the currently known GPIO connections on the IXP425:

to:

The IXP425 CPU has 16 General Purpose Input/Output (GPIO) pins which are used to interface to external hardware. In the case of the NSLU2, the GPIO pins are used to monitor the buttons, control the LEDs, connect to the RTC and USB 2.0 controller. The only pins for which the connections & usage remain uncertain are GPIO(8) and GPIO(15).

GPIO(8) is assigned as INTD on the PCI bus which only has the NEC USB 2.0 controller on. The USB 2.0 controller however does not connect to INTD at all so it appears to be unused. A possible bug in the stock kernel sets the pin type to be an output which it should be tristate/input for it to operate correctly as a interrupt pin. This may be a bug or it may be an intentional kludge to reuse the pin.

GPIO(15) is GPIO_CLK1 and is probably running at 33MHz. It is not known at this time whether anything is actually connected to this pin or not.

The USB 2.0 controller can be configured to only use INTA which would free up GPIO(9) and GPIO(10). If the USB 2.0 controller tristates the INTB0 and INTC0 pins when they are disabled then we may reuse the GPIOs? without cutting traces. If the USB 2.0 controller however actively pulls the pin high or low even when disabled then we must cut traces to allow reuse of the GPIOs.

A much safer and easier option to add extra IO pins is to use a I2C IO extender. Please see PinoutOfI2CPort for more details on the I2C? connection.

Deleted line 10:
Changed line 21 from:
W23GPIO(8)PCI INTDUnused?Output (Bug in stock kernel)
to:
W23GPIO(8)PCI INTDUnused?Output (Bug in stock kernel?)
Changed lines 28-30 from:
U25GPIO(15)Clock of some kind???Output
to:
U25GPIO(15)Clock of some kind???Output
 -- tman
Restore
September 21, 2004, at 01:09 AM by tman --
Changed lines 12-13 from:
V21GPIO(6)I2C SCLXC1205 RTC - Pin 6Tristate/input
AA26GPIO(7)I2C SDAXC1205 RTC - Pin 5Tristate/input
to:
V21GPIO(6)I2C SCLXC1205 RTC - SCL - Pin 6Tristate/input
AA26GPIO(7)I2C SDAXC1205 RTC - SDA - Pin 5Tristate/input
Changed lines 15-17 from:
V22GPIO(9)PCI INTCuPD720101 USB Controller (EHCI) - Pin 22Tristate/input
Y26GPIO(10)PCI INTBuPD720101 USB Controller (OHCI #2) - Pin 21Tristate/input
W25GPIO(11)PCI INTAuPD720101 USB Controller (OHCI #1) - Pin 20Tristate/input
to:
V22GPIO(9)PCI INTCuPD720101 USB (EHCI) - INTC0 - Pin 43Tristate/input
Y26GPIO(10)PCI INTBuPD720101 USB (OHCI #2) - INTB0 - Pin 88Tristate/input
W25GPIO(11)PCI INTAuPD720101 USB (OHCI #1) - INTA0 - Pin 125Tristate/input
Changed lines 19-20 from:
V24GPIO(13)PCI ResetuPD720101 USB Controller?Output
U21GPIO(14)PCI ClockuPD720101 USB Controller - Pin 15Output
to:
V24GPIO(13)PCI ResetuPD720101 USB - VBBRST0 - Pin 87Output
U21GPIO(14)PCI ClockuPD720101 USB - PCLK - Pin 42Output
Restore
September 21, 2004, at 01:00 AM by tman --
Changed line 19 from:
V24GPIO(13)PCI Reset???Output
to:
V24GPIO(13)PCI ResetuPD720101 USB Controller?Output
Restore
September 21, 2004, at 12:49 AM by tman --
Changed line 21 from:
U25GPIO(15)??????Output
to:
U25GPIO(15)Clock of some kind???Output
Restore
September 21, 2004, at 12:20 AM by tman --
Changed line 6 from:
Y22GPIO(0)Red Status LED? (Not confirmed)Status LED?Output
to:
Y22GPIO(0)Red Status LEDStatus LEDOutput
Changed lines 12-17 from:
V21GPIO(6)I2C SCLXC1205 RTC Pin 6Tristate/input
AA26GPIO(7)I2C SDAXC1205 RTC Pin 5Tristate/input
W23GPIO(8)PCI INTDUnused?Output
V22GPIO(9)PCI INTCuPD720101 USB EHCITristate/input
Y26GPIO(10)PCI INTBuPD720101 USB OHCI Controller 2Tristate/input
W25GPIO(11)PCI INTAuPD720101 USB OHCI Controller 1Tristate/input
to:
V21GPIO(6)I2C SCLXC1205 RTC - Pin 6Tristate/input
AA26GPIO(7)I2C SDAXC1205 RTC - Pin 5Tristate/input
W23GPIO(8)PCI INTDUnused?Output (Bug in stock kernel)
V22GPIO(9)PCI INTCuPD720101 USB Controller (EHCI) - Pin 22Tristate/input
Y26GPIO(10)PCI INTBuPD720101 USB Controller (OHCI #2) - Pin 21Tristate/input
W25GPIO(11)PCI INTAuPD720101 USB Controller (OHCI #1) - Pin 20Tristate/input
Changed line 20 from:
U21GPIO(14)PCI Clock (Not confirmed)???Output
to:
U21GPIO(14)PCI ClockuPD720101 USB Controller - Pin 15Output
Restore
September 21, 2004, at 12:14 AM by tman --
Changed lines 14-17 from:
W23GPIO(8)PCI INTD???Output
V22GPIO(9)PCI INTC???Tristate/input
Y26GPIO(10)PCI INTB???Tristate/input
W25GPIO(11)PCI INTA???Tristate/input
to:
W23GPIO(8)PCI INTDUnused?Output
V22GPIO(9)PCI INTCuPD720101 USB EHCITristate/input
Y26GPIO(10)PCI INTBuPD720101 USB OHCI Controller 2Tristate/input
W25GPIO(11)PCI INTAuPD720101 USB OHCI Controller 1Tristate/input
Restore
September 20, 2004, at 11:58 PM by tman --
Changed lines 11-13 from:
Y25GPIO(5)Power ButtonPower ButtonTristate/input
V21GPIO(6)I2C SCLXC1205 Pin 6Tristate/input
AA26GPIO(7)I2C SDAXC1205 Pin 5Tristate/input
to:
Y25GPIO(5)Power Button (Pulse when state change)Power Button via flipflopTristate/input
V21GPIO(6)I2C SCLXC1205 RTC Pin 6Tristate/input
AA26GPIO(7)I2C SDAXC1205 RTC Pin 5Tristate/input
Changed line 18 from:
W26GPIO(12)Reset ButtonReset ButtonTristate/input
to:
W26GPIO(12)Reset Button (0 = Pressed)Reset ButtonTristate/input
Restore
September 20, 2004, at 11:51 PM by tman --
Changed lines 5-21 from:
BallGPIO(X)Functionconnected to:configured as:
Y22GPIO(0)??????Output
W21GPIO(1)Green Ready LED (1 = On)READY LEDOutput
AC26GPIO(2)Disk 2 LED (0 = On)Disk 2 LEDOutput
AA24GPIO(3)Disk 1 LED (0 = On)Disk 1 LEDOutput
AB26GPIO(4)BuzzerBuzzerOutput
Y25GPIO(5)Power ButtonPower Buttontristate/input
V21GPIO(6)I2C SCLXC1205 Pin 6tristate/input
AA26GPIO(7)I2C SDAXC1205 Pin 5tristate/input
W23GPIO(8)PCI INTD???Output
V22GPIO(9)PCI INTC???tristate/input
Y26GPIO(10)PCI INTB???tristate/input
W25GPIO(11)PCI INTA???tristate/input
W26GPIO(12)??????tristate/input
V24GPIO(13)PCI Reset???Output
U21GPIO(14)??????Output
U25GPIO(15)??????Output
to:
BallGPIO(X)FunctionConnected to:Configured as:
Y22GPIO(0)Red Status LED? (Not confirmed)Status LED?Output
W21GPIO(1)Green Ready LED (1 = On)Ready LEDOutput
AC26GPIO(2)Disk 2 LED (0 = On)Disk 2 LEDOutput
AA24GPIO(3)Disk 1 LED (0 = On)Disk 1 LEDOutput
AB26GPIO(4)BuzzerBuzzerOutput
Y25GPIO(5)Power ButtonPower ButtonTristate/input
V21GPIO(6)I2C SCLXC1205 Pin 6Tristate/input
AA26GPIO(7)I2C SDAXC1205 Pin 5Tristate/input
W23GPIO(8)PCI INTD???Output
V22GPIO(9)PCI INTC???Tristate/input
Y26GPIO(10)PCI INTB???Tristate/input
W25GPIO(11)PCI INTA???Tristate/input
W26GPIO(12)Reset ButtonReset ButtonTristate/input
V24GPIO(13)PCI Reset???Output
U21GPIO(14)PCI Clock (Not confirmed)???Output
U25GPIO(15)??????Output
Restore
September 20, 2004, at 11:18 PM by ka6sox --
Changed lines 5-21 from:
BallGPIO(X)Functionconnected to:
Y22GPIO(0)??????
W21GPIO(1)Green Ready LED (1 = On)READY LED
AC26GPIO(2)Disk 2 LED (0 = On)Disk 2 LED
AA24GPIO(3)Disk 1 LED (0 = On)Disk 1 LED
AB26GPIO(4)BuzzerBuzzer
Y25GPIO(5)Power ButtonPower Button
V21GPIO(6)I2C SCLXC1205 Pin 6
AA26GPIO(7)I2C SDAXC1205 Pin 5
W23GPIO(8)PCI INTD???
V22GPIO(9)PCI INTC???
Y26GPIO(10)PCI INTB???
W25GPIO(11)PCI INTA???
W26GPIO(12)??????
V24GPIO(13)PCI Reset???
U21GPIO(14)??????
U25GPIO(15)??????
to:
BallGPIO(X)Functionconnected to:configured as:
Y22GPIO(0)??????Output
W21GPIO(1)Green Ready LED (1 = On)READY LEDOutput
AC26GPIO(2)Disk 2 LED (0 = On)Disk 2 LEDOutput
AA24GPIO(3)Disk 1 LED (0 = On)Disk 1 LEDOutput
AB26GPIO(4)BuzzerBuzzerOutput
Y25GPIO(5)Power ButtonPower Buttontristate/input
V21GPIO(6)I2C SCLXC1205 Pin 6tristate/input
AA26GPIO(7)I2C SDAXC1205 Pin 5tristate/input
W23GPIO(8)PCI INTD???Output
V22GPIO(9)PCI INTC???tristate/input
Y26GPIO(10)PCI INTB???tristate/input
W25GPIO(11)PCI INTA???tristate/input
W26GPIO(12)??????tristate/input
V24GPIO(13)PCI Reset???Output
U21GPIO(14)??????Output
U25GPIO(15)??????Output
Restore
September 20, 2004, at 11:12 PM by tman --
Changed lines 14-17 from:
W23GPIO(8)??????
V22GPIO(9)??????
Y26GPIO(10)??????
W25GPIO(11)??????
to:
W23GPIO(8)PCI INTD???
V22GPIO(9)PCI INTC???
Y26GPIO(10)PCI INTB???
W25GPIO(11)PCI INTA???
Changed line 19 from:
V24GPIO(13)??????
to:
V24GPIO(13)PCI Reset???
Restore
September 20, 2004, at 10:56 PM by ka6sox --
Changed lines 12-13 from:
V21GPIO(6)I2C SCLXC1205 Pin X
AA26GPIO(7)I2C SDAXC1205 Pin Y
to:
V21GPIO(6)I2C SCLXC1205 Pin 6
AA26GPIO(7)I2C SDAXC1205 Pin 5
Restore
September 20, 2004, at 10:52 PM by ka6sox --
Changed lines 3-9 from:
 GPIO1 = Green Ready LED (1 = On)
 GPIO2 = Disk 2 LED (0 = On)
 GPIO3 = Disk 1 LED (0 = On)
 GPIO4 = Buzzer
 GPIO5 = Power Button
 GPIO6 = I2C SCL
 GPIO7 = I2C SDA
to:
BallGPIO(X)Functionconnected to:
Y22GPIO(0)??????
W21GPIO(1)Green Ready LED (1 = On)READY LED
AC26GPIO(2)Disk 2 LED (0 = On)Disk 2 LED
AA24GPIO(3)Disk 1 LED (0 = On)Disk 1 LED
AB26GPIO(4)BuzzerBuzzer
Y25GPIO(5)Power ButtonPower Button
V21GPIO(6)I2C SCLXC1205 Pin X
AA26GPIO(7)I2C SDAXC1205 Pin Y
W23GPIO(8)??????
V22GPIO(9)??????
Y26GPIO(10)??????
W25GPIO(11)??????
W26GPIO(12)??????
V24GPIO(13)??????
U21GPIO(14)??????
U25GPIO(15)??????
Restore
September 20, 2004, at 09:45 PM by ka6sox --
Changed line 1 from:

These are the currently known GPIO connections on the IXP425:

to:

These are the currently known GPIO connections on the IXP425:

Changed lines 8-9 from:
 GPIO6 = I2C? SCL
 GPIO7 = I2C? SDA
to:
 GPIO6 = I2C SCL
 GPIO7 = I2C SDA
Restore
September 20, 2004, at 07:54 PM by tman --
Changed lines 8-9 from:
 GPIO14 = I2C?
 GPIO15 = I2C?
to:
 GPIO6 = I2C? SCL
 GPIO7 = I2C? SDA
Restore
September 20, 2004, at 05:53 PM by tman --
Added line 7:
 GPIO5 = Power Button
Restore
September 20, 2004, at 05:34 PM by tman --
Changed lines 1-8 from:

Describe GPIOConnections here.

to:

These are the currently known GPIO connections on the IXP425: 

 GPIO1 = Green Ready LED (1 = On)
 GPIO2 = Disk 2 LED (0 = On)
 GPIO3 = Disk 1 LED (0 = On)
 GPIO4 = Buzzer
 GPIO14 = I2C?
 GPIO15 = I2C?
Restore
view · edit · print · history · Last edited by rwhitby.
Based on work by Petr Jakes, ep1220, tman, quantin, and ka6sox.
Originally by tman.
Page last modified on January 02, 2008, at 01:30 AM