1 / 23

ECE 412: Microcomputer Laboratory

ECE 412: Microcomputer Laboratory. Lecture 7: Hardware/Software Systems on the XUP Board. Outline. Overview of Linux/HW interaction on the XUP board Resources available for you on the board Discussion of the Virtex-II Pro’s BlockRAMs. Review Questions.

gyan
Download Presentation

ECE 412: Microcomputer Laboratory

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. ECE 412: Microcomputer Laboratory Lecture 7: Hardware/Software Systems on the XUP Board Lecture 7

  2. Outline • Overview of Linux/HW interaction on the XUP board • Resources available for you on the board • Discussion of the Virtex-II Pro’s BlockRAMs Lecture 7

  3. Review Questions • What function does the mmap() call serve in implementing memory-mapped I/O? • What are the two alternatives of communicating between the devices and the processor? Comparison of these methods? Lecture 7

  4. Review Questions • What function does the mmap() call serve in implementing memory-mapped I/O? • mmap() causes a set of device registers or other data to be mapped onto a region in the address space • What are the two alternatives of communicating between the devices and the processor? Comparison of these methods? • Polling: • takes CPU time even if no requests pending • can be better if the processor has nothing better to do and has to respond to an event ASAP • Interrupts: • no overhead when no requests pending • can be better if the processor has other work to do and the time to respond to events isn’t absolutely critical (need context switching) Lecture 7

  5. The XUP Board XUP Board FPGA PowerPC FLASH Card VGA Audio In/Out Serial Port Ethernet SDRAM I/O Connector I/O Connector Lecture 7

  6. Pure-Hardware System XUP Board FPGA PowerPC FLASH Card VGA Audio In/Out Logic Serial Port Ethernet SDRAM I/O Connector I/O Connector Lecture 7

  7. XUP Board as PC XUP Board FPGA PowerPC FLASH Controller FLASH Card VGA Controller VGA PLB Bus Audio Controller Audio In/Out UART Controller Serial Port Ethernet Controller Ethernet SDRAM Controller SDRAM I/O Connector I/O Connector Lecture 7

  8. ECE 412 Approach -- HW/SW System XUP Board FPGA PowerPC FLASH Controller FLASH Card VGA Logic PLB Bus Audio In/Out Serial Port UART Controller Ethernet SDRAM Controller SDRAM I/O Connector I/O Connector Lecture 7

  9. MP2 Configuration XUP Board FPGA PowerPC FLASH Controller FLASH Card VGA Logic PLB Bus Audio In/Out Core OPB Serial Port UART Controller Ethernet SDRAM Controller SDRAM I/O Connector I/O Connector Lecture 7

  10. Embedded Power PC 405 Core Lecture 7

  11. PPC • Functional blocks • Cache units (ICU and DCU, 16 KB each) • Memory Management unit • Fetch Decode unit • Execution unit • Timers • Debug logic unit • It operates on instructions in a five stage pipeline consisting of • fetch, decode, execute, write-back, and load write-back • Most instructions execute in a single cycle, including loads and stores. Lecture 7

  12. Creating a HW/SW System • Custom logic needs to conform to bus/interface protocols • We’ll provide documentation about this • For MP2.1, we provide a prototype for the function you have to write (In VHDL) • Assemble custom logic, IP cores, software into a package that can be downloaded onto the board • EDK tool creates bit file for FPGA • SystemACE HW loads Linux/other SW off of FLASH card • Can also pre-load BlockRAMs w/data as part of FPGA programming Lecture 7

  13. Interfaces to the PowerPC Cores • Processor Local Bus (PLB) • 64-bit bus that handles fast data transfers with the PowerPC and the peripherals • For example, DDR controller hangs on this bus • There is also a 32-bit bus called OPB (On-Chip Peripheral Bus) that handles slower peripheral devices • For example, for UART and SystemACE access • Needs to connect to PLB via a special PLB-to-OPB bridge • OCM (On-Chip Memory) Controller • Allows memory (BlockRAMs) to be accessed at rates comparable to the caches • Great way to build data buffers • Interrupt Controller • Device Control Register • Allows creation of a register file that is “shared” among all of the devices connected to the PowerPC • Clock, Power Management • JTAG Port Lecture 7

  14. Other Resources • SDRAM • Lots of space, complex interface requirements • Controlled via IP core • Your HW can interface with core, simplifying things • BlockRAM • Small, on-chip memory • Can be configured in a number of ways • Fast, simple interface Lecture 7

  15. Virtex Block SelectRAM • 18Kb capacity and configurable at build time to be either: 1 x 16K 2 x 8K 4 x 4K 8 x 2K 16 x 1K 32 x 512 • 136 of these on each XC2VP30 FPGA for total of 2.4Mb total • Dual ported, can be aggregated to form larger structures • Parity bits, possible to pre-load with data in VHDL Lecture 7

  16. Generic Block Diagrams Lecture 7

  17. Interface Signals Lecture 7

  18. Supported Configurations • Your VHDL will instantiate using primitives • Each reference is an individual BRAM • Could form larger memory block by assembling number of primitives, routing delay would determine total access time. Lecture 7

  19. Physical Location Lecture 7

  20. Read and Write Timing Refer to posted application notes for exact details: • XAPP-463 (says Spartan-3 but is applicable to our parts) • XAPP-130 (basic operation, but is for early smaller BRAMS) Lecture 7

  21. Instantiating BlockRAMs • Declare as components, can instantiate multiple copies of a component component RAMB16_s9 Port ( clk : in std_logic; ... ); end component; • Documentation section of the web page has instructions on simulating designs that use BlockRAM, example that links multiple BlockRAMs to form larger memory Lecture 7

  22. Uses for BlockRAMs • “Scratchpad” memories in designs • ROM arrays -- can pre-load BlockRAMs with fixed values • CLBs are reasonably efficient at implementing ROMs, so don’t need to use BlockRAMs unless you have a very big ROM • CLB’s are very inefficient at implementing RAMs, want to use a BlockRAM any time you need more than a few words of RAM/register • Buffer for Linux/HW communication • One simple way to move data between Linux and HW is to use BlockRAM buffer for data, interrupt/register write to signal when data is ready. Lecture 7

  23. Next Time • The PLB bus Lecture 7

More Related