1 / 37

ECE 477 Design Review Team 7  Spring 2009

ECE 477 Design Review Team 7  Spring 2009. Jason Cray. Joseph Mundackal. Ryan Sherlock. Michael Warsco. Outline. Project overview Project-specific success criteria Block diagram Component selection rationale Packaging design Schematic and theory of operation PCB layout

mason-kent
Download Presentation

ECE 477 Design Review Team 7  Spring 2009

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 477 Design Review Team 7  Spring 2009 Jason Cray Joseph Mundackal Ryan Sherlock Michael Warsco

  2. Outline • Project overview • Project-specific success criteria • Block diagram • Component selection rationale • Packaging design • Schematic and theory of operation • PCB layout • Software design/development status • Project completion timeline • Questions / discussion

  3. Project Overview • The Legacy Video Game Console • Load games via USB • Output to VGA Monitor • Digital audio output • Game controllers (Nintendo 64) • Fourteen Buttons • Analog Stick • Serial Interface • High score submission using 802.11b wireless protocol

  4. Project-Specific Success Criteria • An ability to display output onto a monitor connected through VGA • An ability to load game data through USB • An ability to manipulate the game using a controller • An ability to play sound files digitally • An ability to send high scores using wireless technology

  5. Block Diagram

  6. Hammer Evaluation • TinCan Tools Hammer • Positive • Embedded Linux environment • Required I/O features plus GPIO availability • DIP-module (40-pin)  • Internal voltage regulator output • Negative • 5V input requirement • Price $$ • Size (chip with board)

  7. uVGA Evaluation • 4D Systems uVGA Picaso-MD1 • Positive • Displays 8 bit bitmap data • Outputs to VGA through a specified resistor DAC • Supports a data rate of 30 Hz • Has a 512kB SRAM buffer • Negative • Nonstandard pin layout • Needs a DAC to communicate with VGA

  8. Other Components • Audio DAC - Cirrus Logic - CS433x • 8 or 16 bit digital audio conversion • Wireless Transmitter – Roving Networks – Wifly • Cheap

  9. Packaging Design • Hard Plastic Casing • Durable • Manipulatable • Cheap • Lid Unscrewable • Ease of debugging • Dimensions • 9 in x 9 in x 2 in • 1/8th in thickness

  10. Schematic/Theory of Operation • Hammer • 40 pin dip module • Samsung S3C2410A microprocessor + ARM 920T core (200 MHz) • 16MB NOR flash and a 32MB SDRAM • Embedded Linux Controller 1 SPI +5V USB Controller 2 SPI 2 Hammer 3 3 2 3 5 4 RS232 VGA GPIO WiFly GPIO Audio I2S

  11. Schematic/Theory of Operation

  12. Schematic/Theory of Operation • µVGA – PICASO MD1 • Graphics Controller • 512 KB - onboard SRAM • Double Buffering • Serial Interface – 1 Mbps • Outputs Digital Video • DAC – used to get analog output for VGA µVGA 11 DAC VGA Connector 3 3 Input - Hammer 2

  13. Schematic/Theory of Operation

  14. Schematic/Theory of Operation • WiFly – RN-111B • 802.11b WLAN serial embedded module • UART Interface • 921 Kbps • Low power sleep mode (12 µA) • Wakes up on external events • send/receive data Antenna WiFly 5 Input - Hammer

  15. Schematic/Theory of Operation

  16. Schematic/Theory of Operation • Audio – CS4334 • Audio DAC • I2S (Inter IC Sound) interface Audio Left Channel 4 Input - Hammer Right Channel Source : I2S bus specification specifications

  17. Schematic/Theory of Operation

  18. Schematic/Theory of Operation • N64 Controllers • Uses non standard protocol • Start/Stop bits pet bit of data • Bi-directional interface SIMO MISO Switch Circuit Bi-directional interface N64 Controller Data = 1 Data = 0

  19. Schematic/Theory of Operation Switch N64 Controller Interface

  20. Schematic/Theory of Operation USB Type A Interface RS232 Circuit

  21. Schematic/Theory of Operation

  22. PCB Design

  23. Schematic Figures • 7” x 6.8” (wxl) = 47.6” in2 • Reduction in size from previous attempt • Some analog signals too close • +5V and +3.3V power lines • 80 mil trace width • 40 mil trace width minimum • 2 layer board layout • ~15 headers

  24. Design Planning • Separate analog signals (video, audio, and wireless) • Some components are closer due to size limitation (i.e., wireless micro to N64 controllers) • Placement of peripherals • Controllers and USB up front • Video, Audio, and Wireless in the back • Power supply on the side with RS-232 • Digital-to-Analog conversion for RGB video output needs the most room

  25. PCB Design – Controllers & USB

  26. PCB Design – Controllers & USB • USB requirements: • 2 line bus (D+,D-) • +5V • Up to five devices @ 200mA each • N64 Controllers • Bidirectional serial bus • +3.3V @ ~1A

  27. PCB Design – Power & RS-232

  28. PCB Design – Power & RS-232 • Power: • Single +5V power line • +3.3V regulator supplying ~800mA • RS-232 transceiver • +3.3V • UART interface requires two lines from Hammer module

  29. PCB Design – Video

  30. PCB Design – Video • 4-D SystemsuVGA • +3.3V @ ~80mA, max 110mA • 8-bit RGB (3-bit red, 3-bit green, 2-bit blue) plus three blank RGB values (reference values) and Horizontal and Vertical Sync signals • RGB Digital-Analog Converter • +5.0V with minimal current • Uses the blank values as references to determine the gain of the analog signal from the RGB values

  31. PCB Design – Wireless & Audio

  32. PCB Design – Wireless& Audio • Wireless • +3.3V @ ~110mA, max 180mA • UART interface, hardware reset (factory defaults), and two bits for send and receive flags, total of 6 lines • Big concern is analog noise being so close to both Hammer module and N64 controller • Audio • +5.0V with minimal current • Analog noise not as large an issue since outputs are far in the right corner away from any other digital signals

  33. Software Requirements • Drivers for peripherals • USB – Reading files • Audio – Outputting WAV files • Wifi – Sending data to a web server • Controllers – Accepting controller data • uVGA – send bitmap images to VGA controller • Game coding

  34. Software Design • All software written in C or C++ • Compiled on outside machine and transferred to Hammer as executable files. • Games read through USB

  35. Timeline • March 9-13 • Start work on drivers for peripherals • Finish and verify PCB design • March 23-29 • Place power components on PCB • Continue work on drivers for peripherals • March 30-April 5 • Place microcontroller on PCB • Complete drivers for peripherals

  36. Timeline – Cont. • April 6-12 • Begin coding games • Add the peripherals to PCB • April 13-19 • Verify all components on PCB work properly • Finish coding games • Write user manual • April 20-26 • Debug system • Prepare for demonstration

  37. Questions / Discussion

More Related