Looks like the serial port is working fine. Attached is a text file of the
output of the serial port at bootup.
We would like to set the camera up for 1280X720 image size at 30 fps. I was
able to set the image size thru the Camera Interface, but I'm only seeing ~3
fps.
What is the best way to setup the frame rate to be 30 fps, or is this some kind
of limitation due to my Ethernet setup thru a switch box?
Diana
From: [email protected] [mailto:[email protected]] On Behalf Of Andrey Filippov
Sent: Friday, September 02, 2011 9:52 AM
To: Diana Carrigan; [email protected]
Cc: Robert Kuzmak
Subject: Re: [Elphel-support] Can't communicate with Elphel353
Diana,
It is very nice that you were able to fix the problem. But I'm still curious
about the serial port console - did you make it work? What kind of output are
you getting there?
Andrey
On Fri, Sep 2, 2011 at 9:29 AM, Diana Carrigan
<[email protected]<mailto:[email protected]>> wrote:
Looks like I have fixed the problem The ribbon cable connected to the internal
harddrive was loose. I reseated it. Powered it up and everything is working
now! I noticed it booted up really fast this time. In the past it did not.
Thanks,
Diana
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]<mailto:[email protected]>] On Behalf Of Andrey Filippov
Sent: Friday, September 02, 2011 9:18 AM
To: Diana Carrigan
Subject: Re: [Elphel-support] Can't communicate with Elphel353
Diana,
So were you able to communicate via serial port? How did you do that? What was
it exactly there? What happens on the serial port now?
Andrey
On Fri, Sep 2, 2011 at 8:23 AM, Diana Carrigan
<[email protected]<mailto:[email protected]>> wrote:
Hi Andrey,
I don't think I configured anything. I just wanted to see if I could hook up
thru the serial cable at the baud rate 115K and I could. Later in the day, I
could no longer communicate via the Ethernet, so I power cycled. Since then
nothing has worked.
A couple of days ago, when I powered up the camera, it took three power cycles
before the Ethernet communication started working.
So I'm not sure what happened. Possibly a hardware issue?
Diana
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]<mailto:[email protected]>] On Behalf Of Andrey Filippov
Sent: Friday, September 02, 2011 8:17 AM
To: Diana Carrigan;
[email protected]<mailto:[email protected]>
Subject: Re: [Elphel-support] Can't communicate with Elphel353
On Fri, Sep 2, 2011 at 7:59 AM, Diana Carrigan
<[email protected]<mailto:[email protected]>> wrote:
We have not changed any code in the camera. I power cycled the camera and now
we can not communicate to it thru Ethernet or the Serial cable connected to the
10369 IO board.
Diana, you wrote that the serial cable was connected to the camera. Before you
lost communication with the camera - did you configure some terminal emulator
(i.e. minicom) to see camera boot messages on the system console?
If yes - what happens now on that port?
The baud rate on the port is 115k.
Andrey
Prior to power cycling the camera we could communicate and run video and camera
applications. The Ethernet green and yellow lights are blinking, and the light
on the power supply is green.
Any suggestions?
Diana Carrigan
_______________________________________________
Support-list mailing list
[email protected]<mailto:[email protected]>
http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
_______________________________________________
Support-list mailing list
[email protected]<mailto:[email protected]>
http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
_______________________________________________
Support-list mailing list
[email protected]<mailto:[email protected]>
http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Empty flash at 0x00b61378 ends at 0x00b61800
Empty flash at 0x017a7210 ends at 0x017a7800
done
/linuxrc: Starting init.
init: starting up.
Starting system initialization.
Axis Linux, http://developer.axis.com/
Copyright (C) 2000-2007 Axis Communications AB
Elphel (R) Model 353 Camera release 8.1.0
* Mounting filesystems... [ ok ]
* Initializing /var...
[ ok ]
* Determining MAC address...
+ using saved MAC address: 00:0E:64:08:1A:1E [ ok ]
* Initializing random number generator... [ ok ]
* Setting hostname...
+ hostname: "Elphel353" [ ok ]
* Initializing volatile resolver configuration... [ ok ]
* Setting FPGA master clock to 160 MHz... [ ok ]
* Programming FPGA with /etc/x353.bit... [ ok ]
* Loaded FPGA rev... [
353402a ]
**** Unknown FPGA revision ****
* Adjusting DDR SDRAM clock phase... [ PH
90/ ]
* Turn on xtall output (12MHz) to FPGA... [ ok ]
* Some CMOS-based sensor board attached... [
assuming 10338 ]
* Configure broadcast ping... [ ok ]
System initialization is done.
/bin/sh: can't access tty; job control turned off
#
#
#
#
#
# New runlevel: 3
* Starting respawn daemon... [ ok ]
* Starting system and kernel logger...
Jan 1 00:00:17 Elphel353 syslogd 1.4.1: restart.
+ system logger started
+ kernel logger started [ ok ]
* Bringing lo up... [ ok ]
* Bringing eth0 up...
eth0: changed MAC to 00:0E:64:08:1A:1E
+ hardware address: 00:0E:64:08:1A:1E
+ media: auto
+ eth0 going up
eth0: changed MAC to 00:0E:64:08:1A:1E
+ IPv4 on eth0
+ boot protocol: none
+ IP address: 192.168.0.9
+ netmask: 255.255.255.0
+ broadcast address: 192.168.0.255
+ default IPv4 gateway: 192.168.0.15
+ set MDI to MDI (normal) mode
y
+ done [ ok ]
* Waiting for a network interface...
+ eth0 is up [ ok ]
* Starting ipsetd...
Jan 1 00:00:20 Elphel353 ipsetd[708]: Timeout in 120 s.
Jan 1 00:00:20 Elphel353 ipsetd[708]: Expecting echo request payload 408 bytes.
Jan 1 00:00:20 Elphel353 ipsetd[708]: On echo request arrival, execute
/etc/ipsetd.script.
[ ok ]
* Starting telnet server...
telnetd: starting
port: 23; interface: any; login program: /bin/login;
maximum number of allowed simultaneous clients: unlimited [ ok ]
* Starting ftp server...
Jan 1 00:00:20 Elphel353 vftpd[714]: Starting vftpd 0.01
Jan 1 00:00:20 Elphel353 vftpd[715]: qos_setup_socket: unsupported AF [ ok ]
* Starting ssh server...
Jan 1 00:00:20 Elphel353 dropbear[726]: Running in background [ ok ]
* Starting mii-diag... [ ok ]
* Starting image server on port 8081, making Exif... [ ok ]
* Flushing JFFS2 (sync)... [ ok ]
* Starting autocampars daemon... [ ok ]
* Starting autoexposure daemon...
autoexposure started, daemon_bit=0x0, debug=0x1
autoexposure.c:126:main: autoexposure started, daemon_bit=0x0, debug=0x1[ ok ]
* Starting ccamftp daemon... [ ok ]
* initializing camera/sensor parameters...
arch/cris/arch-v32/drivers/elphel/framepars.c:387:initGlobalPars
GLOBALPARS(G_DEBUG)=0
initSequencers:resetting both sequencers
arch/cris/arch-v32/drivers/elphel/framepars.c:417:initMultiPars
GLOBALPARS(G_MULTI_NUM)=0
sensor clock set to 20000000
removing MRST from the sensor
Found MT9P001 2592x1944 sensor, chip ID=1801
trying MT9P001
Resetting MT9X001 sensor
Reading sensor registers to the shadows:
Initializing MT9X001 registers with default values:
Starting hardware sequencers [ ok ]
* Starting lighttpd web server... [ ok ]
* Setting time from NTP server... [
unavailable ]
* Looking for I/O board... [
10369"A" ]
ETRAX FS IOP USB Host Controller version 1.10 (c) 2004, 2005, 2006 Axis
Communications AB
crisv32_hc crisv32_hc.0: ETRAX FS IOP USB Host Controller
crisv32_hc crisv32_hc.0: new USB bus registered, assigned bus number 1
crisv32_hc crisv32_hc.0: irq 51, io base 0x00000000
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
crisv32_hc crisv32_hc.0: ETRAX FS IOP USB Host Controller
usbcore: registered new interface driver snd-usb-audio
usbcore: registered new interface driver snd-usb-caiaq
* Initializing USB hub... [ ok ]
* Setting system time from CMOS clock...
usb 1-1: new full speed USB device using crisv32_hc and address 2
usb 1-1: configuration #1 chosen from 1 choice
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected [ Fri
Sep 2 15:30:58 UTC 2011 ]
* Starting video streamer... [ ok ]
* Starting compas/GPS... [ none ]
launcher: nothing to launch
All scripts for runlevel 3 done in 88.14s.
#
#
#
# netSep 2 15:32:02 Elphel353 ipsetd[708]: Timed out after 120s._______________________________________________
Support-list mailing list
[email protected]
http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
