You are on page 1of 12

appendix

D OCKING
Docking Architecture Overview
The computer uses the same physical interface as the previous generation of Digital
Equipment portable systems i.e., the 160-pin AMP connector and power posts. The
electrical configuration, however, is very different. Rather than provide a classic
docking architecture in which system commands are sent to the dock over a
communication bus where the dock acts intelligently on the signals, all Armada 6500
docking peripherals are passive devices. All of the necessary control signals for devices
in the dock are provided by the system.

Docking A-1

The only two devices supported by the computer are the Convenience Base and the
Mobile Expansion Unit. There are no plans for future docking enhancements.

The Convenience Base and the Mobile Expansion Unit can be attached at the same
time.
Both devices are bottom mounted (attached to the bottom of the computer).
All docking devices are hot-dockable under Windows 95, Windows 98, and
Windows NT.
All docking devices use a locking mechanism for security.
A security mode is available which cannot allow docking devices to be detached in
Suspend or Off, if the user so chooses.
Multiple Mobile Expansion Units cannot be docked together.
The Convenience Base has a top connector only and can be docked to the Mobile
Expansion Unit or to the notebook.
Each dock has an LED to indicate the dock status.
Each dock has an undock button that is used to request that the dock be released.
Windows 95/Windows98 Eject PC option has the same functionality as the
undock button request.

Docking devices do not generate their own buses; their signals are passed through by
the system or by the middle docking device. Bottom docking devices may attach either
to the system or to a middle docking device.
The docking strategy allows two docking devices to be added to the notebook at the
same time. The Mobile Expansion Unit has a connector on top to mate with the
notebook and a connector on the bottom to connect to the Convenience Base. The
bottom connector on the Mobile Expansion Unit is located in the same place as the
connector on the bottom of the notebook. It is not possible to have two Mobile
Expansion Units attached at the same time; this is ensured by mechanical design.

Docking Features
Both the Convenience Base and the Mobile Expansion Unit are hot-dockable. This
means that computer can be on at the time of docking and that after the docking event,
the peripherals in the newly attached dock are immediately usable under Windows 95,
Windows 98, and Windows NT.
After docking, a latch locks the newly attached docking devices. This prohibits the
user from removing the docking devices while its resources are still being accessed.
Undocking can be requested via a button on the dock or via Windows. Windows waits
until the docking devices resources are no longer being used before allowing the
docking devices to be removed. This is done by waiting until Windows accepts the
undock request before releasing the docking device latch.

A-2 Docking

An I2C bus is used to control many functions within the docks. The H8 in the Armada
6500 is the I2C master device. Every docking device has at least the following two I2C
devices:

EEPROM for storing dock functionality and devices

For details refer to the firmware groups EEPROM map document

GPIO device with at least one input

One input = power good indicator

A LED is located on each docking device to indicate the docking status. The LED is off
until the docking process has completed successfully, and the docking device is
latched. After that point, the LED is on unless the system is in the Suspend or Off state.
If an undock request is generated, the LED turns off once the undock request has been
granted, and the docking device is unlocked.

Docking Connector/Signals
The docking connector is a custom designed 160-pin connector with four power posts.
The 160-pins are rated for 0.5 A each. The power posts are rated for 4.0 A each. The
160-pins are used for all signals, 3 volt, 5 volt, and 12 volt power sources, and various
signal ground pins. The four posts are used for ACPOWERRAIL, POWERRAIL,
CHGRAIL, and GND. The female connector is used on the bottom of the notebook and
Mobile Expansion Unit. The male connector is used on the top of the Mobile
Expansion Unit and Convenience Base.
Diskette
Signal
SDD<7..0>
HDSEL, DISKETTE DRIVE_DENSEL
DSKCHG#, DIR, STEP, RDATA#, WDATA#,
WGATE#, INDEX0#, STEP, DR0#, MTR0#,
WRPT#, WDATA#, MEDIA#

Function
FDC data lines
Diskette density select signals
FDC control signals

Audio Interface
Signal
XA0,XA1
XA2,XA3
TXD
RXD
GD<7..4>
GD<3..0>
AUDIO_DOCKED
AUD_DOCK_SD
PC_SPKR
S/PDIF
AGND

Function
Analog audio signals to Mobile Expansion Unit
Analog audio signals from MEUs bay CD-ROM/DVD-ROM
MIDI transmit data
MIDI receive data
Joystick switch inputs (D .. A)
Analog joystick inputs (TD .. TA)
Indication that an audio dock is attached
Controls the shutdown of the audio amplifier
Speaker audio data
Dolby Digital audio data
Audio return path

Docking A-3

IDE
Signal
SDD<15..0>
SDA<0..2>
SDIORDY, SDIOR#, SDIOW#, SDCS1#,
SDCS3#
SDDREQ, SDDACK#
QIRQ15

Function
Secondary IDE data lines
Secondary IDE address lines
Secondary IDE control lines
Secondary IDE DMA handshake lines
Secondary IDE interrupt line

CRT
Signal
DOCK_RED, DOCK_GRN, DOCK_BLU
HSYNC, VSYNC
CRT_AGND
DDCK,DDDA

Function
R-G-B pass-through for external monitor
Horizontal and Vertical sync for external monitor
Return path for CRT video signals
2
DDC I C interface for auto monitor configuration

TV
Signal
TV_Y
TV_C
TV_COMP
TV_VSS

Function
Luminance video data
Chrominance video data
Composite video data
Return path for TV video signals

PS/2
Signal
PS2 KBCLK, PS2 KBDAT
PS2MSCLK, PS2MSDAT

Function
Keyboard PS/2 interface pass-through
Mouse PS/2 interface pass-through

NIC
Signal
NIC_TX+/-, NIC_RX+/-

Function
Twisted pair Ethernet signal pass-through

USB
Signal
USBP1_DAT+, USBP1_DAT-, USB_POK,
USB_EN#

Function
USB port #1 signal pass-through

Docking Control
Signal
DOCKED<1,2>#
DOCK_GNT<1,2>#
UNDOCK_REQ<1,2>#
DOCKTYPE
IICCLK, IICDATA, IICINT
DOCK_BAY_PWRON

A-4 Docking

Function
Dock indicators for first and second dock
Dock grant signals for first and second dock
Undock request signals for first and second dock
Selects Convenience Base (0V) or Expansion Base (2.0 V)
2
I C interface to control docking devices (H8 is the controller)
Enables power to bay module in dock

Second Battery
Signal
DQ2
BATDETECT2

Function
Serial interface to second battery
Detects the presence of the second battery

Power Supplies
Signal
DCDC3
DCDC5
DCDC12
POWERRAIL
ACPOWERRAIL
CHGRAIL
VPWRLOW
GND

Function
3.3 V output from system DC-DC
5.0 V output from system DC-DC
12.0 V output from system DC-DC
System power rail (supplied by either AC cube or battery)
AC power rail (all AC cubes plug directly into this rail)
Battery charging rail
Indicates that power rail is below specification
System common/ground

Misc
Signal
SYSVCCON
BAY2TYPE
CHGEN

Function
System on indicator
Analog bay device identification signal
Battery Charger enable

Parallel Port
Signal
PDA0-PDA7,PACK#,
PBUSY,PPE,PSLCT,
PSLIN#,PINIT#,PPERR#,PAFD#,PSTB#

Function
Parallel Port signal pass-through

Serial port
Signal
DCD#, DSR#, SIN, RI#,
SOUT, CTS#, DTR#,
RTS#

Function
Serial Port signal pass-through

Hot Docking/Undocking
The hot docking mechanism used when the Mobile Expansion Unit or Convenience
Base is attached to a system in the On state requires very little logic since the options
are passive docking device(s).

Docking Procedure
The DOCKED# signal tells the system that a dock is about to occur. There are actually
two DOCKED# pins: DOCKED1# for a middle dock and DOCKED2# for a bottom
dock. The Mobile Expansion Unit activates the DOCKED1#. The Convenience Base
asserts DOCKED2#. In the case where both docking devices are attached to the system,

Docking A-5

DOCKED2# is passed through the Mobile Expansion Unit to the computer via the
docking connector.
The docking connector is a staggered four-row connector. The outside rows are 1mm
taller than the inside rows. All pins on the outside row are ones that may be connected
prior to the I2C bus being disabled. The inside rows are the ones that contain the signals
that can not be dynamically connected between the computer and the docking devices
(such as the Mobile Expansion Unit). These signals would include the I 2C bus.
DOCKED1# and DOCKED2# are on the outside rows.
When the computer recognizes DOCKED1# asserted, the H8 tests for docking devices
attached by reading the IIC EEPROM in the docking device(s) until it gets valid data.
SYSVCCON# turns on the power supply in the Mobile Expansion Unit. The power
supply in the Mobile Expansion Unit, when operating correctly, then asserts a
POWERGOOD signal to the I2C GPIO. The H8, polling the GPIO, then asserts
DOCK_GNT1# (also DOCK_GNT2# if a Convenience Base is attached).
The DOCK_GNT# locks the solenoid in the dock, preventing the user from undocking
the unit without warning. The solenoid also can be used for security. This signal is also
used to turn on the LED which indicates that the dock is successfully attached and that
its resources can be used. At this point, the CPU starts to execute the DOCK SMI. The
BIOS initializes the dock, and the OS is notified.

Docking While System On


The following system sequences occur when docking the devices to the computer while
the system is powered on.
System:
1. As dock starts mating, DOCKED# is asserted and wakes up the H8.
2. When H8 receives DOCKED#, it

a. tests for dock by reading EEPROM until it gets valid data.


b. polls GPIO bit via I2C until it indicates power is good in the dock.
c. asserts SCPSMI.
d. asserts DOCK_GNT#.
1. When DOCK_GNT# is asserted, the
c. solenoid locks the dock (via the I2C bus).
d. LED indicates the dock is locked.
e. CPU starts executing DOCK SMI.
f. BIOS initializes the audio system for external use if docked to a
Mobile Expansion Unit.
g. OS is notified and performs docking process.

A-6 Docking

Docking While System Suspended or Off


The system and the dock are connected. During the boot or resume process, the docks
are polled and then:
1. As the system resumes or is turned on,

a. H8 polls and sees that DOCKED# is asserted.


b. tests for dock by reading EEPROM until it gets valid data.
c. polls GPIO bit via I2C until it indicates power is good in the dock.
d. asserts SCPSMI.
e. asserts DOCK_GNT#.
1. When DOCK_GNT# is asserted, the
b. solenoid locks the dock (via the I2C bus).
c. LED indicates the dock is locked.
d. CPU starts executing DOCK SMI.
e. BIOS initializes the audio system for external use if docked to a Mobile
Expansion Unit
f. OS is notified (once booted) and performs docking process.
g. new devices are enumerated.

Undocking Procedure
The UNDOCK_REQ1# and UNDOCK_REQ2# signals from a docking device tell the
system that an undock event is pending. The Mobile Expansion Unit uses
UNDOCK_REQ1# since it is a middle dock. The system prepares itself and informs
the dock to unlock itself from the system.
The UNDOCK_REQ# signal must be asserted before the system can be removed. The
assertion is defined as a falling edge.
The assertion of UNDOCK_REQ# can come from two sources:
The OS (such as Win95)
The Undock button on the dock

Upon the assertion of UNDOCK_REQ# (in On or Standby), the H8 in the system is


notified that an undock request event has occurred. The H8 issues an SMI, and the
system prepares for undocking by disabling all devices in the docking device. Once the
system has prepared for the undock to take place, it de-asserts DOCK_GNT#.
Or:
If the user wants to undock using the OS, there is no assertion of UNDOCK_REQ#.
The OS is notified directly. In this case, there is no SMI from the H8 to the chipset.
Once the system has prepared for the undock to take place, it de-asserts DOCK_GNT#.

Docking A-7

The de-assertion of DOCK_GNT# turns off the LED to let the user know that the dock
is not active. The OS may also pop up a box notifying the user that the dock is no
longer active, and the solenoid in the dock is switched to an unlocked position. At this
time, the system is still operating; only the audio functions in the Mobile Expansion
Unit are disabled.
If, for some reason, the system is not ejected from the dock, there is a time-out of 45
seconds, the solenoids are locked, and the dock is reconnected to the system. For
example, the user could hit the undock request button on the dock, get notified that it is
OK to undock, and then start to push in the side eject buttons. The user then walks
away from the system. After the timeout, a re-docking is initiated.

Undocking While System On (initiated via undock button or OS)


The following system sequence occurs when undocking the devices while the system is
powered on (initiated via undock button or OS):)
1. Undock button is depressed UNDOCK_REQ# is asserted to the H8.
2. H8 asserts SCPSMI, then

a. The BIOS notifies OS of the undock request. (If the user initiates the undock via
the OS, then the procedure starts here.)
b. If security is enabled, a password is asked for in order to continue. If the correct
password is not given within three attempts then the undock procedure does
NOT continue.
Note: This also means that if security is enabled and the user has a dead battery,
then the user must power the computer from the AC adapter.
c. The OS lets BIOS know that it is okay to remove the docking device (dock has
been disabled).
d. The BIOS notifies H8 that the OS has completed the undock.
1. H8 de-asserts DOCK_GNT#, the
c. solenoid unlocks the dock.
d. LED indicates that the dock is free to be removed.
1. User depresses side eject buttons,
d. UNDOCK_REQ# re-asserts.
e. I2C bus is disabled by H8.
1. User continues to depress side eject buttons, the
e. docking device is disconnected from Armada 6500.
f. DOCKED# is de-asserted.
g. I2C bus is re-enabled.
h. System resumes.

A-8 Docking

1. If User does NOT continue to depress side eject buttons, after 45 seconds the

docking sequence initiates:


f. H8 tests for a dock by reading EEPROM until it gets valid data.
g. Polls GPIO bit via I2C until it indicates power is good in the dock.
h. Asserts SCPSMI.
i. Asserts DOCK_GNT#.
1. When DOCK_GNT# is asserted, the
g. Solenoid locks the dock (via the I2C bus).
h. LED indicates the dock is locked.
i. CPU starts executing DOCK SMI.
j. BIOS initializes the audio in the dock (Mobile Expansion Unit only).
k. OS is notified performs docking process.

Undocking While System Off or Suspend


The following sequence occurs when undocking while the system is off or in
suspend mode:
1. The undock button/side eject button is depressed, if security is enabled, the

procedure stops here. The side eject button can not be depressed. The system must
be resumed/powered on in order to undock. Also, depressing the side eject button
would not have asserted UNDOCK_REQ1#.
2. If the eject button was used and continues to be pushed, system and docking device
are disconnected.
3. If eject button is then depressed after using the front undock request button, the
system and docking device are disconnected.
Note: The front undock request button does not actually do anything. The LED is off,
in Suspend, or powered off (unless security is enabled).
4. When system is resumed or turned on, the

d. H8 polls DOCKED# to see if any docks are attached.


e. O/S is notified that the dock is no longer present.

Docking A-9

Docking Timing Diagram


UNDOCKED

SCPSMI#

DOCK OCCURS
Dock
Start

Dock
SMI

DOCKED

UNDOCK REQUEST
Undock
SMI

UNDOCK OCCURS
Undock Granted
Wait For Removal

Pullup
Rise Time

DOCKED#
DOCK
_GNT#

Undock
Occuring

H8 Okays
Dock

Undock
Request

Unlock
Dock

UNDOCK
_REQ#

Undock
Occurs

Figure A-1. Docking Timing Diagram

Logic Functions
DOCKED# Generation
The DOCKED1# and DOCKED2# signals are connected to GND on the docking
stations and have pull-ups in the notebook.

UNDOCK_REQ# Generation
The UNDOCK_REQ# is generated as discussed above in the Undocking Procedure.

DOCK_GNT# Generation
The DOCK_GNT# is asserted by the H8 as follows:

If a new dock is added, and its power supply has become stable

If during an undock process, the > 45 seconds has transpired, and the dock is not
removed

The DOCK_GNT# is de-asserted by the H8 as follows:

If there is no dock connected

When an undock request process has been completed by the OS

Solenoid Control
The solenoid is controlled by a GPIO in the dock (I2C).
The solenoid is always in the locked position when the system and dock are in the On
state (including Standby). If security is enabled, the solenoid remains in the locked
position until a valid password is given.

A-10 Docking

UN
DOCKED

The solenoid is locked during a docking procedure when the I2C signal SOLND_RED
is asserted. The solenoid is unlocked during an undock when the I2C signal
SOLND_WHITE is asserted. If security is enabled, SOLND_WHITE cannot be
asserted until the undock password is entered.

LED Control (LED for undock request)


The LED is lit whenever DOCKGNT# is asserted.
The LED indicates to the user that the docking device is actively docked to the system
(or secured if security is enabled). The user cannot remove the dock until this LED is
off.

Miscellaneous Functions
I2C Functionality
An I2C bus is used to control many functions within the docks. The H8 is the I2C
master device. Every docking device has at least the following two I2C devices:

EEPROM for storing docking device functionality and devices

For details refer to the EEPROM map in the H8 specification

GPIO device with at least 1 input and 1 output

One output = power supply enable pin

One input = power good indicator

Addressing of I2C Devices


The I2C devices mentioned above have three address inputs (A2-A0). The A2 input is
connected to the DOCK_REQ2# pin on the top connector. The A1 and A0 are available
so that a maximum of four of each type of I2C device could be used in each dock. The
I2C device addresses for the docks are as follows:
Middle dock address:
Bottom dock address:

10X
11X

Note that if only one docking device is attached, the address is 11X because it is the
bottom docking device. If a second docking device is attached, that docking device
becomes the middle docking device and its address changes to 10X. The newly added
docking device is now the bottom docking device and is addressed to 11X.

Docking A-11

Power Supply and power Management


Power Sources
The following are the four 4 Amp posts available on the docking connector:
VACRAIL (AC POWER RAIL) All AC cubes in the notebook or the dock connect
directly to this rail. This supplies power to VPWRRAIL through a sense resistor that
monitors total system power usage.
VPWRRAIL (POWER RAIL) All system power planes are derived from
VPWRRAIL. If a dock needs voltages other than 5 V a DC/DC converter is used
and powered off of the VPWRRAIL.
VCHGRAIL (CHARGE RAIL) This is the rail that is used to charge the batteries.
GND RAIL Supplies GND return for power source.

The following pins supply other power sources:


DCDC5 (2 pins, 1 Amp) This is used for docks that only need 5 Volts. It can be
qualified with SYSVCCON signal from notebook to create SYSVCC5.
DCDC3 (1 pins, 0.5 Amps) This is used to supply the undock logic and solenoid
control.

Power Sequencing
The power rails (AC-input rail, power rail, and charge rail), DCDC5, and DCDC3 are
isolated by FETs to eliminate problems due to in-rush currents. The FETs are
controlled by DOCKx#. If a DC-DC is used to supply power to the docks, the DOCKx#
output connects to its enable/disable pin.
The Mobile Expansion Unit uses its internal DC/DC to supply all power except for the
docking control logic. The docking control logic is always powered by DCDC3.
Docking:

As the dock is attached:

The FETs for the VACRAIL, VCHGRAIL, and VPWRRAIL are turned on

SYSVCCON# enables the DC/DC if one exists. The H8 polls a GPIO pin via I2C
that indicates when all power planes have stabilized.

Undocking:
Power remains to the dock until the user starts splitting the dock.
DCDC3 and DCDC5 are separated by the mechanism that moves the dock away
from the notebook. At this time, DOCK_REQ# also de-asserteds.
The FETs controlling VACRAIL, VCHGRAIL, and VPWRRAIL are turned off
quickly by DOCK_REQ# being de-asserted. The FETs is open before the posts
disconnect.

A-12 Docking