=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
PCI to CardBus Bridge Utilities
June 8, 1998
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
This README.TXT file contains the following information:
1. Introduction
2. Utilities Description
3. Typical Usage
4. What is and isn't Supported in These Utilities
5. When Things Just Won't Work
6. Compatibility List
=-=-=-=-=-=-=-=
1. Introduction
=-=-=-=-=-=-=-=
The PCI-to-CardBus Bridge DOS Utilities are provided to be used
on DOS PCI systems that do not have PCI-to-CardBus bridge (herein referred
to as PCB) BIOS support. They are to be used to fill in the gap between now
and when your system will have another software CardBus support (i.e. Card and
Socket services).
These utilities allow the user to configure the PCB's and the Digital Semiconductor
based CardBus devices downstream of the PCB's without BIOS support.
=-=-=-=-=-=-=-=-=-=-=-=-=
2. Utilities Description
=-=-=-=-=-=-=-=-=-=-=-=-=
These utilities are provided for the developer who intends to write drivers
or diagnostics for a device that is downstream of (behind) a PCI-to-CardBus
bridge. These utilities are intended only as a short term solution, until
the target system is upgraded with a BIOS that supports PCI-to-CardBus
bridges.
There are three (3) utilities available in this release:
1. ROUTEIRQ.EXE
2. ENABLER.EXE
3. PBX.COM
++++++++++++++++
1. ROUTEIRQ.EXE
++++++++++++++++
Usually the PCI BIOS assigns resources at boot time. Most of the BIOS do not
support the CardBus bridge, and hence in most of the cases will not route
PCI interrupts to the CardBus brideg.
In case that the BIOS supports fixed interrupts routing per PCI slot, there is
no need to use this utility.
In all other cases, the user might need to use this utility. If the BIOS did
not assign interrupt to the CardBus bridge, the CardBus card will not generate
an interrupt, and so it's functionality will be partial.
Note that not all interrupt numbers are available for PCI. Usually the following
IRQs can be used for PCI: 5, 9, 10, 11, 15. It is system specific. In case that
the interrupt you select is not routable, the utility will print a notice.
Next release of this utility will select interrupts automatically.
Utility can route IRQs only on systems with PCI BIOS rev 2.1!
Usage:
C:\> ROUTEIRQ [optional switches]
where [optional switches] are:
-h Get help screen
-il INTERRUPT LINE
Note: Use DECIMAL numbers for INTERRUPT LINE
The default interrupt is 9 (when run with no switches).
Example:
This example shows the ROUTEIRQ command without switches. It has assigned
IRQ 9 to the CardBus bridge.
----------------------------------------------------------------------------
C:\> ROUTEIRQ
ÚÂÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³³ CardBus RouteIRQ v1.1, Copyright (c) 1996,1997 Digital Equipment Corp. ³³
ÀÁÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÙ
Build Date: Jan 21 1997
Routing interrupt 9 to CardBus bridge
Found TI1130 bridge
----------------------------------------------------------------------------
Example:
This example shows the ROUTEIRQ command with interrupt number switch used.
It has assigned IRQ 10 to the CardBus bridge.
----------------------------------------------------------------------------
C:\> ROUTEIRQ -il 10
ÚÂÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³³ CardBus RouteIRQ v1.1, Copyright (c) 1996,1997 Digital Equipment Corp. ³³
ÀÁÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÙ
Build Date: Jan 21 1997
Routing interrupt 10 to CardBus bridge
Found TI1130 bridge
----------------------------------------------------------------------------
+++++++++++++++
2. ENABLER.EXE
+++++++++++++++
PCI-to-CardBus bridges and CardBus devices behind the bridges, need to be
configured by software during powerup of a system. Typically configuration
code in the systems BIOS will perform this function. These utilities are
written to be used on systems with BIOS that doesn't have PCB support yet,
so the PCB's and Digital's CardBus devices downstream of the PCB's can be
configured.
This utility will enumerate all the PCI-to-CardBus bridges and configure all
Digital's CardBus devices that it finds in the target system.
Usage:
C:\> ENABLER [optional switches]
where [optional switches] are:
-b (use the system BIOS for all cycles)
-h (display this help text)
-q (quiet, don't display device mapping)
-io IO_ADDRESS (set 16-bit IO mapping address (ie E000)
-pi (use PCI interrupt)
-il INTERRUPT_NO (choose interrupt line)
-v12 (choose VPP1=VPP2=12V )
-v5 (choose VPP1=VPP2=5V )
-v3 (choose VPP1=VPP2=3V )
-legacy (Use CardBus bridge in Legacy mode)
Example:
This example shows the ENABLER command with some switches. It has mapped all
DIGITAL devices behind any PCI-to-CardBus bridges. Notice that the 1
Digital's device have been mapped in I/O space.
The CardBus bridge will use in this example PCI interrupt 10 (0A hex).
The device responds to IDSEL 0 on bus 2 (behind the PCI-to-CardBus bridge on
bus 0 IDSEL 2).
----------------------------------------------------------------------------
C:\>ENABLER -pi -il 0A
ÚÂÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³³ CardBus Enabler v1.3, Copyright (c) 1996,1997 Digital Equipment Corp. ³³
ÀÁÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÙ
Build Date: Jan 21 1997, PCI Config Mechanism: #1, BIOS version: 2.16
For help use: ENABLER -h
Ethernet, [2,0], bridge:[2,0], 128 bytes IO, base: D000h
Ethernet, [2,0], bridge:[2,0], 128 bytes Memory, base: 7E000000h
found 7 PCI devices
mapped 1 PCI devices
----------------------------------------------------------------------------
+++++++++++
3. PBX.COM
+++++++++++
This is actually a TSR (Terminate and Stay Resident) utility that allows the
user to transparently develop drivers or diagnostics for a CardBus device
that might be behind a bridge. The utility will intercept the INT 1A BIOS
call, and provide bridge support for the FIND_PCI_DEVICE and FIND_PCI_CLASSE
requests and other BIOS services which are not aware of the new installed bus.
Use this utility in cases wher your BIOS fail to access PCI devices downstream
the PCB. Many BIOSes 'know' their last bus as the one that was found at boot time.
The CardBus bus will be defined as a subordinate bus (higher number) only by using
the ENABLER. This new bus is sometimes not know to the BIOS.
Usage:
PBX - to load program
PBX /U - to unload the program
----------------------------------------------------------------------------
Examples:
C:\> PBX
PBX V2.01 (970108)
(C) Copyright 1994-1997 Digital Equipment Corp All Rights Reserved.
C:\> PBX /U
PBX V2.01 (970108)
(C) Copyright 1994-1997 Digital Equipment Corp All Rights Reserved.
Unloaded succesfuly
----------------------------------------------------------------------------
=-=-=-=-=-=-=-=-=
3. Typical Usage
=-=-=-=-=-=-=-=-=
Run ENABLER.EXE. If the driver or diagnostic call the PCI BIOS to detect the
PCI devices in the system but fail, then PBX.COM should be run as well.
PBX will provide INT 1A support for find_pci_device and find_pci_class calls
to BIOS and will help to traverse the bridge in case that the BIOS fails to
do so.
In case that interupts are not generated, make sure you know what interrupt
line is routed to your CardBus bridge and run the ENABLER.EXE with interrupt
line override (ENABLER -pi -il NN). If your PCI BIOS is rev 2.1, use
ROUTEIRQ.EXE to route your selected IRQ to the CardBus bridge.
Developing device drivers and diagnostics for a Digital's CardBus device
that is downstream of a PCI-to-CardBus bridge (PCB) should be transparent.
Once the PCB is configured and the Digital's CardBus device is mapped into
I/O or memory space, the driver should function without knowing that there
is a PCI-to-CardBus bridge between it and the CardBus device that it is
driving (the Digital device will appear as a PCI device).
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
4. What Is and Isn't Supported in These Utilities
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
It is important to note here, that this section pertains to the utilities
only and not the different PCI to CardBus bridge chips.
The following is supported in this release of the utilities:
o Up to 16 PCI bridges (this include PCI-to-PCI bridge and PCI-to-CardBus
bridge)
o Up to 32 PCI devices per bus.
o Automatic I/O space mapping (4 Kb boundaries)
o Automatic non-prefetchable memory space mapping (1 Mb boundaries)
o BIOS enable command line switch
o Auto-detect and configuration of PCI devices
o Supports most of the PCI host bridge chipsets available today
o Easy to use interface
o TSR functionality that will intercept all 16 bit INT 1A BIOS calls
o Default configuration values used provide stable system environment
o Ability to use ISA interrupt or PCI interrupt for the CardBus boards
behind PCI-to-CardBus bridge
o Ability to set the interrupt line
The following is NOT supported in this release of the utilities:
o 32-bit protected mode BIOS calls or 16-bit protected BIOS calls.
o Support only Digital devices behind PCI-to-CardBus bridge.
o Doesn't support any kind of bridge behind the PCI-to-CardBus bridge.
o Using the ISA interrupt was not tested in this release and isn't
supported.
PCI to CardBus bridges Supported in this release:
o Texas Instruments' TI1130
o Toshiba
o Cirrus Logic's 6832
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
5. When Things Just Won't Work
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Since we are only using these utilities on PCI systems with BIOS that does
not support PCI-to-CardBus bridges yet, we need to configure the bridge and
map all Digital's CardBus devices downstream of (behind) the bridge. Some
PCI systems have host bridges that are incapable of generating the required
configuration cycles to access devices behind PCI-to-CardBus bridges.
There are three basic categories for PCI systems with respect to
PCI-to-CardBus bridge support:
type description
---- ----------------------------------
1 The hardware and BIOS supports PCI-to-CardBus bridges.
2 The hardware supports PCI-to-CardBus bridges but the BIOS doesn't.
3 The hardware doesn't support PCI-to-CardBus bridges.
For systems in the type 1 category, these utilities are not needed to
configure the system as the BIOS will do this for you.
Systems in type 2 category can take full advantage of these utilities.
Systems in the type 3 category should not be used as they are not compliant
with the PCI Local Bus Specification V2.x. Future expansion on these systems
is limited.
There are some systems that have host bridges that are slightly different
from what is required in the PCI Local Bus Specification.
Since the utilities are expecting the hardware to be compliant with the PCI
Local Bus Specification (with a few exceptions), it is almost impossible to
know about every quirk. The '-b' switch has been implemented on the ENABLER
utility and will allow the user to request the system BIOS generate the
low level I/O cycles.
Most system BIOS will know how to generate the correct configuration cycles,
they just won't auto configure bridges and devices behind them. If a
specific BIOS doesn't generate the correct configuration cycles, then don't
use this switch.
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.