Send commitlog mailing list submissions to
        commitlog@lists.openmoko.org

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.openmoko.org/mailman/listinfo/commitlog
or, via email, send a message with subject or body 'help' to
        commitlog-requ...@lists.openmoko.org

You can reach the person managing the list at
        commitlog-ow...@lists.openmoko.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of commitlog digest..."
Today's Topics:

   1. r5665 - trunk/gta02-core/docs/ecn (r...@docs.openmoko.org)
--- Begin Message ---
Author: rask
Date: 2009-10-01 13:46:58 +0200 (Thu, 01 Oct 2009)
New Revision: 5665

Added:
   trunk/gta02-core/docs/ecn/ecn0041.txt
Modified:
   trunk/gta02-core/docs/ecn/STATUS
Log:
- added ECN0041 (for discussion) "Test points and 0R resistors for camera 
interface"


Modified: trunk/gta02-core/docs/ecn/STATUS
===================================================================
--- trunk/gta02-core/docs/ecn/STATUS    2009-09-24 14:02:51 UTC (rev 5664)
+++ trunk/gta02-core/docs/ecn/STATUS    2009-10-01 11:46:58 UTC (rev 5665)
@@ -40,6 +40,7 @@
 0038    Discuss Loudspeaker EMI filter
 0039   Discuss Insert 0R resistors into SPI signals
 0040   Discuss Remove backup battery (BAT1701)
+0041   Discuss Test points and 0R resistors for camera interface
 
 
 Open ECNs
@@ -66,3 +67,4 @@
 0038    AUDIO
 0039   CPU, LCM
 0040   PMU, MODEM
+0041   CPU

Added: trunk/gta02-core/docs/ecn/ecn0041.txt
===================================================================
--- trunk/gta02-core/docs/ecn/ecn0041.txt                               (rev 0)
+++ trunk/gta02-core/docs/ecn/ecn0041.txt       2009-10-01 11:46:58 UTC (rev 
5665)
@@ -0,0 +1,41 @@
+Test points and 0R resistors for camera interface
+
+
+We should allow for experimentation with the camera interface. The
+24xx/64xx camera interface would be the obvious choice of interface to
+connect a camera to, but a few details need verification:
+
+The SC32442B manual specifies a short VSYNC pulse (high) between lines. 
+Several camera modules instead keep VSYNC high during lines. It is not clear
+from the manual if simply inverting VSYNC polarity is enough to make it
+work.
+
+The SC32442B manual isn't quite clear on how to receive e.g. JPEG compressed
+data as offered by some cameras. E.g. will we need a separate VSYNC
+interrupt pin to deal with variable frame data lengths?
+
+The change is to route unused pins to test points and insert 0R into the
+rest. Current status:
+
+CAMDATA0/GPJ0  Insert 0R (BT_PIO5).
+CAMDATA1/GPJ1  Add test point.
+...
+CAMDATA6/GPJ6  Add test point.
+CAMDATA7/GPJ7  Insert 0R (WLAN_GPIO0).
+CAMPCLK/GPJ8   Add test point.
+CAMVSYNC/GPJ9  Add test point.
+CAMHREF/GPJ10  Insert 0R (WLAN_DATA2).
+CAMCLKOUT/GPJ11        Has 0R and test point (CHIP_PWD).
+CAMRESET/GPJ12 Insert 0R (WLAN_nRESET).
+
+CAMRESET is not really a special function, any GPIO could be used for the
+camera reset signal.
+
+Would it be better to route the camera signals to the debug connector to save
+PCB space and reduce the need to solder wires to the main PCB?
+
+Impact: Little if any. The signals currently routed to the camera port are
+less than 1 Hz or not used at all.
+
+
+Author: Rask Ingemann Lambertsen <ccc94...@vip.cybercity.dk>




--- End Message ---
_______________________________________________
commitlog mailing list
commitlog@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/commitlog

Reply via email to