410 likes | 673 Views
Computer Architecture. Lecture10: Input/output devices Piotr Bilski. Communication with input/output devices. Device is connected with the system bus by the I/O module Speed of the devices and the bus is different – a bridge may be needed!
E N D
Computer Architecture Lecture10: Input/output devices Piotr Bilski
Communication with input/output devices • Device is connected with the system bus by the I/O module • Speed of the devices and the bus is different – a bridge may be needed! • Data formats in the computer system are different for the CPU and I/O devices are different
I/O module scheme Address lines Data lines Control lines Input/output module Peripherial device
External devices • for human communication (monitor, printer) • for machine communication (CD drive) • for remote communication (modem, network interface)
Peripherial device scheme Input/output module Control signals State signals I/O module data Buffer Logical control units Converter I/O external data
Input/output module • control and timing • CPU communication • device communication • data buffering • error detection Classification:
Communication between CPU and module • instruction decoding • data transfer • state information transfer • address identification
Cooperation between CPU and peripherial device • CPU requires device state • I/O module sends information about device state • if device is working, CPU sends data transfer request • I/O module receives data unit from the peripherial device and sends to CPU
I/O modules types • Input/output channel – more complex, performs most of the work related to the communication and device handling (mainframe computers) • Device driver – simple, most of the functions are performed by the software (personal computers)
Input/output techniques • Programmable input/output – high processor load • Interrupt driven input/output – low processor load • Direct memory access – processor is not required
Programmable input/output • CPU sends I/O instructions to the module. It must control read/write process (when output data are accessible?) • Instructions fetched from the memory are mapped into the instructions sent to the I/O module • Disadvantage: processor idle most of the time
Input/output instructions • control (specific for the particular devices) • testing (device state and result of the last operation) • read • write
Programmable input/output scheme Sending read instru-ction to the module CPU I/O Reading I/O module state I/O CPU Error handling State? Not ready Ready Reading word for I/O module I/O CPU NO YES Writing word into memory CPU I/O Execution? Next instruction
Input/output instructions • I/O devices addressing problem: • Memory mapped I/O • Isolated input/output • Start I/O 5 • 201 Test I/O 5 • 203 Branch if St=0 201 • 204 In 5 • Load AC 1 • 201 Store AC 517 • 202 Load AC 517 • 203 Branch if St=0 202 • 204 Load AC 516 (a) (b)
Interrupt-driven Input/output • CPU sends requests to the I/O module, but does not wait for the response • when module is ready to communicate with CPU, raises interrupt signal • CPU in every instruction cycle checks if the interrupt was raised • disadvantage: CPU communicates between peripherials and memory
Interrupt handling scheme CPU I/O Send read instru-ction to the module CPU does something different interrupt!!!! Read I/O module state I/O CPU Error handling State? Ready Read word from I/O module I/O CPU NO YES Writing word into memory CPU I/O Execution? Next instruction
Interrupt handling details hardware software Device driver raises interrupt Saving informations about the process state CPU ends instruction execution Interrupt handling CPU signals interrupt confirmation Restoring information about the process state CPU puts PSW and PC on the stack Restoring PSW and PC CPU loads new PC value (interrupt handling)
Multiple devices handling problem • multiple interrupt lines • Software poll • Hardware poll • bus master (PCI, SCSI) Interrupt lines I/O module devices connections
Daisy chain • module signalizes raising interrupt putting a vector on the data bus bus terminator bus terminator Module 1 Module 2
Interrupt controller Intel 82C59A Slave interrupt controller 82C59 Master interrupt controller 82C59 • with priorities • rotational • maskable Device no 1 CPU 386 IR0 IR1 IR2 IR3 IR4 IR5 IR6 IR7 INT Device no 2 IR0 IR1 IR2 IR3 IR4 IR5 IR6 IR7 INTR INTA INT Slave interrupt controller 82C59 IR0 IR1 IR2 IR3 IR4 IR5 IR6 IR7 INT
ISA bus interrupt system • Two chained 8259 modules • Connection with modules is performed through IRQ 2 • IRQ 9 is used to redirect requests to IRQ 2 • 15 interrupt lines to the chain
Programmable interface for the peripherial devices Intel 82C55A • I/O module used by the 80386 processor • Module programmable by the control register (versatility) • 40 signal lines: • 24 input/output lines • 8 data lines (bits) • 2 address lines
Direct memory access (DMA) • Allows to transfer large amounts of data to/from memory without bothering CPU • Faster than interrupt-driven communication
DMA module scheme Data counter • Memory module „pretends” to be CPU (cycle stealing) Data register Data l,ines Address register Address lines DMA REQ DMA ACK INTR READ WRITE Control logic circuits
DMA work regime • informations requested by the CPU from the DMA controller: • Read or write • Peripherial device address • First memory cell address to read/write • Number of the words for read/write • CPU executes subsequent program instructions • DMA controller controls the flow of information between the peripherials and memory • When the task is finished, the controller raises interrupt
DMA control points Instruction cycle Instruction fetching Instruction decoding Argument fetching Instruction execution Saving result Process interrupt Interrupt control point DMA control points
DMA configurations • Single bus for all modules, software control of input/output • Single bus, integrated DMA • Input/output bus – separated for the peripherials, DMA module is a bridge
Single bus, detached DMA controller • CPU suspension performed twice during the peripherial device communication • bus also used twice
Single bus, integrated DMA controller • DMA controller supports more than one device • transfer requires one bus access, similarly with the CPU suspension
Input/ouput bus • One bus access (DMA to memory) • CPU suspended once
External interfaces types • Parallel interface – multiple lines, fast devices (hard drives) • Serial interface – single line, slow devices (printers) • Two-point connection • Multi-point connection • I/O module must have a buffer for storing data to/from peripherial device
FireWire serial bus • IEEE-1394 standard • Single data line does not require shielding • Devices form daisy chain or tree, to one port 63 devices can be plugged in • hot plugging of the devices
FireWire configuration • No terminators!!
FireWire protocols layers • Physical layers • defines arbitration, data synchronization, coding-decoding, link state, interfaces, signal levels • Link layer • Data transmission (sending and receiving packets, cyucle control) • Transactional layer • Read, write, blocking