[Elphel-support] problem with stereo setup
Jorick Astrego
jorick at netbulae.com
Mon Aug 9 23:37:58 PDT 2010
Dear Oleg/Andrey,
We took everything apart and reattached all the cables and the sensors
now show up most of the time. But not consequently everytime. Still no
image though :-(
What are these JFFS2 notices in the log? It looks like the filesystem
has gone bad....
Jan 1 00:01:00 Elphel353 kernel: VFS: Mounted root (jffs2 filesystem)
readonly.
Jan 1 00:01:00 Elphel353 kernel: Freeing unused kernel memory: 72k freed
Jan 1 00:01:00 Elphel353 kernel: Empty flash at 0x00b24a2c ends at
0x00b25000
Jan 1 00:01:00 Elphel353 kernel: Empty flash at 0x00b2f464 ends at
0x00b2f800
Jan 1 00:01:00 Elphel353 kernel: Empty flash at 0x012c69f4 ends at
0x012c7000
Jan 1 00:01:00 Elphel353 kernel: Empty flash at 0x01dbb444 ends at
0x01dbb800
Jan 1 00:01:00 Elphel353 kernel: Empty flash at 0x03b9daa8 ends at
0x03b9e000
*Jan 1 00:01:00 Elphel353 kernel: JFFS2 notice: (599) check_node_data:
wrong data CRC in data node at 0x03b9d800: read 0xfceecc3d, calculated
0x8a87afb7.
Jan 1 00:01:00 Elphel353 kernel: JFFS2 notice: (599) check_node_data:
wrong data CRC in data node at 0x00b2e000: read 0x2fcf066a, calculated
0xc1b83d1c.
Jan 1 00:01:00 Elphel353 kernel: JFFS2 notice: (599) check_node_data:
wrong data CRC in data node at 0x00b23000: read 0xe045f277, calculated
0x76ac2023.*
Jan 1 00:01:00 Elphel353 kernel: eth0: changed MAC to 00:0E:64:08:10:A6
Jan 1 00:01:00 Elphel353 kernel: eth0: changed MAC to 00:0E:64:08:10:A6
Jan 1 00:01:01 Elphel353 udhcpc[716]: udhcpc (v0.9.9-pre) started
Jan 1 00:01:01 Elphel353 ipsetd[725]: Timeout in 120 s.
Jan 1 00:01:01 Elphel353 ipsetd[725]: Expecting echo request payload
408 bytes.
Jan 1 00:01:01 Elphel353 ipsetd[725]: On echo request arrival, execute
/etc/ipsetd.script.
Jan 1 00:01:01 Elphel353 vftpd[731]: Starting vftpd 0.01
Jan 1 00:01:01 Elphel353 vftpd[732]: qos_setup_socket: unsupported AF
Jan 1 00:01:01 Elphel353 udhcpc[716]: Lease of 192.168.2.199 obtained,
lease time 7200
Jan 1 00:01:02 Elphel353 root: DHCP: eth0: IP address: "192.168.2.199"
Jan 1 00:01:02 Elphel353 root: DHCP: eth0: Netmask: "255.255.255.0"
Jan 1 00:01:02 Elphel353 root: DHCP: eth0: Broadcast (server): "",
(deducted): "192.168.2.255"
Jan 1 00:01:02 Elphel353 root: DHCP: eth0: Default gateway: 192.168.2.1
Jan 1 00:01:02 Elphel353 root: DHCP: Domain: 'netbulae.com'
Jan 1 00:01:02 Elphel353 root: DHCP: DNS server(s): '192.168.2.1'
Jan 1 00:01:14 Elphel353 kernel: initSequencers:resetting both sequencers
Jan 1 00:01:14 Elphel353 kernel: Initializing DMA registers for EXTDMA3
- sensor clock set to 20000000
Jan 1 00:01:14 Elphel353 kernel: 10359 bitstream version =0x0359a04c
Jan 1 00:01:14 Elphel353 kernel: 10353 sensor clock set to 96000000
Jan 1 00:01:14 Elphel353 kernel: 10359A sensor clock set to 96000000
Jan 1 00:01:14 Elphel353 kernel: removing MRST from the sensor
*Jan 1 00:01:14 Elphel353 kernel: Found MT9P001 2592x1944 sensor on
10359A port 1, chip ID=1801
Jan 1 00:01:14 Elphel353 kernel: Found MT9P001 2592x1944 sensor on
10359A port 2, chip ID=1801
Jan 1 00:01:14 Elphel353 kernel: Found MT9P001 2592x1944 sensor, chip
ID=1801*
*Jan 1 00:01:14 Elphel353 kernel:
arch/cris/arch-v32/drivers/elphel/multisensor.c:1226:multisensor_pgm_sensorphase
**** ERROR adjusting SDRAM clock phase in
arch/cris/arch-v32/drivers/elphel/multisensor.c:1227:multisensor_pgm_sensorphase,
result=0xffffffff
Jan 1 00:01:14 Elphel353 kernel: Resetting MT9X001 sensor^M*
Jan 1 00:01:14 Elphel353 kernel: Reading sensor registers to the shadows:^M
Jan 1 00:01:14 Elphel353 kernel: Initializing MT9X001 registers with
default values:^M
Jan 1 00:01:14 Elphel353 kernel: Starting hardware sequencers
Jan 1 00:03:01 Elphel353 ipsetd[725]: Timed out after 120s.
On 08/06/2010 06:36 PM, Oleg K Dzhimiev wrote:
> P.S. just a reminder:
> on the 10359:
> to J2-J4 cables go foil contacts down
> to J1 - foil up
>
> On 6 August 2010 10:21, Oleg K Dzhimiev <oleg at elphel.com
> <mailto:oleg at elphel.com>> wrote:
>
> Dear Jorick,
>
> 1. Check the sensors - unscrew the middle cover - attach each
> cable directly to the camera. To see if the at least work.
>
> 2. Probably just reattaching the cables (one of the sensors should
> be connected to J2 (it's the nearest to the 10353-10359 port J1))
> to 10359 will help if the sensors are detected then you'll get
> lines in the log like:
>
> Found MT9P001 2592x1944 sensor on 10359A port 1, chip ID=1801
> Found MT9P001 2592x1944 sensor on 10359A port 2, chip ID=1801
>
>
> What is strange is that at least one of the sensors was detected
> in your first log but the behavior was as if the TRIG=4.
>
> Best regards,
> Oleg
>
>
> On 6 August 2010 04:14, Jorick Astrego <jorick at netbulae.com
> <mailto:jorick at netbulae.com>> wrote:
>
> Dear Oleg/Andrey,
>
> We reverted back to the older firmware 8.0.8.25 as Andrey
> suggested. One of our developers thought the latest CVS
> version would be better.
>
> After reflashing I tried:
>
> delete /etc/autocampars.xml, disconnect 10359 and rebooting
>
> But still no sensors detected.
>
> When I check "ftp://192.168.2.199/etc/autocampars.xml" the
> TRIG parameter is set to 0, I've attached it to this email
>
> And when I check the sensors, I get:
>
> [root at Elphel353 /root]825# fpcf -i2cr16 4c00
> read failed, returned -1, expected - 2
> [root at Elphel353 /root]825# fpcf -i2cr16 4a00
> read failed, returned -1, expected - 2
> [root at Elphel353 /root]825# fpcf -i2cr16 4e00
> read failed, returned -1, expected - 2
>
> After that I tried:
>
> [root at Elphel353 /root]825# fpcf -X 1
> Clock 1 is OFF
> [root at Elphel353 /root]825# fpcf -X 1 96
> Set clock 1 to 9.600000e+01MHz
> [root at Elphel353 /root]825# fpcf -X 1
> Clock 1 is set to 9.600000e+01MHz
>
> This is is "/var/log/messages
>
> Jan 1 00:00:43 Elphel353 kernel: initSequencers:resetting
> both sequencers
> Jan 1 00:00:43 Elphel353 kernel: Initializing DMA registers
> for EXTDMA3 - sensor clock set to 20000000
> Jan 1 00:00:43 Elphel353 kernel: 10359 bitstream version
> =0x0359a04c
> Jan 1 00:00:43 Elphel353 kernel: 10353 sensor clock set to
> 96000000
> Jan 1 00:00:43 Elphel353 kernel: 10359A sensor clock set to
> 96000000
> Jan 1 00:00:43 Elphel353 kernel: removing MRST from the sensor
> Jan 1 00:00:43 Elphel353 kernel: removing MRST from the sensor
> Jan 1 00:00:43 Elphel353 kernel: trying MT9P001
> Jan 1 00:00:43 Elphel353 kernel: trying other MT9X001
> Jan 1 00:00:43 Elphel353 kernel: sensor power set low^M
> Jan 1 00:00:43 Elphel353 kernel: will set to 0x41^M
> Jan 1 00:00:43 Elphel353 kernel: will set to 0x30^M
> Jan 1 00:00:43 Elphel353 kernel: will set to 0x28^M
> Jan 1 00:00:43 Elphel353 kernel: will set to 0x24^M
> Jan 1 00:00:43 Elphel353 kernel: will set to 0x22^M
> Jan 1 00:00:43 Elphel353 kernel: .. full^M
> Jan 1 00:00:43 Elphel353 kernel: Inverted MRST
> Jan 1 00:00:43 Elphel353 kernel: trying MT9X001
> Jan 1 00:00:43 Elphel353 kernel: No image sensor found^M
> Jan 1 00:00:43 Elphel353 kernel:
> arch/cris/arch-v32/drivers/elphel/multisensor.c:1188:multisensor_pgm_sensorphase
> WARNING: ((thispars->pars[P_CLK_SENSOR] ==
> prevpars->pars[P_CLK_SENSOR])) but multi_phases_initialized is
> not yet set ********
> Jan 1 00:00:43 Elphel353 kernel: Error programming clock 0
> fact=0, err=0xffffff00
> Jan 1 00:00:43 Elphel353 kernel:
> arch/cris/arch-v32/drivers/elphel/multisensor.c:1226:multisensor_pgm_sensorphase
> **** ERROR adjusting SDRAM clock phase in
> arch/cris/arch-v32/drivers/elphel/multisensor.c:1227:multisensor_pgm_sensorphase,
> result=0xfffffffc
> Jan 1 00:02:30 Elphel353 ipsetd[725]: Timed out after 120s.
>
> And on "http://192.168.2.199/359/10359_controls.html"
> <http://192.168.2.199/359/10359_controls.html> when I press
> "read registers" I only get "ffffff" in every field.
>
> So there must be something else wrong :-(
>
> Regards,
>
> Jorick
>
>
> On 08/05/2010 07:15 PM, Oleg K Dzhimiev wrote:
>> Dear Jorick,
>>
>> You probably got my yesterday's letter in spam... If not -
>> have you tried this?
>>
>> You're probably using almost the latest software.
>> So, the problem is - the software when detects
>> the 10359 puts the sensors into the triggered
>> mode - and it needs a sync connection with
>> another camera (we use this in our panorama camera).
>>
>> 1.
>> The solution is to get
>> "ftp://192.168.2.199/etc/autocampars.xml" and set
>> the TRIG parameter to 0:
>> old: 4 //external trigger mode
>> new: 0 //free run
>>
>> Copy it back and in a telnet or ssh session
>> launch: "/usr/html/autocampars.php --init" or
>> just reboot
>>
>> 2.
>> To check if the sensors were detected in
>> telnet/ssh/phpshell type:
>> for J2: fpcf -i2cr16 4a00 (result is 0x1801)
>> for J3: fpcf -i2cr16 4c00 (result is 0x1801)
>> for J4: fpcf -i2cr16 4e00 (result is 0x1801)
>> (there is no sensor there but anyway)
>>
>> About "test_inner_10359.php" -
>>
>> <test name="test_10359">
>>
>> <board_id result="ok">10359</board_id>
>>
>> -
>>
>> <firmware result="fail">
>>
>> An old firmware revision or i2c doesn't work, got -1
>>
>> </firmware>
>>
>> <finish result="fail"/>
>>
>> </test>
>>
>>
>> This can be tested in a telnet/ssh session also:
>> a. "fpcf -X 1" - (shoud be 96MHz) frequency to the 10359.
>> "fpcf -X 1 96" will turn it on if it's off
>> b. If the frequency is on you can read the 10359 registers
>> through http://192.168.2.199/359/10359_controls.html
>>
>> Please modify autocampars.xml first (you can copy the
>> attached one to the camera) and then we will move on.
>>
>> Best regards,
>> Oleg
>>
>> On 5 August 2010 09:18, Jorick Astrego <jorick at netbulae.com
>> <mailto:jorick at netbulae.com>> wrote:
>>
>> Dear people,
>>
>> This week we received an elphel assembled stereo setup
>> (two sensors and
>> a 10359 plus crossbar) to hook to our elphel 10353 with
>> 10369.
>>
>> We are running release 8.0.8.37 from cvs
>>
>> The problem is now that we don't receive any image.
>>
>> The 10359 looks ok but doesn't read the registers with
>> the button on:
>>
>> http://elphel.netbulae.com/index.php?site=camerasetup/setup.php
>>
>> I get an error "failed to start"
>>
>> In the /var/log/messages I get this info:
>>
>> Jan 1 00:00:44 Elphel353 syslogd 1.4.1: restart.
>> Jan 1 00:00:44 Elphel353 kernel: klogd 1.4.1, log source
>> = /proc/kmsg
>> started.
>> Jan 1 00:00:44 Elphel353 kernel: Linux version 2.6.19
>> (root at tsarcasm-mobile) (gcc version 3.2.1 Axis release
>> R64/1.64) #1 Wed
>> Aug 4 15:38:13 CEST 2010
>> Jan 1 00:00:44 Elphel353 kernel: Setting up paging and
>> the MMU.
>> Jan 1 00:00:44 Elphel353 kernel: Linux/CRISv32 port on
>> ETRAX FS (C)
>> 2003, 2004 Axis Communications AB
>> Jan 1 00:00:44 Elphel353 kernel: Built 1 zonelists. Total
>> pages: 8160
>> Jan 1 00:00:44 Elphel353 kernel: Kernel command line:
>> root=/dev/mtdblock3 init=/linuxrc rootfstype=jffs2
>> Jan 1 00:00:44 Elphel353 kernel: PID hash table entries:
>> 256 (order: 8,
>> 1024 bytes)
>> Jan 1 00:00:44 Elphel353 kernel: Dentry cache hash table
>> entries: 8192
>> (order: 2, 32768 bytes)
>> Jan 1 00:00:44 Elphel353 kernel: Inode-cache hash table
>> entries: 4096
>> (order: 1, 16384 bytes)
>> Jan 1 00:00:44 Elphel353 kernel: Memory: 41376k/65536k
>> available (1738k
>> kernel code, 24160k reserved, 607k data, 72k init)
>> Jan 1 00:00:44 Elphel353 kernel: Mount-cache hash table
>> entries: 1024
>> Jan 1 00:00:44 Elphel353 kernel: NET: Registered protocol
>> family 16
>> Jan 1 00:00:44 Elphel353 kernel: SCSI subsystem initialized
>> Jan 1 00:00:44 Elphel353 kernel: usbcore: registered new
>> interface
>> driver usbfs
>> Jan 1 00:00:44 Elphel353 kernel: usbcore: registered new
>> interface
>> driver hub
>> Jan 1 00:00:44 Elphel353 kernel: usbcore: registered new
>> device driver usb
>> Jan 1 00:00:44 Elphel353 kernel: NET: Registered protocol
>> family 2
>> Jan 1 00:00:44 Elphel353 kernel: IP route cache hash
>> table entries: 512
>> (order: -2, 2048 bytes)
>> Jan 1 00:00:44 Elphel353 kernel: TCP established hash
>> table entries:
>> 2048 (order: 0, 8192 bytes)
>> Jan 1 00:00:44 Elphel353 kernel: TCP bind hash table
>> entries: 1024
>> (order: -1, 4096 bytes)
>> Jan 1 00:00:44 Elphel353 kernel: TCP: Hash tables configured
>> (established 2048 bind 1024)
>> Jan 1 00:00:44 Elphel353 kernel: TCP reno registered
>> Jan 1 00:00:44 Elphel353 kernel: Check hardware
>> configuration of Elphel
>> 353 camera
>> Jan 1 00:00:44 Elphel353 kernel: Elphel 10349/10369 IO
>> extension board
>> is present
>> Jan 1 00:00:44 Elphel353 kernel: fast_timer_init()
>> Jan 1 00:00:44 Elphel353 kernel: JFFS2 version 2.2.
>> (NAND) (C) 2001-2006
>> Red Hat, Inc.
>> Jan 1 00:00:44 Elphel353 kernel: io scheduler noop
>> registered (default)
>> Jan 1 00:00:44 Elphel353 kernel: Serial: CRISv32 driver
>> $Revision: 1.78
>> $ <6>ttyS0 at I/O 0xb0026000 (irq = 68) is a CRISv32
>> Jan 1 00:00:44 Elphel353 kernel: RAMDISK driver
>> initialized: 16 RAM
>> disks of 4096K size 1024 blocksize
>> Jan 1 00:00:44 Elphel353 kernel: PPP generic driver
>> version 2.4.2
>> Jan 1 00:00:44 Elphel353 kernel: ETRAX FS 10/100MBit
>> ethernet v0.01 (c)
>> 2003 Axis Communications AB
>> Jan 1 00:00:44 Elphel353 kernel: eth0: changed MAC to
>> 00:40:8C:CD:00:00
>> Jan 1 00:00:44 Elphel353 kernel: Uniform Multi-Platform
>> E-IDE driver
>> Revision: 7.00alpha2
>> Jan 1 00:00:44 Elphel353 kernel: ide: Assuming 50MHz
>> system bus speed
>> for PIO modes; override with idebus=xx
>> Jan 1 00:00:44 Elphel353 kernel: ide: ETRAX FS built-in
>> ATA DMA controller
>> Jan 1 00:00:44 Elphel353 kernel: cris_ide_init()
>> Jan 1 00:00:44 Elphel353 kernel: hdb: probing with
>> STATUS(0xca) instead
>> of ALTSTATUS(0x8a)
>> Jan 1 00:00:44 Elphel353 kernel: hdb: no response (status
>> = 0xff),
>> resetting drive
>> Jan 1 00:00:44 Elphel353 kernel: hdb: no response (status
>> = 0xff)
>> Jan 1 00:00:44 Elphel353 kernel: Initializing USB Mass
>> Storage driver...
>> Jan 1 00:00:44 Elphel353 kernel: usbcore: registered new
>> interface
>> driver usb-storage
>> Jan 1 00:00:44 Elphel353 kernel: USB Mass Storage support
>> registered.
>> Jan 1 00:00:44 Elphel353 kernel: usbcore: registered new
>> interface
>> driver usbserial
>> Jan 1 00:00:44 Elphel353 kernel:
>> drivers/usb/serial/usb-serial.c: USB
>> Serial support registered for generic
>> Jan 1 00:00:44 Elphel353 kernel: usbcore: registered new
>> interface
>> driver usbserial_generic
>> Jan 1 00:00:44 Elphel353 kernel:
>> drivers/usb/serial/usb-serial.c: USB
>> Serial Driver core
>> Jan 1 00:00:44 Elphel353 kernel:
>> drivers/usb/serial/usb-serial.c: USB
>> Serial support registered for Belkin / Peracom / GoHubs
>> USB Serial Adapter
>> Jan 1 00:00:44 Elphel353 kernel: usbcore: registered new
>> interface
>> driver belkin
>> Jan 1 00:00:45 Elphel353 kernel:
>> drivers/usb/serial/belkin_sa.c: USB
>> Belkin Serial converter driver v1.2
>> Jan 1 00:00:45 Elphel353 kernel:
>> drivers/usb/serial/usb-serial.c: USB
>> Serial support registered for cp2101
>> Jan 1 00:00:45 Elphel353 kernel: usbcore: registered new
>> interface
>> driver cp2101
>> Jan 1 00:00:45 Elphel353 kernel:
>> drivers/usb/serial/cp2101.c: Silicon
>> Labs CP2101/CP2102 RS232 serial adaptor driver v0.07
>> Jan 1 00:00:45 Elphel353 kernel:
>> drivers/usb/serial/usb-serial.c: USB
>> Serial support registered for Garmin GPS usb/tty
>> Jan 1 00:00:45 Elphel353 kernel: usbcore: registered new
>> interface
>> driver garmin_gps
>> Jan 1 00:00:45 Elphel353 kernel:
>> drivers/usb/serial/garmin_gps.c: garmin
>> gps driver v0.28
>> Jan 1 00:00:45 Elphel353 kernel:
>> drivers/usb/serial/usb-serial.c: USB
>> Serial support registered for MCT U232
>> Jan 1 00:00:45 Elphel353 kernel: usbcore: registered new
>> interface
>> driver mct_u232
>> Jan 1 00:00:45 Elphel353 kernel:
>> drivers/usb/serial/mct_u232.c: Magic
>> Control Technology USB-RS232 converter driver z2.0
>> Jan 1 00:00:45 Elphel353 kernel:
>> drivers/usb/serial/usb-serial.c: USB
>> Serial support registered for pl2303
>> Jan 1 00:00:45 Elphel353 kernel: usbcore: registered new
>> interface
>> driver pl2303
>> Jan 1 00:00:45 Elphel353 kernel:
>> drivers/usb/serial/pl2303.c: Prolific
>> PL2303 USB to serial adaptor driver
>> Jan 1 00:00:45 Elphel353 kernel: ETRAX FS stream
>> co-processor driver
>> v0.01, (c) 2003 Axis Communications AB
>> Jan 1 00:00:45 Elphel353 kernel: stream co-processor:
>> init done.
>> Jan 1 00:00:45 Elphel353 kernel: axisflashmap: ...
>> Jan 1 00:00:45 Elphel353 kernel: NAND device:
>> Manufacturer ID: 0x20,
>> Chip ID: 0xf1 (ST Micro NAND 128MiB 3,3V 8-bit)
>> Jan 1 00:00:45 Elphel353 kernel: Additional Info: ID
>> byte3=0x80, byte4=0x1d
>> Jan 1 00:00:45 Elphel353 kernel: Flash is rated 30 ns,
>> modifying
>> bif_core_rw_grp3: old=0x6300483, new=0x6300001
>> Jan 1 00:00:45 Elphel353 kernel: NAND 128MiB 3,3V 8-bit:
>> 0x08000000
>> bytes of NAND flash memory.
>> Jan 1 00:00:45 Elphel353 kernel: axisflashmap: Set to
>> boot from NAND
>> flash, making NAND flash primary device.
>> Jan 1 00:00:45 Elphel353 kernel: axisflashmap: flash read
>> 512 bytes at
>> 0x00040000, data: 00 b0 05 f0 25 ff ed 9c
>> Jan 1 00:00:45 Elphel353 kernel: axisflashmap: partition
>> table offset
>> 10, data: ef be 84 00 a1 0d 00 00
>> Jan 1 00:00:45 Elphel353 kernel: axisflashmap: Found a
>> valid partition
>> table at 0xc02fd9ae-0xc02fda3a.
>> Jan 1 00:00:45 Elphel353 kernel: offset == 0x00040000,
>> size == 0x007C0000
>> Jan 1 00:00:45 Elphel353 kernel: offset == 0x00800000,
>> size == 0x01800000
>> Jan 1 00:00:45 Elphel353 kernel: offset == 0x02000000,
>> size == 0x05000000
>> Jan 1 00:00:45 Elphel353 kernel: offset == 0x07000000,
>> size == 0x00C00000
>> Jan 1 00:00:45 Elphel353 kernel: Creating 1 MTD
>> partitions on "NAND
>> 128MiB 3,3V 8-bit":
>> Jan 1 00:00:45 Elphel353 kernel: 0x00000000-0x08000000 :
>> "main"
>> Jan 1 00:00:45 Elphel353 kernel: Creating 1 MTD
>> partitions on "NAND
>> 128MiB 3,3V 8-bit":
>> Jan 1 00:00:45 Elphel353 kernel: 0x00000000-0x00040000 :
>> "part0"
>> Jan 1 00:00:45 Elphel353 kernel: Creating 1 MTD
>> partitions on "NAND
>> 128MiB 3,3V 8-bit":
>> Jan 1 00:00:45 Elphel353 kernel: 0x00040000-0x00800000 :
>> "part1"
>> Jan 1 00:00:45 Elphel353 kernel: Creating 1 MTD
>> partitions on "NAND
>> 128MiB 3,3V 8-bit":
>> Jan 1 00:00:45 Elphel353 kernel: 0x00800000-0x02000000 :
>> "part2"
>> Jan 1 00:00:45 Elphel353 kernel: Creating 1 MTD
>> partitions on "NAND
>> 128MiB 3,3V 8-bit":
>> Jan 1 00:00:45 Elphel353 kernel: 0x02000000-0x07000000 :
>> "part3"
>> Jan 1 00:00:45 Elphel353 kernel: Creating 1 MTD
>> partitions on "NAND
>> 128MiB 3,3V 8-bit":
>> Jan 1 00:00:45 Elphel353 kernel: 0x07000000-0x07c00000 :
>> "part4"
>> Jan 1 00:00:45 Elphel353 kernel: ETRAX FS GPIO driver
>> v2.5, (c)
>> 2003-2006 Axis Communications AB
>> Jan 1 00:00:45 Elphel353 kernel: Elphel (R) model 353
>> FPGA (Xilinx (R)
>> XC3S1200E) configuration driver - 132
>> Jan 1 00:00:45 Elphel353 kernel: Elphel (R) model 353
>> system clocks (PLL
>> frequency synth.) driver - 133
>> Jan 1 00:00:45 Elphel353 kernel: fpga_control- 129
>> Jan 1 00:00:45 Elphel353 kernel:
>> arch/cris/arch-v32/drivers/elphel/framepars.c:384:initGlobalPars
>> GLOBALPARS(G_DEBUG)=0
>> Jan 1 00:00:45 Elphel353 kernel:
>> arch/cris/arch-v32/drivers/elphel/framepars.c:414:initMultiPars
>> GLOBALPARS(G_MULTI_NUM)=0
>> Jan 1 00:00:45 Elphel353 kernel: Elphel (R) Model 353
>> Frame Parameters
>> device driver - 130
>> Jan 1 00:00:45 Elphel353 kernel: Elphel FPGA interrupts
>> initialized
>> Jan 1 00:00:45 Elphel353 kernel: Initializing DMA
>> registers for EXTDMA3
>> - Elphel (R) Model 353 Camera Driver - 126
>> Jan 1 00:00:45 Elphel353 kernel: Elphel (R) model 353 i2c
>> character
>> device driver - 134, 2 channels
>> Jan 1 00:00:45 Elphel353 kernel: Raw image access driver- 131
>> Jan 1 00:00:45 Elphel353 kernel: Elphel (R) Model 353
>> video buffer
>> device driver- 135
>> Jan 1 00:00:45 Elphel353 kernel: Elphel (R) model 353
>> Exif device driver
>> - 125
>> Jan 1 00:00:45 Elphel353 kernel: Starting Elphel (R)
>> Model 353 Gamma
>> Tables device driver - 137
>> Jan 1 00:00:45 Elphel353 kernel: Elphel (R) Model 353
>> Gamma Tables
>> device driver - 137
>> Jan 1 00:00:45 Elphel353 kernel: Elphel (R) Model 353
>> Histograms device
>> driver^M
>> Jan 1 00:00:45 Elphel353 kernel: TCP cubic registered
>> Jan 1 00:00:45 Elphel353 kernel: NET: Registered protocol
>> family 1
>> Jan 1 00:00:45 Elphel353 kernel: NET: Registered protocol
>> family 17
>> Jan 1 00:00:45 Elphel353 kernel: VFS: Mounted root (jffs2
>> filesystem)
>> readonly.
>> Jan 1 00:00:45 Elphel353 kernel: Freeing unused kernel
>> memory: 72k freed
>> Jan 1 00:00:45 Elphel353 kernel: Empty flash at
>> 0x00b20a58 ends at
>> 0x00b21000
>> Jan 1 00:00:45 Elphel353 kernel: Empty flash at
>> 0x00b2f0b8 ends at
>> 0x00b2f800
>> Jan 1 00:00:45 Elphel353 kernel: Empty flash at
>> 0x00b385e0 ends at
>> 0x00b38800
>> Jan 1 00:00:45 Elphel353 kernel: Empty flash at
>> 0x00b45864 ends at
>> 0x00b46000
>> Jan 1 00:00:45 Elphel353 kernel: JFFS2 notice: (599)
>> read_dnode: node
>> CRC failed on dnode at 0xb37fe0: read 0xffffffff,
>> calculated 0x9d8e2f6f
>> Jan 1 00:00:45 Elphel353 kernel: JFFS2 notice: (599)
>> read_dnode: node
>> CRC failed on dnode at 0xb457e8: read 0xffffffff,
>> calculated 0x53d88c0d
>> Jan 1 00:00:45 Elphel353 kernel: JFFS2 notice: (599)
>> check_node_data:
>> wrong data CRC in data node at 0x00b57800: read
>> 0xb24af98f, calculated
>> 0xeada2b3.
>> Jan 1 00:00:45 Elphel353 kernel: eth0: changed MAC to
>> 00:0E:64:08:10:A6
>> Jan 1 00:00:45 Elphel353 kernel: eth0: changed MAC to
>> 00:0E:64:08:10:A6
>> Jan 1 00:00:46 Elphel353 udhcpc[719]: udhcpc (v0.9.9-pre)
>> started
>> Jan 1 00:00:46 Elphel353 ipsetd[728]: Timeout in 120 s.
>> Jan 1 00:00:46 Elphel353 ipsetd[728]: Expecting echo
>> request payload 408
>> bytes.
>> Jan 1 00:00:46 Elphel353 ipsetd[728]: On echo request
>> arrival, execute
>> /etc/ipsetd.script.
>> Jan 1 00:00:46 Elphel353 vftpd[734]: Starting vftpd 0.01
>> Jan 1 00:00:46 Elphel353 vftpd[735]: qos_setup_socket:
>> unsupported AF
>> Jan 1 00:00:46 Elphel353 udhcpc[719]: Lease of
>> 192.168.2.199 obtained,
>> lease time 7200
>> Jan 1 00:00:46 Elphel353 root: DHCP: eth0: IP address:
>> "192.168.2.199"
>> Jan 1 00:00:46 Elphel353 root: DHCP: eth0: Netmask:
>> "255.255.255.0"
>> Jan 1 00:00:46 Elphel353 root: DHCP: eth0: Broadcast
>> (server): "",
>> (deducted): "192.168.2.255"
>> Jan 1 00:00:47 Elphel353 root: DHCP: eth0: Default
>> gateway: 192.168.2.1
>> Jan 1 00:00:47 Elphel353 root: DHCP: Domain:
>> 'netbulae.com <http://netbulae.com>'
>> Jan 1 00:00:47 Elphel353 root: DHCP: DNS server(s):
>> '192.168.2.1'
>> Jan 1 00:00:58 Elphel353 kernel:
>> arch/cris/arch-v32/drivers/elphel/framepars.c:384:initGlobalPars
>> GLOBALPARS(G_DEBUG)=0
>> Jan 1 00:00:58 Elphel353 kernel: initSequencers:resetting
>> both sequencers
>> Jan 1 00:00:58 Elphel353 kernel:
>> arch/cris/arch-v32/drivers/elphel/framepars.c:414:initMultiPars
>> GLOBALPARS(G_MULTI_NUM)=0
>> Jan 1 00:00:59 Elphel353 kernel: Initializing DMA
>> registers for EXTDMA3
>> - sensor clock set to 20000000
>> Jan 1 00:00:59 Elphel353 kernel: 10359 bitstream version
>> =0x0359a04f
>> Jan 1 00:00:59 Elphel353 kernel: 10353 sensor clock set
>> to 96000000
>> Jan 1 00:00:59 Elphel353 kernel: 10359A sensor clock set
>> to 96000000
>> Jan 1 00:00:59 Elphel353 kernel: removing MRST from the
>> sensor
>> Jan 1 00:00:59 Elphel353 kernel: Setting internal HACT
>> generation
>> Jan 1 00:00:59 Elphel353 kernel:
>> arch/cris/arch-v32/drivers/elphel/framepars.c:414:initMultiPars
>> GLOBALPARS(G_MULTI_NUM)=0
>> Jan 1 00:00:59 Elphel353 kernel: removing MRST from the
>> sensor
>> Jan 1 00:00:59 Elphel353 kernel: Found MT9P001 2592x1944
>> sensor, chip
>> ID=1801
>> Jan 1 00:00:59 Elphel353 kernel: trying MT9P001
>> Jan 1 00:00:59 Elphel353 kernel: Error programming clock 0
>> fact=96000000, err=0xffffff00
>> Jan 1 00:00:59 Elphel353 kernel:
>> arch/cris/arch-v32/drivers/elphel/multisensor.c:1271:multisensor_pgm_sensorphase
>> **** ERROR adjusting SDRAM clock phase in
>> arch/cris/arch-v32/drivers/elphel/multisensor.c:1272:multisensor_pgm_sensorphase,
>> result=0xfffffffc
>> Jan 1 00:00:59 Elphel353 kernel: Resetting MT9X001 sensor^M
>> Jan 1 00:00:59 Elphel353 kernel: Reading sensor registers
>> to the shadows:^M
>> Jan 1 00:00:59 Elphel353 kernel: Initializing MT9X001
>> registers with
>> default values:^M
>> Jan 1 00:00:59 Elphel353 kernel: Starting hardware sequencers
>> Jan 1 00:02:46 Elphel353 ipsetd[728]: Timed out after 120s.
>>
>>
>> When I try:
>>
>> http://elphel.netbulae.com/test/test_inner_10359.php
>>
>> I get this result:
>>
>> <test name="test_10359">
>> <board_id result="ok">10359</board_id>
>> -
>> <firmware result="fail">
>> An old firmware revision or i2c doesn't work, got -1
>> </firmware>
>> <finish result="fail"/>
>> </test>
>>
>> and "http://elphel.netbulae.com/359/sensors_init.php"
>> gives problem
>> loading page
>>
>> Any idea what might be wrong?
>>
>> --
>> Regards,
>>
>> Jorick Astrego
>> Technisch Directeur
>>
>> Netbulae B.V.
>> Janninksweg 127
>> 7513 DH Enschede
>>
>> Tel. +31 (0)53 - 20 30 270
>> Fax. +31 (0)53 - 20 30 271
>>
>> Email: jorick at netbulae.com <mailto:jorick at netbulae.com>
>> Site: http://www.netbulae.com
>>
>>
>>
>>
>> _______________________________________________
>> Support-list mailing list
>> Support-list at support.elphel.com
>> <mailto:Support-list at support.elphel.com>
>> http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://support.elphel.com/pipermail/support-list_support.elphel.com/attachments/20100810/7328972a/attachment-0002.html>
More information about the Support-list
mailing list