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 <support-list@support.elphel.com> 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 <lin...@zone4.ca> 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 <support-list@support.elphel.com> >> 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: 0x00040000->0x40440000, len 0x00200000, boot @ 0x40440000 >>>> >>>> >>>> >>>> CPU revision: 0x00000020 >>>> >>>> >>>> >>>> Bootloader main at 0x38000ce2 >>>> >>>> >>>> >>>> Data end: 0x3800573c >>>> >>>> >>>> >>>> Bss: 0x38008000 >>>> >>>> >>>> >>>> Heap: 0x38008000 >>>> >>>> >>>> >>>> Identifying nand chip... >>>> >>>> >>>> >>>> maf_id: 0x0000002c; dev_id: 0x000000f1 >>>> >>>> >>>> >>>> mtd->size == 0x08000000 >>>> >>>> >>>> >>>> scan_bbt(); mtd->size == 0x08000000 >>>> >>>> >>>> >>>> scan_bbt() ...01; mtd->size == 0x08000000 >>>> >>>> >>>> >>>> len == 0x00000100; and BBT_LEN_1 == 0x00000400 >>>> >>>> >>>> >>>> scan_bbt() ...02; mtd->size == 0x08000000 >>>> >>>> >>>> >>>> scan_bbt() ...03; mtd->size == 0x08000000 >>>> >>>> >>>> >>>> scan_bbt() ...1; mtd->size == 0x08000000 >>>> >>>> >>>> >>>> scan_bbt() ...2; mtd->size == 0x08000000 >>>> >>>> >>>> >>>> scan_bbt() search_read_bbts(); mtd->size == 0x08000000 >>>> >>>> >>>> >>>> search_read_bbts() search primary table; mtd->size == 0x08000000 >>>> >>>> >>>> >>>> search_bbt() ...1; mtd->size == 0x08000000 >>>> >>>> >>>> >>>> search_bbt() ...2; maxblocks: 0x00000004; mtd->size == 0x08000000 >>>> >>>> >>>> >>>> Block: 0x000003ff >>>> >>>> >>>> >>>> Check, if we found a bbt for each requested chip >>>> >>>> >>>> >>>> Bad block table found at page0x0000ffc0, version 0x00000001 >>>> >>>> >>>> >>>> search_read_bbts() search mirror table >>>> >>>> >>>> >>>> search_bbt() ...1; mtd->size == 0x08000000 >>>> >>>> >>>> >>>> search_bbt() ...2; maxblocks: 0x00000004; mtd->size == 0x08000000 >>>> >>>> >>>> >>>> Block: 0x000003ff >>>> >>>> >>>> >>>> Block: 0x000003fe >>>> >>>> >>>> >>>> Check, if we found a bbt for each requested chip >>>> >>>> >>>> >>>> Bad block table found at page0x0000ff80, version 0x00000001 >>>> >>>> >>>> >>>> scan_bbt() ...3 >>>> >>>> >>>> >>>> Done. >>>> >>>> >>>> >>>> Chip identified... 3; NAND 128MiB 3,3V 8-bit >>>> >>>> >>>> >>>> type: 0x00000004 >>>> >>>> >>>> >>>> flags: 0x000000c5 >>>> >>>> >>>> >>>> size: 0x08000000 >>>> >>>> >>>> >>>> erasesize: 0x00020000 >>>> >>>> >>>> >>>> oobblock: 0x00000800 >>>> >>>> >>>> >>>> oobsize: 0x00000040 >>>> >>>> >>>> >>>> ecctype: 0x00000002 >>>> >>>> >>>> >>>> eccsize: 0x00000100 >>>> >>>> >>>> >>>> Oob info: >>>> >>>> >>>> >>>> useecc: 0x00000002 >>>> >>>> >>>> >>>> eccbytes: 0x00000018 >>>> >>>> >>>> >>>> eccpos: 0x00000028 0x00000029 0x0000002a 0x0000002b 0x0000002c >>>> 0x0000002d 0x0000002e 0x0000002f 0x00000030 0x00000031 0x00000032 >>>> 0x00000033 0x00000034 0x00000035 0x00000036 0x00000037 0x00000038 >>>> 0x00000039 0x0000003a 0x0000003b 0x0000003c 0x0000003d 0x0000003e 0x0000003 >>>> >>>> Bootload in progress... >>>> >>>> >>>> >>>> New block 0x00040000;len: 0x00200000;start: 0x00040000 >>>> >>>> >>>> >>>> New block 0x00060000;len: 0x001e0000;start: 0x00060000 >>>> >>>> >>>> >>>> New block 0x00080000;len: 0x001c0000;start: 0x00080000 >>>> >>>> >>>> >>>> New block 0x000a0000;len: 0x001a0000;start: 0x000a0000 >>>> >>>> >>>> >>>> New block 0x000c0000;len: 0x00180000;start: 0x000c0000 >>>> >>>> >>>> >>>> New block 0x000e0000;len: 0x00160000;start: 0x000e0000 >>>> >>>> >>>> >>>> New block 0x00100000;len: 0x00140000;start: 0x00100000 >>>> >>>> >>>> >>>> New block 0x00120000;len: 0x00120000;start: 0x00120000 >>>> >>>> >>>> >>>> New block 0x00140000;len: 0x00100000;start: 0x00140000 >>>> >>>> >>>> >>>> New block 0x00160000;len: 0x000e0000;start: 0x00160000 >>>> >>>> >>>> >>>> New block 0x00180000;len: 0x000c0000;start: 0x00180000 >>>> >>>> >>>> >>>> complete, status 0xffffffb6, loaded 0x00140000 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 <lin...@zone4.ca> 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 (&npsp; 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 >>>> won't boot). >>>> >>>> Thanks, >>>> >>>> Linden Mills-Connery >>>> Zone4 Team <https://zone4.ca/contact/> >>>> 205-820 Main Street >>>> Canmore, AB, T1W2B7 >>>> 403-401-7215 >>>> >>>> On 20 August 2018 at 10:43, Oleg <support-list@support.elphel.com> >>>> wrote: >>>> >>>>> 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 <lin...@zone4.ca> >>>>> 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 >>>>>> <https://maps.google.com/?q=205-820+Main+Street+Canmore,+AB,+T1W2B7&entry=gmail&source=g> >>>>>> Canmore, AB, T1W2B7 >>>>>> <https://maps.google.com/?q=205-820+Main+Street+Canmore,+AB,+T1W2B7&entry=gmail&source=g> >>>>>> 403-401-7215 >>>>>> >>>>>> On 17 August 2018 at 17:53, Oleg <support-list@support.elphel.com> >>>>>> 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 >>>> >>> >>> >>> -- >>> Best regards, >>> Oleg Dzhimiev >>> Electronics Engineer >>> phone: +1 801 783 5555 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 Dzhimiev Electronics Engineer phone: +1 801 783 5555 x124 Elphel, Inc.
_______________________________________________ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
