Lecture#4 - Top Level View of Computer Function and Interconnection
Lecture#4 - Top Level View of Computer Function and Interconnection
52
•The PCI Bus was
originally 33Mhz and
then changed to
66Mhz.
•PCI Bus became big
with the release of
Windows 95 with
“Plug and Play”
technology
•“Plug and Play”
utilized the PCI bus
concept.
53
Bus Bus Speed MB/sec Advantages Disadvantages
Bus Type Width
PCI 64 bits 133 MHz 1 GBps very high speed, incompatible with
Plug & Play, older systems,
dominant board- can cost more
level bus
CompactPCI 64 bits 33MHz 132 MBps designed for lower speed than
industrial use, hot PCI, need adapter for
swapping/Plug & PC use, incompatible
Play, ideal for with older systems
embedded
systems
Table 1: How PCI compares to other buses (Tyson, 2004a; Quatech, 2004c)
56
Requirements for Tasks it
full automates:
implementation: ◦ Interrupt Requests
(IRQ)
◦ Plug and Play BIOS
◦ Direct Memory
◦ Extended System Access (DMA)
Configuration Data ◦ Memory Addresses
(ESCD) ◦ Input/Output (I/O)
◦ Plug and Play Configuration
operating system
(Tyson, 2004b)
57
In a typical system, the firmware (or operating
system) queries all PCI buses at startup time (via
PCI Configuration Space) to find out what devices
are present and what system resources (memory
space, I/O space, interrupt lines, etc.) each
needs.
It then allocates the resources and tells each
device what its allocation is.
The PCI configuration space also contains a small
amount of device type information, which helps
an operating system choose device drivers for it,
or at least to have a dialogue with a user about
the system configuration.
Systems lines
◦ Including clock and reset
Address & Data
◦ 32 time mux lines for address/data
◦ Interrupt & validate lines
Interface Control
Arbitration
◦ Not shared
◦ Direct connection to PCI bus arbiter
Error lines
Interrupt lines
◦ Not shared
Cache support
64-bit Bus Extension
◦ Additional 32 lines
◦ Time multiplexed
◦ 2 lines to enable devices to agree to use 64-bit
transfer
JTAG/Boundary Scan
◦ For testing procedures These signal lines support
testing procedures defined in IEEE Standard 1149.1.
Transaction between initiator (master) and
target
Master claims bus
Determine type of transaction
◦ e.g. I/O read/write
Address phase
One or more data phases
Stallings, chapter 3 (all of it)
www.pcguide.com/ref/mbsys/buses/