eecs 373 design of microprocessor-based systems mark brehob
DESCRIPTION
Today Announcements Memory-mapped I/O and bus architecture review ARM’s APB bus in detail Start on interruptsTRANSCRIPT
![Page 1: EECS 373 Design of Microprocessor-Based Systems Mark Brehob](https://reader036.vdocuments.site/reader036/viewer/2022062311/5a4d1afd7f8b9ab059984c24/html5/thumbnails/1.jpg)
1
EECS 373Design of Microprocessor-Based Systems
Mark BrehobUniversity of Michigan
Lecture 5: Memory-mapped I/O review, APB, start interrupts. Mostly APB though
Sept 17th, 2013
![Page 2: EECS 373 Design of Microprocessor-Based Systems Mark Brehob](https://reader036.vdocuments.site/reader036/viewer/2022062311/5a4d1afd7f8b9ab059984c24/html5/thumbnails/2.jpg)
Today
• Announcements
• Memory-mapped I/O and bus architecture review
• ARM’s APB bus in detail
• Start on interrupts
![Page 3: EECS 373 Design of Microprocessor-Based Systems Mark Brehob](https://reader036.vdocuments.site/reader036/viewer/2022062311/5a4d1afd7f8b9ab059984c24/html5/thumbnails/3.jpg)
Announcements
• HW1a return
• Exam timing issues– Can’t have in class. Need to pick night (ick)
• Office hours shifts (updated on website)– Thursdays now 3:30-5:00– Mondays now 9:00-10:30
![Page 4: EECS 373 Design of Microprocessor-Based Systems Mark Brehob](https://reader036.vdocuments.site/reader036/viewer/2022062311/5a4d1afd7f8b9ab059984c24/html5/thumbnails/4.jpg)
Reading
• Scan chapter 9.2 of LeeSeshia.– I’d like you to read the whole thing but not worry
too much about getting it all. – Be aware their terminology is in some cases non-
standard (but then so is everyones)– They are software engineers, thinking about how
software should be written for an embedded system.• A higher-level of abstraction than we work at, but well
worth seeing!
![Page 5: EECS 373 Design of Microprocessor-Based Systems Mark Brehob](https://reader036.vdocuments.site/reader036/viewer/2022062311/5a4d1afd7f8b9ab059984c24/html5/thumbnails/5.jpg)
Today
• Announcements
• Memory-mapped I/O and bus architecture review
• ARM’s APB bus in detail
• Start on interrupts
![Page 6: EECS 373 Design of Microprocessor-Based Systems Mark Brehob](https://reader036.vdocuments.site/reader036/viewer/2022062311/5a4d1afd7f8b9ab059984c24/html5/thumbnails/6.jpg)
Memory-mapped I/O
• The idea is really simple– Instead of real memory at a given memory
address, have an I/O device respond.• Huh?
• Example:– Let’s say we want to have an LED turn on if we
write a “1” to memory location 8.– Further, let’s have a button we can read (pushed
or unpushed) by reading address 4.• If pushed, it returns a 1.• If not pushed, it returns a 0.
6
![Page 7: EECS 373 Design of Microprocessor-Based Systems Mark Brehob](https://reader036.vdocuments.site/reader036/viewer/2022062311/5a4d1afd7f8b9ab059984c24/html5/thumbnails/7.jpg)
Write assembly programs.
LED on if button pressed
LED off if button pressed
7
![Page 8: EECS 373 Design of Microprocessor-Based Systems Mark Brehob](https://reader036.vdocuments.site/reader036/viewer/2022062311/5a4d1afd7f8b9ab059984c24/html5/thumbnails/8.jpg)
Now write button pressed=LED on in C.
#define SW ((volatile uint32 *) 0x4)#define LED ((volatile uint32 *) 0x8)
main(int argc, char * argv[]){ while(1) *LED=*SW;}
8
1. What is uint32?2. Why volatile? What does that do?3. Could I get rid of the dereference in the code? Should I?
![Page 9: EECS 373 Design of Microprocessor-Based Systems Mark Brehob](https://reader036.vdocuments.site/reader036/viewer/2022062311/5a4d1afd7f8b9ab059984c24/html5/thumbnails/9.jpg)
9
#include <stdio.h>#include <inttypes.h>
#define REG_FOO 0x40000140
main () { uint32_t *reg = (uint32_t *)(REG_FOO); *reg += 3;
printf(“0x%x\n”, *reg); // Prints out new value}
A different example…
![Page 10: EECS 373 Design of Microprocessor-Based Systems Mark Brehob](https://reader036.vdocuments.site/reader036/viewer/2022062311/5a4d1afd7f8b9ab059984c24/html5/thumbnails/10.jpg)
10
“*reg += 3” is turned into a ld, add, str sequence
• Load instruction– A bus read operation commences– The CPU drives the address “reg” onto the address bus– The CPU indicated a read operation is in process (e.g. R/W#)– Some “handshaking” occurs– The target drives the contents of “reg” onto the data lines– The contents of “reg” is loaded into a CPU register (e.g. r0)
• Add instruction– An immediate add (e.g. add r0, #3) adds three to this value
• Store instruction– A bus write operation commences– The CPU drives the address “reg” onto the address bus– The CPU indicated a write operation is in process (e.g. R/W#)– Some “handshaking” occurs– The CPU drives the contents of “r0” onto the data lines– The target stores the data value into address “reg”
![Page 11: EECS 373 Design of Microprocessor-Based Systems Mark Brehob](https://reader036.vdocuments.site/reader036/viewer/2022062311/5a4d1afd7f8b9ab059984c24/html5/thumbnails/11.jpg)
Modern embedded systems have multiple busses
11
Atmel SAM3U
Historical 373 focus
Expanded373 focus
![Page 12: EECS 373 Design of Microprocessor-Based Systems Mark Brehob](https://reader036.vdocuments.site/reader036/viewer/2022062311/5a4d1afd7f8b9ab059984c24/html5/thumbnails/12.jpg)
Bus terminology
• Any given transaction have an “initiator” and “target”
• Any device capable of being an initiator is said to be a “bus master”– In many cases there is only one bus master
(single master vs. multi-master).
• A device that can only be a target is said to be a slave device.
• Some wires might be shared among all devices while others might be point-to-point connections (generally connecting the master to each target). 12
![Page 13: EECS 373 Design of Microprocessor-Based Systems Mark Brehob](https://reader036.vdocuments.site/reader036/viewer/2022062311/5a4d1afd7f8b9ab059984c24/html5/thumbnails/13.jpg)
Today
• Announcements
• Memory-mapped I/O and bus architecture review
• ARM’s APB bus in detail
• Start on interrupts
![Page 14: EECS 373 Design of Microprocessor-Based Systems Mark Brehob](https://reader036.vdocuments.site/reader036/viewer/2022062311/5a4d1afd7f8b9ab059984c24/html5/thumbnails/14.jpg)
14
APB is a fairly simple bus designed to be easy to work with.
• Low-cost
• Low-power
• Low-complexity
• Low-bandwidth
• Non-pipelined
• Ideal for peripherals
![Page 15: EECS 373 Design of Microprocessor-Based Systems Mark Brehob](https://reader036.vdocuments.site/reader036/viewer/2022062311/5a4d1afd7f8b9ab059984c24/html5/thumbnails/15.jpg)
Let’s just look at APB writes (Master writing to device)as a starting point. • We’ll add reads shortly.
15
![Page 16: EECS 373 Design of Microprocessor-Based Systems Mark Brehob](https://reader036.vdocuments.site/reader036/viewer/2022062311/5a4d1afd7f8b9ab059984c24/html5/thumbnails/16.jpg)
Notation
16
![Page 17: EECS 373 Design of Microprocessor-Based Systems Mark Brehob](https://reader036.vdocuments.site/reader036/viewer/2022062311/5a4d1afd7f8b9ab059984c24/html5/thumbnails/17.jpg)
APB bus signals
• PCLK – Clock
• PADDR– Address on bus
• PWRITE– 1=Write, 0=Read
• PWDATA– Data written to
the I/O device. Supplied by the bus master/processor.
17
![Page 18: EECS 373 Design of Microprocessor-Based Systems Mark Brehob](https://reader036.vdocuments.site/reader036/viewer/2022062311/5a4d1afd7f8b9ab059984c24/html5/thumbnails/18.jpg)
APB bus signals
• PSEL– Asserted if the current
bus transaction is targeted to this device
• PENABLE– High during entire
transaction other than the first cycle.
• PREADY– Driven by target.
Similar to our #ACK. Indicates if the target is ready to do transaction.Each target has it’s own PREADY
18
![Page 19: EECS 373 Design of Microprocessor-Based Systems Mark Brehob](https://reader036.vdocuments.site/reader036/viewer/2022062311/5a4d1afd7f8b9ab059984c24/html5/thumbnails/19.jpg)
So what’s happening here?
![Page 20: EECS 373 Design of Microprocessor-Based Systems Mark Brehob](https://reader036.vdocuments.site/reader036/viewer/2022062311/5a4d1afd7f8b9ab059984c24/html5/thumbnails/20.jpg)
Example setup
• For the next couple of slides, we will assume we have one bus master “CPU” and two slave devices (D1 and D2)– D1 is mapped to address 0x00001000-
0x0000100F – D2 is mapped to 0x00001010-
0x0000101F
![Page 21: EECS 373 Design of Microprocessor-Based Systems Mark Brehob](https://reader036.vdocuments.site/reader036/viewer/2022062311/5a4d1afd7f8b9ab059984c24/html5/thumbnails/21.jpg)
Say the CPU does a store to location 0x00001004with no stalls
21
D1
D2
![Page 22: EECS 373 Design of Microprocessor-Based Systems Mark Brehob](https://reader036.vdocuments.site/reader036/viewer/2022062311/5a4d1afd7f8b9ab059984c24/html5/thumbnails/22.jpg)
Design a device which writes to a register wheneverany address in its range is written
22
PWDATA[31:0]
PWRITE
PENABLE
PSEL
PADDR[7:0]
PCLK
PREADY
32-bit Reg
D[31:0] Q[31:0]EN C
We are assuming APB only gets lowest 8 bits of address here…
What if we want to have the LSB of this register control an LED?
![Page 23: EECS 373 Design of Microprocessor-Based Systems Mark Brehob](https://reader036.vdocuments.site/reader036/viewer/2022062311/5a4d1afd7f8b9ab059984c24/html5/thumbnails/23.jpg)
Reg A should be written at address 0x00001000Reg B should be written at address 0x00001004
23
PWDATA[31:0]
PWRITE
PENABLE
PSEL
PADDR[7:0]
PCLK
PREADY
32-bit Reg A
D[31:0] Q[31:0]EN C
We are assuming APB only gets lowest 8 bits of address here…
32-bit Reg B
D[31:0] Q[31:0]EN C
![Page 24: EECS 373 Design of Microprocessor-Based Systems Mark Brehob](https://reader036.vdocuments.site/reader036/viewer/2022062311/5a4d1afd7f8b9ab059984c24/html5/thumbnails/24.jpg)
Reads…
24
The key thing here is that each slave device has its own read data (PRDATA) bus!
![Page 25: EECS 373 Design of Microprocessor-Based Systems Mark Brehob](https://reader036.vdocuments.site/reader036/viewer/2022062311/5a4d1afd7f8b9ab059984c24/html5/thumbnails/25.jpg)
Let’s say we want a device that provides data froma switch on a read to any address it is assigned. (so returns a 0 or 1)
25
PRDATA[31:0]
PWRITE
PENABLE
PSEL
PADDR[7:0]
PCLK
PREADY
Mr. Switch
![Page 26: EECS 373 Design of Microprocessor-Based Systems Mark Brehob](https://reader036.vdocuments.site/reader036/viewer/2022062311/5a4d1afd7f8b9ab059984c24/html5/thumbnails/26.jpg)
Device provides data from switch A if address 0x00001000 is read from. B if address 0x00001004is read from
26
PRDATA[31:0]
PWRITE
PENABLE
PSEL
PADDR[7:0]
PCLK
PREADY
Switch A
Switch B
![Page 27: EECS 373 Design of Microprocessor-Based Systems Mark Brehob](https://reader036.vdocuments.site/reader036/viewer/2022062311/5a4d1afd7f8b9ab059984c24/html5/thumbnails/27.jpg)
All reads read from register, all writes write…
27
PWDATA[31:0]
PWRITE
PENABLE
PSEL
PADDR[7:0]
PCLK
PREADY
32-bit Reg
D[31:0] Q[31:0]EN C
We are assuming APB only gets lowest 8 bits of address here…
![Page 28: EECS 373 Design of Microprocessor-Based Systems Mark Brehob](https://reader036.vdocuments.site/reader036/viewer/2022062311/5a4d1afd7f8b9ab059984c24/html5/thumbnails/28.jpg)
28
A write transfer with wait states
Setup phase beginswith this rising edge
SetupPhase
Access
Phase
WaitState
WaitState
![Page 29: EECS 373 Design of Microprocessor-Based Systems Mark Brehob](https://reader036.vdocuments.site/reader036/viewer/2022062311/5a4d1afd7f8b9ab059984c24/html5/thumbnails/29.jpg)
29
A read transfer with wait states
Setup phase beginswith this rising edge
SetupPhase
Access
Phase
WaitState
WaitState
![Page 30: EECS 373 Design of Microprocessor-Based Systems Mark Brehob](https://reader036.vdocuments.site/reader036/viewer/2022062311/5a4d1afd7f8b9ab059984c24/html5/thumbnails/30.jpg)
Things left out…
• There is another signal, PSLVERR (APB Slave Error) which we can drive high if things go bad.– We’ll just tie that to 0.
• Notice we are assuming that our device need not stall.– We could stall if we needed.
• I can’t find a limit on how long, but I suspect at some point the processor would generate an error.
30
![Page 31: EECS 373 Design of Microprocessor-Based Systems Mark Brehob](https://reader036.vdocuments.site/reader036/viewer/2022062311/5a4d1afd7f8b9ab059984c24/html5/thumbnails/31.jpg)
Verilog!
31
/*** APB3 BUS INTERFACE ***/ input PCLK, // clock input PRESERN, // system reset input PSEL, // peripheral select input PENABLE, // distinguishes access phase output wire PREADY, // peripheral ready signal output wire PSLVERR, // error signal input PWRITE, // distinguishes read and write cycles input [31:0] PADDR, // I/O address input wire [31:0] PWDATA, // data from processor to I/O device (32 bits) output reg [31:0] PRDATA, // data to processor from I/O device (32-bits) /*** I/O PORTS DECLARATION ***/ output reg LEDOUT, // port to LED input SW // port to switch ); assign PSLVERR = 0; assign PREADY = 1;
![Page 32: EECS 373 Design of Microprocessor-Based Systems Mark Brehob](https://reader036.vdocuments.site/reader036/viewer/2022062311/5a4d1afd7f8b9ab059984c24/html5/thumbnails/32.jpg)
32
APB state machine
• IDLE– Default APB state
• SETUP– When transfer required– PSELx is asserted– Only one cycle
• ACCESS– PENABLE is asserted– Addr, write, select, and
write data remain stable
– Stay if PREADY = L– Goto IDLE if PREADY =
H and no more data– Goto SETUP is PREADY
= H and more data pending
We’ll spend a bit more time on this next week…
![Page 33: EECS 373 Design of Microprocessor-Based Systems Mark Brehob](https://reader036.vdocuments.site/reader036/viewer/2022062311/5a4d1afd7f8b9ab059984c24/html5/thumbnails/33.jpg)
Today
• Announcements
• Memory-mapped I/O and bus architecture review
• ARM’s APB bus in detail
• Start on interrupts
![Page 34: EECS 373 Design of Microprocessor-Based Systems Mark Brehob](https://reader036.vdocuments.site/reader036/viewer/2022062311/5a4d1afd7f8b9ab059984c24/html5/thumbnails/34.jpg)
Interrupts
Merriam-Webster: – “to break the uniformity or continuity of”
• Informs a program of some external events• Breaks execution flow
Key questions:• Where do interrupts come from?• How do we save state for later
continuation?• How can we ignore interrupts?• How can we prioritize interrupts?• How can we share interrupts?
34
![Page 35: EECS 373 Design of Microprocessor-Based Systems Mark Brehob](https://reader036.vdocuments.site/reader036/viewer/2022062311/5a4d1afd7f8b9ab059984c24/html5/thumbnails/35.jpg)
I/O Data Transfer
Two key questions to determine how data is transferred to/from a non-trivial I/O device:
1. How does the CPU know when data is available?a. Pollingb. Interrupts
2. How is data transferred into and out of the device?a. Programmed I/Ob. Direct Memory Access (DMA)
![Page 36: EECS 373 Design of Microprocessor-Based Systems Mark Brehob](https://reader036.vdocuments.site/reader036/viewer/2022062311/5a4d1afd7f8b9ab059984c24/html5/thumbnails/36.jpg)
Interrupts
Interrupt (a.k.a. exception or trap): • An event that causes the CPU to stop executing the current
program and begin executing a special piece of code called an interrupt handler or interrupt service routine (ISR). Typically, the ISR does some work and then resumes the interrupted program.
Interrupts are really glorified procedure calls, except that they:• can occur between any two instructions• are transparent to the running program (usually)• are not explicitly requested by the program (typically)• call a procedure at an address determined by the type of
interrupt, not the program
![Page 37: EECS 373 Design of Microprocessor-Based Systems Mark Brehob](https://reader036.vdocuments.site/reader036/viewer/2022062311/5a4d1afd7f8b9ab059984c24/html5/thumbnails/37.jpg)
Two basic types of interrupts(1/2)
• Those caused by an instruction– Examples:
• TLB miss• Illegal/unimplemented instruction• div by 0
– Names:• Trap, exception
![Page 38: EECS 373 Design of Microprocessor-Based Systems Mark Brehob](https://reader036.vdocuments.site/reader036/viewer/2022062311/5a4d1afd7f8b9ab059984c24/html5/thumbnails/38.jpg)
Two basic types of interrupts(2/2)
• Those caused by the external world– External device– Reset button– Timer expires– Power failure– System error
• Names:– interrupt, external interrupt
![Page 39: EECS 373 Design of Microprocessor-Based Systems Mark Brehob](https://reader036.vdocuments.site/reader036/viewer/2022062311/5a4d1afd7f8b9ab059984c24/html5/thumbnails/39.jpg)
How it works
• Something tells the processor core there is an interrupt
• Core transfers control to code that needs to be executed
• Said code “returns” to old program• Much harder then it looks.
– Why?
![Page 40: EECS 373 Design of Microprocessor-Based Systems Mark Brehob](https://reader036.vdocuments.site/reader036/viewer/2022062311/5a4d1afd7f8b9ab059984c24/html5/thumbnails/40.jpg)
… is in the details
• How do you figure out where to branch to?
• How to you ensure that you can get back to where you started?
• Don’t we have a pipeline? What about partially executed instructions?
• What if we get an interrupt while we are processing our interrupt?
• What if we are in a “critical section?”
![Page 41: EECS 373 Design of Microprocessor-Based Systems Mark Brehob](https://reader036.vdocuments.site/reader036/viewer/2022062311/5a4d1afd7f8b9ab059984c24/html5/thumbnails/41.jpg)
Where
• If you know what caused the interrupt then you want to jump to the code that handles that interrupt.– If you number the possible interrupt
cases, and an interrupt comes in, you can just branch to a location, using that number as an offset (this is a branch table)
– If you don’t have the number, you need to poll all possible sources of the interrupt to see who caused it.• Then you branch to the right code
![Page 42: EECS 373 Design of Microprocessor-Based Systems Mark Brehob](https://reader036.vdocuments.site/reader036/viewer/2022062311/5a4d1afd7f8b9ab059984c24/html5/thumbnails/42.jpg)
Get back to where you once belonged
• Need to store the return address somewhere.– Stack might be a scary place.
• That would involve a load/store and might cause an interrupt (page fault)!
– So a dedicated register seems like a good choice• But that might cause problems later…
![Page 43: EECS 373 Design of Microprocessor-Based Systems Mark Brehob](https://reader036.vdocuments.site/reader036/viewer/2022062311/5a4d1afd7f8b9ab059984c24/html5/thumbnails/43.jpg)
Snazzy architectures
• A modern processor has many (often 50+) instructions in-flight at once.– What do we do with them?
• Drain the pipeline?– What if one of them causes an
exception?• Punt all that work
– Slows us down• What if the instruction that caused
the exception was executed before some other instruction?– What if that other instruction caused an
interrupt?
![Page 44: EECS 373 Design of Microprocessor-Based Systems Mark Brehob](https://reader036.vdocuments.site/reader036/viewer/2022062311/5a4d1afd7f8b9ab059984c24/html5/thumbnails/44.jpg)
Nested interrupts
• If we get one interrupt while handling another what to do?– Just handle it
• But what about that dedicated register?
• What if I’m doing something that can’t be stopped?
– Ignore it• But what if it is important?
– Prioritize• Take those interrupts you care about.
Ignore the rest• Still have dedicated register problems.
![Page 45: EECS 373 Design of Microprocessor-Based Systems Mark Brehob](https://reader036.vdocuments.site/reader036/viewer/2022062311/5a4d1afd7f8b9ab059984c24/html5/thumbnails/45.jpg)
Critical section
• We probably need to ignore some interrupts but take others.– Probably should be sure our code can’t cause an
exception.– Use same prioritization as before.
![Page 46: EECS 373 Design of Microprocessor-Based Systems Mark Brehob](https://reader036.vdocuments.site/reader036/viewer/2022062311/5a4d1afd7f8b9ab059984c24/html5/thumbnails/46.jpg)
Our processor
• Over 100 interrupt sources– Power on reset, bus errors, I/O pins changing
state, data in on a serial bus etc.• Need a great deal of control
– Ability to enable and disable interrupt sources– Ability to control where to branch to for each
interrupt– Ability to set interrupt priorities
• Who wins in case of a tie• Can interrupt A interrupt the ISR for interrupt
B?– If so, A can “preempt” B.
• All that control will involve memory mapped I/O.– And given the number of interrupts that’s going
to be a pain in the rear. 46
![Page 47: EECS 373 Design of Microprocessor-Based Systems Mark Brehob](https://reader036.vdocuments.site/reader036/viewer/2022062311/5a4d1afd7f8b9ab059984c24/html5/thumbnails/47.jpg)
47
Enabling and disabling interrupt sources
![Page 48: EECS 373 Design of Microprocessor-Based Systems Mark Brehob](https://reader036.vdocuments.site/reader036/viewer/2022062311/5a4d1afd7f8b9ab059984c24/html5/thumbnails/48.jpg)
How to know where to go on an interrupt.
48