cpe/ee 421 microcomputers - engineering - …milenka/cpe421-05f/notes/cpe421-s24_21.pdf · cpe/ee...

Alex Milenkovich 1

CPE/EE 421/521 Microcomputers 1

U

A

HU

A

H

U

A

H

CPE/EE 421Microcomputers

Instructor: Dr Aleksandar MilenkovicLecture Note

S24


U

A

HU

A

H

U

A

HCourse Administration

Instructor: Aleksandar [email protected]/~milenkaEB 217-LMon. 5:30 PM – 6:30 PM, Wen. 12:30 – 13:30 PM

URL: http://www.ece.uah.edu/~milenka/cpe421-05F

TA: Joel Wilder

Labs: hw3&lab5 due on 11/28/05.

Text: Microprocessor Systems Design: 68000 Hardware, Software, and Interfacing

Today: M68000 Hw

Review: Chapter 4, Chapter 5, Chapter 6 (M68K hw)

Alex Milenkovich 2


U

A

HU

A

H

U

A

H

THE 68000 CPU HARDWARE MODELChapter 4

68000 interface

Timing diagram

Minimal configuration using the 68000


U

A

HU

A

H

U

A

HReview: 68000 Interface

M68000: 64 pins, arranged in 9 groups: Address Bus: A01 – A23

Data Bus: D00 – D15

Asynchronous bus control: AS*, R/W*, UDS*, LDS*,DTACK*, BERR*

Synchronous bus control: E, VPA*, VMA*Bus arbitration control: BR*, BG*, BGACK*Function code: FC0, FC1, FC2System control: CLK, RESET*, HALT*Interrupt control: IPL0*, IPL1*, IPL2*Miscellaneous: Vcc(2), Gnd(2)

Legend: Type• XX Input• XX Output• XX Input/Output

Alex Milenkovich 3


U

A

HU

A

H

U

A

H

Review: Memory and Peripheral Interface Pins

Figure 4.3


U

A

HU

A

H

U

A

H

Review:Special-Function Pins of the 68000

Function Code Output FC2 FC1 FC0 Processor Cycle Type

0 0 0 Undefined, reserved 0 0 1 User data 0 1 0 User program 0 1 1 Undefined, reserved 1 0 0 Undefined, reserved 1 0 1 Supervisor data 1 1 0 Supervisor program 1 1 1 CPU space (interrupt acknowledge)

Function Code Output FC2 FC1 FC0 Processor Cycle Type

0 0 0 Undefined, reserved 0 0 1 User data 0 1 0 User program 0 1 1 Undefined, reserved 1 0 0 Undefined, reserved 1 0 1 Supervisor data 1 1 0 Supervisor program 1 1 1 CPU space (interrupt acknowledge)

Alex Milenkovich 4


U

A

HU

A

H

U

A

H

Review: Special-Function Pins of the 68000, cont’dUsing the 68000’s function code outputs

User data memory

User program memory

Supervisor program and data memory

Figure 4.8


U

A

HU

A

H

U

A

HReview: Special-Function Pins of the 68000, cont’dAsynchronous Bus Control

The 68000 is not fully asynchronous because its actions are synchronized with a clock input

It can prolong a memory access until an ACK is received, but it has to be in increments of one clock cycle

Figure 4.11

Alex Milenkovich 5


U

A

HU

A

H

U

A

H

3 tcyc = tCLAV + tacc + tDICL

Review: Bus Read Cycle


U

A

HU

A

H

U

A

H

Figure 4.14

A 68000 Read Cycle

Alex Milenkovich 6


U

A

HU

A

H

U

A

H

Figure 4.15

Extended Read Cycle

DTACK* did not go low at least 20ns before the falling edge of state S4

Designer has to provide logic to control DTACK*


U

A

HU

A

H

U

A

H

Figure 4.18

Memory Timing Diagram

The 6116 static memory component2K x 8bit memory – byte-oriented!Two 6116’s configured in parallel to allow word accessesEleven address inputs

Alex Milenkovich 7


U

A

HU

A

H

U

A

H

Figure 4.17

Assumptions:R/W* is high for the duration of the read cycleOE* is low

Memory Timing Diagram, cont’d(min 200ns – address stable)

(max 200ns)

(max 15ns)

Data is floating

(max 50ns)

(usually derived from UDS*/LDS*)


U

A

HU

A

H

U

A

HD00

D07

D08

D15

A12

A23

A01

A11

A01

A11

A01

A11

Figure 4.19

Connec

ting T

he

6116 R

AM

to a

68000 C

PU

No operation111100Lower byte read010100Upper byte read101000

Word read000000No operation11XX1XNo operation11XXX1OperationCS2*CS1*LDS*UDS*RAMCS*AS*

OutputsInputs

Alex Milenkovich 8


U

A

HU

A

H

U

A

H

Figure 4.20

Connec

ting T

he

6116 R

AM

to

a 68000 C

PUTim

ing D

iagra

m

Turnoff time70+10+60 =

140ns

70ns

10ns

60ns


U

A

HU

A

H

U

A

HTiming Example

68000 clock 8 MHz tCYC = 125 ns68000 CPU tCLAV = 70 ns68000 CPU tDICL = 15 nsWhat is the minimum tacc?3 × tCYC > tCLAV + tacc + tDICL

375 > 70 + tacc + 15tacc < 290 ns (or tAA from the timing diagram, access time)

For the 12.5MHz version of 68000 tCYC = 80 ns68000 CPU tCLAV = 55 ns68000 CPU tDICL = 10 ns3×80 > 55 + tacc + 10tacc < 175 ns

Remember, maximum tAA for the 6116 RAM was 200 ns

Alex Milenkovich 9


U

A

HU

A

H

U

A

H

68000 Write Cycle

68000 transmits a byte or a word to memory or a peripheral

Essential differences:The CPU provides data at the beginning of a write cycleOne of the bus slaves (see later) reads the data

In a read cycle DS* and AS* were asserted concurrentlyThis will be not a case here!

Reason for that: 68000 asserts DS* only when the contents of data bus have stabilized

Therefore, memory can use UDS*/LDS* to latch data from the CPU


U

A

HU

A

H

U

A

HSimplified write cycle timing diagram

In a write cycle: UDS*/LDS* is asserted

one cycle after AS*

Figure 4.22

Alex Milenkovich 10


U

A

HU

A

H

U

A

H

Figure 4.23

Follow this sequence of events in a write cycle:

Address stableAS* assertedR/W* brought lowData validDS* asserted


U

A

HU

A

H

U

A

H

Figure 4.24

Write Cycle Timing Diagram of a 6116 RAM

Address setup time(min 20ns)

Address valid to end of write(min 120ns)

Write pulse width(min 90ns)

Write recovery time(min 10ns)

Alex Milenkovich 11


U

A

HU

A

H

U

A

H

Write Cycle Timing Diagram of a 6116 RAM, cont’d

Write cycle ends with either CS* or WE* being negated (CS* and WE* internally combined)

An address must be valid for at least tAS nanoseconds before WE* is asserted

Must remain valid for at least tWR nanoseconds after WE* is negated

Data from the CPU must be valid for at least tDW nanoseconds before WE* is negated

Must remain valid for at least tDH nanoseconds after the end of the cycle


U

A

HU

A

H

U

A

H

Designing a Memory Subsystem, an example

Design a M68000 memory subsystem usingTwo 32K × 8 RAM chips residing at address $00 8000Two 8K × 8 RAM chips residing in the consecutive windowLS 138 (3 to 8 decoder) and basic logic gates

Solution32K is 4 × 8K

=> Let’s split the address space into 8K modulesIn total, we have five (4+1) 8K windowsTo address each line in 8K window

=> 13 bits (23*210 = 213 = 8K)To address five modules we need 3 bitsDon’t forget that there is no A0, we will use LDS/UDS

Alex Milenkovich 12


U

A

HU

A

H

U

A

H


A Q0

Q1

Q2

Q3

Q4

Q5

Q6

Q7

B

C

LS138

E1

E2

E3

A14

A16A15

AS*

LDS*

A17

A23

...

R1CSL*

RAM2*Vcc

RAM1*

UDS*

R2CSL*

R1CSU*

R2CSU*

A23 A22 A21 A20 A19 A18 A17 A16 A15 A14 A13 A12 A11 A10 A09 A08 A07 A06 A05 A04 A03 A02 A01 A00

address within 8K modulemodule address

UDS LDS

0 0 8 0 0 0


U

A

HU

A

H

U

A

H


RAM32Kx8

A0

A14

...

CE*OE*

D0

D7D6

D5

D4

D3

D2

D1

RAM32Kx8

A0

A14

...

CE*OE*

D0

D7D6

D5

D4

D3

D2

D1

RAM8Kx8

A0

A12

...

CE*OE*

D0

D7D6

D5

D4

D3

D2

D1

WE*

A13

A1

A15

A1

D7D6D5D4D3D2D1D0

A1..A23

A15

A1

D0..D15

R/W*

R1CSL* R1CSLU*

R2CSL* R2CSLU*

RAM8Kx8

A0

A12

...

CE*OE*

D0

D7D6

D5

D4

D3

D2

D1

WE*

A13

A1

R/W*

WE*R/W* WE*R/W*

D7D6D5D4D3D2D1D0

D15D14D13D12D11D10D9D8

D15D14D13D12D11D10D9D8

Alex Milenkovich 13


U

A

HU

A

H

U

A

H

Figure 4.9

Interrupt Control Interface (details later)

priority

low

high


U

A

HU

A

H

U

A

H

Data bus

Address bus

Control bus

Arbitration bus

Slave module

Memory

Master module

Local memory

CPU

I/O

Master module

Local memory

CPU

I/O

Bus Arbitration ControlWhen 68000 controls the address and data buses, we call it the bus master

The 68000 may allow another 68000 or DMA controller to take control over buses

In the system with only one bus master, 68000 would have permanent control of the address and data buses

Alex Milenkovich 14


U

A

HU

A

H

U

A

HBus Arbitration Control, cont’d

68000 must respond to BR* request (it cannot be masked)

Assertion of BG* indicates that the bus will be given up at the end of present bus cycle

Requesting device waits until AS*, DTACK*, and BGACK* have been negated, and only then asserts its own BGACK* output

Old master negates its BG*, and BR* can be asserted by another potential master


U

A

HU

A

H

U

A

H

Figure 4.27a

Data Bus Contention in Microcomputers

Situation where more than one device attempts to drive the bus simultaneously

Example: Two memory modules, M1 selected during read cycle 1, M2 selected during read cycle 2

Assumption: M1 has data bus drivers with relatively long turn-off timesM2 has data bus drivers with relatively short turn-on times

Alex Milenkovich 15


U

A

HU

A

H

U

A

H

Long turn-off time

Data Bus Contention in Microcomputers, cont’d

Short turn-on time


U

A

HU

A

H

U

A

HBus Contention and Data Bus Transceivers

Data bus transceiver – consists of a transmitter (driver) and a receiverDriver – tristate output, can be driven high, low, or internally disconnected form the rest of the circuitTwo control inputs: Enable (active low) and DIR (direction)Dynamic data bus contention

Alex Milenkovich 16


U

A

HU

A

H

U

A

H

Minimal Configuration Using The 68000


U

A

HU

A

H

U

A

H

DESIGN CONSTRAINTS

Used in stand-alone mode

Classroom teaching aid

16 KB EPROM-based monitor

Speed is not important

At least 4 KB RAM

1 serial and 1 parallel port

Memory expandable

No interrupts and multiple processors

Alex Milenkovich 17


U

A

HU

A

H

U

A

H

MAJOR COMPONENTS

ROM – Two 8K × 8 components

RAM – Two 2K × 8 components

Parallel – 6821 Peripheral Interface Adapter (PIA)

Serial – 6850 Asynchronous Comm. Interface Adapter (ACIA)


U

A

HU

A

H

U

A

H

DESIGH CHOICES

Chose the location of ROM (16KB) and RAM (8 KB) within the address space (16 MB)

Unimportant, as long as the reset vectors are located at $00 0000

Chose the location of memory-mapped peripherals

Control of DTACK* (is delay applied or not?)

Alex Milenkovich 18


U

A

HU

A

H

U

A

H

The 68000’s Reset Sequence

Fetch SSP fromaddress 0

RESET SEQUENCE

Set SR S bit to 1Set SR T bit to 0

Set SR mask to 111

Transfer longwordto SSP

Fetch initial PC fromaddress 4

Transfer longwordto PC

Begin processing inthe supervisor state

Bus erroroccurs?

Double buserror

Bus erroroccurs?

FATALERROR


U

A

HU

A

H

U

A

H

REMEMBER

When the RESET* pin is asserted for the appropriate duration:

SR = $2700SSP is loaded with the longword @ $00 0000PC is loaded with the longword @ $00 0004

Alex Milenkovich 19


U

A

HU

A

H

U

A

H

Blo

ck D

iagra

m o

f a

68000-b

ased

mic

roco

mpute

r

Figure 4.43


U

A

HU

A

H

U

A

H

Memory and Peripheral Components

We assigned address lines to address pins, and data lines to data pins.

Before designing logic that will generate chip select signals, we have to decide about RAM/ROM location.

To assure that the reset vector location is at $00 0000, let’s situate 16 KB of ROM at $00 0000

Alex Milenkovich 20


U

A

HU

A

H

U

A

H

Mem

ory

and P

erip

her

al C

om

ponen

ts

Figure 4.44


U

A

HU

A

H

U

A

H

Control Section

We will divide the memory space $00 0000 - $01 FFFF into eight blocks of 16 KB (IC1a,b, IC2a, IC3)

16 KBytes of ROM are at $00 0000 to $00 3FFF

Where is the RAM situated? Peripherals?

Note: there is no delay applied to DTACK*.

What will happen if we access non-decoded memory?

Alex Milenkovich 21


U

A

HU

A

H

U

A

H

Contr

ol Sec

tion

Figure 4.45


U

A

HU

A

H

U

A

HDifferent approaches to memory arrangement

Largest memory window (16 KB)[MEMORY GAPS]

A23 A17A16A15A14A13 A1

SELECT DECODER

DECODER

Alex Milenkovich 22


U

A

HU

A

H

U

A

HDifferent approaches to memory arrangement, cont’d

Smallest memory window (4 KB)[NO MEMORY GAPS]

A23 A15A14A13A12A11 A1

SELECT DECODER

DECODER

A Q0

Q1

Q2

Q3

Q4

Q5

Q6

Q7

B

C

E1

E2

E3

A12

A14A13

ROM (16 KB)4 Windows (Blocks)

RAM

A23...

AS*A15

Vcc


U

A

HU

A

H

U

A

HHow can we make it better?

ROM is EPROM-based, and thus slower

With EPROMs from the same generation, we’ll need wait states, maybe even with RAM components

Watchdog for non-decoded memory addresses

Alex Milenkovich 23


U

A

HU

A

H

U

A

H

How

can

we

mak

e it b

ette

r?

Figure 4.46


U

A

HU

A

H

U

A

HHow can we make it better? Cont’d

CONTROL OF INTERRUPTSUse 74LS148 priority encoder to provide 7 levels of interrupt

EXTERNAL BUS INTERFACECPU can supply only the limited current to drive the busSOLUTION: Bus drivers (buffers)

Alex Milenkovich 24


U

A

HU

A

H

U

A

HDTACK* Generation

DTACK* generator based on a shift register

Figure 4.72


U

A

HU

A

H

U

A

HDTACK* GenerationShift register and its timing diagram

Alex Milenkovich 25


U

A

HU

A

H

U

A

HDTACK* GenerationShift register and its timing diagram


U

A

HU

A

H

U

A

HDTACK* GenerationDTACK* generator based on a counter

Figure 4.74

Alex Milenkovich 26


U

A

HU

A

H

U

A

H

Interrupt Processing Mechanism

Interrupt is an asynchronous event

When an interrupt occur, the computer can: Service it Ignore it (for the time being)


U

A

HU

A

H

U

A

H

Figure 4.9

Interrupt Control Interface (details later)

priority

low

high

Alex Milenkovich 27


U

A

HU

A

H

U

A

HInterrupt processing mechanism, cont’d

Sequence of actions when an interrupt is being serviced:

1. The computer completes its current machine-level instruction

2. The contents of PC is saved (on stack)

3. The state of the processor (status word) is saved on the stack

4. Jump to the location of the interrupt handling routine


U

A

HU

A

H

U

A

H

Interrupt processing mechanism, cont’d

The interrupt is transparent to the interrupted program

Interrupt request: Can be deferred or denied When it is deferred, it is said to be maskedSpecial one: nonmaskable interrupt request (NMI)The 68000 NMI: IRQ7 (MSP430: RST*/NMI pin)

Prioritized interrupts

Vectored interrupts Requesting peripheral identifies itself, CPU doesn’t have to poll the status of each device to discover the interrupter

Alex Milenkovich 28


U

A

HU

A

H

U

A

H

The

68000 I

nte

rrupt

Inte

rfac

e


U

A

HU

A

H

U

A

HThe 68000 Interrupt Interface

Alex Milenkovich 29


U

A

HU

A

H

U

A

H

The 68000 Interrupt Interface

Reset, bus error, address error, and trace exceptions take precedence over an interrupt

A level 7 interrupt CAN interrupt level 7 interrupt


U

A

HU

A

H

U

A

H

Pro

cess

ing t

he

Inte

r rupt

Alex Milenkovich 30


U

A

HU

A

H

U

A

H

Interrupt Timing Diagram


U

A

HU

A

H

U

A

H

Ve c

tor e

d I

nte

rrupts

cpe/ee 421 microcomputers - engineering - …milenka/cpe421-05f/notes/cpe421-s24_21.pdf · cpe/ee...

Documents