Re: [Elphel-support] An error in replacing the 14-megapixel sensor(mt9f002) by 5-megapixel sensor(mt9006)
Ali, I see. So, you just need to go http://community.elphel.com/bootblock393/ again and put the correct data to make 5MPx work. See the attached image. In short - in the AUX Board table - make sure, *Application* field is *MT9P006 *, and the *Application mode* is *15 *. Then hit "PROGRAM AUX" - it's slow, so wait a bit (10 sec?). Then "READ AUX" to check the changes were made. Then reboot the camera. And it should work. If not, please send the autocampars log again. I want to back up the micro-SD card but it dose not mount on any OS; how to > can I do it? It will mount in any Linux OS. Simply copying the files will not work - you need raw cloning - please, read about "dd"-utility. If you have Windows only then it should see the BOOT partition - it's FAT. Regards, Oleg On Tue, Oct 20, 2020 at 6:04 AM ali tamimi wrote: > > Oleg, > Everything is OK with "14 Mpix" sensor; but when I connect the "5 Mpix" > no picture is seen at all. I'm sure that there is no problem with cable(it > works well with "14 Mpix" sensor ). The micro-SD card marked "5MPx" is also > insert to the slot too. I put the log files below. > And another question. I want to back up the micro-SD card but it dose not > mount on any OS; how to can I do it? > > *log files:* > *The "Read AUX" output:* > > Elphel > 10389 > B > F80008 > 1603185256 > Eyesis4pi393 > 1001 > > > *The "autocampars.log" :* > root@elphel393:~# cat /var/log/autocampars.log > 00014.09 autocampars: initializing state file /var/volatile/state/camera > 00014.27 autocampars: Application - Eyesis4pi393, mode: 1001 > > 00014.30 autocampars: Processing camera state: BOOT > 00014.33 autocampars: Got sensor map from sysfs: > 0: mt9p006, none, none, none > 1: mt9p006, none, none, none > 2: mt9p006, none, none, none > 3: mt9p006, none, none, none > 00014.35 autocampars: Active sensor ports: 0,1,2,3 master_port = 0 > 00014.38 autocampars: Sensors map read from the sysfs: [mt9p006, none, > none, none],[mt9p006, none, none, none],[mt9p006, none, none, > none],[mt9p006, none, none, none] > 00014.41 autocampars: Parsed existing ini file > 00014.43 autocampars: get_application_mode()->1013623 > 00014.46 autocampars: Parsed existing ini file > 00014.49 autocampars: Detecting sensors for Eyesis4pi393 > 00014.51 autocampars: Got --init command, initialization was not > completed, just continue > 00014.54 autocampars: detect_camera() > 00014.56 autocampars: detect_camera(): > 0: mt9p006, none, none, none > 1: mt9p006, none, none, none > 2: mt9p006, none, none, none > 3: mt9p006, none, none, none > 00014.59 autocampars: ports:0, 1, 2, 3 > 00014.62 autocampars: boot > 00014.64 autocampars: Parsed existing ini file > 00014.67 autocampars: Using sensor mask 0xf > 00016.95 autocampars: Setting sensors/multiplexers power > 00016.98 autocampars: set_eyesis_power_control()=>Array > ( > [result] => OK > [retval] => 0 > ) > > 00017.00 autocampars: GLOBALS['camera_state_arr']=>Array > ( > [exit_stage] => > [state] => BOOT > [rev10389] => B > [application] => Eyesis4pi393 > [mode] => 1001 > [max_frame_time] => 30 > [is_slave] => 1 > [eyesis_top] => 1 > [is_eyesis] => 1 > [eyesis_power] => 1 > [max_latency] => 5 > ) > > 00017.03 autocampars: Current state: BOOT > 00017.06 autocampars: This is a slave camera - waiting for master to > contol next steps > 00017.08 autocampars: Log file saved as /var/log/autocampars.log > 00017.11 autocampars: -- > root@elphel393:~# > > On Mon, Oct 19, 2020 at 10:18 PM Oleg > wrote: > >> Ali, >> >> 1. Please send the /var/log/autocampars.log. It can help to rule out a >> possible misconfiguration. If everything is correct then one can assume >> it's a bad cable. >> >> 2. (just want to double check your configuration) Go >> http://community.elphel.com/bootblock393/, make sure the ip address in >> the 1st table is correct, then click "Read AUX" in the "AUX board >> (10389)"-table - what's the output? >> >> Regards, >> Oleg >> >> On Mon, Oct 19, 2020 at 9:21 AM Elphel Support < >> support-list@support.elphel.com> wrote: >> >>> Hello Ali, >>> >>> There should be no problems with impedance matching, we tested both >>> types of sensors with up to 450mm cables (for ectremely long cable >>> programmatic phase adjustment may be needed). And the cables are the same >>> for both serial (14MPix) and
Re: [Elphel-support] An error in replacing the 14-megapixel sensor(mt9f002) by 5-megapixel sensor(mt9006)
Ali, 1. Please send the /var/log/autocampars.log. It can help to rule out a possible misconfiguration. If everything is correct then one can assume it's a bad cable. 2. (just want to double check your configuration) Go http://community.elphel.com/bootblock393/, make sure the ip address in the 1st table is correct, then click "Read AUX" in the "AUX board (10389)"-table - what's the output? Regards, Oleg On Mon, Oct 19, 2020 at 9:21 AM Elphel Support < support-list@support.elphel.com> wrote: > Hello Ali, > > There should be no problems with impedance matching, we tested both types > of sensors with up to 450mm cables (for ectremely long cable programmatic > phase adjustment may be needed). And the cables are the same for both > serial (14MPix) and parallel (5MPix). > > Andrey > > > On Mon, 19 Oct 2020 05:33:14 -0600 *ali tamimi > >* wrote > > Hello Oleg > yes, i can 'ssh' to camera and also can send the/var/log/autocampars.log. > The microSD card marked "5MPx" is also insert to the slot. > We opened the camera. When closing the sensor cable was pressed slightly > and deformed. I guess the cable is damaged. In the parts list of the "5 > MPx" sensor, FFC cable with model number 050-30-51B, is provided. But by > connecting this cable, the sensor is not detected eaither.The connection > photo is sent in the attachment. Could there be a problem with the cable > (for example, impedance matching, etc.)? > > On Sun, Oct 18, 2020 at 11:23 AM Oleg > wrote: > > Hello Ali, > > Can you 'ssh' to the camera? Could you send the /var/log/autocampars.log? > > ~$ ssh root@192.168.0.9 <http://mailto:root@192.168.0.9> > ~# cat /var/log/autocampars.log > > > Or if you use minicom - send the boot log. > > If I remember right you should have a microSD card marked a "5MPx" - the > camera autoboots from the card - I suggest you try the card first. And the > only thing you will need is to set "MT9*P*006" from the bootblock393 page. > > Regards, > Oleg > > On Sun, Oct 18, 2020 at 7:56 AM ali tamimi wrote: > > Hello > We have provided your product 10393. Your camera is very well designed and > made. Thank you for your good products and complete documentation and > your support. > Sensor installed on 10393 is a 14-megapixel sensor (10398) "mt9f002" by > default that Works well. We also bought the 10338 "mt9006" sensor. By > replacing the sensors, the new one is not detectable and no image is seen. > We downloaded the latest firmware, although the default sensor is > "mt9006" in the manual, the "devicetree.dtb" replacement process was > performed according to the instructions,10393 nand flash was programmed > but the sensor is not detected again.The image of error in web interface > sent in the attachment. Thanks for your support in solving the problem. > ___ > Support-list mailing list > Support-list@support.elphel.com > http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com > > > ___ > Support-list mailing list > Support-list@support.elphel.com > http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com > > > > ___ > Support-list mailing list > Support-list@support.elphel.com > http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com > -- Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] An error in replacing the 14-megapixel sensor(mt9f002) by 5-megapixel sensor(mt9006)
Hello Ali, Can you 'ssh' to the camera? Could you send the /var/log/autocampars.log? > ~$ ssh root@192.168.0.9 > ~# cat /var/log/autocampars.log Or if you use minicom - send the boot log. If I remember right you should have a microSD card marked a "5MPx" - the camera autoboots from the card - I suggest you try the card first. And the only thing you will need is to set "MT9*P*006" from the bootblock393 page. Regards, Oleg On Sun, Oct 18, 2020 at 7:56 AM ali tamimi wrote: > Hello > We have provided your product 10393. Your camera is very well designed and > made. Thank you for your good products and complete documentation and > your support. > Sensor installed on 10393 is a 14-megapixel sensor (10398) "mt9f002" by > default that Works well. We also bought the 10338 "mt9006" sensor. By > replacing the sensors, the new one is not detectable and no image is seen. > We downloaded the latest firmware, although the default sensor is > "mt9006" in the manual, the "devicetree.dtb" replacement process was > performed according to the instructions,10393 nand flash was programmed > but the sensor is not detected again.The image of error in web interface > sent in the attachment. Thanks for your support in solving the problem. > ___ > Support-list mailing list > Support-list@support.elphel.com > http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com > ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] NC353L Recording Issue
Hi William, Could you provide a bit more details? Note: In the comments below I use the camera's default ip address - 192.168.0.9. 1. When recording freezes is the compressor still running? > Refresh this page a few times: http://192.168.0.9:8081/meta > Check the FrameNumber is getting updated. or just check if the images are being refreshed in the control interface: > http://192.168.0.9/camvc.html 2. Is autoexposure on? Can it get above 100ms? This will result in a reduced frame rate. Have you tried recording with fixed exposure or limiting it? To limit autoexposure, go to parameter editor and change AUTOEXP_EXP_MAX, here's a quick link <http://192.168.0.9/parsedit.php?title=Parameters+for+groups:+autoexposure+_ON_EXP_MAX_FRACPIX_LEVEL_DUR_VEXPOS_THRESH_PERIOD_DIM_01_DIM_23>. Try 10 or less. 3. Do you use http://192.168.0.9/camogmgui.php for recording? If the frame rate got limited by long exposure and you use the web interface - my guess is the web server got overwhelmed with status requests from the recording interface - you won't be able to refresh the page as well. 4. Do you use internal HDD or external SATA? It's probably not relevant but still. 5. What's the camera firmware? It is printed on the camera's front page. Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. On Wed, Sep 30, 2020 at 1:19 AM William Smith wrote: > To whom It may concern > > Hi we are facing an issue where we record images for about 2 hours, then > the recording freezes and when we stop and refresh and try to record again, > nothing happens. also we can not create a folder when this issue happens. > > Regards > William > 000 > > [image: PMM Logo] > William Smith > Device Manager/ IT Technician > m: +27 73 371 7657 > t: +27 18 468 1170 > a: 36 Radloff Street Klerksdorp > www.profmap.co.za > > > ___ > Support-list mailing list > Support-list@support.elphel.com > http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] Stream stopping after setting decimation
Hi, scale at the source That's not possible right away. - one relatively simple way I can think of would be installing gstreamer plugins on the camera then scale and restream. That will increase latency. - another way would be modifying the streamer program (elphel-apps-astreamer <https://git.elphel.com/Elphel/elphel-apps-astreamer/tree/rocko>). Are you required to use rtsp? If not then it's possible to have a script/program that would do the scaling and you would get images by http-requests. Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. On Wed, Aug 5, 2020 at 6:13 AM Daniele Forsi wrote: > Hello Oleg, > >> >> > Meanwhile, you can try: > > * lowering the compression quality - QUALITY parameter, the default one > is 80%. > > * wider lens allowing for a smaller window of interest with the required > field of view. fps rate is programmable. > > thank you for your answer, since one of our requirements is todisplay the > video on a 10 inches screen with a resolution of 1024x600. Is there a way > to scale the stream at the source in addition to setting a WOI or the DCM_* > parameters? > > > thank you > > Daniele Forsi > ___ > Support-list mailing list > Support-list@support.elphel.com > http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] Stream stopping after setting decimation
Hi, I reproduced the problem. What happens is the compressor freezes when the DCM_* parameters are applied. Since it's not used very often something probably broke along the way. We'll try to fix this. Meanwhile, you can try: * lowering the compression quality - QUALITY parameter, the default one is 80%. * wider lens allowing for a smaller window of interest with the required field of view. fps rate is programmable. Regards, Oleg On Mon, Aug 3, 2020 at 6:37 AM Daniele Forsi wrote: > Hi, > > > 1. Do you see the image degradation and image dimensions changes in the > web interface after the parameters are applied? > > wtih DCM_HOR and DCM_VERT both at 2 the dimensions changed from 2592x1936 > to 1293x960 > > > Do images keep refreshing there (or check mjpeg stream)? > > only one static image is received with the new size at > http://192.168.0.9:2323/bimg but the stream at > http://192.168.0.9:2323/mimg is showing a black page > > > Also, check http://192.168.0.9:2323/meta - refresh the page a few times > and check if the frame counters are updating? > > currentSensorFrame and currentSensorFrameHex are updating but all other > parameters aren't updating > > This XML file does not appear to have any style information associated > with it. The document tree is shown below. > > > 0x2abf440 > 0xa390400 > 0xa390400 > 0xa390400 > 0xa390400 > 0x50 > 0x0 > 0x0 > 0x510 > 0x3c0 > 0x568 > 1588812730.071853 > 0x > 4659 > 3646 > 5eb35bba 000118ad > 0x1233 > 0x0e3e > > "1384 (0x568)" > "0x0009ac10" > "REDACTED" > "" > "3646" > "1" > "0" > "2020:05:07 00:52:10.071853" > "0.001019" > "REDACTED" > > > > > > 2. In your log I see fps was 2.5. > > Was autoexposure running? > > yes > > it's 2.5 in the last line printed but it's 10 in the previous lines > > thanks, > Daniele Forsi > > > ___ > Support-list mailing list > Support-list@support.elphel.com > http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] Stream stopping after setting decimation
Hi, 1. Do you see the image degradation and image dimensions changes in the web interface after the parameters are applied? Do images keep refreshing there (or check mjpeg stream)? Also, check http://192.168.0.9:2323/meta - refresh the page a few times and check if the frame counters are updating? 2. In your log I see fps was 2.5. Was autoexposure running? Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. On Fri, Jul 31, 2020 at 10:44 AM Daniele Forsi wrote: > Hello, > > when I change the parameters DCM_HOR and DCM_VERT the stream stops and the > str daemon can't be stopped with Ctrl-C or kill -KILL and I need to reboot > the board (the web server and ssh server are still working). > I have set those parameters to 2, 3 and 4 using the web interface. > > This happens both if str is not running and when it is running , in this > case the last lines printed are: > > streamer.cpp: handler: 366: sensor port: 0 event: running= 0 streamer.cpp: > update_settings: 131: sensor port: 0 update_settings > video.cpp: getFramePars: 285: sensor port: 0 before=0 > metadata_start=46106528 > video.cpp: getFramePars: 285: sensor port: 0 before=0 > metadata_start=45742816 > video.cpp: get_current_desc: 350: sensor port: 0 fps=2.5 > Socket::poll()... > socket.fd == 8; 9; > revents == 0; POLLIN == 1 > revents == 0; POLLIN == 1 > streamer.cpp: handler: 366: sensor port: 0 event: running= 0 streamer.cpp: > update_settings: 131: sensor port: 0 update_settings > > > after a couple of seconds another line is printed: > > video.cpp: getFramePars: 285: sensor port: 0 before=0 > metadata_start=41742464 > > and then nothing more. > > How can we debug this situation? > > thanks you > Daniele Forsi > > > > ___ > Support-list mailing list > Support-list@support.elphel.com > http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] Elphel 353 / 359 stereo camera problem
Yes, 8.2.15 should be fine too... as long as you find the MULTI_* parameters. Regards, Oleg On Mon, Jun 22, 2020 at 12:25 PM Simon Vogl wrote: > Hi Oleg, > > thanks for the timely feedback, let me answer inline: > Am 22.06.20 um 19:44 schrieb Oleg: > > Hi, > > When stacking images vertically the mux board let's the 1st sensor (top > image) through w/o buffering in SDRAM. The second is buffered. So, it could > be SDRAM phase. > > Well, this is definitely involved - when I set the right clock parameters, > I could get reasonable picture content again (although only on one image). > > 1. What firmware version are you using? > ~# cat /etc/issue > or > ~# cat /etc/release > > [root@Elphel353 /root]817# cat /etc/release > JFFSID="8.2.15" > > close to .16 but not exactly - does an upgrade in the field make sense? > > 2. If the firmware is 8.2.16 (hopefully), then the phase settings are > available through the camera parameters: > http://192.168.0.9/autocampars.php -> check 'unsafe' - in the table you > will find: > >> MULTI_PHASE_SDRAM >> MULTI_PHASE1 >> MULTI_PHASE2 >> MULTI_PHASE3 > > Check the values from a camera that works ok. And try to fix them for a > bad camera from this autocampars page (not 10359_controls.html, which > communicates directly with fpga - cannot not store settings across reboots) > Once you set the values, go back to http://192.168.0.9/autocampars.php > and 'save' the config in the second table. Then reboot. > > ok great, will try it this way, guess that's what I was missing. > > 3. Has anything changed recently? Like you stored a new configuration? > Reboot often? Applied any changes? > The camera stores and loads its firmware from flash - sometimes the fs or > some file there would get corrupted when changes to the filesystem are > applied but not properly synced. > With a single lens camera most of the trouble was usually caused by > /etc/autocampars.xml going corrupt. Then backing it up, removing the file > and then rebooting (it autoregenerated on reboot if not there) might help. > Note - if you manipulate files manually from a command line - run 'sync' > when done. Then repeat step 2 if firmware is 8.2.16. > > The maintenaince guys did a few reboots last week (suspected troubles with > a poe switch) and I am hoping that this is the cause of the trouble I > bit-compared the bit files, they're identical to a running camera. The xml > files looked fine as well. > > Will try around more and come back to you - thanks a lot! > Simon > > > Regards, > Oleg > > On Mon, Jun 22, 2020 at 10:29 AM Simon Vogl wrote: > >> Dear all, >> >> we have a bunch of 353-based stereo cameras that are in operation for >> seven years meanwhile and we've been very happy with them. Over the last >> weeks, some of them have image errors, at first sight it looks like one of >> the sensor is not configured correctly, a combined image looks like: >> >> I found that this seems to be a problem with the 10359 multiplexer board >> -- exchanging this resolves the issue for a camera. >> >> When booting, the relevant portion of dmesg reports this error on the >> affected cameras: >> >> arch/cris/arch-v32/drivers/elphel/framepars.c:390:initGlobalPars >> GLOBALPARS(G_DEBUG)=0 >> initSequencers:resetting both sequencers >> arch/cris/arch-v32/drivers/elphel/framepars.c:420:initMultiPars >> GLOBALPARS(G_MULTI_NUM)=0 >> Initializing DMA registers for EXTDMA3 - >> sensor clock set to 4800 >> 10359 bitstream version =0x0359a054 >> 10353 sensor clock set to 9600 >> 10359A sensor clock set to 9600 >> removing MRST from the sensor >> Found MT9P001 2592x1944 sensor on 10359A port 1, chip ID=1801 >> Found MT9P001 2592x1944 sensor on 10359A port 2, chip ID=1801 >> Setting internal HACT generation >> Found MT9P001 2592x1944 sensor, chip ID=1801 >> arch/cris/arch-v32/drivers/elphel/framepars.c:420:initMultiPars >> GLOBALPARS(G_MULTI_NUM)=f >> ERROR adjusting SDRAM clock phase in >> arch/cris/arch-v32/drivers/elphel/multisensor.c:1697:multisensor_adjustSDRAM >> low90=3, low_l=249, high90=3, high_l=-250 >> arch/cris/arch-v32/drivers/elphel/multisensor.c:1310:multisensor_pgm_sensorphase >> ERROR adjusting SDRAM clock phase in >> arch/cris/arch-v32/drivers/elphel/multisensor.c:1311:multisensor_pgm_sensorphase, >> result=0x >> Resetting MT9X001 sensor >> Reading sensor registers to the shadows: >> Initializing MT9X001 registers with default values: >> Starting hardware sequencers >> arch/cris/arch-v32/drivers/elphel/quantizatio
Re: [Elphel-support] 353 Problem Mainboards
Hi Linden, Follow up. Were you able to get the serial output? Regards, Oleg On Tue, Sep 10, 2019 at 5:29 PM Oleg wrote: > Link to the image of parts 1 & 2 > <https://wiki.elphel.com/wiki/File:Cable_RS232_out.jpeg> > > On Tue, Sep 10, 2019 at 5:25 PM Oleg > wrote: > >> Hi Linden, >> >> You need a program like minicom to display a serial port output. >> The speed settings for the serial port are 115200 8N1 >> <https://wiki.elphel.com/wiki/Elphel_353_series_quick_start_guide#Serial_port_.2810369_board_required.29>. >> And the device is normally: /dev/ttyUSB0 >> >> Do you have the cable? >> >> It consists of 3 parts: parts 1 & 2, part 3 >> <https://wiki.elphel.com/wiki/File:Rs232-usb.jpeg>): >> parts 1&2: >> >>> RS-232 Adapter/Cable is used to connect to the serial port of NC353L-369 >>> cameras. This port outputs all the boot and debug messages and provides >>> system console that can be used for software development - this console >>> allows to control the camera even if the network is misconfigured. >>> This kit consists of 2 parts: 0353-01-04 - DB9 to modular adapter with >>> custom wiring and a >>> 0353-01-05 - 6-wire modular cable with crossover wiring (6-wire modular >>> telephone cable) >> >> part3: >> >>> USB to RS-232 converter cable - an addition to RS-232 Adapter/Cable that >>> allows to use a host PC's USB port instead of RS232. >> >> >> Regards, >> Oleg >> >> On Tue, Sep 10, 2019 at 5:01 PM Linden @ Zone4 wrote: >> >>> Hi Oleg, >>> >>> I have another camera with issues booting that I would like to diagnose. >>> Discovered I have a 10369 board can you pass along some instructions and I >>> will see if it has a bad block. >>> >>> Thanks, >>> >>> Linden Mills-Connery >>> Zone4 Team <https://zone4.ca/contact/> >>> 205-820 Main Street >>> Canmore, AB, T1W2B7 >>> 403-401-7215 >>> >>> >>> On Tue, 28 Aug 2018 at 16:19, Oleg >>> wrote: >>> >>>> Linden, >>>> >>>> I reflashed the 000E64081CA1 - and it works now. >>>> >>>> It had a bad block. See the old bootlog from the serial output (via the >>>> extension board 10369) below. >>>> >>>> Have you ever reflashed a camera? One of the tests that can tell if the >>>> flash is probably corrupted is putting the camera in the netboot mode. Then >>>> reflash if possible - during reflashing it detects and skips the bad >>>> blocks. >>>> >>>> Boot log: >>>> >>>>> ETRAX FS NAND boot loader >>>>> >>>>> >>>>> >>>>> = >>>>> >>>>> >>>>> >>>>> Rev 1, Nov 23 2009 12:31:43 >>>>> >>>>> >>>>> >>>>> Boot config: 0x0004->0x4044, len 0x0020, boot @ 0x4044 >>>>> >>>>> >>>>> >>>>> CPU revision: 0x0020 >>>>> >>>>> >>>>> >>>>> Bootloader main at 0x38000ce2 >>>>> >>>>> >>>>> >>>>> Data end: 0x3800573c >>>>> >>>>> >>>>> >>>>> Bss: 0x38008000 >>>>> >>>>> >>>>> >>>>> Heap: 0x38008000 >>>>> >>>>> >>>>> >>>>> Identifying nand chip... >>>>> >>>>> >>>>> >>>>> maf_id: 0x002c; dev_id: 0x00f1 >>>>> >>>>> >>>>> >>>>> mtd->size == 0x0800 >>>>> >>>>> >>>>> >>>>> scan_bbt(); mtd->size == 0x0800 >>>>> >>>>> >>>>> >>>>> scan_bbt() ...01; mtd->size == 0x0800 >>>>> >>>>> >>>>> >>>>> len == 0x0100; and BBT_LEN_1 == 0x0400 >>>>> >>>>> >>>>> >>>>> scan_bbt() ...02; mtd->size == 0x0800 >>>>> >>>>> >>>>> >>>>> scan_bbt() ...03; mtd->size == 0x0800 >>>>> >>>>> >>>>> >>&
Re: [Elphel-support] 353 Problem Mainboards
Link to the image of parts 1 & 2 <https://wiki.elphel.com/wiki/File:Cable_RS232_out.jpeg> On Tue, Sep 10, 2019 at 5:25 PM Oleg wrote: > Hi Linden, > > You need a program like minicom to display a serial port output. > The speed settings for the serial port are 115200 8N1 > <https://wiki.elphel.com/wiki/Elphel_353_series_quick_start_guide#Serial_port_.2810369_board_required.29>. > And the device is normally: /dev/ttyUSB0 > > Do you have the cable? > > It consists of 3 parts: parts 1 & 2, part 3 > <https://wiki.elphel.com/wiki/File:Rs232-usb.jpeg>): > parts 1&2: > >> RS-232 Adapter/Cable is used to connect to the serial port of NC353L-369 >> cameras. This port outputs all the boot and debug messages and provides >> system console that can be used for software development - this console >> allows to control the camera even if the network is misconfigured. >> This kit consists of 2 parts: 0353-01-04 - DB9 to modular adapter with >> custom wiring and a >> 0353-01-05 - 6-wire modular cable with crossover wiring (6-wire modular >> telephone cable) > > part3: > >> USB to RS-232 converter cable - an addition to RS-232 Adapter/Cable that >> allows to use a host PC's USB port instead of RS232. > > > Regards, > Oleg > > On Tue, Sep 10, 2019 at 5:01 PM Linden @ Zone4 wrote: > >> Hi Oleg, >> >> I have another camera with issues booting that I would like to diagnose. >> Discovered I have a 10369 board can you pass along some instructions and I >> will see if it has a bad block. >> >> Thanks, >> >> Linden Mills-Connery >> Zone4 Team <https://zone4.ca/contact/> >> 205-820 Main Street >> Canmore, AB, T1W2B7 >> 403-401-7215 >> >> >> On Tue, 28 Aug 2018 at 16:19, Oleg >> wrote: >> >>> Linden, >>> >>> I reflashed the 000E64081CA1 - and it works now. >>> >>> It had a bad block. See the old bootlog from the serial output (via the >>> extension board 10369) below. >>> >>> Have you ever reflashed a camera? One of the tests that can tell if the >>> flash is probably corrupted is putting the camera in the netboot mode. Then >>> reflash if possible - during reflashing it detects and skips the bad blocks. >>> >>> Boot log: >>> >>>> ETRAX FS NAND boot loader >>>> >>>> >>>> >>>> = >>>> >>>> >>>> >>>> Rev 1, Nov 23 2009 12:31:43 >>>> >>>> >>>> >>>> Boot config: 0x0004->0x4044, len 0x0020, boot @ 0x4044 >>>> >>>> >>>> >>>> CPU revision: 0x0020 >>>> >>>> >>>> >>>> Bootloader main at 0x38000ce2 >>>> >>>> >>>> >>>> Data end: 0x3800573c >>>> >>>> >>>> >>>> Bss: 0x38008000 >>>> >>>> >>>> >>>> Heap: 0x38008000 >>>> >>>> >>>> >>>> Identifying nand chip... >>>> >>>> >>>> >>>> maf_id: 0x002c; dev_id: 0x00f1 >>>> >>>> >>>> >>>> mtd->size == 0x0800 >>>> >>>> >>>> >>>> scan_bbt(); mtd->size == 0x0800 >>>> >>>> >>>> >>>> scan_bbt() ...01; mtd->size == 0x0800 >>>> >>>> >>>> >>>> len == 0x0100; and BBT_LEN_1 == 0x0400 >>>> >>>> >>>> >>>> scan_bbt() ...02; mtd->size == 0x0800 >>>> >>>> >>>> >>>> scan_bbt() ...03; mtd->size == 0x0800 >>>> >>>> >>>> >>>> scan_bbt() ...1; mtd->size == 0x0800 >>>> >>>> >>>> >>>> scan_bbt() ...2; mtd->size == 0x0800 >>>> >>>> >>>> >>>> scan_bbt() search_read_bbts(); mtd->size == 0x0800 >>>> >>>> >>>> >>>> search_read_bbts() search primary table; mtd->size == 0x0800 >>>> >>>> >>>> >>>> search_bbt() ...1; mtd->size == 0x0800 >>>> >>>> >>>> >>>> search_bbt() ...2; maxblocks: 0x0004; mtd->size == 0x0800 >>>> >>>> >>>&
Re: [Elphel-support] 353 Problem Mainboards
Hi Linden, You need a program like minicom to display a serial port output. The speed settings for the serial port are 115200 8N1 <https://wiki.elphel.com/wiki/Elphel_353_series_quick_start_guide#Serial_port_.2810369_board_required.29>. And the device is normally: /dev/ttyUSB0 Do you have the cable? It consists of 3 parts: parts 1 & 2, part 3 <https://wiki.elphel.com/wiki/File:Rs232-usb.jpeg>): parts 1&2: > RS-232 Adapter/Cable is used to connect to the serial port of NC353L-369 > cameras. This port outputs all the boot and debug messages and provides > system console that can be used for software development - this console > allows to control the camera even if the network is misconfigured. > This kit consists of 2 parts: 0353-01-04 - DB9 to modular adapter with > custom wiring and a > 0353-01-05 - 6-wire modular cable with crossover wiring (6-wire modular > telephone cable) part3: > USB to RS-232 converter cable - an addition to RS-232 Adapter/Cable that > allows to use a host PC's USB port instead of RS232. Regards, Oleg On Tue, Sep 10, 2019 at 5:01 PM Linden @ Zone4 wrote: > Hi Oleg, > > I have another camera with issues booting that I would like to diagnose. > Discovered I have a 10369 board can you pass along some instructions and I > will see if it has a bad block. > > Thanks, > > Linden Mills-Connery > Zone4 Team <https://zone4.ca/contact/> > 205-820 Main Street > Canmore, AB, T1W2B7 > 403-401-7215 > > > On Tue, 28 Aug 2018 at 16:19, Oleg > wrote: > >> Linden, >> >> I reflashed the 000E64081CA1 - and it works now. >> >> It had a bad block. See the old bootlog from the serial output (via the >> extension board 10369) below. >> >> Have you ever reflashed a camera? One of the tests that can tell if the >> flash is probably corrupted is putting the camera in the netboot mode. Then >> reflash if possible - during reflashing it detects and skips the bad blocks. >> >> Boot log: >> >>> ETRAX FS NAND boot loader >>> >>> >>> >>> = >>> >>> >>> >>> Rev 1, Nov 23 2009 12:31:43 >>> >>> >>> >>> Boot config: 0x0004->0x4044, len 0x0020, boot @ 0x4044 >>> >>> >>> >>> CPU revision: 0x0020 >>> >>> >>> >>> Bootloader main at 0x38000ce2 >>> >>> >>> >>> Data end: 0x3800573c >>> >>> >>> >>> Bss: 0x38008000 >>> >>> >>> >>> Heap: 0x38008000 >>> >>> >>> >>> Identifying nand chip... >>> >>> >>> >>> maf_id: 0x002c; dev_id: 0x00f1 >>> >>> >>> >>> mtd->size == 0x0800 >>> >>> >>> >>> scan_bbt(); mtd->size == 0x0800 >>> >>> >>> >>> scan_bbt() ...01; mtd->size == 0x0800 >>> >>> >>> >>> len == 0x0100; and BBT_LEN_1 == 0x0400 >>> >>> >>> >>> scan_bbt() ...02; mtd->size == 0x0800 >>> >>> >>> >>> scan_bbt() ...03; mtd->size == 0x0800 >>> >>> >>> >>> scan_bbt() ...1; mtd->size == 0x0800 >>> >>> >>> >>> scan_bbt() ...2; mtd->size == 0x0800 >>> >>> >>> >>> scan_bbt() search_read_bbts(); mtd->size == 0x0800 >>> >>> >>> >>> search_read_bbts() search primary table; mtd->size == 0x0800 >>> >>> >>> >>> search_bbt() ...1; mtd->size == 0x0800 >>> >>> >>> >>> search_bbt() ...2; maxblocks: 0x0004; mtd->size == 0x0800 >>> >>> >>> >>> Block: 0x03ff >>> >>> >>> >>> Check, if we found a bbt for each requested chip >>> >>> >>> >>> Bad block table found at page0xffc0, version 0x0001 >>> >>> >>> >>> search_read_bbts() search mirror table >>> >>> >>> >>> search_bbt() ...1; mtd->size == 0x0800 >>> >>> >>> >>> search_bbt() ...2; maxblocks: 0x0004; mtd->size == 0x0800 >>> >>> >>> >>> Block: 0x03ff >>> >>> >>> >>> Block: 0x03fe >>> >>> >>> >>> Check, if we found a b
Re: [Elphel-support] make "permanent" changes on a 393 camera ?
Hi, > What can be done eg for adding a startup script on the 393 or for adding a > ssh public key for authentication (beside rebuilding and flashing the > firmware) ? > > a. Add it like you would normally do with SysV - script to /etc/init.d, then set a runlevel. b. Edit /etc/init.d/init_elphel393 (around where it's running /etc/elphel393/init_elphel393.py) - its runlevel is 94 c. Edit /etc/elphel393/init_elphel393.py If you boot from flash to permanently store the changes you will have to run: root@elphel393:~# overlay_sync 1 root@elphel393:~# shutdown -hP now #powercycle PS: > > For the public key there the SSH_ASKPASS workaround, eg s.sh: > > #!/bin/bash > export SSH_ASKPASS=$(mktemp) > echo echo pass > $SSH_ASKPASS > chmod +x $SSH_ASKPASS > setsid -w ssh $USER_AT_HOST $@ > EXIT_STATUS=$? > rm $SSH_ASKPASS > exit $EXIT_STATUS > > ? Regards, Oleg ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] Elphel 393 Nand upgrade
Alright, so it's some marginal 3.3V. If you need 3.3V - try replacing the wires or the power supply. On Thu, Dec 13, 2018 at 2:26 PM Mohamed Morsy wrote: > I replaced it with the 10385 board and now it works. Thanks. > > On Thu, Dec 13, 2018 at 4:21 PM Mohamed Morsy wrote: > >> There are no sensors connected. I'm using direct 3.3V from a power >> supply. I can try the 10385 board. >> >> On Thu, Dec 13, 2018 at 4:19 PM Oleg >> wrote: >> >>> This happens when the board tries to turn on 5V and fails. >>> >>> Try: >>> * disconnect sensors if any connected >>> * another power supply (how do you power the board? direct 3.3V or 48V >>> via 10385 board?) >>> * another power cable >>> >>> On Thu, Dec 13, 2018 at 1:50 PM Mohamed Morsy >>> wrote: >>> >>>> No it does not boot from flash. >>>> The card does work with other boards. >>>> >>>> On Thu, Dec 13, 2018 at 3:46 PM Oleg >>>> wrote: >>>> >>>>> Hi Mohamed, >>>>> >>>>> Does the board boot fine from flash? >>>>> Does the same uSD card work with other rev B boards? >>>>> >>>>> On Thu, Dec 13, 2018 at 1:30 PM Mohamed Morsy >>>>> wrote: >>>>> >>>>>> Hi Oleg, >>>>>> >>>>>> I'm having another issue with another Elphel. It doesn't seem to boot >>>>>> up completely. When I connect the USB cable, open minicom, and power on >>>>>> the >>>>>> Elphel, it starts booting up for 2 seconds then stops and minicom says >>>>>> "Cannot open /dev/ttyUSB0!" The last thing on minicom before it stops is: >>>>>> >>>>>> [2.034545] elphel393-pwr elphel393-pwr@0: Probing elphel393-pwr >>>>>> >>>>>> This is a Rev B Elphel running on a uSD card. Do you know what the >>>>>> issue might be? >>>>>> >>>>>> Thanks, >>>>>> >>>>>> Mohamed >>>>>> >>>>>> On Wed, Dec 5, 2018 at 9:48 AM Mohamed Morsy >>>>>> wrote: >>>>>> >>>>>>> That worked. Thanks. >>>>>>> >>>>>>> Mohamed >>>>>>> >>>>>>> On Tue, Dec 4, 2018 at 5:30 PM Oleg >>>>>>> wrote: >>>>>>> >>>>>>>> Wrong file. My bad. Try this one. >>>>>>>> >>>>>>>> On Tue, Dec 4, 2018 at 3:17 PM Morsy, Mohamed K >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Hi Oleg, >>>>>>>>> >>>>>>>>> >>>>>>>>> I tried replacing the devicetree.dtb file in the nand folder from >>>>>>>>> elphel393_20180511 >>>>>>>>> with the one you sent. I tried the ipaddress/update_software.html >>>>>>>>> tool again but nothing changed. When I log into the elphel from >>>>>>>>> minicom and >>>>>>>>> try ifconfig I still only get the local address at 127.0.0.1. This is >>>>>>>>> on a >>>>>>>>> Rev C board. Do you have any other ideas? >>>>>>>>> >>>>>>>>> >>>>>>>>> Also I meant to send the previous email from my Redzone email so >>>>>>>>> I'll CC myself to this chain. >>>>>>>>> >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> >>>>>>>>> >>>>>>>>> Mohamed Morsy >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> *From:* Oleg >>>>>>>>> *Sent:* Tuesday, December 4, 2018 2:51 PM >>>>>>>>> *To:* Morsy, Mohamed K >>>>>>>>> *Cc:* elphel support-list >>>>>>>>> *Subject:* Re: [Elphel-support] Elphel 393 Nand upgrade >>>>>>>>> >>>>>>>>> Hi Mohamed, >>>>>>>>> >>>>>>>>> I think it's not related. >>>>>>>>> >>>>>>>
Re: [Elphel-support] Elphel 393 Nand upgrade
This happens when the board tries to turn on 5V and fails. Try: * disconnect sensors if any connected * another power supply (how do you power the board? direct 3.3V or 48V via 10385 board?) * another power cable On Thu, Dec 13, 2018 at 1:50 PM Mohamed Morsy wrote: > No it does not boot from flash. > The card does work with other boards. > > On Thu, Dec 13, 2018 at 3:46 PM Oleg > wrote: > >> Hi Mohamed, >> >> Does the board boot fine from flash? >> Does the same uSD card work with other rev B boards? >> >> On Thu, Dec 13, 2018 at 1:30 PM Mohamed Morsy wrote: >> >>> Hi Oleg, >>> >>> I'm having another issue with another Elphel. It doesn't seem to boot up >>> completely. When I connect the USB cable, open minicom, and power on the >>> Elphel, it starts booting up for 2 seconds then stops and minicom says >>> "Cannot open /dev/ttyUSB0!" The last thing on minicom before it stops is: >>> >>> [2.034545] elphel393-pwr elphel393-pwr@0: Probing elphel393-pwr >>> >>> This is a Rev B Elphel running on a uSD card. Do you know what the issue >>> might be? >>> >>> Thanks, >>> >>> Mohamed >>> >>> On Wed, Dec 5, 2018 at 9:48 AM Mohamed Morsy wrote: >>> >>>> That worked. Thanks. >>>> >>>> Mohamed >>>> >>>> On Tue, Dec 4, 2018 at 5:30 PM Oleg >>>> wrote: >>>> >>>>> Wrong file. My bad. Try this one. >>>>> >>>>> On Tue, Dec 4, 2018 at 3:17 PM Morsy, Mohamed K >>>>> wrote: >>>>> >>>>>> Hi Oleg, >>>>>> >>>>>> >>>>>> I tried replacing the devicetree.dtb file in the nand folder from >>>>>> elphel393_20180511 >>>>>> with the one you sent. I tried the ipaddress/update_software.html >>>>>> tool again but nothing changed. When I log into the elphel from minicom >>>>>> and >>>>>> try ifconfig I still only get the local address at 127.0.0.1. This is on >>>>>> a >>>>>> Rev C board. Do you have any other ideas? >>>>>> >>>>>> >>>>>> Also I meant to send the previous email from my Redzone email so I'll >>>>>> CC myself to this chain. >>>>>> >>>>>> >>>>>> Thanks, >>>>>> >>>>>> >>>>>> Mohamed Morsy >>>>>> >>>>>> >>>>>> -- >>>>>> *From:* Oleg >>>>>> *Sent:* Tuesday, December 4, 2018 2:51 PM >>>>>> *To:* Morsy, Mohamed K >>>>>> *Cc:* elphel support-list >>>>>> *Subject:* Re: [Elphel-support] Elphel 393 Nand upgrade >>>>>> >>>>>> Hi Mohamed, >>>>>> >>>>>> I think it's not related. >>>>>> >>>>>> Most likely you need an updated device tree (devicetree.dtb). The >>>>>> newest boards are revC - they have a different PHY reg address compared >>>>>> to >>>>>> revB (and older). The recovery cards came with updated devicetree - and >>>>>> so, >>>>>> the network is working. >>>>>> The revision letter is printed near the network connector on top of >>>>>> the board. For revC - try devicetree.dtb from the attachment. >>>>>> >>>>>> fix_net_config.tar.gz - just moves network configuration from >>>>>> /etc/elphel393/init_elphel393.py to /etc/network/interfaces which is a >>>>>> more >>>>>> conventional place for linux. And it will be included in the next >>>>>> release. >>>>>> >>>>>> I'm having trouble upgrading the NAND memory on an elphel 393. I've >>>>>> tried it with multiple boards. I used the ipaddress/update_software.html >>>>>> tool. When I flash the board, I shut it down, remove the uSD card, and >>>>>> reboot it. But it doesn't boot up correctly. I'm able to log in on >>>>>> minicom >>>>>> but when I try ifconfig I find that the board doesn't have an ip address. >>>>>> Do you know how to resolve this issue? I noticed there's a recent upload >>>>>> at >>>>>> community.elphel.com/files/393 &
Re: [Elphel-support] Elphel 393 Nand upgrade
Hi Mohamed, Does the board boot fine from flash? Does the same uSD card work with other rev B boards? On Thu, Dec 13, 2018 at 1:30 PM Mohamed Morsy wrote: > Hi Oleg, > > I'm having another issue with another Elphel. It doesn't seem to boot up > completely. When I connect the USB cable, open minicom, and power on the > Elphel, it starts booting up for 2 seconds then stops and minicom says > "Cannot open /dev/ttyUSB0!" The last thing on minicom before it stops is: > > [2.034545] elphel393-pwr elphel393-pwr@0: Probing elphel393-pwr > > This is a Rev B Elphel running on a uSD card. Do you know what the issue > might be? > > Thanks, > > Mohamed > > On Wed, Dec 5, 2018 at 9:48 AM Mohamed Morsy wrote: > >> That worked. Thanks. >> >> Mohamed >> >> On Tue, Dec 4, 2018 at 5:30 PM Oleg >> wrote: >> >>> Wrong file. My bad. Try this one. >>> >>> On Tue, Dec 4, 2018 at 3:17 PM Morsy, Mohamed K wrote: >>> >>>> Hi Oleg, >>>> >>>> >>>> I tried replacing the devicetree.dtb file in the nand folder from >>>> elphel393_20180511 >>>> with the one you sent. I tried the ipaddress/update_software.html tool >>>> again but nothing changed. When I log into the elphel from minicom and try >>>> ifconfig I still only get the local address at 127.0.0.1. This is on a Rev >>>> C board. Do you have any other ideas? >>>> >>>> >>>> Also I meant to send the previous email from my Redzone email so I'll >>>> CC myself to this chain. >>>> >>>> >>>> Thanks, >>>> >>>> >>>> Mohamed Morsy >>>> >>>> >>>> -- >>>> *From:* Oleg >>>> *Sent:* Tuesday, December 4, 2018 2:51 PM >>>> *To:* Morsy, Mohamed K >>>> *Cc:* elphel support-list >>>> *Subject:* Re: [Elphel-support] Elphel 393 Nand upgrade >>>> >>>> Hi Mohamed, >>>> >>>> I think it's not related. >>>> >>>> Most likely you need an updated device tree (devicetree.dtb). The >>>> newest boards are revC - they have a different PHY reg address compared to >>>> revB (and older). The recovery cards came with updated devicetree - and so, >>>> the network is working. >>>> The revision letter is printed near the network connector on top of the >>>> board. For revC - try devicetree.dtb from the attachment. >>>> >>>> fix_net_config.tar.gz - just moves network configuration from >>>> /etc/elphel393/init_elphel393.py to /etc/network/interfaces which is a more >>>> conventional place for linux. And it will be included in the next release. >>>> >>>> I'm having trouble upgrading the NAND memory on an elphel 393. I've >>>> tried it with multiple boards. I used the ipaddress/update_software.html >>>> tool. When I flash the board, I shut it down, remove the uSD card, and >>>> reboot it. But it doesn't boot up correctly. I'm able to log in on minicom >>>> but when I try ifconfig I find that the board doesn't have an ip address. >>>> Do you know how to resolve this issue? I noticed there's a recent upload at >>>> community.elphel.com/files/393 >>>> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcommunity.elphel.com%2Ffiles%2F393=02%7C01%7CMKM89%40pitt.edu%7C69e9fd539853460af0b808d65a21ddbc%7C9ef9f489e0a04eeb87cc3a526112fd0d%7C1%7C1%7C63679549885600=nmNC%2B4fi8iv%2FKJk2i5mVpAEVZ4r1A5H%2FCS3woLV3%2Bhc%3D=0> >>>> called fix_net_config.tar.gz. Is that related to my issue? >>>> >>>> Thanks, >>>> Mohamed Morsy >>>> RedZone Robotics >>>> ___ >>>> Support-list mailing list >>>> Support-list@support.elphel.com >>>> >>>> http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com >>>> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fsupport.elphel.com%2Fmailman%2Flistinfo%2Fsupport-list_support.elphel.com=02%7C01%7CMKM89%40pitt.edu%7C69e9fd539853460af0b808d65a21ddbc%7C9ef9f489e0a04eeb87cc3a526112fd0d%7C1%7C1%7C636795498844455609=6WuAVJxImp03qJEMvMDpWa%2BCth%2BT%2B3t1bkmiWJ07tGE%3D=0> >>>> >>>> >>>> ___ >>>> Support-list mailing list >>>> Support-list@support.elphel.com >>>> >>>> http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com >>>> >>> >>> Best regards, >>> Oleg Dzhimiev >>> Electronics Engineer >>> phone: +1 801 783 x124 >>> Elphel, Inc. >>> >> ___ > Support-list mailing list > Support-list@support.elphel.com > http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] 答复: 答复: 答复: 答复: 答复: sync stereo with lidar
Hello, In the link you used the internal trigger generator is working and is routed out to the sync cable (which is probably self-looped - input and output wires are connected): Try: *1.* Set TRIG_OUT=0x0 to stop internal pulses at the sync cable output: # old link: http://192.168.0.9/parsedit.php?sensor_port=0_CONDITION=0x9_OUT=0x66555_PERIOD=1=4 # new link: http://192.168.0.9/parsedit.php?sensor_port=0_CONDITION=0x9; > *TRIG_OUT=0x0*_PERIOD=1=4 *or * *2.* If the sync cable inputs and outputs connected. Disconnect the wires from each other and apply your trigger source: signal or "+" - to Black wire, ground or "-" - to Green wire. Please, check the wire colors and pinout here <https://wiki.elphel.com/wiki/103891>. Let us know if that worked. Thanks. I'll update our docs to make them clear. Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. On Tue, Dec 11, 2018 at 9:04 PM Winston Zhang wrote: > Hi, Andrey! > Thany you for your patience to answer our questions! > I have some new questions about external trigger. When I set the > trigger parameter as the page > http://192.168.0.9/parsedit.php?sensor_port=0_CONDITION=0x9_OUT=0x66555_PERIOD=1000=4, > <http://192.168.0.9/parsedit.php?sensor_port=0_CONDITION=0x9_OUT=0x66555_PERIOD=1=4,> > and > I made the trigger board pulsing out the signal(10HZ), I found we could get > 10 images. But I stopped the trigger board signal, I also could update the > image(10hz). I wanted to konw that how can I test the external trigger > signal work? Because when i stop external source trigger signal, it could > receive images too. > > -- > > *---* > > *Best Regrad!* > > *Yicheng-Zhang* > > *Email: winston.zhang@bst .ai* > > *Tel:18516291005* > > *Black Sesame Technologies (Shanghai) Co., Ltd. www.bst.ai > <http://www.bst.ai/>* > > *Rm 1102-1108, Bldg36, No.2777, East Jinxiu Rd, Pudong District, Shanghai, > China* > > > *发件人：* Oleg > *发送时间：* 2018-09-19 02:38 > *收件人：* david.zh...@bst.ai > *抄送：* winston.zh...@bst.ai; tao.zh...@bst.ai; Qun Gu > ; elphel support-list > > *主题：* Re: [Elphel-support] 答复: 答复: 答复: 答复: 答复: sync stereo with lidar > Hello, > > Here are a couple commands (in linux) that can help to check and sync the > system clock: > - Compare PC and camera clock: > >> ~$ ssh root@192.168.0.9 date;date -u > > - Write PC time into camera clock: > >> ~$ ssh root@192.168.0.9 "date -s @`( date -u +"%s" )` && hwclock -w" > > > After setting the system clock check if the time survives the reboot. If > it does not - then please update the firmware to 20180511 > <https://wiki.elphel.com/wiki/10393_manual#Firmware.2Fsoftware_update>. > There was a bug in the clock driver we had to fix a while ago. > > Regards, > Oleg > > On Mon, Sep 17, 2018 at 11:27 PM David Zhang wrote: > >> Hi, Andrey, >> >> >> We use default configuration(TRIG=4 and TRIG_PERIOD=2500). Is that >> OK? And now our situation is there are timestamps in EXIF header. But it is >> not >> >> the kernel's system time. >> >> e.g. the timestamp in EXIF may be 2018/09/14 but actually system's date >> is 2018/09/18. >> >> How can i fix it? Thanks. >> >> >> Best, >> >> David >> >> >> >> >> -- >> *发件人:* Elphel Support >> *发送时间:* 2018年9月18日 10:03:19 >> *收件人:* Winston Zhang >> *抄送:* Winston Zhang; Tao Zhang; Qun Gu; David Zhang >> *主题:* Re: [Elphel-support] 答复: 答复: 答复: 答复: sync stereo with lidar >> >> Winston, >> >> What trigger settings do you use ( >> https://wiki.elphel.com/wiki/Trigger_393 )? >> Trigger 393 - ElphelWiki - wiki.elphel.com >> <https://wiki.elphel.com/wiki/Trigger_393> >> wiki.elphel.com >> Description. 10389 board is required. The triggering is used for one or >> several cameras synchronization or setting the frame rate (or fps). The >> conditions of the trigger can be generated either internally or externally. >> >> >> >> Camera channels should be in triggered mode (TRIG=4) and have correct >> TRIG_PERIOD. Then all channels will be exactly synchronized. If you set >> TRIG_PERIOD to some "even" number (like exactly 10fps with >> TRIG_PERIOD=1000), then timestamps will have all digits but seconds and >> tenths of a second the same for all frames. >> >> Andrey >> >
Re: [Elphel-support] Elphel 393 Nand upgrade
Wrong file. My bad. Try this one. On Tue, Dec 4, 2018 at 3:17 PM Morsy, Mohamed K wrote: > Hi Oleg, > > > I tried replacing the devicetree.dtb file in the nand folder from > elphel393_20180511 > with the one you sent. I tried the ipaddress/update_software.html tool > again but nothing changed. When I log into the elphel from minicom and try > ifconfig I still only get the local address at 127.0.0.1. This is on a Rev > C board. Do you have any other ideas? > > > Also I meant to send the previous email from my Redzone email so I'll CC > myself to this chain. > > > Thanks, > > > Mohamed Morsy > > > -- > *From:* Oleg > *Sent:* Tuesday, December 4, 2018 2:51 PM > *To:* Morsy, Mohamed K > *Cc:* elphel support-list > *Subject:* Re: [Elphel-support] Elphel 393 Nand upgrade > > Hi Mohamed, > > I think it's not related. > > Most likely you need an updated device tree (devicetree.dtb). The newest > boards are revC - they have a different PHY reg address compared to revB > (and older). The recovery cards came with updated devicetree - and so, the > network is working. > The revision letter is printed near the network connector on top of the > board. For revC - try devicetree.dtb from the attachment. > > fix_net_config.tar.gz - just moves network configuration from > /etc/elphel393/init_elphel393.py to /etc/network/interfaces which is a more > conventional place for linux. And it will be included in the next release. > > I'm having trouble upgrading the NAND memory on an elphel 393. I've tried > it with multiple boards. I used the ipaddress/update_software.html tool. > When I flash the board, I shut it down, remove the uSD card, and reboot it. > But it doesn't boot up correctly. I'm able to log in on minicom but when I > try ifconfig I find that the board doesn't have an ip address. Do you know > how to resolve this issue? I noticed there's a recent upload at > community.elphel.com/files/393 > <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcommunity.elphel.com%2Ffiles%2F393=02%7C01%7CMKM89%40pitt.edu%7C69e9fd539853460af0b808d65a21ddbc%7C9ef9f489e0a04eeb87cc3a526112fd0d%7C1%7C1%7C63679549885600=nmNC%2B4fi8iv%2FKJk2i5mVpAEVZ4r1A5H%2FCS3woLV3%2Bhc%3D=0> > called fix_net_config.tar.gz. Is that related to my issue? > > Thanks, > Mohamed Morsy > RedZone Robotics > ___ > Support-list mailing list > Support-list@support.elphel.com > http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com > <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fsupport.elphel.com%2Fmailman%2Flistinfo%2Fsupport-list_support.elphel.com=02%7C01%7CMKM89%40pitt.edu%7C69e9fd539853460af0b808d65a21ddbc%7C9ef9f489e0a04eeb87cc3a526112fd0d%7C1%7C1%7C636795498844455609=6WuAVJxImp03qJEMvMDpWa%2BCth%2BT%2B3t1bkmiWJ07tGE%3D=0> > > > ___ > Support-list mailing list > Support-list@support.elphel.com > http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com > Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. devicetree.dtb Description: Binary data ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] Elphel 393 Nand upgrade
Hi Mohamed, I think it's not related. Most likely you need an updated device tree (devicetree.dtb). The newest boards are revC - they have a different PHY reg address compared to revB (and older). The recovery cards came with updated devicetree - and so, the network is working. The revision letter is printed near the network connector on top of the board. For revC - try devicetree.dtb from the attachment. fix_net_config.tar.gz - just moves network configuration from /etc/elphel393/init_elphel393.py to /etc/network/interfaces which is a more conventional place for linux. And it will be included in the next release. I'm having trouble upgrading the NAND memory on an elphel 393. I've tried > it with multiple boards. I used the ipaddress/update_software.html tool. > When I flash the board, I shut it down, remove the uSD card, and reboot it. > But it doesn't boot up correctly. I'm able to log in on minicom but when I > try ifconfig I find that the board doesn't have an ip address. Do you know > how to resolve this issue? I noticed there's a recent upload at > community.elphel.com/files/393 called fix_net_config.tar.gz. Is that > related to my issue? > > Thanks, > Mohamed Morsy > RedZone Robotics > ___ > Support-list mailing list > Support-list@support.elphel.com > http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com > devicetree.dtb Description: Binary data ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] Complaint
Veronika, I have inspected the logs. 1. 000E64081D8D: With the corrupted flash - it needs to have its firmware reflashed (the badblocks are skipped during the reflashing process). You should be able to do it by yourself: a. Boot from the live usb (you should have at least one - a credit card size usb key). If you don't have it - it's available for downloading <https://www3.elphel.com/liveusb> (there are a few links from there with more details). b. Download and flash this firmware <https://sourceforge.net/projects/elphel/files/elphel353-8/8.2.16/> (image353-8.2.16.tar.gz) - instructions <http://community.elphel.com/files/live-dvd/readme.html> (follow section III.4. (or 3.)) Let me know if you need further assistance. 2. 000E64081D9B: Try removing /etc/autocampars.xml and rebooting: >From *http://192.168.0.9/phpshell.php <http://192.168.0.9/phpshell.php>* type: > rm /etc/autocampars.xml sync Then reboot - a new config file will be generated. Let me know if it fixed the camera. Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] 答复: 答复: 答复: 答复: 答复: sync stereo with lidar
Hello, Here are a couple commands (in linux) that can help to check and sync the system clock: - Compare PC and camera clock: > ~$ ssh root@192.168.0.9 date;date -u - Write PC time into camera clock: > ~$ ssh root@192.168.0.9 "date -s @`( date -u +"%s" )` && hwclock -w" After setting the system clock check if the time survives the reboot. If it does not - then please update the firmware to 20180511 <https://wiki.elphel.com/wiki/10393_manual#Firmware.2Fsoftware_update>. There was a bug in the clock driver we had to fix a while ago. Regards, Oleg On Mon, Sep 17, 2018 at 11:27 PM David Zhang wrote: > Hi, Andrey, > > > We use default configuration(TRIG=4 and TRIG_PERIOD=2500). Is that OK? > And now our situation is there are timestamps in EXIF header. But it is not > > the kernel's system time. > > e.g. the timestamp in EXIF may be 2018/09/14 but actually system's date is > 2018/09/18. > > How can i fix it? Thanks. > > > Best, > > David > > > > > -- > *发件人:* Elphel Support > *发送时间:* 2018年9月18日 10:03:19 > *收件人:* Winston Zhang > *抄送:* Winston Zhang; Tao Zhang; Qun Gu; David Zhang > *主题:* Re: [Elphel-support] 答复: 答复: 答复: 答复: sync stereo with lidar > > Winston, > > What trigger settings do you use ( > https://wiki.elphel.com/wiki/Trigger_393 )? > Trigger 393 - ElphelWiki - wiki.elphel.com > <https://wiki.elphel.com/wiki/Trigger_393> > wiki.elphel.com > Description. 10389 board is required. The triggering is used for one or > several cameras synchronization or setting the frame rate (or fps). The > conditions of the trigger can be generated either internally or externally. > > > > Camera channels should be in triggered mode (TRIG=4) and have correct > TRIG_PERIOD. Then all channels will be exactly synchronized. If you set > TRIG_PERIOD to some "even" number (like exactly 10fps with > TRIG_PERIOD=1000), then timestamps will have all digits but seconds and > tenths of a second the same for all frames. > > Andrey > > > On Mon, 17 Sep 2018 18:31:26 -0700 * >* wrote > > Hi, Andrey! > I captured some images form camera with the timestamp image name. This > timestamp was the same with camera system timestamp. And the other way, > each image had its exif information that contained the real timestamp. But > this timestamp from exif information was not the same with system > timestamp. So can you provided some detials about where was the exif > timestamp from. And how did i do can solve this problem. > > (i had synchronized the camera system time with the GPS timestamp.) > > -- > > *---* > > *Best Regrad!* > > *Yicheng-Zhang* > > *Email: winston.zhang@bst .ai* > > *Tel:18516291005* > > *Addr: 707 room, 7th floor, building 4th, No.1761, Zhangdong road, > Pudong area* > > > *发件人：* Oleg > *发送时间：* 2018-05-12 06:32 > *收件人：* Winston Zhang > *抄送：* Tao Zhang ; Qun Gu > ; David Zhang ; elphel > support-list > *主题：* Re: [Elphel-support] 答复: 答复: 答复: 答复: sync stereo with lidar > Winston, > > > I could get the info from the 192.168.0.9:2323. This web could help me to > get some information. But if I tried the > http://192.168.0.9:2323/timestamp_name, the timestamp file saved web did > not appear. How did I use it? > > > http://192.168.0.9:2323*/pointer_value/img* > > Try the following: > 1. get diagnostics.php > <https://git.elphel.com/Elphel/elphel-web-393/blob/master/src/diagnostics/diagnostics.php> > 2. copy to 192.168.0.9:/www/pages/ > 3. In the browser open: > > view-source:http://192.168.0.9/diagnostics.php?pointers > > > You will get xml output similar to this one: > > > > > > > > ... > > 1526075540.347616 > ... > > > Take the pointer_value from the last for a particular port. Don't > forget to add "/img" or "/bimg". > > If something does not work. Please send me your xml. > > Best regards, > Oleg Dzhimiev > Electronics Engineer > phone: +1 801 783 x124 > Elphel, Inc. > > ___ > Support-list mailing list > Support-list@support.elphel.com > http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com > > > > > ___ > Support-list mailing list > Support-list@support.elphel.com > http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com > ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] Synchronizing imagers...
Todd, Here <https://wiki.elphel.com/wiki/Parsedit.php#change_multiple_ports> - it's linked from the manual but hard to locate (I'll update the docs). Example: > http://192.168.0.9/parsedit.php?immediate_port=0=5&*COLOR=0xf PARNAME=value&***PARNAME=bitmask bitmask - 4-bits, where bitmask[0] corresponds to port 0, ... bitmask values: 1 - enabled, 0 - disabled Regards, Oleg On Wed, Aug 29, 2018 at 12:09 PM TODD KUENY wrote: > Oleg - > > I recall asking about this and the upshot was that adding a ‘*’ on some > PHP parameters would synchronize parameter settings across imagers, either > for settings in general or for capturing images. > > I can’t seem to locate this on the 393 web site. > > Do you recall or can you help? > > Thanks > Todd > > > ___ > Support-list mailing list > Support-list@support.elphel.com > http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com > ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] 353 Problem Mainboards
Linden, I reflashed the 000E64081CA1 - and it works now. It had a bad block. See the old bootlog from the serial output (via the extension board 10369) below. Have you ever reflashed a camera? One of the tests that can tell if the flash is probably corrupted is putting the camera in the netboot mode. Then reflash if possible - during reflashing it detects and skips the bad blocks. Boot log: > ETRAX FS NAND boot loader > > > > = > > > > Rev 1, Nov 23 2009 12:31:43 > > > > Boot config: 0x0004->0x4044, len 0x0020, boot @ 0x4044 > > > > CPU revision: 0x0020 > > > > Bootloader main at 0x38000ce2 > > > > Data end: 0x3800573c > > > > Bss: 0x38008000 > > > > Heap: 0x38008000 > > > > Identifying nand chip... > > > > maf_id: 0x002c; dev_id: 0x00f1 > > > > mtd->size == 0x0800 > > > > scan_bbt(); mtd->size == 0x0800 > > > > scan_bbt() ...01; mtd->size == 0x0800 > > > > len == 0x0100; and BBT_LEN_1 == 0x0400 > > > > scan_bbt() ...02; mtd->size == 0x0800 > > > > scan_bbt() ...03; mtd->size == 0x0800 > > > > scan_bbt() ...1; mtd->size == 0x0800 > > > > scan_bbt() ...2; mtd->size == 0x0800 > > > > scan_bbt() search_read_bbts(); mtd->size == 0x0800 > > > > search_read_bbts() search primary table; mtd->size == 0x0800 > > > > search_bbt() ...1; mtd->size == 0x0800 > > > > search_bbt() ...2; maxblocks: 0x0004; mtd->size == 0x0800 > > > > Block: 0x03ff > > > > Check, if we found a bbt for each requested chip > > > > Bad block table found at page0xffc0, version 0x0001 > > > > search_read_bbts() search mirror table > > > > search_bbt() ...1; mtd->size == 0x0800 > > > > search_bbt() ...2; maxblocks: 0x0004; mtd->size == 0x0800 > > > > Block: 0x03ff > > > > Block: 0x03fe > > > > Check, if we found a bbt for each requested chip > > > > Bad block table found at page0xff80, version 0x0001 > > > > scan_bbt() ...3 > > > > Done. > > > > Chip identified... 3; NAND 128MiB 3,3V 8-bit > > > > type: 0x0004 > > > > flags: 0x00c5 > > > > size: 0x0800 > > > > erasesize: 0x0002 > > > > oobblock: 0x0800 > > > > oobsize: 0x0040 > > > > ecctype: 0x0002 > > > > eccsize: 0x0100 > > > > Oob info: > > > > useecc: 0x0002 > > > > eccbytes: 0x0018 > > > > eccpos: 0x0028 0x0029 0x002a 0x002b 0x002c 0x002d > 0x002e 0x002f 0x0030 0x0031 0x0032 0x0033 > 0x0034 0x0035 0x0036 0x0037 0x0038 0x0039 > 0x003a 0x003b 0x003c 0x003d 0x003e 0x003 > Bootload in progress... > > > > New block 0x0004;len: 0x0020;start: 0x0004 > > > > New block 0x0006;len: 0x001e;start: 0x0006 > > > > New block 0x0008;len: 0x001c;start: 0x0008 > > > > New block 0x000a;len: 0x001a;start: 0x000a > > > > New block 0x000c;len: 0x0018;start: 0x000c > > > > New block 0x000e;len: 0x0016;start: 0x000e > > > > New block 0x0010;len: 0x0014;start: 0x0010 > > > > New block 0x0012;len: 0x0012;start: 0x0012 > > > > New block 0x0014;len: 0x0010;start: 0x0014 > > > > New block 0x0016;len: 0x000e;start: 0x0016 > > > > New block 0x0018;len: 0x000c;start: 0x0018 > > > > complete, status 0xffb6, loaded 0x0014 bytes > > > > Data in DRAM: > > > > 0x25f005b0 0x009cedff 0xbeef05b0 > > > > > > > > > > Corrupt data in NAND flash. > > > > > > > > -- System halted On Mon, Aug 20, 2018 at 1:53 PM Linden @ Zone4 wrote: > Thanks for the tip, solved it: > I recall the autocampars.php file was causing issues on this camera before > and I probably tried to fix it by pasting in the file from source into the > web based terminal (http://10.23.33.9/index.php?site=phpshell.php). This > converts all the HTML entities ( etc...) to the wrong thing. I SCPed > in the original source, deleted /etc/autocampars.xml and ran > /usr/html/autocampars.php --init. Working again. > > I am still going to ship you the 000E64081CA1 mainboard (the one that > w
Re: [Elphel-support] 353 Problem Mainboards
Linden, Does the file look ok? It should have ~4k lines. http://192.168.0.9/index.php?site=admin-bin/editcgi.cgi?file=/usr/html/autocampars.php Regards, Oleg On Fri, Aug 17, 2018 at 6:57 PM Linden @ Zone4 wrote: > I have run '/usr/html/autocampars.php --init', looks like a very similar > error trace to loading http://10.23.33.9/index.php?site=autocampars.php. > Output posted at bottom of GDoc: > > https://docs.google.com/document/d/1WfGlWGk0A7zLgAl1EptMntTKoKLJLodron0P0zYcpB4/edit?usp=sharing > > Linden Mills-Connery > Zone4 Team <https://zone4.ca/contact/> > 205-820 Main Street > Canmore, AB, T1W2B7 > 403-401-7215 > > On 17 August 2018 at 17:53, Oleg wrote: > >> I deleted /etc/autocampars.xml and went to >>> http://10.23.33.9/index.php?site=autocampars.php again to re-generate >>> it which just resulted in an error message. The error message is also in >>> the GDoc. >>> >> That worked with the board I'm testing. >> >> What if you reboot? >> Try from command line? >> >> [root@Elphel353 /root]759# */usr/html/autocampars.php --init* >>> autocampars.php created a new configuration file /etc/autocampars.xml >>> from defaults. >>> Current frame=1266, sleeping to give daemons a chance >>> Current frame=1319, waking up, daemons should be dead already >>> before reset - current frame=0 >>> after reset - current frame=2 >>> setting COMPRESSOR_RUN=2 >>> setting DAEMON_EN=Array >>> ( >>>[DAEMON_EN_AUTOEXPOSURE] => 1 >>>[DAEMON_EN_STREAMER] => 1 >>>[DAEMON_EN_CCAMFTP] => 0 >>>[DAEMON_EN_CAMOGM] => 0 >>>[DAEMON_EN_TEMPERATURE] => 0 >>>[DAEMON_EN] => 3 >>> ) >>> after setParsFromPage - current frame=12 >>> Sensor was successfully initialized at August 17, 2018, 11:49 pm from >>> /etc/autocampars.xml page 0 >> >> >> Regards, >> Oleg >> >> > ___ > Support-list mailing list > Support-list@support.elphel.com > http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com > ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] 353 Problem Mainboards
> > I deleted /etc/autocampars.xml and went to > http://10.23.33.9/index.php?site=autocampars.php again to re-generate it > which just resulted in an error message. The error message is also in the > GDoc. > That worked with the board I'm testing. What if you reboot? Try from command line? [root@Elphel353 /root]759# */usr/html/autocampars.php --init* > autocampars.php created a new configuration file /etc/autocampars.xml from > defaults. > Current frame=1266, sleeping to give daemons a chance > Current frame=1319, waking up, daemons should be dead already > before reset - current frame=0 > after reset - current frame=2 > setting COMPRESSOR_RUN=2 > setting DAEMON_EN=Array > ( >[DAEMON_EN_AUTOEXPOSURE] => 1 >[DAEMON_EN_STREAMER] => 1 >[DAEMON_EN_CCAMFTP] => 0 >[DAEMON_EN_CAMOGM] => 0 >[DAEMON_EN_TEMPERATURE] => 0 >[DAEMON_EN] => 3 > ) > after setParsFromPage - current frame=12 > Sensor was successfully initialized at August 17, 2018, 11:49 pm from > /etc/autocampars.xml page 0 Regards, Oleg ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] 353 Problem Mainboards
So, it does not detect the sensor. What's the firmware? > # cat /etc/issue You might have tried another cable. If it's the board - I would check the connector first. Then the power, then i2c bus. Links to schematics are under the diagrams here <https://wiki.elphel.com/wiki/10353>. Regards, Oleg On Fri, Aug 17, 2018 at 1:41 PM Linden @ Zone4 wrote: > Thanks Oleg. > > 000E64081C8B > Here is the requested diagnostics: > > https://docs.google.com/document/d/1WfGlWGk0A7zLgAl1EptMntTKoKLJLodron0P0zYcpB4/edit?usp=sharing > > 000E64081CA1 > I will send that one back to you. Will wait until we know if 000E64081C8B > needs to go back as well or if I can resolve the issue here. > > The one with the color tinting is behaving much better. > > Thanks, > ___ > Support-list mailing list > Support-list@support.elphel.com > http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] 353 Problem Mainboards
Hello Linden, 000E64081C8B > Boots up fine and I can access it on the network fine. The problem is with > the interface to the image sensor. All that is available on bimg is a 1px x > 1px white image. I have tried connecting this mainboard to a working sensor > and there was no change in behavior, still a 1x1 bimg. I have also > connected a working mainboard to this sensor and the sensor is working > fine. So this points to an issue with the sensor interface on the 000E64081C8B > mainboard. > telnet or http://192.168.0.9/phpshell.php, then 1. ~$ dmesg > ... The sensor clock set to 2000 > removing MRST from the sensor > trying MT9P001 > Found MT9P001 2592x1944 sensor, chip ID=1801 > trying MT9X001 > Resetting MT9X001 sensor > Reading sensor registers to the shadows: > Initializing MT9X001 registers with default values: > arch/cris/arch-v32/drivers/elphel/quantization_tables.c:174:init_qtable_head_cache > 2. ~$ fpcf -i2cr16 4800 100 It will just read sensor's registers: > 004800: 1801 32c 793 a23 1c2 28420 15000 >000 > 004810: 50 640400 36 100000000 >0 40060 > 004820: 40000200b0 480 1086 10 18 > 16f0 > 004830:000008000000 171d >5 80414 > 004840:7033 203 1010 1010 1010 10 a8 10 28 10 > 120f 1010 14 > 004850: 80007 80007 160 204 8000741 5a > 2d13 41ff 231d > 004860: 13 130 1b 1b0000 cf ef ed ea > f100 > 004870: ac a700 a700 c00 600 5617 6b57 6b57 a500 ab00 a904 a700 a700 > ff00 a9000 > 004880: 22 1f040 1b06 1d080 1806 1a0800000 >000 > 004890: 7d0010000000000 >000 > 0048a0:00000000000 794 a24 > 2809 b3 49f5 > 0048b0: d6f0 ba9c ace6 fcf4 d8b6 fe6e fa7e f1f 4fd ac1 dff c87 fcf > ff7 57d dea > 0048c0: cff dfa 3ca b7a adb e97 bfa dcef e7ff dffe 187f 4957 eef3 > 7f79 6fad 37ff > 0048d0: 68bc 7fad fedd fd3e fabb f263 2f7a 95de 3fcb faff ff33 9e9f f779 > cbf7 8b0d fe6d > 0048e0: d9a6 ff3a fd7a 855d e85f a9fc dd4f 6e7f 2ebf fe71 7fef fffe 5cb7 > 71fd ecfc 11fd > 0048f0:0000000010 e0b0 48cf 8068 > e1180 1801 3. Check if write pointer is changing: http://192.168.0.9:8081/pointers 4. Check if frame number is increasing: http://192.168.0.9:8081/meta 5. http://192.168.0.9/parsedit.php?images=9:3:.2 If 1 & 2 do not fail. Try removing autocampars.xml? Sometimes it gets corrupted for some reason. 000E64081CA1 > Won't boot at all, no LEDs on Ethernet port or switch it is connected to. > I have done a visual inspection and cleaned the Ethernet port pins but no > luck. I have also connected a working mainboard to this sensor and the > sensor is working fine. So this points to an issue with the 000E64081CA1 > mainboard. > Hard to say. Need to have a look. I would check the serial console output but it requires 10389. I also have another camera that is producing color tinted images: > > https://drive.google.com/drive/folders/1bA6VOga8DPdiyhQXq7PWLPg5b7u-4L03?usp=sharing > I had a look and the ZIF connector between the mainboard and sensor *may* > have been loose. I am running some more tests on it but wondering if a > loose connected would result in those tinted sample images. > It could have, yes. > How should I proceed with the bad mainboards? > You can send them to us - we will inspect them and see what we can do. Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] Elphel NC353L
Hello, Try setting triggering from internal generator: https://wiki.elphel.com/wiki/Trigger_353 See the very 1st example. TRIG_PERIOD is set in 96MHz clocks (9600 is 1 fps) Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] 答复: 答复: 答复: 答复: sync stereo with lidar
Winston, > I could get the info from the 192.168.0.9:2323. This web could help me to > get some information. But if I tried the http://192.168.0.9:2323/ > timestamp_name, the timestamp file saved web did not appear. How did I > use it? http://192.168.0.9:2323*/pointer_value/img* Try the following: 1. get diagnostics.php <https://git.elphel.com/Elphel/elphel-web-393/blob/master/src/diagnostics/diagnostics.php> 2. copy to 192.168.0.9:/www/pages/ 3. In the browser open: > view-source:http://192.168.0.9/diagnostics.php?pointers You will get xml output similar to this one: > > > > > > ... > 1526075540.347616 > ... Take the pointer_value from the last for a particular port. Don't forget to add "/img" or "/bimg". If something does not work. Please send me your xml. Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] 答复: 答复: 答复: sync stereo with lidar
Hi, > Another question is the two camera timestamp are not the same no matter > whether or not we connect the gps. Is the difference random? Supposing sensors run at default 10fps - do the last 4-5 digits (of microseconds) of timestamps match? Also, what timestamps do you read from: 192.168.0.9/parsedit.php > there's link to 9 image previews with timestamps - run for port 0 and 1 Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] 答复: 答复: sync stereo with lidar
Hi, Olga will send you a quote. Meanwhile, you can test your USB GPS. Plug it in the "eSATA+USB" port ( https://wiki.elphel.com/wiki/File:NC393-CS_marked_ports.jpeg) Then to check if it's working: a. $ ssh root@192.168.0.9 elphel393~# dmesg | grep Garmin > [ 47.236566] usb 1-1.4: new full-speed USB device number 3 using ci_hdrc > [ 47.398450] garmin_gps 1-1.4:1.0: Garmin GPS usb/tty converter detected > [ 47.405759] usb 1-1.4: Garmin GPS usb/tty converter now attached to > ttyUSB0 b. 192.168.0.9:2323/meta will have GPS related tags: > ... > "2" > "2018:05:07 22:29:14.00" > "-111.885652" > "40.780143" > "1378.20" > ... If b. works then camera images are geotagged. Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] 答复: 答复: sync stereo with lidar
Hi, so we need to buy a 103696 board. after we have the board, we need to open > the shell to connect to j8 and j9，but then we will not be able to close the > shell，right? can you give an instructions of how to connect that board to > 10393 camera. No shell. J8 and J9 are physical connectors - please, check with PCB schematics - https://wiki.elphel.com/wiki/10389 - there's link to 10389b.pdf. Or inspect the 10389 board you have - they are in the 'front' on the same side as SSD. Connect: GPS receiver > 103696 > 10389, then boot the camera and it's supposed to work. Could you send a picture of the connector on the cable end of your GPS receiver? Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] 答复: 答复: sync stereo with lidar
Hello, Did you mean this question? > We have Garmin GPS 18x 5Hz GPS receiver bought from you. How should we > connect GPS to stereo camera? Shall we have a 103696 board? But I can not > find how to connect it to 10393 camera on 103696 introduction page (- > https://wiki.elphel.com/wiki/103696). For 10393 you should have 10389 board (https://wiki.elphel.com/wiki/10389) Garmin GPS 18x 5Hz GPS - is it serial? or usb? If usb then use a eSATA+USB port or micro usb port If serial then you need to have 103696 - 103696 is connected to J8 or J9 ports of 10389 with 10-contact flat cable. Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] 答复: 答复: 答复: 答复: 答复: 答复: 答复: 答复: 答复: 答复: Re: Quote for 1 NC393-Stereo camera
> What is different of the format yuv and yours jp4? How can I get yuv-data? > If I want to get high quality image not to be compressed, whether I choose > the yuv data or jp4 data? Thank you! See https://wiki.elphel.com/wiki/JP4 JP4 is 4:0:0 YCbCr encoded. After reordering back blocks of pixels you get the pixel values of the Bayer pattern. Try this python script <https://wiki.elphel.com/wiki/JP4#python> for deblocking. After deblocking you can: * unapply gammas to get to linear scale * unapply gains to work with unamplified data I want to get camera image raw data(.jp4) buffer, but I cannot get it > through gstreamer. I should do a demo app with C/C++, how can I get the > camera image raw data, and keep the two camera sync? > > The sensors are always in sync (if exposure time is less than 1/fps). Your problem is to download matching jp4 images from different ports buffers, correct? If yes then here's what you can do in your program - example for port 0 and port 1: *I.* Without stopping compressor/sensors *step 1* Read current image pointers in port 0 and port 1 buffers: port0: http://192.168.0.9:2323/pointers port1: http://192.168.0.9:2324/pointers (responses are xml, extract ... value) port0: > ... 55801952 ... port1: > ... xxx1 ... And so: $THISPOINTER0 = 55801952 $THISPOINTER1 = xxx1 *step 2 *Read meta data http://192.168.0.9:2323/$THISPOINTER0/meta http://192.168.0.9:2324/$THISPOINTER1/meta Responses are xml - extract and compare timestamps (from ...) *step 2a *If timestamps don't match and 'port 0 timestamp' < 'port 1 timestamp' - you will need check one frame back for port 1. Note: there a short help how to navigate the buffers: http://192.168.0.9:2323 port1: http://192.168.0.9:2324/$THISPOINTER1/prev/pointers > ... xxx2 ... $NEWPOINTER1 = xxx2 next read timestamp from http://192.168.0.9:2324/$NEWPOINTER1/meta and compare. If 'port 0 timestamp' still < 'port 1 timestamp' then $THISPOINTER1 = $NEWPOINTER1, repeat this step *step 3* When timestamps are finally matching, download image(s): http://192.168.0.9:2323/$THISPOINTER0/img http://192.168.0.9:2324/$THISPOINTER1/img Here, we are assuming all requests are performed quickly enough *II.* With stopping triggering *step 1 * Set TRIG_PERIOD=0 ... next steps are the same as in I. but most likely the latest timestamps will match and you won't have to navigate through buffers: meta: http://192.168.0.9:2323/meta meta: http://192.168.0.9:2324/meta image: http://192.168.0.9:2323/img image: http://192.168.0.9:2324/img *step X* Restore TRIG_PERIOD I could probably make a script to do those things and put on the camera. https://wiki.elphel.com/wiki/Using_gstreamer please look at the red > rectangle area, what is this mean? This is outdated information. It should work as described here <https://wiki.elphel.com/wiki/Tmp_manual#RTSP>. So, after you start the streamers: > elphel393~# /usr/bin/str To watch a stream with gstreamer from PC, example: port0: gst-launch-1.0 rtspsrc location=rtsp://192.168.0.9:554 ! rtpjpegdepay ! jpegdec ! videoscale ! video/x-raw,width=640,height=480 ! xvimagesink sync=false port1: gst-launch-1.0 rtspsrc location=rtsp://192.168.0.9:554 ! rtpjpegdepay ! jpegdec ! videoscale ! video/x-raw,width=640,height=480 ! xvimagesink sync=false And this web paper introduce an stream of yuv-format(“gst-launch -v > rtspsrc location=rtsp://192.168.0.9:554 ! queue ! rtpjpegdepay ! queue ! > jpegdec ! queue ! \ videorate ! capsfilter caps="video/x-raw-yuv, format=(fourcc)I420, > width=(int)1024, height=(int)768, framerate (fraction)25/1" ! \ queue ! avimux ! filesink location=/tmp/test.avi”), but in you setting web > of image, I cannot find the value point to the yuv Value point? This is an old example - I cannot make it work. Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] Elphel Storage Drive
Mohamed, I think the problem was in the driver - the delay after sensor reset was too close to a minimum from docs. Try new uImage from here <https://community.elphel.com/files/393/20180406/longer_detect_delay/> - the same file for mmc and nand (also updated the archive). Regards, Oleg On Mon, Apr 9, 2018 at 1:16 PM, Oleg <support-list@support.elphel.com> wrote: > There's no need to remove them - sda2 is written like a memory buffer in > a circular way - overwriting old images. > > Right now you need to read /mnt/sda1/camogm.disk to track where recording > started/stopped. > > If you remove it the recording will be started from the beginning of the > partition: > elphel393~# rm /mnt/sda1/camogm.disk (camogm might need to be restarted > after this) > > To actually erase data you can use dd, getting data from "if=/dev/zero" > and writing to "of=/dev/sda2". > > Sometimes only one shows up (it isn't always the same port). >> > Reproduced the problem. > > Oleg > > On Mon, Apr 9, 2018 at 12:39 PM, Mohamed Morsy <mmo...@redzone.com> wrote: > >> Also, how can I remove the files from the sda2 partition once I'm done? >> >> On Mon, Apr 9, 2018 at 2:26 PM, Mohamed Morsy <mmo...@redzone.com> wrote: >> >>> I'm using 3 sensors. Sometimes only one shows up (it isn't always the >>> same port). >>> >>> On Mon, Apr 9, 2018 at 1:58 PM, Oleg <support-list@support.elphel.com> >>> wrote: >>> >>>> Mohamed, >>>> >>>> >>>>> I reformatted the drive so sda2 is raw. Now I'm trying to copy a >>>>> recording from there. I'm not sure what you meant by: >>>>> run https://git.elphel.com/Elphel/eyesis4pi-393-gui/blob/mas >>>>> ter/footage_downloader/split_mov.php from inside the directory with >>>>> image.bin >>>>> >>>> >>>> I meant - download the script and run it (provided php is installed), >>>> for example: >>>> * save the split_mov.php to directory with downloaded footage >>>> () >>>> Then in terminal: >>>> $ cd >>>> $ php split_mov.php >>>> >>>> * The footage can be the one you downloaded from the raw partition or >>>> you can test with any .mov (just change the extension to .bin). >>>> * The script scans the working directory () for *.bin files >>>> then opens them as binary, looks for images (by exif header marker) and >>>> extracts them. >>>> >>>> Also, when I use the 14MPx sensors with nand, the cameras don't always >>>>> show up. Sometimes only one shows up or none of them do. Any ideas what >>>>> might be wrong? >>>>> >>>> Don't know, need to test. >>>> Are there 2 sensors? >>>> When a single sensor shows up - is it always the same port? which one? >>>> >>>> Best regards, >>>> Oleg Dzhimiev >>>> Electronics Engineer >>>> phone: +1 801 783 x124 >>>> Elphel, Inc. >>>> >>> >>> >> >> ___ >> Support-list mailing list >> Support-list@support.elphel.com >> http://support.elphel.com/mailman/listinfo/support-list_supp >> ort.elphel.com >> > -- Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] Elphel Storage Drive
Mohamed, > I reformatted the drive so sda2 is raw. Now I'm trying to copy a recording > from there. I'm not sure what you meant by: > run https://git.elphel.com/Elphel/eyesis4pi-393-gui/blob/ > master/footage_downloader/split_mov.php from inside the directory with > image.bin > I meant - download the script and run it (provided php is installed), for example: * save the split_mov.php to directory with downloaded footage () Then in terminal: $ cd $ php split_mov.php * The footage can be the one you downloaded from the raw partition or you can test with any .mov (just change the extension to .bin). * The script scans the working directory () for *.bin files then opens them as binary, looks for images (by exif header marker) and extracts them. Also, when I use the 14MPx sensors with nand, the cameras don't always show > up. Sometimes only one shows up or none of them do. Any ideas what might be > wrong? > Don't know, need to test. Are there 2 sensors? When a single sensor shows up - is it always the same port? which one? Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] Elphel Storage Drive
Mohamed, I formatted the drive using ip_address/format_disk.php. This created sda1 > and raw sda2. Then I used mkfs.ext4 /dev/sda2 to format the 2nd partition. > I made a directory sda2 in mnt and mounted /dev/sda2 there. I can copy > files from /mnt/sda2 using scp. Is this the right way? I'm not sure why I > need 2 partitions. > 2 partitions are used for 'fast recording'. Not having a file system on sda2 partition saves some time to perform writes, and also should reduce the wearing out of SSD. And ext4 sda1 partition is intended to store information where to start/continue recording from (camogm.disk). You don't have to use it if normal recording works. In this case you can have only a single partition - use fdisk to repartition. But if you increase the image quality normal recording might be too slow - you can test this - in camogm gui click on the 'show buffers' and run recording. When I use the Apple Quicktime Movie format, I get videos of the frames > from each port alternating. Is there a way to separate them so I get a > video for each port? > Camogm does not have an option to store different ports into separate files. Though it's possible to implement but will probably slow down recording. You can separate them on your PC. split_mov.php which I mentioned before - does splitting and naming files as _. Then they can be combined back to movs with ffmpeg, for example. For image format, COLOR is set as 0. Does that matter? > JP4 is a kind of a raw image format we implemented - see this article <https://wiki.elphel.com/wiki/JP4>. > By the way, I was curious if it's possible to use 14 MPix sensors with > nand? > Yes. I didn't include the device tree for nand for 14MPx. Now it's here(devicetree.dtb) <https://community.elphel.com/files/393/20180406/nand/mt9f002/>. Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] Elphel Storage Drive
Hi Mohamed, 1. For 14MPx - there's incorrect fps from the sensor in the firmware you've been using - we have fixed it - you can find it here (20180406) <https://community.elphel.com/files/393/20180406/>. To enable 14Mpx - apart from the changes in the device tree and 10389's eeprom, set the TRIG parameter to 0 (the default config is 0x4 meaning triggered mode) then you can check the timestamps in http://camera-ip/parsedit.php > "last 9 images, 3 per row, scale=0.2". It should be ~11.07 for the full frame. Then you can save the config at http://192.168.0.9/autocampars.php?sensor_port=0 2. About recording. Don't know how you are downloading the footage. Do you record on the sda1 or sda2? Also, image format jpeg (COLOR=0) or jp4 (COLOR=5)? If sda1 - it's scp over network or switching camera's SSD to PC, mounting and copying. If sda2 (which is the raw partition) - don't know if you figured out how to download images - there are a few ways: - over network using dd: Note: When recording to the raw parition the driver creates a file /mnt/sda1/camogm.disk and stores partition info with write pointers measured in LBA units (512B each). It uses the info to restart recording from where it left of (to start from the beginning remove this file). This camogm.disk will also tell you how much you need to download from the partition. # line below will download 200MB from the start of the partition: ssh root@camera-ip "dd if=/dev/sda2 bs=20M count=10 | gzip -1 -" | dd of=image.bin.gz unpack to image.bin run https://git.elphel.com/Elphel/eyesis4pi-393-gui/blob/master/footage_downloader/split_mov.php from inside the directory with image.bin - via eSATA cable connected to PC and the camera: Try using int_ssd_download.py (from https://git.elphel.com/Elphel/elphel-tools-x393). Then you will need split_mov.php as well. Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] Elphel Storage Drive
Hi Mohamed, 1. http://camera-ip > Recorder docs: https://wiki.elphel.com/wiki/Camogmgui 2. There should be 2 partitions on SSD: sda1 ~6GB - formatted to EXT4 - sda1 is automounted to /mnt/sda1 (check with 'df -h' or ) sda2 ~122GB - not formatted - for 'raw' recording If it's not formatted, see 4b.. Other info: 3. To check if SSD is detected: 3a. > root@elphel393:~# cat /proc/partitions 3b. > root@elphel393:~# dmesg Example output: > [ 23.160946] ata1: SATA max UDMA/133 mmio [mem 0x8000-0x8fff] > port 0x100 irq 163 > [ 23.510004] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) > [ 23.517599] ata1.00: ATA-9: TS128GMTS600, P1225CE, max UDMA/133 > [ 23.523846] ata1.00: 250069680 sectors, multi 1: LBA48 NCQ (depth 0/32) > [ 23.532486] ata1.00: configured for UDMA/133 > [ 23.541610] scsi 0:0:0:0: Direct-Access ATA TS128GMTS600 > 5CE PQ: 0 ANSI: 5 > [ 23.555202] sd 0:0:0:0: Attached scsi generic sg0 type 0 > [ 23.555418] sd 0:0:0:0: [sda] 250069680 512-byte logical blocks: (128 > GB/119 GiB) > [ 23.556425] sd 0:0:0:0: [sda] Write Protect is off > [ 23.556437] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 > [ 23.556545] sd 0:0:0:0: [sda] Write cache: enabled, read cache: > enabled, doesn't support DPO or FUA > [ 23.583494] sda: sda1 sda2 > [ 23.591877] sd 0:0:0:0: [sda] Attached SCSI disk > [ 24.171488] random: nonblocking pool is initialized > [ 24.950555] EXT4-fs (sda1): recovery complete > [ 24.956238] EXT4-fs (sda1): mounted filesystem with ordered data mode. > Opts: (null) 3c. > root@elphel393:~# hdparm -I /dev/sda 4. Some information if you would like to reformat it: 4a. https://wiki.elphel.com/wiki/Format_SSD_MMC#SSD_or_USB Mainly it's 2 programs: fdisk and mkfs 4b. http://192.168.0.9/format_disk.php Let me know if you have any further questions or need more details. Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] 14Mpix sensor update
Hi, https://community.elphel.com/files/393/20180322/ - 5MPx works - there's serial number added to http://192.168.0.9:2323/meta (2323 = port 0 ... 2326 = port 3) > "00:0E:64:10:F2:7F" - see instructions in readme_14MPx.md for 14MPx in the archive. Try with SD card. - I'm working on exposure - there are incorrect fps readings. Let me know if you have any problems. Regards, Oleg On Wed, Mar 21, 2018 at 7:41 PM, Richard Rigby <rri...@redzone.com> wrote: > Awesome, thank you. > > > Kind regards, > > *Richard Rigby* > Software Developer > > > www.redzone.com > > Ph: +64 9 479 9901 > > Fax: +64 9 479 9904 > > > 13 Tarndale Grove • Albany • Auckland 0632 • New Zealand > > On 22 March 2018 at 14:40, Oleg <support-list@support.elphel.com> wrote: > >> Ok. Will upload tomorrow. Need to test a little if it still works for >> 5MPx. >> Oleg >> > > > ___ > Support-list mailing list > Support-list@support.elphel.com > http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com > > ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] Building firmware
> > coping files to root partition on another PC > You copied them then remounted the card and there are not there, right? Try from the command line - you should get some error if they are not copied. - Check permissions or unmount properly or run sync boot camera off SD card and copy files over using ssh Not copied? If copied - it might be permissions - not executable? not owned by root? $ scp files root@192.168.0.9:/user/bin/ then ssh to the camera: elphel393~# ls -all /usr/bin/ Oleg On Wed, Mar 21, 2018 at 6:46 PM, Richard Rigby <rri...@redzone.com> wrote: > Hi Oleg, > > I first tried coping files to root partition on another PC, then when that > didn't work I tried to boot camera off SD card and copy files over using > ssh. That also didn't work. > > I must have build master, I will try rocko branch next. > > Thank you for your support. > > Kind regards, > > *Richard Rigby* > Software Developer > > > www.redzone.com > > Ph: +64 9 479 9901 > > Fax: +64 9 479 9904 > > > 13 Tarndale Grove • Albany • Auckland 0632 • New Zealand > > On 22 March 2018 at 12:56, Oleg <support-list@support.elphel.com> wrote: > >> Hi, >> >> I have trying to build the firmware and flash the camera however I have >>> not been successful. I build the firmware on my machine and the used the >>> web interface to upload the new firmware to the camera, however this >>> bricked the camera. Do you have any advice about why this may have happened? >>> >> >>- Did you build master (= jethro) or rocko branch? git clone -b >>rocko https://git.elphel.com/Elphel/elphel393.git? >>- I'm working with the kernel in rocko plus some application projects >>are on their master branches. Can break things from time to time but I >>recommend to build the rocko branch for the main project. >>- If you have a serial port up you should see at least some output >>from u-boot and kernel. >>- First try putting your built files on the recovery SD card and boot >>from it - >> >> In elphel393/tools/elphel-tools-update/ there's a write_bootable_mmc.py >> - if you used it to write the card then copy it >> to elphel393/bootable-images/mmc/ and run it. >> If it boots and works - then flash it from the web interface >> >>- If you boot from flash - you can only reflash u-boot, device tree >>and kernel, but not rootfs (cause it's mounted). To reflash rootfs - boot >>from the recovery card and use the web interface. >> >> >> >>> I then tried to add extra files onto the SD card, however the camera >>> would not boot from SD card after adding extra files. Is it not possible to >>> add files to filesystem on the SD card. >>> >> >> It is possible. Did you copy files to the ROOT partition or BOOT? Serial >> output would help. >> >> >>> I would like to be able to flash the camera with custom firmware with >>> additional services running on the camera. Will this be easy to do? >>> >> >> Brief info: >> https://wiki.elphel.com/wiki/Development_for_10393#Applications >> >> It needs a one time setup. Take/copy 'init' project as an example. After >> it's set up there's an extra bitbake task to copy files to the camera - I >> boot from SD card for development: >> >>> $ bitbake somerecipe -c compile -f; bitbake somerecipe -c target_scp -f >> >> This task requires pwdless access to the camera: ssh-copy-id >> root@192.168.0.9 >> >> If some application already exists in Yocto or OE - you just need to >> include it to the list in the elphel393/meta/meta-elphel393/ >> recipes-core/images/core-image-elphel393.bb >> >> Best regards, >> Oleg Dzhimiev >> Electronics Engineer >> phone: +1 801 783 x124 <(801)%20783-> >> Elphel, Inc. >> > > > ___ > Support-list mailing list > Support-list@support.elphel.com > http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com > ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] 14Mpix sensor update
Ok. Will upload tomorrow. Need to test a little if it still works for 5MPx. Oleg ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] 14Mpix sensor update
Hello, > Is there an update regarding support for the 14 Mpix sensor? > What works: - cable phase adjusting on detect - free running mode - exposure / autoexposure - gains and autowhite balance - changing window size can freeze - so, it's better to turn off compressor before changing Things to do: - binning / skipping - flips - test get rid of freezing - triggered mode You can try it if you like. I can upload a firmware image or just a device tree. - to switch between sensor types - the device tree has to be recompiled. for 14MPx: > ... > elphel393-detect_sensors,sensors = "mt9f002", "mt9f002", "mt9f002", > "mt9f002"; > ... for 5MPx: > ... > elphel393-detect_sensors,sensors = "mt9p006", "mt9p006", "mt9p006", " > mt9p006"; > ... Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] Building firmware
Hi, I have trying to build the firmware and flash the camera however I have not > been successful. I build the firmware on my machine and the used the web > interface to upload the new firmware to the camera, however this bricked > the camera. Do you have any advice about why this may have happened? > - Did you build master (= jethro) or rocko branch? git clone -b rocko https://git.elphel.com/Elphel/elphel393.git? - I'm working with the kernel in rocko plus some application projects are on their master branches. Can break things from time to time but I recommend to build the rocko branch for the main project. - If you have a serial port up you should see at least some output from u-boot and kernel. - First try putting your built files on the recovery SD card and boot from it - In elphel393/tools/elphel-tools-update/ there's a write_bootable_mmc.py - if you used it to write the card then copy it to elphel393/bootable-images/mmc/ and run it. If it boots and works - then flash it from the web interface - If you boot from flash - you can only reflash u-boot, device tree and kernel, but not rootfs (cause it's mounted). To reflash rootfs - boot from the recovery card and use the web interface. > I then tried to add extra files onto the SD card, however the camera would > not boot from SD card after adding extra files. Is it not possible to add > files to filesystem on the SD card. > It is possible. Did you copy files to the ROOT partition or BOOT? Serial output would help. > I would like to be able to flash the camera with custom firmware with > additional services running on the camera. Will this be easy to do? > Brief info: https://wiki.elphel.com/wiki/Development_for_10393#Applications It needs a one time setup. Take/copy 'init' project as an example. After it's set up there's an extra bitbake task to copy files to the camera - I boot from SD card for development: > $ bitbake somerecipe -c compile -f; bitbake somerecipe -c target_scp -f This task requires pwdless access to the camera: ssh-copy-id root@192.168.0.9 If some application already exists in Yocto or OE - you just need to include it to the list in the elphel393/meta/meta-elphel393/recipes-core/images/core-image-elphel393.bb Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 <(801)%20783-> Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] Script for changing the SADDR bit for the MT9P031 sensor
Hi, 1. To check if camogm is alive: > root@elphel393:~# ps | grep camogm 3059 root 267m Scamogm -n /var/state/camogm_cmd -p 3456 -s > /mnt/sda1/camogm.disk > 3081 root 2764 Sgrep camogm 2. Check camogm status: http://192.168.0.9/camogm_interface.php?cmd=status 3. Start manually (Normally it's started by camogmgui.php (linked from the main page)): > root@elphel393:~# camogm -n /var/state/camogm_cmd -p 3456 When started from a command line there should be some output when it receives commands. Regards, Oleg On Thu, Mar 15, 2018 at 9:50 AM, Elphel Support < support-list@support.elphel.com> wrote: > Frederick, > > A link to what? > > How were you starting camogm? Did it work before? How were you using it? > How did it fail to load? > > Andrey > > On Thu, 15 Mar 2018 08:31:29 -0700 *Frederick > Gamache<frederick.gama...@gmail.com <frederick.gama...@gmail.com>>* wrote > > > Another thing, > > After I tried pluging a USB drive through an hub, attached to the 10389B > board, it seems that the camogm is failing to load, even after re-booting. > > Is there a link? > > Frederick > > On Thu, Mar 15, 2018 at 10:53 AM, Frederick Gamache < > frederick.gama...@gmail.com> wrote: > > Andrey, > > The supply current drawn is nearly 2.0 Amps @ 3.3V, once the FPGA is > loaded. > I have the 10389 interface board but no SSD mounted and no external SATA > drive attached at the moment. > > When I received the camera kit, I found that the unit was especially hot > when touching it. > I don't have the camera enclosure, but only an aluminium frame on which > the boards are mounted. I guess that the frame serves as a heat sink at > same time? > > For the power board failure, maybe I accidentally created a short when I > plug/unplugged the wall adapter from the power board connector while the > power adapter was plugged into the wall... > > It is hard to tell what component failed on the power board because many > components are mounted underneath the Traco DC-DC converter itself... > > When I plug the 48 V source, no 3.3V appears at the output. > > Frederick > > > On Thu, Mar 15, 2018 at 10:29 AM, Elphel Support < > support-list@support.elphel.com> wrote: > > Hello Frederick, > > Do you know power consumption on the ports? Do you have 10389 interface > board with the SSD? If you run camera from the 3.3V - can you measure the > total 3.3V current? Do you have sufficient fan cooling or heat sink? > > We never had 10385 failures before - Traco DC-DC converter seems to have > all required protection - current, temperature so we had the system shut > down when overloaded, but not failed. We would like to try to find out - > what component actually failed - is it DC-DC or something else. > > We do have a new power supply design (https://wiki.elphel.com/wiki/10386 > - temporary images are for 10385B), but it is not built yet., we just > released the PCB design a few days ago. > > Andrey > > On Thu, 15 Mar 2018 06:38:07 -0700 *Frederick Gamache > <frederick.gama...@gmail.com <frederick.gama...@gmail.com>>* wrote > > Hi, > > Its seems that my power board (10385-B power board - 48V) is out of > service and I'm now powering the 3.3V from an external power supply. > Do I really need the 10385-B power board to supply the SATA adapter board > (10389-B) or should it works ok from my external 3.3V power source? > > Frederick > > > On Wed, Mar 14, 2018 at 11:10 AM, Frederick Gamache < > frederick.gama...@gmail.com> wrote: > > Hello Andrey, > > I owe at least this for your great support. > By the way, congratulations for your great products! > > Best regards, > Frederick > > On Wed, Mar 14, 2018 at 10:53 AM, Elphel Support < > support-list@support.elphel.com> wrote: > > Frederick, > > Thank you for letting us know it did work. Sometimes the only indication > of the problem being solved is the lack of the continuation in the thread. > > Andrey > > On Wed, 14 Mar 2018 07:12:13 -0700 *Frederick Gamache > <frederick.gama...@gmail.com <frederick.gama...@gmail.com>>* wrote > > Hello, > > Just to let you know guys that my circuit is now working since I mounted > my DC-DC converter on my PCB. > > Many thanks for your support! > Frederick > > On Tue, Mar 13, 2018 at 12:18 PM, Elphel Support < > support-list@support.elphel.com> wrote: > > Frederick, > > Yes - your last problem (system getting stuck after bitstream) is caused > by the wrong power sequencing. But as 1) you have 10338 working and 2) your > board is tested w/o 10393 it should be
Re: [Elphel-support] Script for changing the SADDR bit for the MT9P031 sensor
Hi, > Question: does the software needs to reach the 34VL02 EEPROM at any point? > Because I don't have one on my own sensor board... > It should work fine without eeprom. Did it read chip id? or is it 0x? Do you use minicom or putty or other terminal program? Regards, Oleg ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] Script for changing the SADDR bit for the MT9P031 sensor
Frederick,
1. Here are the files: https://community.elphel.com/f
iles/393/20180308_test_0x5d/
2. Before copying - boot from the card and check the linux version:
> root@elphel393:~# uname -r
> 4.9.0-xilinx-v2017.3
* If it's 4.9.0-xilinx-v2017.3 then copying only devicetree.dtb and uImage
might be enough - they are on the FAT partition of the card.
* In case of fail if you use minicom (or putty or other serial terminal
program) there will be some kind of a kernel panic.
3.
My bootlog for 0x5d:
> ...
> [ 21.692018] {0} Setting i2c_addr to 0x5d
> [ 21.696039] Read i2c (port = 0, sa7=0x5d, reg=0x0) chip ID=
> ...
> [ 21.747074] {1} Setting i2c_addr to 0x5d
> [ 21.756495] Read i2c (port = 1, sa7=0x5d, reg=0x0) chip ID=
> ...
> [ 21.807904] {2} Setting i2c_addr to 0x5d
> [ 21.817282] Read i2c (port = 2, sa7=0x5d, reg=0x0) chip ID=
> ...
> [ 21.868874] {3} Setting i2c_addr to 0x5d
> [ 21.878291] Read i2c (port = 3, sa7=0x5d, reg=0x0) chip ID=
...
bootlog for 0x48 (2 sensors connected):
> ...
[ 21.607985] {0} Setting i2c_addr to 0x48
> [ 21.612007] Read i2c (port = 0, sa7=0x48, reg=0x0) chip ID=1801
> [ 21.617888] Found MT9P001 2592x1944 sensor, chip ID=1801
> [ 21.674977] {1} Setting i2c_addr to 0x48
> [ 21.684454] Read i2c (port = 1, sa7=0x48, reg=0x0) chip ID=1801
> [ 21.690690] Found MT9P001 2592x1944 sensor, chip ID=1801
> [ 21.747575] {2} Setting i2c_addr to 0x48
> [ 21.757033] Read i2c (port = 2, sa7=0x48, reg=0x0) chip ID=
> ...
> [ 21.808291] {3} Setting i2c_addr to 0x48
> [ 21.817738] Read i2c (port = 3, sa7=0x48, reg=0x0) chip ID=
> ...
Best regards,
Oleg Dzhimiev
Electronics Engineer
phone: +1 801 783 x124
Elphel, Inc.
___
Support-list mailing list
Support-list@support.elphel.com
http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] Script for changing the SADDR bit for the MT9P031 sensor
Hi, > Can you send me an updated version of the firmware using the 0x5D addr > please? > Ok, I will send you a link once I prepare it later today. I will turn the kernel debug on. Will I be able to copy the files you will send me on the camera micro SD > card so I can boot from it? > Do you have linux? There will be a script *write_bootable_mmc.py* in the archive that can format it, provided it's discovered in the system as /dev/sdX (if it's discovered as /dev/mmcblk the script will need a minor modification) The instructions how to format it manually can be found here <https://wiki.elphel.com/wiki/Sd_boot_rootfs>. Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 <(801)%20783-> Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] Script for changing the SADDR bit for the MT9P031 sensor
Hi,
1.
I made change so it could be set int device tree (0x48) - just noticed a
bug and had to fix it:
> ...
elphel393_sensor_i2c: elphel393-sensor-i2c@0 {
> compatible = "elphel,elphel393-sensor-i2c-1.00";
> /* Add known devices: name, slave address (7-bit), number
> of address bytes, number of data bytes, SCL frequency (kHz) */
> elphel393-sensor-i2c,i2c_devices = "mt9f0020x10 2
> 2 500",
>"mt9p006*0x48*
> 1 2 500",
>"el103590x08 1
> 2 500",
>"el10359_32 0x08 1
> 4 500",
>"pca9500_eeprom 0x50 1
> 1 100",
>"sensor_eeprom 0x50 1
> 1 100",
>"sensor_temp0x18 1
> 2 100",
>"cy223930x69 1
> 1 100";
> } ;
...
Commands to recompile devicetree:
decompile:
> $ dtc -I dtb -O dts devicetree.dtb -o devicetree.dts
compile:
> $ dtc -I dts -O dtb devicetree.dts -o devicetree.dtb
2. Are you able to build the firmware or should I upload it to somewhere?
3. Before any updating - can you read sensor's registers?
> ~$ ssh root@192.168.0.9
> root@elphel393:~# cd /usr/local/verilog/
> root@elphel393:~# test_mcntrl.py @hargs-after
> x393 --> r
> x393 --> print_sensor_i2c (without args it will print usage)
>
> *...*
> *print_sensor_i2c *
> *...*x393 --> print_sensor_i2c 0 0x3000 0xff *0x10* 0
> * Result: 0x2e01*
- 10393's port the sensor is connected to. Can be: 0..3
- I tried on a sensor that has 16-bit addresses (0x3000), for
MT9P006 it can be 0x0 (ID register addr)
* *- set 0xff
* -* SADDR
4. Side note (sensor power and clock):
At boot autocampars.php calls: test_mcntrl.py @hargs
test_mcntrl.py (located at /usr/local/bin/)
hargs (located at /usr/local/verilog/)
Inside hargs file there are commands for:
- which bitstream to load
- setting sensor power: for MT9P006 it's PAR12 which translates to
{"mv":2800, "freq":24.0,"iface":"2V5_LVDS"}
- setting sensor clock frequency: for MT9P006 it's 24.0 "2V5_LVDS"
Best regards,
Oleg Dzhimiev
Electronics Engineer
phone: +1 801 783 x124
Elphel, Inc.
___
Support-list mailing list
Support-list@support.elphel.com
http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] Elphel 393 Question
Hi, I'm experiencing another issue. I'm trying to create a bootable micro sd > card. I was able to get it to work on one of my elphels (the older one that > doesn't work without a card). However it's not working with the other 3 > newer elphels. They just boot using NAND memory. I filed off the corner on > the card I'm using so it's like the recovery card. Do you know what the > issue might be? We have tried a number cards before - there's a high chance that a card will not survive filing as it can have circuitry in that corner. So, we bought ones that are working. You should have a few of recovery cards or we can send you some extra if you need. So, your card might need a bit more filing - it probably still locks the CD pin on the other boards. https://wiki.elphel.com/wiki/Boot_options_393 Regards, Oleg On Mon, Feb 26, 2018 at 2:28 PM, Mohamed Morsy <mmo...@redzone.com> wrote: > Hi Oleg, > > I'm experiencing another issue. I'm trying to create a bootable micro sd > card. I was able to get it to work on one of my elphels (the older one that > doesn't work without a card). However it's not working with the other 3 > newer elphels. They just boot using NAND memory. I filed off the corner on > the card I'm using so it's like the recovery card. Do you know what the > issue might be? > > Thanks, > > Mohamed > > On Thu, Feb 22, 2018 at 2:08 PM, Mohamed Morsy <mmo...@redzone.com> wrote: > >> That worked. Thanks >> >> On Thu, Feb 22, 2018 at 1:04 PM, Oleg <support-list@support.elphel.com> >> wrote: >> >>> You don't have to close minicom. >>> >>> It works with the card, right? Then: >>> >>> 1. If the board is one of the first we sent you (what's the serial >>> number?) then... later we had to make a minor fix. The problem was it >>> wouldn't boot from flash without a card. >>> >>> Try: if you have some other micro sd card at hand (w/o a cut corner) - >>> insert it and see if it boots. If yes then you can send us the board and we >>> will fix it. >>> >>> 2. Make sure you flashed boot.bin. >>> >>> Oleg >>> >>> On Thu, Feb 22, 2018 at 10:38 AM, Mohamed Morsy <mmo...@redzone.com> >>> wrote: >>> >>>> The 2 leds (green and yellow) are on. I'm using power from a battery >>>> without the traco board. This is what I did with the 1st board. I also have >>>> the traco board if i need it which is 18-75V. I haven't changed anything in >>>> minicom. I just flashed with the recovery card in, removed it, and tried to >>>> connect with minicom but I can't type anything in. >>>> >>>> On Thu, Feb 22, 2018 at 12:01 PM, Oleg <support-list@support.elphel.com >>>> > wrote: >>>> >>>>> No it doesn't print anything at all. I can't connect via ssh. Is it >>>>>> possible the baud rate isn't 115200? >>>>> >>>>> No. >>>>> Any network leds blinking? Or at least light up temporarily? >>>>> Is the board getting warm? >>>>> Do you power with the power supply board (TRACO)? Is it the same you >>>>> used for the 1st board? Is it "18-75V" or "9-36V" - can't remember if you >>>>> have both types. >>>>> Did you guys manage to power 10393 with 3.3V directly (Todd asked >>>>> about this recently)? In this case you can check the current. >>>>> >>>>> On Thu, Feb 22, 2018 at 9:44 AM, Mohamed Morsy <mmo...@redzone.com> >>>>> wrote: >>>>> >>>>>> No it doesn't print anything at all. I can't connect via ssh. Is it >>>>>> possible the baud rate isn't 115200? >>>>>> >>>>>> On Thu, Feb 22, 2018 at 11:35 AM, Oleg <support-list@support.elphel.c >>>>>> om> wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> Is it printing anything when you power on? >>>>>>> Can you connect to the camera via ssh? >>>>>>> >>>>>>> Oleg >>>>>>> >>>>>>> On Thu, Feb 22, 2018 at 7:38 AM, Mohamed Morsy <mmo...@redzone.com> >>>>>>> wrote: >>>>>>> >>>>>>>> Hello Oleg, >>>>>>>> >>>>>>>> I was able to fix one of my elphels yesterday using the methods you >>>>>>>> suggested. Now I'm trying to do the same with my other one but when I >
Re: [Elphel-support] Fwd: 14Mpix sensor not detected
Hi, 14MPx is not yet supported in the current firmware but I'm working on the driver at the moment - hopefully will have something within a couple weeks. There's an old firmware where exposure, gains and lane phases can be set, not much more. Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. On Fri, Feb 23, 2018 at 11:23 AM, Andrey Filippov <and...@elphel.com> wrote: > > > == == == == == == Forwarded message == == == == == == > From : Richard Rigby<rri...@redzone.com> > To : <support-l...@elphel.com> > Date : Thu, 22 Feb 2018 18:28:08 -0800 > Subject : 14Mpix sensor not detected > == == == == == == Forwarded message == == == == == == > > Hello, > > I have a 393 board as well as one 5 Mpix sensor and one 14 Mpix sensor. > However only the 5Mpix sensor is working. > > I am using the web interface to view the camera. > > I have tried to run the init_elphel393.py script for both sensors and it > looks to me that the 14 Mpix sensor cannot be detected. > > This is the output from init_elphel393.py when only the 14 Mpix sensor is > connected: > [ 443.35] init_elphel393: Fan on > [ 443.36] init_elphel393: Initialize USB hub > [ 443.37] init_elphel393: 10389 was not detected: skipping USB hub init > [ 443.37] init_elphel393: init_elphel393.py: ip = 192.168.0.9, mask = > 255.255.255.0 > [ 443.38] init_elphel393: init_elphel393.py: imgsrv > Set port number: 2323 > Set port number: 2324 > Set port number: 2325 > Set port number: 2326 > [ 443.77] init_elphel393: init_elphel393.py: auto exposure daemon > autoexposure#0 started, daemon_bit=0x0, debug=0x1 > autoexposure#1 started, daemon_bit=0x0, debug=0x1 > autoexposure#2 started, daemon_bit=0x0, debug=0x1 > autoexposure#3 started, daemon_bit=0x0, debug=0x1 > [ 443.99] autocampars: Processing camera state: INITIALIZED > [ 444.05] autocampars: Active sensor ports: master_port = -1 > [ 444.07] autocampars: Sensors map read from the sysfs: [none, none, > none, none],[none, none, none, none],[none, none, none, none],[none, none, > none, none] > [ 444.12] autocampars: get_application_mode()->4369 > [ 444.17] autocampars: Detecting sensors for MT9P006 > [ 444.20] autocampars: Got --init command for already initialized > camera, trying to re-initialize > [ 444.22] autocampars: after reset - current frame on master port = > [ 444.25] autocampars: Reset camera state to BITSTREAM > [ 444.33] autocampars: ports: > [ 444.35] autocampars: *System FPGA version: 0x039300da* > [ 444.38] autocampars: *Sensor interface type: PAR12* > [ 444.45] autocampars: *Detected sensors: [none, none, none, > none],[none, none, none, none],[none, none, none, none],[none, none, none, > none]* > [ 444.48] autocampars: Reached state: SENSORS_DETECTED > [ 444.53] autocampars: Disabling sensor port 0 > [ 444.56] autocampars: Disabling sensor port 1 > [ 444.58] autocampars: Disabling sensor port 2 > [ 444.61] autocampars: Disabling sensor port 3 > [ 444.69] autocampars: Frames: -1, -1, -1, -1 > [ 444.71] autocampars: Reached state: SENSORS_SYNCHRONIZED > [ 444.74] autocampars: ports: > [ 444.81] autocampars: init_cameras() start: camera_state=SENSORS_ > SYNCHRONIZED > [ 444.86] autocampars: Collected gammas == Array > ( > ) > > [ 444.89] autocampars: will need to skip local frames > [ 444.92] autocampars: Reached state PARAMETERS_PRESET > [ 444.94] autocampars: Skipping frames > [ 444.97] autocampars: Frame delay = 0 s > [ 445.02] autocampars: Remaining trigger parameters: > > Warning: array_key_exists() expects parameter 2 to be array, null given in > /usr/bin/autocampars.php on line 1074 > > Warning: array_key_exists() expects parameter 2 to be array, null given in > /usr/bin/autocampars.php on line 1085 > > Warning: array_key_exists() expects parameter 2 to be array, null given in > /usr/bin/autocampars.php on line 1086 > > Warning: array_key_exists() expects parameter 2 to be array, null given in > /usr/bin/autocampars.php on line 1091 > > Warning: elphel_set_P_arr() expects parameter 2 to be array, null given in > /usr/bin/autocampars.php on line 1095 > [ 445.09] autocampars: Skipping more frames > [ 445.14] autocampars: Reached state PARAMETERS_PRESET > [ 445.17] autocampars: Reached state INITIALIZED > [ 445.20] autocampars: Sensors on ports: were successfully initialized > [ 445.22] autocampars: *INITIALIZED* > [ 445.25] autocampars: *revisions differ* > [ 445.27] autocampars: *Log file saved as /var/log/autocampars.log* > [ 445.32] init_elphel393: init SATA > [ 445.32] init_elphel393: 10389 was not detected: skipping SATA init > [ 445.32] init_elphel393: Start GPS and event logger &g
Re: [Elphel-support] Elphel 393 Question
You don't have to close minicom. It works with the card, right? Then: 1. If the board is one of the first we sent you (what's the serial number?) then... later we had to make a minor fix. The problem was it wouldn't boot from flash without a card. Try: if you have some other micro sd card at hand (w/o a cut corner) - insert it and see if it boots. If yes then you can send us the board and we will fix it. 2. Make sure you flashed boot.bin. Oleg On Thu, Feb 22, 2018 at 10:38 AM, Mohamed Morsy <mmo...@redzone.com> wrote: > The 2 leds (green and yellow) are on. I'm using power from a battery > without the traco board. This is what I did with the 1st board. I also have > the traco board if i need it which is 18-75V. I haven't changed anything in > minicom. I just flashed with the recovery card in, removed it, and tried to > connect with minicom but I can't type anything in. > > On Thu, Feb 22, 2018 at 12:01 PM, Oleg <support-list@support.elphel.com> > wrote: > >> No it doesn't print anything at all. I can't connect via ssh. Is it >>> possible the baud rate isn't 115200? >> >> No. >> Any network leds blinking? Or at least light up temporarily? >> Is the board getting warm? >> Do you power with the power supply board (TRACO)? Is it the same you used >> for the 1st board? Is it "18-75V" or "9-36V" - can't remember if you have >> both types. >> Did you guys manage to power 10393 with 3.3V directly (Todd asked about >> this recently)? In this case you can check the current. >> >> On Thu, Feb 22, 2018 at 9:44 AM, Mohamed Morsy <mmo...@redzone.com> >> wrote: >> >>> No it doesn't print anything at all. I can't connect via ssh. Is it >>> possible the baud rate isn't 115200? >>> >>> On Thu, Feb 22, 2018 at 11:35 AM, Oleg <support-list@support.elphel.com> >>> wrote: >>> >>>> Hi, >>>> >>>> Is it printing anything when you power on? >>>> Can you connect to the camera via ssh? >>>> >>>> Oleg >>>> >>>> On Thu, Feb 22, 2018 at 7:38 AM, Mohamed Morsy <mmo...@redzone.com> >>>> wrote: >>>> >>>>> Hello Oleg, >>>>> >>>>> I was able to fix one of my elphels yesterday using the methods you >>>>> suggested. Now I'm trying to do the same with my other one but when I open >>>>> the minicom console I can't type anything. Do you have any idea how to fix >>>>> this? >>>>> >>>>> Thanks, >>>>> >>>>> Mohamed >>>>> >>>>> On Wed, Feb 21, 2018 at 4:06 PM, Mohamed Morsy <mmo...@redzone.com> >>>>> wrote: >>>>> >>>>>> Thank you very much >>>>>> >>>>>> On Wed, Feb 21, 2018 at 3:53 PM, Oleg <support-list@support.elphel.c >>>>>> om> wrote: >>>>>> >>>>>>> Alright. Since you're modifying files on flash rootfs, don't forget >>>>>>> to run: >>>>>>> >>>>>>>> root@elphel393:~# overlay_sync 1 >>>>>>>> root@elphel393:~# shutdown -hP now >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Wed, Feb 21, 2018 at 1:50 PM, Mohamed Morsy <mmo...@redzone.com> >>>>>>> wrote: >>>>>>> >>>>>>>> actually i think i found my answer. >>>>>>>> >>>>>>>> Thanks! >>>>>>>> >>>>>>>> On Wed, Feb 21, 2018 at 3:44 PM, Mohamed Morsy <mmo...@redzone.com> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> ok so the ip was 192.168.0.9. I changed it and it works. But when >>>>>>>>> i power it off and restart it, it goes back to 192.168.0.9. Do i have >>>>>>>>> to >>>>>>>>> save it somehow? >>>>>>>>> >>>>>>>>> On Wed, Feb 21, 2018 at 3:35 PM, Oleg < >>>>>>>>> support-list@support.elphel.com> wrote: >>>>>>>>> >>>>>>>>>> It's 'root' >>>>>>>>>> >>>>>>>>>> On Wed, Feb 21, 2018 at 1:32 PM, Mohamed Morsy < >>>>>>>>>> mmo...@redzone.com> wrote: >>>>>>>>>> >>>>>>>>>>&g
Re: [Elphel-support] Elphel 393 Question
> > No it doesn't print anything at all. I can't connect via ssh. Is it > possible the baud rate isn't 115200? No. Any network leds blinking? Or at least light up temporarily? Is the board getting warm? Do you power with the power supply board (TRACO)? Is it the same you used for the 1st board? Is it "18-75V" or "9-36V" - can't remember if you have both types. Did you guys manage to power 10393 with 3.3V directly (Todd asked about this recently)? In this case you can check the current. On Thu, Feb 22, 2018 at 9:44 AM, Mohamed Morsy <mmo...@redzone.com> wrote: > No it doesn't print anything at all. I can't connect via ssh. Is it > possible the baud rate isn't 115200? > > On Thu, Feb 22, 2018 at 11:35 AM, Oleg <support-list@support.elphel.com> > wrote: > >> Hi, >> >> Is it printing anything when you power on? >> Can you connect to the camera via ssh? >> >> Oleg >> >> On Thu, Feb 22, 2018 at 7:38 AM, Mohamed Morsy <mmo...@redzone.com> >> wrote: >> >>> Hello Oleg, >>> >>> I was able to fix one of my elphels yesterday using the methods you >>> suggested. Now I'm trying to do the same with my other one but when I open >>> the minicom console I can't type anything. Do you have any idea how to fix >>> this? >>> >>> Thanks, >>> >>> Mohamed >>> >>> On Wed, Feb 21, 2018 at 4:06 PM, Mohamed Morsy <mmo...@redzone.com> >>> wrote: >>> >>>> Thank you very much >>>> >>>> On Wed, Feb 21, 2018 at 3:53 PM, Oleg <support-list@support.elphel.com> >>>> wrote: >>>> >>>>> Alright. Since you're modifying files on flash rootfs, don't forget to >>>>> run: >>>>> >>>>>> root@elphel393:~# overlay_sync 1 >>>>>> root@elphel393:~# shutdown -hP now >>>>> >>>>> >>>>> >>>>> On Wed, Feb 21, 2018 at 1:50 PM, Mohamed Morsy <mmo...@redzone.com> >>>>> wrote: >>>>> >>>>>> actually i think i found my answer. >>>>>> >>>>>> Thanks! >>>>>> >>>>>> On Wed, Feb 21, 2018 at 3:44 PM, Mohamed Morsy <mmo...@redzone.com> >>>>>> wrote: >>>>>> >>>>>>> ok so the ip was 192.168.0.9. I changed it and it works. But when i >>>>>>> power it off and restart it, it goes back to 192.168.0.9. Do i have to >>>>>>> save >>>>>>> it somehow? >>>>>>> >>>>>>> On Wed, Feb 21, 2018 at 3:35 PM, Oleg <support-list@support.elphel.c >>>>>>> om> wrote: >>>>>>> >>>>>>>> It's 'root' >>>>>>>> >>>>>>>> On Wed, Feb 21, 2018 at 1:32 PM, Mohamed Morsy <mmo...@redzone.com> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> It's asking for a login and password. I know the password is pass >>>>>>>>> but what is the login? >>>>>>>>> >>>>>>>>> On Wed, Feb 21, 2018 at 3:12 PM, Oleg < >>>>>>>>> support-list@support.elphel.com> wrote: >>>>>>>>> >>>>>>>>>> Get the serial console up and type: >>>>>>>>>> >>>>>>>>>>> root@elphel393:~# ifconfig >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Wed, Feb 21, 2018 at 1:08 PM, Mohamed Morsy < >>>>>>>>>> mmo...@redzone.com> wrote: >>>>>>>>>> >>>>>>>>>>> Is it possible the ip address of the elphel changed. If so, how >>>>>>>>>>> do i find it? >>>>>>>>>>> >>>>>>>>>>> -Mohamed >>>>>>>>>>> >>>>>>>>>>> On Wed, Feb 21, 2018 at 1:52 PM, Mohamed Morsy < >>>>>>>>>>> mmo...@redzone.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> I have not used the mircro usb port. The default ip address has >>>>>>>>>>>> been changed to 10.4.1.4. >>>>>>>>>>>> >>>>>>>>>>>&
Re: [Elphel-support] Elphel 393 Question
Hi, Is it printing anything when you power on? Can you connect to the camera via ssh? Oleg On Thu, Feb 22, 2018 at 7:38 AM, Mohamed Morsy <mmo...@redzone.com> wrote: > Hello Oleg, > > I was able to fix one of my elphels yesterday using the methods you > suggested. Now I'm trying to do the same with my other one but when I open > the minicom console I can't type anything. Do you have any idea how to fix > this? > > Thanks, > > Mohamed > > On Wed, Feb 21, 2018 at 4:06 PM, Mohamed Morsy <mmo...@redzone.com> wrote: > >> Thank you very much >> >> On Wed, Feb 21, 2018 at 3:53 PM, Oleg <support-list@support.elphel.com> >> wrote: >> >>> Alright. Since you're modifying files on flash rootfs, don't forget to >>> run: >>> >>>> root@elphel393:~# overlay_sync 1 >>>> root@elphel393:~# shutdown -hP now >>> >>> >>> >>> On Wed, Feb 21, 2018 at 1:50 PM, Mohamed Morsy <mmo...@redzone.com> >>> wrote: >>> >>>> actually i think i found my answer. >>>> >>>> Thanks! >>>> >>>> On Wed, Feb 21, 2018 at 3:44 PM, Mohamed Morsy <mmo...@redzone.com> >>>> wrote: >>>> >>>>> ok so the ip was 192.168.0.9. I changed it and it works. But when i >>>>> power it off and restart it, it goes back to 192.168.0.9. Do i have to >>>>> save >>>>> it somehow? >>>>> >>>>> On Wed, Feb 21, 2018 at 3:35 PM, Oleg <support-list@support.elphel.com >>>>> > wrote: >>>>> >>>>>> It's 'root' >>>>>> >>>>>> On Wed, Feb 21, 2018 at 1:32 PM, Mohamed Morsy <mmo...@redzone.com> >>>>>> wrote: >>>>>> >>>>>>> It's asking for a login and password. I know the password is pass >>>>>>> but what is the login? >>>>>>> >>>>>>> On Wed, Feb 21, 2018 at 3:12 PM, Oleg <support-list@support.elphel.c >>>>>>> om> wrote: >>>>>>> >>>>>>>> Get the serial console up and type: >>>>>>>> >>>>>>>>> root@elphel393:~# ifconfig >>>>>>>> >>>>>>>> >>>>>>>> On Wed, Feb 21, 2018 at 1:08 PM, Mohamed Morsy <mmo...@redzone.com> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Is it possible the ip address of the elphel changed. If so, how do >>>>>>>>> i find it? >>>>>>>>> >>>>>>>>> -Mohamed >>>>>>>>> >>>>>>>>> On Wed, Feb 21, 2018 at 1:52 PM, Mohamed Morsy <mmo...@redzone.com >>>>>>>>> > wrote: >>>>>>>>> >>>>>>>>>> I have not used the mircro usb port. The default ip address has >>>>>>>>>> been changed to 10.4.1.4. >>>>>>>>>> >>>>>>>>>> -Mohamed >>>>>>>>>> >>>>>>>>>> On Wed, Feb 21, 2018 at 1:34 PM, Oleg < >>>>>>>>>> support-list@support.elphel.com> wrote: >>>>>>>>>> >>>>>>>>>>> Hi Mohamed, >>>>>>>>>>> >>>>>>>>>>> 10.4.1.4 is that elphel's ip. >>>>>>>>>>>> Do you know how to resolve this issue? >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> The default IP is 192.168.0.9 >>>>>>>>>>> On the 10393 there's a micro USB port - this is serial console: >>>>>>>>>>> >>>>>>>>>>>> https://wiki.elphel.com/wiki/Tmp_manual > *serial console >>>>>>>>>>>> access*. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Do you use it? See any bootlog when power on? >>>>>>>>>>> >>>>>>>>>>> Todd was changing the default IP addresses like this: >>>>>>>>>>> https://wiki.elphel.com/wiki/Tmp_manual > >>>>>>>>>>> *Change_default_ip_address* >>>>>>>>>>
Re: [Elphel-support] Elphel 393 Question
Alright. Since you're modifying files on flash rootfs, don't forget to run: > root@elphel393:~# overlay_sync 1 > root@elphel393:~# shutdown -hP now On Wed, Feb 21, 2018 at 1:50 PM, Mohamed Morsy <mmo...@redzone.com> wrote: > actually i think i found my answer. > > Thanks! > > On Wed, Feb 21, 2018 at 3:44 PM, Mohamed Morsy <mmo...@redzone.com> wrote: > >> ok so the ip was 192.168.0.9. I changed it and it works. But when i power >> it off and restart it, it goes back to 192.168.0.9. Do i have to save it >> somehow? >> >> On Wed, Feb 21, 2018 at 3:35 PM, Oleg <support-list@support.elphel.com> >> wrote: >> >>> It's 'root' >>> >>> On Wed, Feb 21, 2018 at 1:32 PM, Mohamed Morsy <mmo...@redzone.com> >>> wrote: >>> >>>> It's asking for a login and password. I know the password is pass but >>>> what is the login? >>>> >>>> On Wed, Feb 21, 2018 at 3:12 PM, Oleg <support-list@support.elphel.com> >>>> wrote: >>>> >>>>> Get the serial console up and type: >>>>> >>>>>> root@elphel393:~# ifconfig >>>>> >>>>> >>>>> On Wed, Feb 21, 2018 at 1:08 PM, Mohamed Morsy <mmo...@redzone.com> >>>>> wrote: >>>>> >>>>>> Is it possible the ip address of the elphel changed. If so, how do i >>>>>> find it? >>>>>> >>>>>> -Mohamed >>>>>> >>>>>> On Wed, Feb 21, 2018 at 1:52 PM, Mohamed Morsy <mmo...@redzone.com> >>>>>> wrote: >>>>>> >>>>>>> I have not used the mircro usb port. The default ip address has been >>>>>>> changed to 10.4.1.4. >>>>>>> >>>>>>> -Mohamed >>>>>>> >>>>>>> On Wed, Feb 21, 2018 at 1:34 PM, Oleg <support-list@support.elphel.c >>>>>>> om> wrote: >>>>>>> >>>>>>>> Hi Mohamed, >>>>>>>> >>>>>>>> 10.4.1.4 is that elphel's ip. >>>>>>>>> Do you know how to resolve this issue? >>>>>>>> >>>>>>>> >>>>>>>> The default IP is 192.168.0.9 >>>>>>>> On the 10393 there's a micro USB port - this is serial console: >>>>>>>> >>>>>>>>> https://wiki.elphel.com/wiki/Tmp_manual > *serial console access*. >>>>>>>> >>>>>>>> >>>>>>>> Do you use it? See any bootlog when power on? >>>>>>>> >>>>>>>> Todd was changing the default IP addresses like this: >>>>>>>> https://wiki.elphel.com/wiki/Tmp_manual > >>>>>>>> *Change_default_ip_address* >>>>>>>> >>>>>>>> Regards, >>>>>>>> Oleg >>>>>>>> >>>>>>>> On Wed, Feb 21, 2018 at 11:18 AM, Mohamed Morsy <mmo...@redzone.com >>>>>>>> > wrote: >>>>>>>> >>>>>>>>> Hello Oleg, >>>>>>>>> >>>>>>>>> I was having some difficulties with my linux computer so I hold >>>>>>>>> off on this. I followed your instructions and I increased the php >>>>>>>>> upload >>>>>>>>> limit and I was able to upload rootfs. I'm still having some issues. >>>>>>>>> Here's >>>>>>>>> what I've done: >>>>>>>>> 1. Put recovery card in elphel >>>>>>>>> 2. Went to http://camera-ip-address/update_software.html and >>>>>>>>> flashed it from NAND folder >>>>>>>>> 3. Powered off elphel. >>>>>>>>> 4. Removed card >>>>>>>>> 5. Powered on elphel >>>>>>>>> >>>>>>>>> Now the connection is not working. In my terminal I typed arp and >>>>>>>>> i got this result >>>>>>>>> >>>>>>>>> Address HWtypeHWaddress >>>>>>>>> 10.4.1.4 (incomplete) >>>>>>>>> >>>>>>>>> 10.4.1.4 is tha
Re: [Elphel-support] Elphel 393 Question
It's 'root' On Wed, Feb 21, 2018 at 1:32 PM, Mohamed Morsy <mmo...@redzone.com> wrote: > It's asking for a login and password. I know the password is pass but what > is the login? > > On Wed, Feb 21, 2018 at 3:12 PM, Oleg <support-list@support.elphel.com> > wrote: > >> Get the serial console up and type: >> >>> root@elphel393:~# ifconfig >> >> >> On Wed, Feb 21, 2018 at 1:08 PM, Mohamed Morsy <mmo...@redzone.com> >> wrote: >> >>> Is it possible the ip address of the elphel changed. If so, how do i >>> find it? >>> >>> -Mohamed >>> >>> On Wed, Feb 21, 2018 at 1:52 PM, Mohamed Morsy <mmo...@redzone.com> >>> wrote: >>> >>>> I have not used the mircro usb port. The default ip address has been >>>> changed to 10.4.1.4. >>>> >>>> -Mohamed >>>> >>>> On Wed, Feb 21, 2018 at 1:34 PM, Oleg <support-list@support.elphel.com> >>>> wrote: >>>> >>>>> Hi Mohamed, >>>>> >>>>> 10.4.1.4 is that elphel's ip. >>>>>> Do you know how to resolve this issue? >>>>> >>>>> >>>>> The default IP is 192.168.0.9 >>>>> On the 10393 there's a micro USB port - this is serial console: >>>>> >>>>>> https://wiki.elphel.com/wiki/Tmp_manual > *serial console access*. >>>>> >>>>> >>>>> Do you use it? See any bootlog when power on? >>>>> >>>>> Todd was changing the default IP addresses like this: >>>>> https://wiki.elphel.com/wiki/Tmp_manual > *Change_default_ip_address* >>>>> >>>>> Regards, >>>>> Oleg >>>>> >>>>> On Wed, Feb 21, 2018 at 11:18 AM, Mohamed Morsy <mmo...@redzone.com> >>>>> wrote: >>>>> >>>>>> Hello Oleg, >>>>>> >>>>>> I was having some difficulties with my linux computer so I hold off >>>>>> on this. I followed your instructions and I increased the php upload >>>>>> limit >>>>>> and I was able to upload rootfs. I'm still having some issues. Here's >>>>>> what >>>>>> I've done: >>>>>> 1. Put recovery card in elphel >>>>>> 2. Went to http://camera-ip-address/update_software.html and >>>>>> flashed it from NAND folder >>>>>> 3. Powered off elphel. >>>>>> 4. Removed card >>>>>> 5. Powered on elphel >>>>>> >>>>>> Now the connection is not working. In my terminal I typed arp and i >>>>>> got this result >>>>>> >>>>>> Address HWtypeHWaddress >>>>>> 10.4.1.4 (incomplete) >>>>>> >>>>>> 10.4.1.4 is that elphel's ip. >>>>>> >>>>>> Do you know how to resolve this issue? >>>>>> >>>>>> Thanks, >>>>>> >>>>>> Mohamed Morsy >>>>>> >>>>>> On Tue, Feb 20, 2018 at 12:49 PM, Oleg <support-list@support.elphel.c >>>>>> om> wrote: >>>>>> >>>>>>> Hi Mohamed, >>>>>>> >>>>>>> >>>>>>>> However, I'm still having the same problem. On one of my elphels, >>>>>>>> when I use the recovery card it works fine but when I remove the card >>>>>>>> the >>>>>>>> feed is very laggy. Do you know what the issue is? >>>>>>> >>>>>>> It's hard to say without seeing the actual bootlog. If you boot from >>>>>>> recovery card, uploaded and flashed *boot.bin*, *u-boot-dtb.img*, >>>>>>> *devicetree.dtb* and *uImage*, but not rootfs.ubi - I would expect >>>>>>> some kind of "kernel panic" on any of the boards. >>>>>>> >>>>>>> >>>>>>>> Also, when I uploaded the files to ipaddress/update_software.html >>>>>>>> the rootf file would not upload. I don't know if that is a problem. >>>>>>> >>>>>>> The Note in my previous letter addresses this problem - the upload >>>>>>> limit in php on the recovery card. There are 3
Re: [Elphel-support] Elphel 393 Question
Get the serial console up and type: > root@elphel393:~# ifconfig On Wed, Feb 21, 2018 at 1:08 PM, Mohamed Morsy <mmo...@redzone.com> wrote: > Is it possible the ip address of the elphel changed. If so, how do i find > it? > > -Mohamed > > On Wed, Feb 21, 2018 at 1:52 PM, Mohamed Morsy <mmo...@redzone.com> wrote: > >> I have not used the mircro usb port. The default ip address has been >> changed to 10.4.1.4. >> >> -Mohamed >> >> On Wed, Feb 21, 2018 at 1:34 PM, Oleg <support-list@support.elphel.com> >> wrote: >> >>> Hi Mohamed, >>> >>> 10.4.1.4 is that elphel's ip. >>>> Do you know how to resolve this issue? >>> >>> >>> The default IP is 192.168.0.9 >>> On the 10393 there's a micro USB port - this is serial console: >>> >>>> https://wiki.elphel.com/wiki/Tmp_manual > *serial console access*. >>> >>> >>> Do you use it? See any bootlog when power on? >>> >>> Todd was changing the default IP addresses like this: >>> https://wiki.elphel.com/wiki/Tmp_manual > *Change_default_ip_address* >>> >>> Regards, >>> Oleg >>> >>> On Wed, Feb 21, 2018 at 11:18 AM, Mohamed Morsy <mmo...@redzone.com> >>> wrote: >>> >>>> Hello Oleg, >>>> >>>> I was having some difficulties with my linux computer so I hold off on >>>> this. I followed your instructions and I increased the php upload limit and >>>> I was able to upload rootfs. I'm still having some issues. Here's what I've >>>> done: >>>> 1. Put recovery card in elphel >>>> 2. Went to http://camera-ip-address/update_software.html and flashed >>>> it from NAND folder >>>> 3. Powered off elphel. >>>> 4. Removed card >>>> 5. Powered on elphel >>>> >>>> Now the connection is not working. In my terminal I typed arp and i got >>>> this result >>>> >>>> Address HWtypeHWaddress >>>> 10.4.1.4 (incomplete) >>>> >>>> 10.4.1.4 is that elphel's ip. >>>> >>>> Do you know how to resolve this issue? >>>> >>>> Thanks, >>>> >>>> Mohamed Morsy >>>> >>>> On Tue, Feb 20, 2018 at 12:49 PM, Oleg <support-list@support.elphel.com >>>> > wrote: >>>> >>>>> Hi Mohamed, >>>>> >>>>> >>>>>> However, I'm still having the same problem. On one of my elphels, >>>>>> when I use the recovery card it works fine but when I remove the card the >>>>>> feed is very laggy. Do you know what the issue is? >>>>> >>>>> It's hard to say without seeing the actual bootlog. If you boot from >>>>> recovery card, uploaded and flashed *boot.bin*, *u-boot-dtb.img*, >>>>> *devicetree.dtb* and *uImage*, but not rootfs.ubi - I would expect >>>>> some kind of "kernel panic" on any of the boards. >>>>> >>>>> >>>>>> Also, when I uploaded the files to ipaddress/update_software.html the >>>>>> rootf file would not upload. I don't know if that is a problem. >>>>> >>>>> The Note in my previous letter addresses this problem - the upload >>>>> limit in php on the recovery card. There are 3 options: >>>>> 1. Copy rootfs.ubi manually >>>>> >>>>>- http://camera-ip/update_software.html >>>>>- upload all files except rootfs.ubi >>>>>- from PC terminal window: >>>>> >>>>> ...$ scp rootfs.ubi root@camera-ip:/var/volatile/html/update/ >>>>> >>>>> >>>>>- go back to http://camera-ip/update_software.html - hit 'verify' >>>>>and you should see rootfs in the list >>>>> >>>>> 2. Increase php upload limit of the recovery image on the card >>>>> >>>>> 2a. when boot from the recovery card: >>>>> >>>>>- boot from the recovery card >>>>>- In the browser: http://camera-ip/phpinfo.php - find: >>>>>*post_max_size* and *upload_max_filesize *- they are 128M probably. >>>>>- from PC terminal window: >>>>> >>>>> ...$ ssh root@camera-ip >>>>> >>>>> >>>&g
Re: [Elphel-support] Elphel 393 Question
Hi Mohamed, 10.4.1.4 is that elphel's ip. > Do you know how to resolve this issue? The default IP is 192.168.0.9 On the 10393 there's a micro USB port - this is serial console: > https://wiki.elphel.com/wiki/Tmp_manual > *serial console access*. Do you use it? See any bootlog when power on? Todd was changing the default IP addresses like this: https://wiki.elphel.com/wiki/Tmp_manual > *Change_default_ip_address* Regards, Oleg On Wed, Feb 21, 2018 at 11:18 AM, Mohamed Morsy <mmo...@redzone.com> wrote: > Hello Oleg, > > I was having some difficulties with my linux computer so I hold off on > this. I followed your instructions and I increased the php upload limit and > I was able to upload rootfs. I'm still having some issues. Here's what I've > done: > 1. Put recovery card in elphel > 2. Went to http://camera-ip-address/update_software.html and flashed it > from NAND folder > 3. Powered off elphel. > 4. Removed card > 5. Powered on elphel > > Now the connection is not working. In my terminal I typed arp and i got > this result > > Address HWtypeHWaddress > 10.4.1.4 (incomplete) > > 10.4.1.4 is that elphel's ip. > > Do you know how to resolve this issue? > > Thanks, > > Mohamed Morsy > > On Tue, Feb 20, 2018 at 12:49 PM, Oleg <support-list@support.elphel.com> > wrote: > >> Hi Mohamed, >> >> >>> However, I'm still having the same problem. On one of my elphels, when I >>> use the recovery card it works fine but when I remove the card the feed is >>> very laggy. Do you know what the issue is? >> >> It's hard to say without seeing the actual bootlog. If you boot from >> recovery card, uploaded and flashed *boot.bin*, *u-boot-dtb.img*, >> *devicetree.dtb* and *uImage*, but not rootfs.ubi - I would expect some >> kind of "kernel panic" on any of the boards. >> >> >>> Also, when I uploaded the files to ipaddress/update_software.html the >>> rootf file would not upload. I don't know if that is a problem. >> >> The Note in my previous letter addresses this problem - the upload limit >> in php on the recovery card. There are 3 options: >> 1. Copy rootfs.ubi manually >> >>- http://camera-ip/update_software.html >>- upload all files except rootfs.ubi >>- from PC terminal window: >> >> ...$ scp rootfs.ubi root@camera-ip:/var/volatile/html/update/ >> >> >>- go back to http://camera-ip/update_software.html - hit 'verify' and >>you should see rootfs in the list >> >> 2. Increase php upload limit of the recovery image on the card >> >> 2a. when boot from the recovery card: >> >>- boot from the recovery card >>- In the browser: http://camera-ip/phpinfo.php - find: *post_max_size* >>and *upload_max_filesize *- they are 128M probably. >>- from PC terminal window: >> >> ...$ ssh root@camera-ip >> >> >>- Edit the /etc/php/php.ini - you will see that the limit is less >>than rootfs size - increase it so it will read: >> >> upload_max_filesize = 512M >>> >>> >>> >>> post_max_size = 512M >> >> >>- sync command just makes sure changes are stored on the card. >> >> root@elphel393:~# sync >> >> >>- restart web server (or reboot) >> >> root@elphel393:~# /etc/init.d/lighttpd restart >> >> >>- In the browser: http://camera-ip/phpinfo.php - check if those >>variables have changed to 512. >>- In the browser: http://camera-ip/update_software.html - upload >>rootfs, and other files as well >> >> 2b. If you have a linux os and a usb card reader - insert in PC, mount >> rootfs partition and edit /mountpoint/etc/php/php.ini as in 2a. >> >> 3. Update recovery card. This option requires linux os and a usb card >> reader... and a few programs installed: parted, kpartx >> >>- insert the card - check with dmesg the device name, you will see >>something like this: >> >> [83470.681265] sd 6:0:0:0: [sdb] 7806976 512-byte logical blocks: (4.00 >>> GB/3.72 GiB) >>> [83470.686369] *sdb*: sdb1 sdb2 >> >> If the card is discovered by PC as *mmcblk0* then the script will not >> work - as I didn't cover this case. >> >>- Open konsole, using 'cd' navigate to write_bootable_mmc.py in the >>unpacked firmware image (elphel393_20180130/mmc/) >>- ...$ sudo ./write_bootable_mmc.py */dev/sdb* (sdb as reported by >>dmesg - this is impor
Re: [Elphel-support] Elphel 393 Question
Hi Mohamed, > However, I'm still having the same problem. On one of my elphels, when I > use the recovery card it works fine but when I remove the card the feed is > very laggy. Do you know what the issue is? It's hard to say without seeing the actual bootlog. If you boot from recovery card, uploaded and flashed *boot.bin*, *u-boot-dtb.img*, *devicetree.dtb* and *uImage*, but not rootfs.ubi - I would expect some kind of "kernel panic" on any of the boards. > Also, when I uploaded the files to ipaddress/update_software.html the > rootf file would not upload. I don't know if that is a problem. The Note in my previous letter addresses this problem - the upload limit in php on the recovery card. There are 3 options: 1. Copy rootfs.ubi manually - http://camera-ip/update_software.html - upload all files except rootfs.ubi - from PC terminal window: ...$ scp rootfs.ubi root@camera-ip:/var/volatile/html/update/ - go back to http://camera-ip/update_software.html - hit 'verify' and you should see rootfs in the list 2. Increase php upload limit of the recovery image on the card 2a. when boot from the recovery card: - boot from the recovery card - In the browser: http://camera-ip/phpinfo.php - find: *post_max_size* and *upload_max_filesize *- they are 128M probably. - from PC terminal window: ...$ ssh root@camera-ip - Edit the /etc/php/php.ini - you will see that the limit is less than rootfs size - increase it so it will read: upload_max_filesize = 512M > > > > post_max_size = 512M - sync command just makes sure changes are stored on the card. root@elphel393:~# sync - restart web server (or reboot) root@elphel393:~# /etc/init.d/lighttpd restart - In the browser: http://camera-ip/phpinfo.php - check if those variables have changed to 512. - In the browser: http://camera-ip/update_software.html - upload rootfs, and other files as well 2b. If you have a linux os and a usb card reader - insert in PC, mount rootfs partition and edit /mountpoint/etc/php/php.ini as in 2a. 3. Update recovery card. This option requires linux os and a usb card reader... and a few programs installed: parted, kpartx - insert the card - check with dmesg the device name, you will see something like this: [83470.681265] sd 6:0:0:0: [sdb] 7806976 512-byte logical blocks: (4.00 > GB/3.72 GiB) > [83470.686369] *sdb*: sdb1 sdb2 If the card is discovered by PC as *mmcblk0* then the script will not work - as I didn't cover this case. - Open konsole, using 'cd' navigate to write_bootable_mmc.py in the unpacked firmware image (elphel393_20180130/mmc/) - ...$ sudo ./write_bootable_mmc.py */dev/sdb* (sdb as reported by dmesg - this is important) - After the script is done - boot this from this card. Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 <(801)%20783-> Elphel, Inc. On Feb 20, 2018 8:20 AM, "Mohamed Morsy" <mmo...@redzone.com> wrote: Hi Oleg, Thank you for your help. However, I'm still having the same problem. On one of my elphels, when I use the recovery card it works fine but when I remove the card the feed is very laggy. Do you know what the issue is? Also, when I uploaded the files to ipaddress/update_software.html the rootf file would not upload. I don't know if that is a problem. Thanks, Mohamed On Mon, Feb 19, 2018 at 6:27 PM, Oleg <support-list@support.elphel.com> wrote: > Hi, > > I have 2 Elphel 393 boards and I believe both of their internal flash are >> corrupt or old. I am trying to update them. Do you have a link for the >> files or any instructions on how to do so? >> > > Before updating: > How are you trying to update them? What image do you use? > > Update instructions: > 1. The latest is 20180130 - download and unpack archive from here: > https://community.elphel.com/files/393/20180130/ (a list of firmware > images can be found here > <https://wiki.elphel.com/wiki/Tmp_manual#Firmware_images>) > 2. Inside there's readme.md with instructions and images for SD card and > the internal flash. > > Note: if you have an old recovery card you will probably need to create a > new one as rootfs grew a bit bigger than php's upload limit. There's a > script (*write_bootable_mmc.py*) that will partition the card - it's > linux only. > Alternatively you can increase the limit: > > >- boot from the recovery card (default ip address is 192.168.0.9 - >change with ifconfig if needed) >- ssh root@camera-ip-address >- (using nano or vi) edit /etc/php/php.ini: > > upload_max_filesize = 512M >> post_max_size = 512M > > >- save, restart lighttpd or reboot, then 3. > > 3. Once boot from a recovery card: > >- go to http://camera-ip-address/update_software.html >- upload all files from
Re: [Elphel-support] Elphel 393 Question
Hi, I have 2 Elphel 393 boards and I believe both of their internal flash are > corrupt or old. I am trying to update them. Do you have a link for the > files or any instructions on how to do so? > Before updating: How are you trying to update them? What image do you use? Update instructions: 1. The latest is 20180130 - download and unpack archive from here: https://community.elphel.com/files/393/20180130/ (a list of firmware images can be found here <https://wiki.elphel.com/wiki/Tmp_manual#Firmware_images>) 2. Inside there's readme.md with instructions and images for SD card and the internal flash. Note: if you have an old recovery card you will probably need to create a new one as rootfs grew a bit bigger than php's upload limit. There's a script (*write_bootable_mmc.py*) that will partition the card - it's linux only. Alternatively you can increase the limit: - boot from the recovery card (default ip address is 192.168.0.9 - change with ifconfig if needed) - ssh root@camera-ip-address - (using nano or vi) edit /etc/php/php.ini: upload_max_filesize = 512M > post_max_size = 512M - save, restart lighttpd or reboot, then 3. 3. Once boot from a recovery card: - go to http://camera-ip-address/update_software.html - upload all files from *nand/* folder - hit flash, wait until done - power off, remove card, power on Let me know if you have any further questions. Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] Sensor Synchronization and Memory
Fabjan, > I already reviewed and tested the driver and it works good. For converting > the raw data we use OpenCV with numpy. Feel free to copy the snippet below > to your wiki page. If there are any problems oder open questions I will > write you an E-Mail. > Thanks, I added your code to that wiki page. I made a few changes which are now available at https://community.elphel.com/files/393/20180118/ Raw image info is accessible in sysfs. Examples are in demo scripts: a. /usr/bin/raw.py - demo for mmap b. http://192.168.0.9/raw.php - demo for getting images via http requests The scripts do not interrupt triggering - so images may not be in sync (different frame numbers). Also, note: if exposure ever gets longer than the trigger period the frame numbers will get different. More info about the scripts: https://wiki.elphel.com/wiki/Working_with_raw_image_data#Capturing_and_downloading So, do you transfer raw images over network? I can add a small header to the data streamed by raw.php. Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 <(801)%20783-> Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] Sensor Synchronization and Memory
Hi, I modified the videomem driver so it is able to get raw pixels, the firmware is available here <https://community.elphel.com/files/393/20180116/> - built in rocko branch. So, the basic functionality is implemented: read and mmap. There are a few more things to be done: * in the fpga memory the buffer for pixel data is 2-frames long (for each port) - right now there's no way to learn which image to start from in that buffer, based on the absolute frame number or anything else. Once started it's easy to follow, of course. Alternatively, those memory channels and counters can be reset, so the start would always be in the beginning - I need to test it. * finish a demo script with setting proper sizes, frame waiting, and getting frames from 2 channels (only a single port can be accessed for raw data at a time) * test 16bpp *demo:* > root@elphel393:~# raw.py *instructions:* > https://wiki.elphel.com/wiki/Working_with_raw_image_data#Downloading Let me know if you have any comments/wishes. Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] 答复: 答复: 答复: 答复: 答复: 答复: 答复: 答复: 答复: 答复: 答复: Re: Quote for 1 NC393-Stereo camera
Hi, If you still would like to use SD card (USB drive will work as well) then: 1. recorder program: https://wiki.elphel.com/wiki/Tmp_manual#Record a. If run from the command line then *prefix* parameter can point to any location - it includes absolute path. b. If setup from web ui - https://wiki.elphel.com/wiki/ Using_camogm_with_Elphel393_camera#Normal_recording uncheck fast recording and provide "Directory" ending with / The program can store images in separate files or a single *.mov (better because of less files in a folder) which can be split later. *.mov size is limited by a few settings - after limit is reached a new file is started - so the recording is not interrupted. 2. Example on how you can format an SD card (I'd go with EXT4): a. https://wiki.elphel.com/wiki/Format_SSD_MMC#MMC b. If it doesn't automount - automount rules can be added to udev config files at /etc/udev/rules.d/ 3. There's a way to start recording automatically. Let me know if you have any further questions. Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 <(801)%20783-> Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] 答复: 答复: 答复: 答复: 答复: 答复: 答复: 答复: 答复: 答复: Re: Quote for 1 NC393-Stereo camera
Hello, Here's an updated firmware image: https://community.elphel.com/files/393/20180109/ The instructions are in the readme.md in the zip archive. Let me know if you have any questions. To update camera's NAND flash you will need to boot from the recovery uSD card. Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] 答复: 答复: 答复: 答复: 答复: Re: Quote for 1 NC393-Stereo camera
Hello, 1)How could I get the raw data of camera. Because when I got the rgb > data from multipart jpeg stream, the image had some color blocks if I > amplified eight times. I thought it could be caused by image conversion > compression.(please look at the attachments). You can switch to JP4 format <https://wiki.elphel.com/wiki/JP4> - it's close to raw. What I see in the attached images is they have different white balance. And also there are overexposed areas which can affect the correct balance. The white balance is run independently for each sensor - you can try to set it so the images look the same and then turn off for both sensors: a) open the web interface for each sensor <https://wiki.elphel.com/wiki/Tmp_manual#Web_user_interface_.28camvc.29> - click on the green circle OR b) set WB_EN=0 (also for both channels) in parameters <https://wiki.elphel.com/wiki/Tmp_manual#Change_parameters> - if you change it through a table (http://192.168.0.9 > Parameter Editor > select whiteBalance > View/Edit Current <http://192.168.0.9/parsedit.php?sensor_port=2=Parameters+for+groups:+whiteBalance+_R_G_GB_B_THRESH_PERIOD_MASK_EN_WHITELEV_WHITEFRAC_MAXWHITE_SCALE_R_SCALE_GB_SCALE_B_MIN_MAX_CTRL_STEP_GAIN_ENABLE>) then there is a broadcast mask to set the parameter for all sensors at the same time - set it to F. if I amplified eight times. What are the gains and exposure for each sensor? 2)The camera temperature has risen quickly, and I could not capture > images. Because it was so slowly to run the video when the camera had been > opened for four hours. But If I closed the camera and the temperature > dropped down, the video was showed normally. What is the temperature? http://192.168.0.9 > Temperature monitor If it's around 70-80 it's ok (at 90 degrees the camera is forced to shut down) Also, the camera should reach the steady temperature pretty much in the the first 30-60 mins. - what is the image quality? - what are the exposure times? you can try limiting exposure time. The default fps is 10 - so, It will get slow if exposure times are >100ms. - is the camera and the pc the only devices in the network? camera connected directly to PC vie cable? - connect to the camera via ssh and check cpu load: > $ ssh root@192.168.0.9 > root@elphel393:~# htop then click on CPU% table header. - your PC's cpu load? If you are watching from the browser - it might not be able to handle the streams as well. Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 <(801)%20783-> Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] problem retreiving raw partition data
Hello Jorick,
> Currently we want to retreive the footage of our elphel NC393. When
> running the script "./int_ssd_download.py", we see the disk getting
> unmounted. But my thinkpad doesn't see the drive. Maybe it's been fixed in
> the later firmware but we like to get the data save first, before we
> upgrade the firmware. What could be the problem?
>
Most likely */dev/disk/by-id/* contents are not what the script expects (on
Kubuntu 16.04).
It calls a few commands filtering device list by the disk ID.
~$ ls /dev/disk/by-id/ -all | grep ...
> ~$ sudo blkid | grep ...
...
It can be a bug in the script - which I will check.
> The thinkpad notebook has an unpowered esata I believe, but I think the
> ssd is powered internally?
>
> <root@192.168.0.9>
>
> Yes, SSD is powered internally.
Try the following (manual instructions):
1. run "./int_ssd_download.py", do not "Press Enter", then from another
terminal:
2. check your pc's dmesg or if it detected the first partition.
2a. if SSD is detected. Let's say it appeared as
> *[ 864.532399] sdc: sdc1 sdc2 *
The raw partition name was read from the camera and reported as "...-part2"
=> /dev/sdc2
Then run *dd* to copy the data from the partition.
> $ dd if=/dev/sdc2 of=somefile.img bs=100M count=1 skip=0
This will copy 1 block of 100MB skipping 0 blocks.
Then try splitting it (extract_images.php)
2b. if it's not detected
> http://192.168.0.9/x393_vsc330x.php?state
It will display a connection table. The *"state"* row should be reporting
"active" for ESATA and SSD columns. if "LOS" - then I would try another PC.
More info (+ a screenshot of the table):
> https://wiki.elphel.com/wiki/Sata_multiplexer_10389
Best regards,
Oleg Dzhimiev
Electronics Engineer
phone: +1 801 783 x124
Elphel, Inc.
> root@192.168.0.9: connection ok
> root@192.168.0.9: Enabled connection: internal SSD <-> Camera
> root@192.168.0.9: raw partition name: Crucial_CT250MX200SSD6_
> 1531103B7285-part2
> umounting /dev/sda1
> root@192.168.0.9: Enabled connection: internal SSD <-> PC
> Connect camera (eSATA) to PC (eSATA/SATA). Press Enter to continue...
> Waiting for disks to show up:
> ['Crucial_CT250MX200SSD6_1531103B7285-part2']
> Waiting for disks to show up:
> ['Crucial_CT250MX200SSD6_1531103B7285-part2']
> PC: Error: Disks were not found:
> ['Crucial_CT250MX200SSD6_1531103B7285-part2']
>
> From the elphel dmesg
>
> [ 586.941027] ata1: exception Emask 0x10 SAct 0x0 SErr 0x9 action 0xe
> frozen
> [ 586.948183] ata1: irq_stat 0x0040, PHY RDY changed
> [ 586.953342] ata1: SError: { PHYRdyChg 10B8B }
> [ 586.957657] ata1: hard resetting link
> [ 587.728906] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> [ 587.735622] ata1.00: supports DRM functions and may not be fully
> accessible
> [ 587.744397] ata1.00: supports DRM functions and may not be fully
> accessible
> [ 587.752539] ata1.00: configured for UDMA/133
> [ 587.756730] ata1: EH complete
> [ 587.759918] ata1.00: Enabling discard_zeroes_data
> [ 589.751271] elphel-ahci 8000.elphel-ahci: removing Elphel AHCI
> driver
> [ 589.758068] ata1.00: disabled
> [ 589.763808] sd 0:0:0:0: [sda] Synchronizing SCSI cache
> [ 589.771170] sd 0:0:0:0: [sda] Synchronize Cache(10) failed: Result:
> hostbyte=0x04 driverbyte=0x00
> [ 589.780050] sd 0:0:0:0: [sda] Stopping disk
> [ 589.784362] sd 0:0:0:0: [sda] Start/Stop Unit failed: Result:
> hostbyte=0x04 driverbyte=0x00
> [ 862.005272] elphel-ahci 8000.elphel-ahci: AHCI driver loading is
> deferred. Load bitstream and write 1 into /sys/devices/soc0/amba@0/
> 8000.elphel-ahci/load_module to continue
> [ 864.038894] elphel-ahci 8000.elphel-ahci: probing Elphel AHCI driver
> [ 864.058897] elphel-ahci 8000.elphel-ahci: AHCI 0001.0301 1 slots 1
> ports 3 Gbps 0x1 impl platform mode
> [ 864.068471] elphel-ahci 8000.elphel-ahci: flags: only sxs
> [ 864.077415] scsi host1: elphel-ahci
> [ 864.081236] ata2: SATA max UDMA/133 mmio [mem 0x8000-0x8fff]
> port 0x100 irq 163
> [ 864.438887] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> [ 864.445486] ata2.00: supports DRM functions and may not be fully
> accessible
> [ 864.452393] ata2.00: ATA-10: Crucial_CT250MX200SSD6, MU02, max UDMA/133
> [ 864.458989] ata2.00: 488397168 sectors, multi 16: LBA48 NCQ (depth 0/32)
> [ 864.467280] ata2.00: supports DRM functions and may not be fully
> accessible
> [ 864.475512] ata2.00: configured for UDMA/133
> [ 864.480095] scsi 1:0:0:0: Direct-Access ATA Crucial_CT250MX2
> MU02 PQ: 0 ANSI: 5
> [ 864.489163] ata2.00: Enabling discard_zeroes_data
> [ 864.493934] sd 1:0:0:0: [sda] 488397168 512-by
Re: [Elphel-support] Fwd: Your message to Support-list awaits moderator approval
Hi, > Still getting the banned error: > Andrey added your email to the whitelist for posting messages but missed the ban list which blocked you from subscribing. Should be ok now. There was a record that was blocking all .eu addresses - I guess back in the days spam was coming from a few addresses and there was noone with .eu on the list. Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] video camera for drone project
Maria, We conducted a few tests to measure the live stream latency. Results: * Test images <https://community.elphel.com/pictures/10393_video_stream_latency/> * For 1080p - ~70ms from exposure to display (720p - ~50ms). So, having in mind 40ms (sensor readout + compression) - it takes about 30ms to transfer and display the stream (for the pc used in tests) Notes: * LAN: PC and camera only, 1GigE * Played rtsp and multipart jpeg streams * Used gstreamer - as it performed the fastest among other players/browsers. ** Chrome and Firefox seem to buffer at least 1 frame when displaying mjpeg stream = extra lag. Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] video camera for drone project
Hello, > This is an student project with the idea of developing a real time game > and for this reason we need a low latency and good quality video. Currently, for 1080p the latency is roughly 40ms - the camera needs to compress a single frame before sending it out over network. There's also network latency and time it takes for PC to display an image. There is room for improvement - reduce it down to ~0.7ms if one don't wait for the compressor to finish. This just needs the fpga modification. Answering your initial letter... > Communications: Wireless operating at 5 GHZ, with transmitter built-in or > external HDMI transmitter > to be processed /displayed in local computer. Range : >50 feet Available options would be: usb dongles (USB2.0): * https://www.amazon.com/Mailiya-AC600Mbps-Wireless-Adapter- Mini/dp/B01MYQW7IR/ref=sr_1_18?ie=UTF8=1497389691= 8-18=nano+router * https://www.amazon.com/dp/B06XRG9QDV?psc=1 There are more that are 2.4GHz of course. In terms of speed for 1080p@30fps 300Mbps should be enough Resolution Video: 1080p at 30 frames/sc > Yes > View angle: > 120 > Yes Image sensor's format is 1/2.5". Possible options (small lenses, M12x0.5 thread): * hfov=~135 : http://www.optics-online.com/OOL/DSL/DSL315.PDF, * hfov=~180 : http://www.optics-online.com/OOL/DSL/DSL227.PDF Note: for 1080p (full res = 2592x1936) the FoV is smaller. Power: Battery operated with duration of an hour before recharged Weight: < the minimum as possible < 1pound Do you have a video camera that we can use? NC393-DEV (12V) with a single SFE will be the lightest - 150-200g. The power consumption is 6-8W. The input voltage range is 9-36V. We recommend getting a 14.8V battery, 0.5-1Ah should be enough for 1 hour of operation. (Of course, if possible try to use a single battery for the whole system). Example (240g): https://www.dollarhobbyz.com/collections/batteries- 4s-14-8v-lipo/products/venom-lipo-battery-4s-1p-2100-mah- 20c-starter-box-15004 The total weight comes up to 1lb. Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. On 14 June 2017 at 16:28, Maria Gonzalez <margonza...@ucdavis.edu> wrote: > Thanks for the detailed answer covering the internal electronics. This is > an student project with the idea of developing a real time game and for > this reason we need a low latency and good quality video. The video will be > processed in the computer adding some additional elements which where we > will put our effort. The other elements such as drone, camera, > communications to the computer /google, we are hoping to purchase these > parts ready to be operational . > Sincerely, we do not know if our specifications are feasible to > materialize with existing ready to go equipment. > > Maria C. Gonzalez > > > On Tue, Jun 13, 2017 at 4:57 PM, Elphel Support < > support-list@support.elphel.com> wrote: > >> Hello Maria, >> >> The camera uses mt9p031 sensors, this datasheet >> http://www.onsemi.com/pub/Collateral/MT9P031-D.PDF lists some of the >> frame rate/resolution combinations - camera supports all what sensor can >> provide. >> With latency with default firmware camera sends acquired frame >> immediately after it is acquired - when the frame sync pulse comes from the >> sensor, it starts sending the previous frame. >> It is possible to reduce the latency even more, but that will require >> some software development and custom software on the receiving side as for >> sending standard files you need to know file size, and the file size is >> available only after the full frame is compressed. >> >> The FPGA code that acquires and compresses image frames has latency of 18 >> scan lines plus under 1000 pixels - this is the lag between the pixels >> acquired from the sensors and compressed data is stored in the system >> memory. So it is possible to send it not waiting for the full frame to be >> compressed. >> >> Oleg will reply you about the power and weight, but yes - it is possible. >> And with the same weight you can have up to 4 simultaneous sensors >> operating. >> >> Andrey >> >> >> On Tue, 13 Jun 2017 16:34:23 -0700 *Maria Gonzalez >> <margonza...@ucdavis.edu <margonza...@ucdavis.edu>>* wrote >> >> Hello >> >> We are looking for a camera with the following characteristics: >> >> *Desired Camera and Communications Specifications* >> >> *Communications*: Wireless operating at 5 GHZ, with transmitter built-in >> or external HDMI transmitter >> >> to be processed /displayed in local computer. >> >> *Resolution Video*: 1080p at 30 frames/sc >> >> * System* *Communic
Re: [Elphel-support] auto exposure on multi sensor setup & binning question.
Hi, Jorick, with the limited dynamic range of the small format sensors it is a > challenge to capture maximal data from the image, and there is no universal > fits-all set of autoexposure parameters. We probably need to create some > tutorial about it. Here are a few screenshots with gui and parameters you might need to control histogram window and the autoexposure program - https://wiki.elphel.com/wiki/Autoexposure > I could probably also modify the streamer to output a lower resolution. > h264/h265 support would be even better. The idea is to run the analytics > and streaming and only grab the interesting frames in raw from the circular > buffer. > How difficult would a color space conversion to YUV be on the elphel? > We're streaming so much the same color (green ;-) and this would save > bandwith, it would also be easier to change the brightness on parts of the > image. > JPEGs are YCbCr 4:2:0 encoded. There are a few other formats: https://wiki.elphel.com/wiki/JP4#Format_variations Most of the time we use JP4 to preserve pixel data, though it does not save bandwidth. I will look into 'jp4diff' - see if it still works and try to decode it. Will let you know. Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 <(801)%20783-> Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] elphel393 setup.py
Hi, Try: $ sudo apt-get install python-numpy It might be missing. Are you following this guide <https://wiki.elphel.com/wiki/Poky_2.0_manual>? Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] Python on 393
Hello Shashank, *We have recently moved git repositories to our own server - https://git.elphel.com <https://git.elphel.com>* Assuming you have followed our setup instuctions <https://wiki.elphel.com/wiki/Poky_2.0_manual#Setup> - *project path* will be related to the top project's root. Python scripts: 1. *init_elphel393.py* *10393 path*:* /etc/elphel393/* *Project path*: *elphel393/rootfs-elphel/elphel-init* *Description*: * run at boot by /etc/init.d/init_elphel393 with a few parameters defined in poky's local.conf * sets the ip address and netmask * initializes: ** temperature monitor: tempmon.py ** programs USB hub on 10389 (if there is one) ** starts image server (imgsrv, c app) for all detected ports ** starts autoexposure daemon (autoexposure, c app) ** default camera parameters - autocampars.php (results are stored in /etc/elphel393/autocampars[port#].xml) ** enables SATA switch multiplexing (x393sata.py(init) & x393sata_control.py(mux)) and loads SATA driver 1a. *tempmon.py* *10393 path*:* /usr/bin/* *Project path*: *elphel393/rootfs-elphel/elphel-apps-tempmon/* *Description*: temperature monitor 1b. python scripts related to SATA (and SATA module in fpga): *10393 path*: */usr/local/bin/* *Project path*: *elphel393/fpga-elphel/x393_sata/py393sata/* *Description*: there are a few scripts, the major one is x393sata.py - there are examples of usage in the end of the script. 2. Python scripts related to x393 fpga *10393 path*: */usr/local/bin/* *Project path*: *elphel393/fpga-elphel/x393/py393/* *Description*: * fpga: memory controller, rtc, gpio, compressor, AXI * Most of them are not used - but can be used for testing, some have examples inside. Don't know if you need it or already figured it out, the whole project sources structure in short: https://git.elphel.com/Elphel/elphel393/tree/master: 1. *setup.py*: * clones all the projects * rerun to update all repositories - then rebuild with bitbake * creates a working copy of projects-default.json - projects.json 2.* check_versions.py*: * ./check_versions.py root@192.168.0.9) * compares software versions on the 10393 vs current sources 3. *elphel393/meta/meta-elphel393/* - all of the recipes for the projects. * rootfs recipe with the list of included packages: *elphel393/meta/meta-elphel393/recipes-core/images/core-image-elphel393.bb <http://core-image-elphel393.bb>* All of the python packages are listed there. 4. Projects: The paths in the recipes point to the project sources which are cloned outside of poky structure - so "bitbake ... -c clean" does not remove the sources (we tried Quilt but it's not convenient). And so all the source repositories are in: ** elphel393/linux-elphel/ - *which is a kernel tree with our sources only - it is merged with the full kernel tree. * *elphel393/rootfs-elphel/ - *user applicatons projects and init scripts, matching resipes are found in *meta/meta-elphel393/recipes-core/* * *elphel393/fpga-elphel/ - *fpga projects, matching recipes are in *meta/meta-elphel393/recipes-core/* Some of the recipes for applications do not have sources in *elphel393/rootfs-elphel/* 5. The boot images are linked to the top directory: * *elphel393/bootable-images/mmc/ *(see https://wiki.elphel.com/wiki/Sd_boot_rootfs) * *elphel393/bootable-images/nand/ *(see https://wiki.elphel.com/wiki/NAND_flash_boot_rootfs) 6. Have a look at the elphel393/poky/build/local.conf * The default ip address of the rootfs can be set there. Tips for development: * Better to boot from a micro SD card (recovery or regular, see boot options <https://wiki.elphel.com/wiki/Boot_options_393>) * Most of the projects (even the kernel and fpga) are configured for Eclipse IDE ** If you build a project it will compile it and copy the binaries (or installed scripts) to the target hardware - the ip address is set in poky's local.conf, but the requirement is exporting your key: ssh-copy-id root@192.168.0.9 If you prefer to build from the command line then "bitbake ... -c target_scp" which does binaries/scripts copying Let us know if you have further questions or need more details. Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] recording questions for NC353L-369-IMU-GPS
Hello, What's the compression quality? and a single image size on average? Does the camera behave the same if image quality is lower? The max write speed to the CF card is around 19MB/s. I forgot how much of the bandwidth the logger uses - I will remeasure it and let you know. Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] Fw: Re: Collecting Visual Inertial Data with NC353L-369-IMU-GPS
Hi, Alright, 1. Did you try the logger? My instructions above were for /dev/hda1... should be /dev/hdb1 - the script should automatically mount if to /var/html/CF and start recording. 2. If you ran recording from this page: http://192.168.0.9/index.php?site=camogmgui/camogmgui.php Go to the "format tab" and check if the selected device is also /dev/hdb1 Or you can manually mount it to /var/hdd/ anytime. Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] Wide angle high resolution lens for Elphel 353L
Hello Jan, Search in the following list (M12 mount lenses as well): 1. Sunex <http://www.optics-online.com/dsl_1_2.5.asp> 2. Leading Optics <http://www.leadingoptics.com/Product.aspx?ID=1> 3. Vision Dimension <https://www.vision-dimension.com/en/lenses/mini-lenses-s-mount/?p=1> We usually get lenses from them and rmaelectronics. Hope you find what you need. Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] "Whiteout" camera problem...
Hello Todd, /etc/autocampars.xml - got corrupted or rewritten somehow. The sensor/camera's settings were not applied and the result is 1x1 white image. 1. Could you please send me this file? I will just try to find if it contains that error. 2. How you can fix this: from telnet (or 192.168.0.X/phpshell.php): > mv /etc/autocampars.xml /etc/autocampars.xml.bkp sync reboot -f At boot /etc/autocampars.xml with the default settings will be generated. You will need to restore your saved settings manually and then save them from 192.168.0.X/autocampars.php Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] Problems to detect timestamps
Jennifer, An update. 1. Follow the updated the wiki page <http://wiki.elphel.com/index.php?title=Trigger#External_.28J15.29>: * The parameters to change: http://192.168.0.9/parsedit.php?TRIG_CONDITION_OUT_PERIOD_RUN * Set COMPRESSOR_RUN=0x0 before applying other params, set it back to 0x2 after everything is set. OR 2. The older method will also work if after applying all the parameters, the settings are saved - http://192.168.0.9/autocampars.php and the camera is rebooted. Sorry for the trouble. Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] Problems to detect timestamps
Hello Jennifer, Were you able to solve your problem? I think there has been a confusion, when I referred to the "original" code > live555, I was referring to the latest version without changing code. The > problem is that when I connect to the camera with the instruction openrtsp > -m, I get files with the timestamp (PresentationTime) in the filename and > these values are incorrect. > > video-JPEG-1-1448298848.836308 >> video-JPEG-1-3534277304.245330 >> video-JPEG-1-3534277304.281407 >> video-JPEG-1-3534277304.317484 >> video-JPEG-1-3534277304.353561 >> video-JPEG-1-3534277304.389627 > > > The first file has a correct timestamp, but in the following files have > incorrect "times" (year 2081). > I was able to reproduce your problem. Installed live555 version (dated 2015-11-09). The first correct timestamp is the timestamp of the PC. Might be something with the RTSP server implementation in the camera. To find out I need to have a closer look at the code: http://elphel.cvs.sourceforge.net/viewvc/elphel/elphel353-8.0/apps/astreamer/ Will take some time - busy with other things. Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] Camera Sensor Failing
Linden, > I believe I tried the same thing previously but missed the 'sync' command. > This looks to have worked for camera_1 and it is back functioning > normally. Thanks. > camera_2 however is still not working after three attempts of removing > autocampars.xml. > Strange... > Well, I don't think 'sync' was very important. 'reboot -f' should include it (as Andrey has just told me). The files you sent look fine. It might be bad blocks in the flash - as it degrades over time. So, recently I had to reflash one old board to fix 'kernel panic' - and it worked. So, I would try reflashing camera_2. And camera_1 as well. The bad block tables in the file system are updated when reflash - if the problem is with new bad blocks Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] More Kubuntu/flash questions...
Hi, Sure, send the boards and I'll have a look. Thanks. Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] Fwd: Re: firmware update 8.0.9.2 to 8.2.16 failed
Hi, update: I build the firmware with the elphel liveCD :) followed http://wiki.elphel.com/index.php?title=Netboot_firmware_upgrade failed at step 2 camera well not go into netboot mode leds: orange sold green flashing tried five times :( If the camera connected directly to the PC (/ virtual box) - please check the ip address. And the script will not finish, right? Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] Elphel NC353L-369 Master - Slave external triggering
Jan, Just one last question - the frames do seem to be in sync now, but I wanted to ask whether it’s necessary to have the same TRIG_PERIOD set on both cameras in order for this to work or whether the TRIG_PERIOD doesn’t matter for the second camera as it just waits for the signal high? You might have already tested it - yes, TRIG_PERIOD of the slave camera does not have effect in this mode. Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] Elphel NC353L-369 Master - Slave external triggering
Apologies, there was a wrong wiring on the picture on our wiki - check out the corrected version http://wiki.elphel.com/index.php?title=File:Sync_cable.png. Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] Elphel NC353L-369 Master - Slave external triggering
Hi Jan, In the second case TRIG is still 0, because as soon as I set that it stops responding. That's what happens when you set up external triggering but the signals are not received for some reason. Another way to test your cable would be trying the following settings: Master Camera: TRIG_PERIOD=3840 TRIG_OUT=0x80 (send trigger signals to J15) TRIG_CONDITION=0x20 (trigger source - J15) TRIG=0x4 1. The order of applying TRIG and TRIG_CONDITION doesn't matter. If trigger signal is not generated then the camera will stop responding after applying the last parameter of these two. 2. If the Master camera doesn't stop responding then the cable and the port are ok. 3. The Slave camera can have exactly the same settings - so, you can test it in the Master mode as well - which only depends on the end of the sync cable plugged in. What results are you getting? Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] Extension of stereobase and elongation sensor's cable length
We got a good results with 0x1ff80 value for MULTI_PHASE[n] in both channels without changing SENSOR_PHASE. I would measure the range around 0x1ff80 while the image is still good, then set the phase to the middle. For a 450mm cable the working range is ~60-100 steps. At first we get a broken images at same manner. By the way, if we use 450 mm cable with MULTI_PHASE = 0x1ff80 we get same problem, so MULTI_PHASE is strongly depends on cable length. Yes - signal propagation delay. If the experiment will give us a good results we intend to expand a stereobase for second setup at the same manner. In with case we will order to you addition cables. Do you offer now a sensor board (compatible with our 10359) with monochrome sensor? If so what type of sensor installed into such board? We do have some monochrome sensor boards. You can buy them but using a monochrome sensor reduces overall resolution of the sensor+lens combination. And most of nowadays the applications deal with color sensors. So, you can: a. Keep using a color sensor - just work with R, G and B channels separately, then combine. b. Get a monochrome sensor - but use a green color band filter in front of the lens to a have better resolution. Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] Extension of stereobase and elongation sensor's cable length
Forgot to send a copy back to the mailing-list: I found that next values are: SENSOR_PHASE - 0x9 MULTI_PHASE1 - 0x100b0. 1. I don't know. With SENSOR_PHASE unchanged try several points within each quarter for MULTI_PHASE1, e.g.: 0x8ff70, 0x8, 0x80070, 0x9ff70, ... 0xaff70, ... 0xbff70, 0xb, 0xb0070. Sometimes a phase shifter (digital clock manager in the fpga) can get stuck - so it's safer to set 15th bit to 1 to reset it. You can try with a 450mm cable if the long one can be easily disassembled. 2. How exactly do you connect 2 cables? picture? Any difference in the voltage levels on the ends between 450mm and 900mm setups? 3. If both images are broken in the same manner then try to change the SENSOR_PHASE. Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] Extension of stereobase and elongation sensor's cable length
Hi, To do so we have connected two cables in serial, so we obtained total cable length 450mm + 450 mm = 900 mm between 359 board and each sensor board. There's no guarantee this length will work. We try use control page http://192.168.0.9/359/10359_controls.html but it is not clear which values I have to change. I'd need to test if it still works fine. A better way to adjust phases is this one: Go to: http://192.168.0.9/ Parameter Editor Check Unsafe View/Edit Current Or here's a link http://192.168.0.9/parsedit.php?title=Parameters+for+groups:+unsafe+CLK_FPGACLK_SENSORSENSOR_PHASEI2C_QPERIODI2C_BYTESMULTI_PHASE_SDRAMMULTI_PHASE1MULTI_PHASE2MULTI_PHASE3 . The phases are changed with: SENSOR_PHASE - system board - MUX (in stereo setup) MULTI_PHASE1 - MUX - sensor 1 MULTI_PHASE2 - MUX - sensor 2 MULTI_PHASE3... bits[18:17] - 90 degree shift bits[15:0] - fine steps (with sign) 0xff01...0x00ff Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] Elphel 353 - Question about Focus
Hi, *Lens:* E3Z4518CS-MPIR We haven't been able to get the focus to show the cards as sharp that with the Sanyo cameras. The cards are a 124cm from the camera, and with the Sanyo ones we are using a Pentax 5-50mm lens. Any advice or recommendation you may have to help us out with this project will be really appreciated. When the focus is the best - is the focusing ring at its extreme position? If yes: a. ideally you need to increase the sensor's distance from the lens by adjusting the sensor's plate position (1-2 mm probably) in the front end. or b. decrease the working focal length (wider field of view) - rotate the ring towards W until you get the best focus. c. you can also try closing the iris a little to increase the depth of field. If no, then a better lens should be tried probably. What's the image quality? frame dimensions? Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] Fwd: expected imu data fortmat
Hello Hamid, The parsed logged data looks ok - both, GPS and IMU. * Fatal error: Maximum execution time of 30 seconds exceeded in /mnt/flash/html/read_imu_log.php on line 101 The timeout can be set in the PHP configuration Please, let me know if you need any further help. Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] Fwd: expected imu data fortmat
Hello Hamid, Yes, the data from 'fpcf -imu 1 | grep 0:' looks wrong. I guess, the best way to troubleshoot would be sending the camera to us. Or you can try to record a log and check what's inside or send it to us. 1. Record a log (do you have a CF card inside?) - START: http://192.168.0.9/logger_launcher.php ?file=/usr/html/CF/test.logindex=1n=100 STOP: http://192.168.0.9/phpshell.php?command=killall%20-1%20log_imu You can open the logger_launcher.php and check what actual commands are executed. 2. Some parsers: http://wiki.elphel.com/index.php?title=Event_logger Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. On 2 October 2014 16:37, Elphel Support Team elphelsupp...@gmail.com wrote: -- Forwarded message -- From: Hamid M mokh0...@umn.edu Date: Wed, Oct 1, 2014 at 1:59 PM Subject: expected imu data fortmat To: support-l...@elphel.com Hi elphel, We have an NC353L combined with Garmin18 for GPS and ADIS 16375A IMU. The goal is to save pictures with known position and orientation (derivable from IMU). I've tried to get up to speed using the wiki and past e-mails, but am still having trouble. Here is my first question: 1) What is the data format of the imu data? When running cat /dev/imu a series of non-ascii characters are printed. Hence, either the data is streamed in a binary format or the communication settings are incorrect. If helpful, here are some outputs fpcf -imu 1 | grep 0: 0: 1387427810.526442 (0x52b277e2 0x8086a) 0x 0x 0x 0x 0x 0x 0x 0x 0x 0x 0x 0x 0x 0x 0: 1387427810.526849 (0x52b277e2 0x80a01) 0x 0x 0x 0x 0x 0x 0x 0x 0x 0x 0x 0x 0x 0x 0: 1387427810.527255 (0x52b277e2 0x80b97) 0x 0x 0x 0x 0x 0x 0x 0x 0x 0x 0x 0x 0x 0x ^C fpcf -imu 1 | grep 1: 1: 1387425332.154346 (0x52b26e34 0x25aea) 0xf0414001 0x174e8544 0x1390cef8 0x7f7468e3 0xfff00f0d 0xfffcdfcd 0xc5ff 0x 0x 0x 0x 0x 0x 0x 1: 1387425332.154346 (0x52b26e34 0x25aea) 0x1c12 0x 0x 0x 0x 0x 0x 0x 0x 0x 0x 0x 0x 0x ^C Thanks in advance, -Hamid -- Elphel Support Team supp...@elphel.com ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] dropbear-0.46
Hi Luc, Trying to add dropbear-2014.65 to the software. Patch applied. Then I get missing libtomcrypt.a and libtommath.a: crisv32-axis-linux-gnu-gcc: libtomcrypt/libtomcrypt.a: No such file or directory crisv32-axis-linux-gnu-gcc: libtommath/libtommath.a: No such file or directory Did you build those? After building them manually I get: libtomcrypt/libtomcrypt.a: could not read symbols: File format not recognized collect2: ld returned 1 exit status make: *** [dropbear] Error 1 Did something wrong probably - looking at it. Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] dropbear-0.46
Hello Luc, Latest dropbear, meaning 0.53.1 or 2014.65? Yes, CVS is the latest, what another one do you mean? There are some extra steps needed in order to update the revision and files for a correct build. What would you prefer? a) You send me the changes made and I update it. or b) I tell you that extra steps and add you to the developers if you have an account on the sf.net. Thanks, Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] NC353L Camera for video recording
Hello, I’m working on a project that will require 12 cameras setup in different locations throughout our building. All locations will have Ethernet available. I’m interested in the Elphel NC353L camera because it seems to have the features we need. However, I’m not an expert in video systems and I’m also not a software engineer. I need to speak with someone on your team to find out if I will be able to get your camera to do what I need. Essentially, we need the camera to record video directly to a Network Attached Storage device. If the cameras can do what I need them to do, then I will need help putting a quote together for the equipment so I can put it in my project plan. NAS need to have/support Network File System (NFS) server - then it can be mounted to each camera and be used for recording. A single camera's recording rate over network is 100Mb/s max - depending on the required FPS and frame dimensions one might have to lower the compression quality. Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] build-in AF motor
Hi, Do your cameras provide build-in AF motor, which could be controlled by my own codes? No, but there is a solution - you can get: * camera * lens with built-in AF motor * arduino, for example - the camera has a USB port and you will be able to control the lens' motor through arduino. Also, writing and running your own program or script for focus evaluation/monitor on any camera model is a relatively simple task - requires php or c. There is some work in the AF direction: http://wiki.elphel.com/index.php?title=Focus_helper - shows high frequency components of the image. Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] captured image location in memory
Dear Guarav, 1. I want to perform correlation over raw data but as you mentioned it is very difficult to find location of captured image and as you don t know about it ,so can you please tell me who is able to answer my question?? 1. Did you run the simulation of x353_1.tf? There you can track what happens to the raw sensor data. 2. To process the raw data you don't have to know where it's stored - you can intercept it right when it's coming from the sensor - PXD[..], HACT,VACT 2. i download all x353.v and x353.ucf file and its supporting files ,as i try to create .bit file then i got some errors during implementation as below: output no error: i got x353.bit file but as i reboot camera with this newly genrated x353.bit file i got some strips of different color. please find attachment of blurred image . SO IS I DID SOMETHING WRONG? 1. Timing, synthesis and Implementation reports from ISE Webpack? 2. What image do you get from the default x353.bit? - http://elphel.cvs.sourceforge.net/viewvc/elphel/elphel353-8.0/fpga/x3x3/x353.bit Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] captured image location in memory
Hello Gaurav, 1. when camera ON then it provide us blurred image. so how to overcome?? What kind of lens do you have? One possible problem can be is that you are using CS mount lens with CS-to-C 5mm adapter ring - http://wiki.elphel.com/index.php?title=File:Cap_and_ring.jpeg 2. when camera ON then it is blinking continuously so what it means ?? is it video recording or image capturing ?? The blinking green led means the camera is connected to a network - network packets. Recording or capturing is is not indicated anyhow. Solid orange - power. 3. i want to capture a image (say for reference image) and then by rotating camera some degree i want to capture another image (say current image) after that i want to perform correlation between reference image and current image. http://wiki.elphel.com/index.php?title=Elphel_353_series_quick_start_guide#Getting_the_first_images Store the images and perform correlation if you have a program that does it. 4. i want to reprogram fpga for finding correlation , so i should know storage location of my current image and reference image so can you please tell me where image is store in memory?? That's a difficult question and I cannot answer it right away as I don't know. Could you please have a look at the verilog simulation of the compressor? Are you intending to run correlation over compressed images or raw data? 5. when image is captured then are you applying any kind of image processing operation and then image is stored in camera.?? After the image is captured - the raw pixel data is converted and compressed into a chosen image format. No other processing is performed. http://wiki.elphel.com/index.php?title=JP4 http://wiki.elphel.com/index.php?title=Circbuf 6. I successfully generate a x353.bit file but for rebooting camera i unplug Ethernet cable and after 1 minute i plug it again, so it is rebooted but there is no message popup for ensuring that it is rebooted and is it right way to reboot camera?? Did you meet the timing constraints? Rebooting: a. Not clear. You don't have to wait for 1 min - just unplug and plug the cable to the camera network port and wait until it boots for ~1min. But if you copied something on the camera it's better to run sync over the filesystem first, in a browser: http://192.168.0.9/phpshell.php?command=sync So, it's not rebooted if the power supply is on and left connected to the camera. b. if you have Linux, run terminal and type: telnet 192.168.0.9 root/pass to login, then type: sync reboot -f You can perform this from any telnet program. Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] how to dump code into camera
Hi, Is it during synthesis or implementation? I think the last time it was built it was ISE WebPack 9.1 or 10.1 - and was ok. 14.7 looks like working as well. I check the Synthesis only. You can try: change all ROM32X1 instances: ROM32X1 i_z0 ( .A0(rom_a[0]), .A1(rom_a[1]), .A2(rom_a[2]), .A3(rom_a[3]), .A4(rom_a[4]), .O(rom_q[0])); ... defparam i_z0.INIT = 32'hC67319CC; to: ROM32X1 (.INIT(32'hC67319CC)) i_z0 ( .A0(rom_a[0]), .A1(rom_a[1]), .A2(rom_a[2]), .A3(rom_a[3]), .A4(rom_a[4]), .O(rom_q[0])); On 13 August 2014 02:25, gaurav dasondhi gauravdasondhi2...@gmail.com wrote: Hi QUESTION IN ISE WEBPACK DURING IMPLMENT DESIGN I GOT SOME ERRORS. DESIGN SUMMARY AND ERRORS ARE GIVEN BLOW. Target Device: xc3s1200e-5ft256 Product Version: ISE 12.1 - Warnings: 836 Warnings (1 new) - Errors: X 6 Errors (2 new) I GOT THESE 6 EROORS PLEASE PROVIDE SOLUTION. 1.ERROR:LIT:241 - Attribute INIT on ROM32X1 instance i_compressor/i_quantizator/i_zigzag/i_z5 has a hexadecimal value, 111011001000, which is too large. INIT should contain a maximum of 32 bits. ERROR:LIT:241 - Attribute INIT on ROM32X1 instance i_compressor/i_quantizator/i_zigzag/i_z4 has a hexadecimal value, 10001100100110110110, which is too large. INIT should contain a maximum of 32 bits. ERROR:LIT:241 - Attribute INIT on ROM32X1 instance i_compressor/i_quantizator/i_zigzag/i_z3 has a hexadecimal value, 01001010010011011000, which is too large. INIT should contain a maximum of 32 bits. ERROR:LIT:241 - Attribute INIT on ROM32X1 instance i_compressor/i_quantizator/i_zigzag/i_z2 has a hexadecimal value, 011000110101001000100110, which is too large. INIT should contain a maximum of 32 bits. ERROR:LIT:239 - Attribute INIT on ROM32X1 instance i_compressor/i_quantizator/i_zigzag/i_z1 has an invalid hexadecimal value, h611A7896. ERROR:LIT:241 - Attribute INIT on ROM32X1 instance i_compressor/i_quantizator/i_zigzag/i_z0 has a hexadecimal value, 11000110011100110001100111001100, which is too large. INIT should contain a maximum of 32 bits. On Tue, Aug 12, 2014 at 3:58 PM, gaurav dasondhi gauravdasondhi2...@gmail.com wrote: Dear oleg clarify it : bad bitstream can cause losing connection or damaging the hardware. here damaging hardware means ?? so if i used bad bitstream , then is there any way to keep camera again to its default setting.? On Tue, Aug 12, 2014 at 1:03 AM, Oleg support-list@support.elphel.com wrote: Guarav, 1. i want to perform correlation between two images ,i have a code written in verilog but how to dump that code into camera?? If you have a single lens camera (NC353, NC353-... - meaning there's no 10359 board installed that has an extra fpga) : The src verilog files for the system board fpga are here: http://elphel.cvs.sourceforge.net/viewvc/elphel/elphel353-8.0/fpga/x3x3/ In short, you need to add your code to the project, but most likely it won't fit in the fpga or won't meet the timing the fpga on the system board is almost full. If you manage to create a bitstream - it should be called x353.bit and copied it to the camera /etc/ - after rebooting the fpga will be configured with a new bitstream. If the camera doesn't have the serial output port on the side (NC353-369) - it will be hard to debug possible problems - bad bitstream can cause losing connection or damaging the hardware. 2. is iverilog 0.9.5-1 will work instead of 0.9.3 and is we need to install icraus verilog as we already have ISE WEBPACK.?? iverilog 0.9.5-1 should work - never tested though. For verilog verification you can use both ISE Webpack or Icarus Verilog + GTKWave. 3. i installed mplayer by command line but as i typed : mplayer rtsp:// 192.168.0.9:554 -vo x11 -fs -zoom then camera is in working mode but we got blurred image?? Blurred - compared to http://192.168.0.9:8081/bimg? *SO WHAT I DID IS IT OK OR I NEED TO INSTALL SOMETHING ELSE * For verilog: ISE Webpack, Icarus and GTKWave For the camera software: cross-compiler, get the camera firmware built from cvs http://wiki.elphel.com/index.php?title=Elphel_Software_Kit_for_Ubuntu#Build_Elphel_Software - then you can modify sources and rebuild it. KDevelop makes it easier to navigate through the project. Building the firmware requires to have the NFS server set up. ImageJ plugins are mostly for our calibrated/stereo/multi-sensor cameras. You can use them as a base to write your own plugin for correlation, for example. Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com -- Best regards, Oleg
Re: [Elphel-support] how to dump code into camera
Hi, I understand that the 10359 has an additional XC3S1200 FPGA that can be used for image processing routines without modifying the FPGA on the 353 main board. Is there a simple way to dump a Verilog generated bitstream onto the 10359 FPGA, such as putting it into a file like /etc/x353.bit? Yes, it's the same - copy x359.bit to /etc/x359.bit and reboot. Verilog for 10359 http://elphel.cvs.sourceforge.net/viewvc/elphel/elphel353-8.0/fpga/x359/. The 10359 is connected between the sensor and the system board: sensor - 10359 - 10353 The 10359's input is raw pixel data and so the output needs to mimic the sensor as well - the compression is done on the system board. Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] FW: Product Enquiry
Hi Ian, Apologies for the delay getting back to you, I've been away with work. I can install the battery inside the casing, would it be possible to re-charge it through a USB drive or something similar? It depends on the battery. Most are charged from a wall outlet. As the camera will also be used for cycling the camera view will need to adjust from close up to further away distances (for example the road ahead) so the focal lengths will need to be variable. Ok, we got a couple lenses listed on our website http://www3.elphel.com/accessories. For more, please have a look here http://www.rmaelectronics.com/lenses/ - the camera's lens mount is C/CS. Did you have a chance to speak with Oleg regarding the prices? Sorry, Olga was busy and now she's on vacation. I'll remind her - she might be available. Meanwhile, we got the price list http://www3.elphel.com/price_list Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] Elphel 353 no connection after RTSP interuption
Hi Hugo, Sorry, it took me to long to answer. Yes, we received the camera. The network chip on the system board doesn't work - burnt. It is possible to replace it. Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
Re: [Elphel-support] FW: Product Enquiry
Hello Ian, Could you please give me a price for the following: I'll ask Olga to send you quotes for these. Some important things: 1. The cameras do not have batteries inside - you would have to buy them from somewhere. As I said above we have 12-36V camera modification (11.1V is strongly not recommended). Hopefully you will be able to find something suitable. Normally a camera is powered through the network jack, but it's possible to provide power directly to the board. 2. The cameras can only be controlled/programmed over the network. For the software, I was wondering if you can also supply the software where I can upload the recorded videos on my computer where I can edit them and as there will be two views (front and back) it could change between views on the final edited video. Videos (MOV format) can be transferred through FTP. Could you please clarify on your question for the fields for the view of the camera's? Do you mean the types of views? I mean the field of view (or angle of view) for lenses as in this article http://en.wikipedia.org/wiki/Field_of_view. In other words, what are the focal lengths? Variable? You can estimate here http://community.elphel.com/files/dof/index.html (by varying focal length) - our default sensor (1/2.5 format) is preselected. Also, since full FoV is for the full res (2592x1944) - the FoV for 1080p will be proportionally smaller. Best regards, Oleg Dzhimiev Electronics Engineer phone: +1 801 783 x124 Elphel, Inc. ___ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
