[Elphel-support] Elphel 353 server

Thu Feb 9 08:15:54 PST 2017

Hello Oleg,

Sorry for the delay, but I was travelling.
I may had previously a problem with one of the two RJ45 cables. 
I succeed in having the solid orange and blinking green LEDs and
finally to telnet on 192.168.0.9

Here is the response to dmesg :

Linux version 2.6.19 (andrey at inspiron) (gcc version 3.2.1 Axis release R64/1.64) #4 Thu Nov 4 20:21:16 MDT 2010
Setting up paging and the MMU.
On node 0 totalpages: 8192
  DMA zone: 32 pages used for memmap
  DMA zone: 0 pages reserved
  DMA zone: 8160 pages, LIFO batch:0
  Normal zone: 0 pages used for memmap
Linux/CRISv32 port on ETRAX FS (C) 2003, 2004 Axis Communications AB
Built 1 zonelists.  Total pages: 8160
Kernel command line: root=/dev/mtdblock3 init=/linuxrc rootfstype=jffs2
PID hash table entries: 256 (order: 8, 1024 bytes)
Dentry cache hash table entries: 8192 (order: 2, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 1, 16384 bytes)
Memory: 41376k/65536k available (1740k kernel code, 24160k reserved, 605k data, 72k init)
Calibrating delay loop... 199.47 BogoMIPS (lpj=997376)
Mount-cache hash table entries: 1024
NET: Registered protocol family 16
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
NET: Registered protocol family 2
IP route cache hash table entries: 512 (order: -2, 2048 bytes)
TCP established hash table entries: 2048 (order: 0, 8192 bytes)
TCP bind hash table entries: 1024 (order: -1, 4096 bytes)
TCP: Hash tables configured (established 2048 bind 1024)
TCP reno registered
Check hardware configuration of Elphel 353 camera
Elphel 10349/10369 IO extension board is not present
fast_timer_init()
JFFS2 version 2.2. (NAND) (C) 2001-2006 Red Hat, Inc.
io scheduler noop registered (default)
Serial: CRISv32 driver $Revision: 1.78 $ <6>ttyS0 at I/O 0xb0026000 (irq = 68) is a CRISv32
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
PPP generic driver version 2.4.2
ETRAX FS 10/100MBit ethernet v0.01 (c) 2003 Axis Communications AB
eth0: changed MAC to 00:40:8C:CD:00:00
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
ide: ETRAX FS built-in ATA DMA controller
ide: Elphel 353 io extension board not found, skipping initialization
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver usbserial
drivers/usb/serial/usb-serial.c: USB Serial support registered for generic
usbcore: registered new interface driver usbserial_generic
drivers/usb/serial/usb-serial.c: USB Serial Driver core
drivers/usb/serial/usb-serial.c: USB Serial support registered for Belkin / Peracom / GoHubs USB Serial Adapter
usbcore: registered new interface driver belkin
drivers/usb/serial/belkin_sa.c: USB Belkin Serial converter driver v1.2
drivers/usb/serial/usb-serial.c: USB Serial support registered for cp2101
usbcore: registered new interface driver cp2101
drivers/usb/serial/cp2101.c: Silicon Labs CP2101/CP2102 RS232 serial adaptor driver v0.07
drivers/usb/serial/usb-serial.c: USB Serial support registered for Garmin GPS usb/tty
usbcore: registered new interface driver garmin_gps
drivers/usb/serial/garmin_gps.c: garmin gps driver v0.28
drivers/usb/serial/usb-serial.c: USB Serial support registered for MCT U232
usbcore: registered new interface driver mct_u232
drivers/usb/serial/mct_u232.c: Magic Control Technology USB-RS232 converter driver z2.0
drivers/usb/serial/usb-serial.c: USB Serial support registered for pl2303
usbcore: registered new interface driver pl2303
drivers/usb/serial/pl2303.c: Prolific PL2303 USB to serial adaptor driver
ETRAX FS stream co-processor driver v0.01, (c) 2003 Axis Communications AB
stream co-processor: init done.
axisflashmap: ...
NAND device: Manufacturer ID: 0x20, Chip ID: 0xf1 (ST Micro NAND 128MiB 3,3V 8-bit)
Additional Info: ID byte3=0x0, byte4=0x1d
Bad block table found at page 65472, version 0x01
Bad block table found at page 65408, version 0x01
Flash is rated 30 ns, modifying bif_core_rw_grp3: old=0x6300483, new=0x6300001
NAND 128MiB 3,3V 8-bit: 0x08000000 bytes of NAND flash memory.
axisflashmap: Set to boot from NAND flash, making NAND flash primary device.
axisflashmap: flash read 512 bytes at 0x00040000, data: 00 b0 05 f0 25 ff ed 9c
axisflashmap: partition table offset 10, data: ef be 84 00 2d 0e 00 00
axisflashmap: Found a valid partition table at 0xc02fd9ae-0xc02fda3a.
offset == 0x00040000, size == 0x007C0000
offset == 0x00800000, size == 0x01800000
offset == 0x02000000, size == 0x05000000
offset == 0x07000000, size == 0x00C00000
Creating 1 MTD partitions on "NAND 128MiB 3,3V 8-bit":
0x00000000-0x08000000 : "main"
Creating 1 MTD partitions on "NAND 128MiB 3,3V 8-bit":
0x00000000-0x00040000 : "part0"
Creating 1 MTD partitions on "NAND 128MiB 3,3V 8-bit":
0x00040000-0x00800000 : "part1"
Creating 1 MTD partitions on "NAND 128MiB 3,3V 8-bit":
0x00800000-0x02000000 : "part2"
Creating 1 MTD partitions on "NAND 128MiB 3,3V 8-bit":
0x02000000-0x07000000 : "part3"
Creating 1 MTD partitions on "NAND 128MiB 3,3V 8-bit":
0x07000000-0x07c00000 : "part4"
ETRAX FS GPIO driver v2.5, (c) 2003-2006 Axis Communications AB
Elphel (R) model 353 FPGA (Xilinx (R) XC3S1200E) configuration driver - 132
Elphel (R) model 353 system clocks (PLL frequency synth.) driver - 133
fpga_control- 129
arch/cris/arch-v32/drivers/elphel/framepars.c:387:initGlobalPars GLOBALPARS(G_DEBUG)=0
arch/cris/arch-v32/drivers/elphel/framepars.c:417:initMultiPars GLOBALPARS(G_MULTI_NUM)=0
Elphel (R) Model 353 Frame Parameters device driver - 130 
Elphel FPGA interrupts initialized
Initializing DMA registers for EXTDMA3 - Elphel (R) Model 353 Camera Driver - 126
Elphel (R) model 353 i2c character device driver - 134, 2 channels
Raw image access driver- 131
Elphel (R) Model 353 video buffer device driver- 135
Elphel (R) model 353 Exif device driver - 125
Starting Elphel (R) Model 353 Gamma Tables device driver - 137 
Elphel (R) Model 353 Gamma Tables device driver - 137 
Elphel (R) Model 353 Histograms device driver
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
VFS: Mounted root (jffs2 filesystem) readonly.
Freeing unused kernel memory: 72k freed
Empty flash at 0x00b3bf48 ends at 0x00b3c000
Empty flash at 0x038e8f80 ends at 0x038e9000
Empty flash at 0x03a25b58 ends at 0x03a26000
Empty flash at 0x03a2e39c ends at 0x03a2e800
JFFS2 notice: (599) check_node_data: wrong data CRC in data node at 0x03a25800: read 0x1bad8012, calculated 0x5301fb24.
JFFS2 notice: (599) check_node_data: wrong data CRC in data node at 0x03a2e000: read 0xa142145c, calculated 0x81988289.
eth0: changed MAC to 00:0E:64:08:1C:AA
eth0: changed MAC to 00:0E:64:08:1C:AA
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
Initializing DMA registers for EXTDMA3 - sensor clock set to 20000000
10359 bitstream version =0x0359a053
10353 sensor clock set to 96000000
10359A sensor clock set to 96000000
removing MRST from the sensor
Setting internal HACT generation
arch/cris/arch-v32/drivers/elphel/framepars.c:417:initMultiPars GLOBALPARS(G_MULTI_NUM)=0
removing MRST from the sensor
trying MT9P001
trying other MT9X001
sensor power set low
 will set to 0x41
will set to 0x30
will set to 0x28
will set to 0x24
will set to 0x22
.. full
Inverted MRST
trying MT9X001
No image sensor found
arch/cris/arch-v32/drivers/elphel/multisensor.c:1255:multisensor_pgm_sensorphase WARNING: ((thispars->pars[P_CLK_SENSOR] == prevpars->pars[P_CLK_SENSOR])) but multi_phases_initialized is not yet set (re-init?)
Error programming clock 0 fact=0, err=0xffffff00
arch/cris/arch-v32/drivers/elphel/multisensor.c:1297:multisensor_pgm_sensorphase **** ERROR adjusting SDRAM clock phase in arch/cris/arch-v32/drivers/elphel/multisensor.c:1298:multisensor_pgm_sensorphase, result=0xfffffffb

Thanks for your advices to come.

 regards

  Daniel

Le 1 févr. 2017 à 01:52, Oleg <support-list at support.elphel.com> a écrit :

> Hello Daniel,
> 
> 1. LEDs:
> 
> In the normal operation:
> - orange: solid
> - green: blinking
> 
> 
> 2. If the software is reinstalled the ip address could have reset back to the default 192.168.0.9.
> 
> a. check your PC ip address
> b.
> ping 192.168.0.9
> The camera should respond to broadcast ping:
> ping -b 192.168.0.255
> 
> If the camera's ip is different then you are probably just getting (in chrome) ERR_ADDRESS_UNREACHABLE in the browser.
> 
> 
> 3. If you successfully pinged the camera and the browser reports (in chrome) ERR_CONNECTION_REFUSED - then you should be able to open a telnet session.
> telnet 192.168.0.x
> root/pass
> 
> run and send us the output:
> root at Elphel353 /root]764# dmesg
> 
> 
> Best regards,
> Oleg Dzhimiev
> Electronics Engineer
> phone: +1 801 783 5555 x124
> Elphel, Inc.
> 
> On 31 January 2017 at 14:05, Daniel Rouan <dan.rouan at free.fr> wrote:
> Thanks Andrey,
> 
> I'll do the direct identification as soon as I'm back in the lab where the camera is, but
> here attached is the order that was placed with details on parts.
> 
> The server no longer works means that I cannot connect through my browser as
> usual (using 192.168.0.4). I'll test the telnet. 
> 
> Leds are blinking if I remember well (again I've to do the test when I'm back).
> 
> 	Daniel
> 
> <Capture d’écran 2017-01-31 à 21.33.11.png>
> 
> 
> 
> Le 31 janv. 2017 à 17:38, Andrey Filippov <andrey at elphel.com> a écrit :
> 
>> Hello Daniel,
>> 
>> Certainly we can do that but maybe it is still possible to fix without sending it here? Can you tell - what do you have  - what camera boards (all boards are on Elphel wiki - you may search by number)? Does it have 10369 (interface board)? You mentioned 2 sensors - is it something like stereo with a multiplexer (10359)?
>> 
>> What do you mean "web server no longer works" - camera looks completely dead or you can telnet to it? What do the LEDs on the network connector do?
>> 
>> Andrey
>> 
>> ---- On Tue, 31 Jan 2017 01:30:16 -0800 Daniel Rouan<dan.rouan at free.fr> wrote ---- 
>>> Hello, 
>>> 
>>> In 2013, I bought a Elphel 353 with 2 BW sensors and used it several years 
>>> without  serious problems. 
>>> 
>>> From now, the web server no longer works and I did not succeed, after many attempts 
>>> and with the help of good engineers of my lab, to reinstall the sw, following your 
>>> instructions. 
>>> 
>>> If I send you the camera, could you solve the problem and return it to me within 
>>> the 3 coming weeks (I need it absolutely for the beginning of March) ? 
>>> 
>>> 
>>> Regards, 
>>> 
>>>  Daniel Rouan 
>>> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://support.elphel.com/pipermail/support-list_support.elphel.com/attachments/20170209/897f71c8/attachment-0002.html>