1 / 21

Digital Camera

Digital Camera. Chad Hantak COMP290-052 December 12, 2003. Hardware Overview. XSA-100 connected to XST-2 XStend C3188A Camera Module Lens Omnivision 7620 CMOS USB Mod2. XStend Board. Brings out pins of XSA to a prototyping area Extended Hardware More SRAM IDE Etc.

hanzila
Download Presentation

Digital Camera

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. Digital Camera Chad Hantak COMP290-052 December 12, 2003

  2. Hardware Overview • XSA-100 connected to XST-2 XStend • C3188A Camera Module • Lens • Omnivision 7620 CMOS • USB Mod2

  3. XStend Board • Brings out pins of XSA to a prototyping area • Extended Hardware • More SRAM • IDE • Etc.

  4. C3188A Camera Module • Mounted Lens • Minimum pins from CMOS Sensor • Clock

  5. OmniVision OV7620 • CMOS / Digital • VGA, QVGA • YCrCb, GRB, RGB • 16 / 8 bit color • Interlaced / Progressive • Configurable via I2C • Many, many imaging options

  6. USB Mod2 • FIFO via USB

  7. Crash Course on CMOS

  8. Crash Course on CMOS • Important signals • VSYNC, HREF, PCLK • VSYNC • Indicates start of frame • HREF • High during active pixel window • PCLK • Every rising edge pixels present on data lines

  9. Crash Course on CMOS

  10. Crash Course on CMOS

  11. Crash Course on I2C • Simple 2-line multi-master bus • Lines • Serial Clock • Serial Data • Devices have two addresses (Reading / Writing) • Typically slow, just used for configuration • Protocol / Information can be found at: • http://www.semiconductors.philips.com/buses/i2c/facts/

  12. Implemented Hardware • Show and Tell Time • Wire wrapping • Soldering

  13. System Overview

  14. Flow Control • Initialization / Wait for go • Wait for a VSYNC • Grab pixels till end of VSYNC • Count # of pixels • Dump captured pixels to USB • Check for a command • Repeat

  15. Command Processor • Two Internal Systems • Controller • Read Register • Write Register • Start • I2C Interface to the Sensor • Looks like a simple memory interface • Hides I2C from outside components

  16. Image Sensor Interface • Operates on the pixel clock from the sensor • Tracks whether or not on a valid line (In Raw RGB mode, first HREF line is invalid) • Munges the data bits from Y, UV Channels and places it on the data bus

  17. Memory Controller • What data bits go where • Two FIFOs • Controls SDRAM • Counting of data to and from SDRAM

  18. What Went Wrong? (Fixed) • Two different clocks • System 50Mhz, Pixel Clock 27Mhz • Missing Pixels • Dual-Clocked FIFO • Fills on the pixel clock, drained on the system clock

  19. What Went Wrong? (Broken) • I2C Does not work • Simulates Great • No good on hardware • Claims Opencores component may be flakey? • Intermittent USB->PC transfer problem • One build, works great • Next build, state machine in transfer system hangs • Bridged signal?

  20. Where from here? • Debugging I2C • Can’t use ChipScope • Serial clock line running on 100 KHz clock • Use a standard analyzer • Check the hardware over • Rewire wrap all the signals • Look for bridged connections

More Related