CPSC 483 – Computer System DesignCoff-e-mail Biweekly Report 2March 29, 2004Don McGeeEric PedenPayton QuackenbushZack RomanPage 2 of 8StatusThe project status of Coff-e-mail, as of March 29, 2004, is shown in Figure 1:IDTask NameDuration1Write proposal11 days2Proposal Approved0 days3Prototype Java code24 days4Order Snap18 days5Order Sensors14 days6Order Camera14 days7Status Report 10 days8Order mounting hardware7 days9Critical Design Review0 days10Store images on SNAP12 days11Verify camera output3 days12Camera->SNAP interface13 days13Raw image captured0 days14Image compression10 days?15Compressed Image Captured0 days16Camera trigger test-run on coffee machine5 days17Deploy system1 day18Gather test data5 days19Evaluate results2 days20Program SNAP- run HelloWorld5 days21Serve static web page4 days22Serve dynamic web page4 days23Browser Compatibility Testing2 days24SNAP stores sensor events18.5 days25Serve dynamic images5 days26Write final report5 days27Verify sensor values with multimeter1 day?28Determine mount techniques11 days?29Get sensor mounts approved1 day30Test-mount sensors1 day31Get sensor appearance feedback5 days32Sensor events test-run on coffee machine5 days33 Get cabling/drop approval 5 days34 Run cable 5 days?100%2/1783%100%100%100%2/250%3/1033%100%46%3/29100%4/150%0%0%0%100%100%50%0%59%40%0%50%0%0%0%0%0%40%0%12151821242714710131619222528313691215182124273036912February 2004March 2004April 2004May 2004Figure 1 - Project StatusNetwork ConnectionThe SNAP/Tilt Kit arrived on Friday, March 5th. When we got the SNAP board and Tilt Kit we initiallyhad to load the default firmware on the board. This was done by connecting the SNAP board to acomputer using a serial connection. The software that came with the board had an interface forprogramming and setting the board up for the first time. The setup procedure was easily completed theday we got the board.After getting the board setup we had to contact CSG in order to get a network connection for the board.In order to get the network connection, a request was entered on the csg.cs.tamu.edu website. It tookabout a week to get the network connection setup with CSG. The first part of the week after springbreak we were able to connect the SNAP board to the internet and get the web server up and running.After getting the board connected to the network, CSG was contacted again to get a DNS entry for theSNAP board. The web site on the SNAP board can now be reached at http://coffee.cs.tamu.edu.Page 3 of 8Pin Input/OutputResearch and experiments have been done to determine how to take input and send output to pins onthe SNAP board. Research was first done to determine which pins could be used on the SNAP board forI/O. There is a good listserv available on the IMSYS.se website specifically for the SNAPmicrocontroller. From the listserv we got the following info on the availability of I/O pins:* Using the BitPort class you can make use of several pins that are otherwiseused for other dedicated purposes. For instance, if you are not usingserial1, you can use its pins (TX1 and XRX1) as general purpose I/O throughthis class.* If you are using the data bus (DataPort class), but have your locic mappedinto CE3 space, you can at least use PCE0-PCE3 as general purpose I/O. Thisis also done through the BitPort class.* If you are not using the data bus, then most of its pins are available foralternate purposes. Exceptions are the RD pin (PA0), and the WR pin andD7..D0 pins (PA1 and PC7-PC0) if you are using CAN.* Many pins in ports D,E,H,I and J are actually available on the SNAP edge,although this is not very well documented yet. All the available D and E pinsare also accessible via the BitPort class, but ports H,I and J, that are usedto control the DataPort address, are only accessible through PortIO. Theconnections are as follows: PH7..PH0 => A15..A8 PI7..Pi0 => A7..A0 PJ7..PJ4 => A19..A16Basically there are at least 20 pins that could be used for general purpose I/O if needed. A program wasrun to test the output on the pins. Pins were set to a logic high value for a period of time and then alogic low value, and the values were checked with a voltage meter. Information was also collected fromthe listserv about all the member functions for setting the I/O pins. The member functions in thePortIO class were not well documented, but after a post on the listserv, all the necessary informationwas collected about these functions.One big task that remains will be interfacing the SNAP board and the PIC microcontroller. The plan forinterfacing these two microcontrollers is to use a serial connection. The SNAP board has a class thatcontains code for easily implementing a serial protocol. Examples have also been found for workingwith the serial connection on www.vinculum.com. The example code that is given in this website was allwritten for the TINI microcontroller, so we will need to modify it slightly for running on the SNAPmicrocontroller. Once this is done, it will be relatively easy to set up the SNAP for transferring dataserially with the PIC.Camera InterfacingOur design for the camera has been iterated. The original color camera design, using an OmniVisionOV6620, has been replaced with a grayscale camera, the Mitsubishi M64282FP (aka. the “GameboyCamera”). The major reason for this switch is that it synchronizes with an external clock, whereas theOV6620, has an internal clock that must be synchronized with externally. The only ways to do this areto hook its pixel clock to an FPGA or an interrupt on a high speed microcontroller, and we did notdiscover this until actually trying to implement the camera. Thus, we took the tradeoff with theinexpensive, grayscale M65282FP.The M65282FP is a 128 x 123 grayscale CMOS image sensor, with a simple external interface. Therelevant pins for use in Coff-e-mail are:Page 4 of 8PinTypeDescriptionVDD-+5VDCGND-Common groundSINDigital InputSerial input for configurationLOADDigital InputConfiguration latch signalSTARTDigital InputImage exposure and frame start signalRESETDigital InputSynchronous resetXCKDigital InputRising-edge clock signalREADDigital OutputRising edge indicates camera exposure completeHigh value indicates that a pixel value exists on VOUTVOUTAnalog Output0 to Vref analog pixel output (0VDC indicates pure blackvalue, Vref indicates pure white value)M65282FP Operation:1. Perform a chip reset by holding the RESET pin low through a rising edge of XCK.2. Configure each