Track the most recent changes to the wiki in this feed.
MediaWiki 1.28.0
Updated: 48 min 16 sec ago
Tmp manual
Record:
← Older revision Revision as of 00:44, 18 December 2016 (6 intermediate revisions not shown)Line 59: Line 59: ** likely device: <b>/dev/ttyUSB0</b> ** likely device: <b>/dev/ttyUSB0</b> ** settings: <b>115200 8N1, no</b> for hardware/software flow control ** settings: <b>115200 8N1, no</b> for hardware/software flow control + +==<font color="blue">web interface (camvc)</font>== +http://192.168.0.9/closeme.html (will get changed soon) ==<font color="blue">Get images</font>== ==<font color="blue">Get images</font>== Line 91: Line 94: Example 1: (provide a correct media mount point) Example 1: (provide a correct media mount point) <font size='2'> <font size='2'> -* http://192.168.0.9/camogm.html+* http://192.168.0.9/camogmgui.php -</font>+ - + -Example 2:+ -<font size='2'>+ -* channel '''0''', '''/dev/sda1''', w/o a file name prefix+ -** setup:+ - http://192.168.0.9/camogm.php?chn=0&cmd=prefix=/mnt/sda1/;+ -** start:+ - http://192.168.0.9/camogm.php?chn=0&cmd=start;+ -** stop:+ - http://192.168.0.9/camogm.php?chn=0&cmd=stop;+ </font> </font> Line 110: Line 102: * channel '''2''', '''/home/root''', file prefix='''test_''', '''1GB''' or '''10min''' files whichever occurs first * channel '''2''', '''/home/root''', file prefix='''test_''', '''1GB''' or '''10min''' files whichever occurs first ** setup and start (in one line): ** setup and start (in one line): - echo "format=mov;status=/var/tmp/camogm2.status;prefix=/home/root/test_;duration=600;length=1073741824;start" > /var/volatile/camogm_cmd2+ echo "format=mov;status=/var/tmp/camogm.status;prefix=/home/root/test_;duration=600;length=1073741824;start" > /var/volatile/camogm_cmd ** stop recording: ** stop recording: - echo "stop" > /var/volatile/camogm_cmd2+ echo "stop" > /var/volatile/camogm_cmd sync sync </font> </font> ==<font color="blue">Change parameters</font>== ==<font color="blue">Change parameters</font>== -* http://192.168.0.9/controls.html - previews and basic parameters:+* http://192.168.0.9/autocampars.php - read & write parameters (through parsedit.php), save configuration (if boot from NAND flash - "shutdown -r now" will sync changes or copy /etc/elphel393/*.xml to /tmp/rootfs.ro/etc/elphel393/) -** Exposure - the values are in the sensor lines. Currently conversion to seconds is not correct.+* parsedit.php -** WB - r,g,b gains+The response is in XML form: -** Quality - compression quality - individual for compressor but common for the buffer driver - it's better to have the same value for all channels.+ +Read: + http://192.168.0.9/parsedit.php?immediate&sensor_port=0&PAR1&PAR2 +Change: + http://192.168.0.9/parsedit.php?immediate&sensor_port=0&PAR1=VAL1&PAR2=VAL2 + +Note 1: It's just if the parameter value is specified it will be applied. The call can have mixed specified and unspecified parameters. + +Note 2: The new value is read on the next call. -* For 5MPix the startup settings are defined int the ''/usr/local/verilog/startup5'' on the micro SD card, FAT32 partition:+===Notes=== - ...+* parsedit.php and autocampars.php were ported from 353 camera series. There are a few changes from the originals related to 4x sensor ports: - -c write_sensor_i2c all 1 0 0x9009001e (exposure)+** parameters are individual for each sensor port - writing parameters to multiple port at once is controlled with a (bit-)'''mask''' input box - -c write_sensor_i2c all 1 0 0x9035000a (set all gains to 0xa)+** if opened w/o sensor_port specified the page will show links to available ports - -c write_sensor_i2c all 1 0 0x902c000e (blue gain to 0xe)+** '''sensor_port=x''', where x=0..3 - in the address string - for a single sensor camera it is normally 0 - -c write_sensor_i2c all 1 0 0x9009001d (red gain to 0xd)+ - ...+ -{|+ -|[[File:10393_controls.jpeg|thumb|200px]]+ -|}+ ==<font color="blue">Temperature monitor</font>== ==<font color="blue">Temperature monitor</font>== OlegBoot options 393
Internal NAND flash (default):
← Older revision Revision as of 00:27, 17 December 2016 Line 17: Line 17: ==<font color="blue">Boot instructions</font>== ==<font color="blue">Boot instructions</font>== ===Internal NAND flash (default)=== ===Internal NAND flash (default)=== -* Make sure the recovery card is not inserted+* Make sure the recovery card is not inserted (recovery card can stay in) * Power on * Power on OlegNAND flash boot rootfs
← Older revision
Revision as of 23:44, 16 December 2016
(One intermediate revision not shown)Line 1:
Line 1:
-==Boot from NAND flash (rootfs)==
-* The default boot option - power on.
-* A UBIFS image of rootfs is written to /dev/mtd4 ('''ubi0:elphel393-rootfs''' in bootargs in the device tree) - mounted as '''/'''
-
==Reflash factory image== ==Reflash factory image==
===Notes=== ===Notes===
-* Update software/firmware or corrupt flash partition+* Will overwrite software/firmware or corrupt flash partition
* To update u-boot images, device tree and kernel - booting from micro SD card is not required. * To update u-boot images, device tree and kernel - booting from micro SD card is not required.
-* To update rootfs - boot from micro SD card otherwise a mounted flash partition will be rewritten, get corrupt and the camera won't boot - boot from micro SD card and reflash rootfs partition to recover. +* To update rootfs - boot from micro SD card otherwise a mounted flash partition will be rewritten, get corrupt and the camera might not boot - to recover, boot from micro SD card and reflash rootfs partition.
* '''boot.bin''', '''u-boot-dtb.img''' - most likely won't need updating at all. Only if their partitions get corrupt * '''boot.bin''', '''u-boot-dtb.img''' - most likely won't need updating at all. Only if their partitions get corrupt
-** As Zynq's BootROM performs 32KB jumps within the first 128MiB of flash in the search of a boot.bin header with a correct checksum it is possible to flash a few backup images to the 1st flash partition (mtd0) in the device tree. The partition size is 1MB, boot.bin size is normally around 100KB (<192KB - Zynq OCM requirement)+** As Zynq's BootROM performs 32KB jumps within the first 128MiB of flash in the search of a boot.bin header with a correct checksum it is possible to flash a few backup images to the 1st flash partition (mtd0) in the device tree. The partition size is 1MB, boot.bin size is normally around 100KB (<192KB - Zynq's OCM requirement)
===Instructions=== ===Instructions===
-* Use files from '''.../poky/build/tmp/deploy/images/elphel393/nand/'''+* Use files from '''elphel393/bootable-images/elphel393/nand/'''
** '''boot.bin''' ** '''boot.bin'''
** '''u-boot-dtb.img''' ** '''u-boot-dtb.img'''
** '''devicetree.dtb''' ** '''devicetree.dtb'''
** '''uImage''' ** '''uImage'''
-** '''rootfs.ubifs''' (<font color='green'>recommended</font>), '''rootfs.ubi''' (<font color='red'>radical</font>)+** '''rootfs.ubi''' or '''rootfs.ubifs'''
-* Copy all of the image files to a micro SD card (or boot first from the card then copy over network)+
-* Boot from micro SD card (<font color='red'>important for rootfs updates</font>)+====Option 1====
+* Boot the camera from the micro SD card (<font color='red'>important for rootfs update</font>)
+* Go to the http://192.168.0.9/update_software.html
+* Upload '''uImage''' and '''rootfs.ubi'''
+* Verify, download backup then Flash
+
+====Option 2: manual====
+* Boot the camera from the micro SD card (<font color='red'>important for rootfs update</font>)
+* Copy file to the camera, example from the PC terminal:
+ $ scp boot.bin u-boot-dtb.img devicetree.dtb uImage rootfs.ubi root@192.168.0.9:/tmp/
* Reflash what is needed: * Reflash what is needed:
** Reflash SPL ('''boot.bin''', /dev/mtd0) ** Reflash SPL ('''boot.bin''', /dev/mtd0)
Oleg
Boot options 393
← Older revision
Revision as of 23:05, 16 December 2016
Line 70:
Line 70:
* '''RAM''' - unpack an archive from a μSD card FAT32 partition into RAM but it was tested a while ago: * '''RAM''' - unpack an archive from a μSD card FAT32 partition into RAM but it was tested a while ago:
bootargs = "cma=336M console=ttyPS0,115200 root=/dev/ram rw ip=192.168.0.9 earlyprintk ramdisk_size=262144"; bootargs = "cma=336M console=ttyPS0,115200 root=/dev/ram rw ip=192.168.0.9 earlyprintk ramdisk_size=262144";
+** Changes will not be stored
+** Modify env commands in the u-boot (in elphel393.h or when in the u-boot command line)
+** Carefully check the actual and hardcoded images' sizes in the u-boot (elphel393.h) and the device tree (elphel393_xxx.dts) with the actual sizes.
+** Don't want to waste the RAM - make tiny rootfs
====Notes==== ====Notes====
* when loaded the full-size u-boot can be key-interrupted and override bootargs parameter of the device tree. * when loaded the full-size u-boot can be key-interrupted and override bootargs parameter of the device tree.
* '''To build a custom device tree''', see [http://wiki.elphel.com/index.php?title=Poky_2.0_manual SDK manual]''' * '''To build a custom device tree''', see [http://wiki.elphel.com/index.php?title=Poky_2.0_manual SDK manual]'''
-
==<font color="blue">cp210x_gpio.py -h</font>== ==<font color="blue">cp210x_gpio.py -h</font>==
Oleg
Poky 2.0 manual
Write files to media and boot:
← Older revision Revision as of 23:04, 16 December 2016 (5 intermediate revisions not shown)Line 38: Line 38: </font> </font> ==<font color="blue">Output files</font>== ==<font color="blue">Output files</font>== -Found in the poky's deploy directory: +The names are listed as they appear in the u-boot configuration header file - actual output files have different names: -* files for rootfs in NAND Flash: '''poky/build/tmp/deploy/images/elphel393/nand/'''+ -* files for rootfs on MMC (micro SD card): '''poky/build/tmp/deploy/images/elphel393/mmc/'''+ - + -These names are listed as they appear in the u-boot configuration header file - actual output files have different names:+ * '''boot.bin''' - u-boot as the first stage bootloader = Secondary Program Loader that boots '''u-boot-dtb.img''' * '''boot.bin''' - u-boot as the first stage bootloader = Secondary Program Loader that boots '''u-boot-dtb.img''' * '''u-boot-dtb.img''' - full size u-boot with a stripped device tree (''cat u-boot.img some_stripped_devicetree.dtb > u-boot-dtb.img'') * '''u-boot-dtb.img''' - full size u-boot with a stripped device tree (''cat u-boot.img some_stripped_devicetree.dtb > u-boot-dtb.img'') -* '''devicetree.dtb''' - device tree with listed interfaces, zynq registers, interrupts and drivers+* '''devicetree.dtb''' - device tree with listed interfaces, zynq registers, interrupts and drivers. +** ''elphel393/bootable-images/mmc/devicetree.dtb'' - mount rootfs from mmc partition +** ''elphel393/bootable-images/nand/devicetree.dtb'' - mount rootfs from NAND flash * '''uImage''' - kernel, drivers * '''uImage''' - kernel, drivers -* '''rootfs.ubifs''' or '''rootfs.tar.gz''' - rootfs+* '''rootfs.ubifs''', '''rootfs.ubi''', '''rootfs.tar.gz''' - rootfs in different formats + +They are found poky's deploy directory '''elphel393/poky/build/tmp/deploy/images/elphel393/''', linked to +'''elphel393/bootable-images/''' for convenience. + +* complete set of files for rootfs in NAND Flash: ''elphel393/bootable-images/nand/'' +* complete set of files for rootfs on MMC (micro SD card): ''elphel393/bootable-images/mmc/'' -==<font color="blue">Boot options</font>==+==<font color="blue">Write files to media and boot</font>== -===Boot from micro SD card (rootfs)===+===Boot from micro SD card=== -* The micro SD card/adapter must be modified for this boot mode (to keep CD pin high) - only then the camera will boot+* Use recovery or regular μSD card * EXT4 partition mounted as '''/''' * EXT4 partition mounted as '''/''' -* [[Sd_boot_rootfs|Detailed instructions]]+[[Sd_boot_rootfs|Detailed instructions]] -===Boot from NAND flash (rootfs)===+===Boot from NAND flash=== * The default boot option - power on. * The default boot option - power on. * A UBIFS image is written to /dev/mtd4 - is mounted as '''/''' * A UBIFS image is written to /dev/mtd4 - is mounted as '''/''' -* [[NAND_flash_boot_rootfs|Detailed instructions]]+[[NAND_flash_boot_rootfs|Detailed instructions]] ===Notes=== ===Notes=== -* It is possible to unpack rootfs to RAM not mounting any partitions ('''/''' in RAM, ramdisk):+* [[Boot_options_393|'''Read more''']] about boot options. -** Changes are not stored+ -** Boot faster?+ -** Work faster?+ -** Modify env commands in the u-boot (in elphel393.h or when in the u-boot command line)+ -** Carefully check the actual and hardcoded images' sizes in the u-boot (elphel393.h) and the device tree (elphel393_xxx.dts) with the actual sizes.+ ==<font color="blue">Setup</font>== ==<font color="blue">Setup</font>== OlegPoky 2.0 manual
Boot options:
← Older revision Revision as of 22:54, 16 December 2016 (3 intermediate revisions not shown)Line 38: Line 38: </font> </font> ==<font color="blue">Output files</font>== ==<font color="blue">Output files</font>== -Found in the poky's deploy directory: +The names are listed as they appear in the u-boot configuration header file - actual output files have different names: -* files for rootfs in NAND Flash: '''poky/build/tmp/deploy/images/elphel393/nand/'''+ -* files for rootfs on MMC (micro SD card): '''poky/build/tmp/deploy/images/elphel393/mmc/'''+ - + -These names are listed as they appear in the u-boot configuration header file - actual output files have different names:+ * '''boot.bin''' - u-boot as the first stage bootloader = Secondary Program Loader that boots '''u-boot-dtb.img''' * '''boot.bin''' - u-boot as the first stage bootloader = Secondary Program Loader that boots '''u-boot-dtb.img''' * '''u-boot-dtb.img''' - full size u-boot with a stripped device tree (''cat u-boot.img some_stripped_devicetree.dtb > u-boot-dtb.img'') * '''u-boot-dtb.img''' - full size u-boot with a stripped device tree (''cat u-boot.img some_stripped_devicetree.dtb > u-boot-dtb.img'') -* '''devicetree.dtb''' - device tree with listed interfaces, zynq registers, interrupts and drivers+* '''devicetree.dtb''' - device tree with listed interfaces, zynq registers, interrupts and drivers. +** ''elphel393/bootable-images/mmc/devicetree.dtb'' - mount rootfs from mmc partition +** ''elphel393/bootable-images/nand/devicetree.dtb'' - mount rootfs from NAND flash * '''uImage''' - kernel, drivers * '''uImage''' - kernel, drivers -* '''rootfs.ubifs''' or '''rootfs.tar.gz''' - rootfs+* '''rootfs.ubifs''', '''rootfs.ubi''', '''rootfs.tar.gz''' - rootfs in different formats + +They are found poky's deploy directory '''elphel393/poky/build/tmp/deploy/images/elphel393/''', linked to +'''elphel393/bootable-images/''' for convenience. + +* complete set of files for rootfs in NAND Flash: ''elphel393/bootable-images/nand/'' +* complete set of files for rootfs on MMC (micro SD card): ''elphel393/bootable-images/mmc/'' -==<font color="blue">Boot options</font>==+==<font color="blue">Write files to media and boot</font>== ===Boot from micro SD card (rootfs)=== ===Boot from micro SD card (rootfs)=== -* The micro SD card/adapter must be modified for this boot mode (to keep CD pin high) - only then the camera will boot+* Use recovery or regular μSD card * EXT4 partition mounted as '''/''' * EXT4 partition mounted as '''/''' -* [[Sd_boot_rootfs|Detailed instructions]]+[[Sd_boot_rootfs|Detailed instructions]] ===Boot from NAND flash (rootfs)=== ===Boot from NAND flash (rootfs)=== * The default boot option - power on. * The default boot option - power on. * A UBIFS image is written to /dev/mtd4 - is mounted as '''/''' * A UBIFS image is written to /dev/mtd4 - is mounted as '''/''' -* [[NAND_flash_boot_rootfs|Detailed instructions]]+[[NAND_flash_boot_rootfs|Detailed instructions]] ===Notes=== ===Notes=== * It is possible to unpack rootfs to RAM not mounting any partitions ('''/''' in RAM, ramdisk): * It is possible to unpack rootfs to RAM not mounting any partitions ('''/''' in RAM, ramdisk): -** Changes are not stored+** Changes will not be stored -** Boot faster?+ -** Work faster?+ ** Modify env commands in the u-boot (in elphel393.h or when in the u-boot command line) ** Modify env commands in the u-boot (in elphel393.h or when in the u-boot command line) ** Carefully check the actual and hardcoded images' sizes in the u-boot (elphel393.h) and the device tree (elphel393_xxx.dts) with the actual sizes. ** Carefully check the actual and hardcoded images' sizes in the u-boot (elphel393.h) and the device tree (elphel393_xxx.dts) with the actual sizes. +** Don't want to waste RAM ==<font color="blue">Setup</font>== ==<font color="blue">Setup</font>== OlegBoot options 393
← Older revision
Revision as of 18:43, 16 December 2016
(3 intermediate revisions not shown)Line 51:
Line 51:
./cp210x_gpio.py 0xf; ./cp210x_gpio.py 0xf;
-===Other boot options===+===Other boot options (set in u-boot or device tree)===
-The instructions are defined by the 3 options above.+Follow the instructions of the 3 options above but with different bootloader or device tree.
-They define where the camera will load the u-boot, device tree and kernel from: μSD card or NAND flash. The location of rootfs ("/") is set in the device tree. Available locations for rootfs:+
+The 3 options above define where the cpu's boot ROM loads SPL version of u-boot from: NAND flash or μSD card. The SPL u-boot loads the full-size u-boot.
+In its turn he full size u-boot can be instructed where to load the device tree and the kernel from, available options:
+* NAND flash (default if SPL was loaded from flash)
+* μSD card (default if SPL was loaded from μSD card)
+* internal SSD (not tested)
+* network (not tested)
+
+Next, the location of rootfs ("/") is set in the device tree. Available locations for rootfs:
+
* '''any μSD card partition'''. The default device tree parameter is: * '''any μSD card partition'''. The default device tree parameter is:
bootargs = "cma=336M console=ttyPS0,115200 root=/dev/mmcblk0p2 rw ip=192.168.0.9 earlyprintk rootwait rootfstype=ext4"; bootargs = "cma=336M console=ttyPS0,115200 root=/dev/mmcblk0p2 rw ip=192.168.0.9 earlyprintk rootwait rootfstype=ext4";
Line 62:
Line 71:
bootargs = "cma=336M console=ttyPS0,115200 root=/dev/ram rw ip=192.168.0.9 earlyprintk ramdisk_size=262144"; bootargs = "cma=336M console=ttyPS0,115200 root=/dev/ram rw ip=192.168.0.9 earlyprintk ramdisk_size=262144";
+====Notes====
+* when loaded the full-size u-boot can be key-interrupted and override bootargs parameter of the device tree.
+* '''To build a custom device tree''', see [http://wiki.elphel.com/index.php?title=Poky_2.0_manual SDK manual]'''
-'''To build a custom device tree''', see [http://wiki.elphel.com/index.php?title=Poky_2.0_manual SDK manual]'''
==<font color="blue">cp210x_gpio.py -h</font>== ==<font color="blue">cp210x_gpio.py -h</font>==
Oleg
Ezynq
"Free" the code part:
← Older revision Revision as of 18:13, 16 December 2016 Line 14: Line 14: <b>as of 2016/03/18...</b> <b>as of 2016/03/18...</b> * u-boot-xlnx master-next branch is removed long ago - so the link above is broken * u-boot-xlnx master-next branch is removed long ago - so the link above is broken + +<b>as of 2016/06/25...</b> +* ezynq depends on original u-boot instead of u-boot-xlnx ==Supported boards== ==Supported boards== OlegTmp manual
← Older revision
Revision as of 02:25, 16 December 2016
(6 intermediate revisions not shown)Line 1:
Line 1:
+==<font color="blue">Important Notes</font>==
+* As of 2016/12/15, the software supports only 5MPix sensors, for 14MPix, please see:
+**[http://wiki.elphel.com/index.php?title=Tmp_manual&oldid=14676 older version of this manual with links to older software images]
+
==<font color="blue">In the package</font>== ==<font color="blue">In the package</font>==
-* 10393 system+* 10393 camera system
{| {|
|[[File:NC393-CS marked ports.jpeg|thumb|200px]] |[[File:NC393-CS marked ports.jpeg|thumb|200px]]
|} |}
-* Power supply wall adapter (48V)+* Power supply wall adapter (default: 18-75V, [[10393_power|more information]])
* CAT6 network cable * CAT6 network cable
* μUSB-to-USB cable * μUSB-to-USB cable
Line 13:
Line 17:
* Connect to LAN using the network cable * Connect to LAN using the network cable
-NOTE: the boot time is ~30s+====Notes====
+* Boot time: ~40s
+* The default boot is from the on-board NAND flash. [[Boot_options_393|More information]] on available boot options and recovery boot.
==<font color="blue">Connections</font>== ==<font color="blue">Connections</font>==
Line 22:
Line 28:
|} |}
* [[10393_power|Power supply]] * [[10393_power|Power supply]]
-
-==<font color="blue">Important Notes</font>==
-* As of 2016/12/15, the software supports only 5MPix sensors, for 14MPix, please see:
-**[http://wiki.elphel.com/index.php?title=Tmp_manual&oldid=14676 older version of this manual with links to older software images]
==<font color="blue">Defaults</font>== ==<font color="blue">Defaults</font>==
Line 46:
Line 48:
* /etc/elphel393/init_elphel393.py * /etc/elphel393/init_elphel393.py
-==<font color="blue">Boot</font>==
-Normally camera boots from the internal NAND flash memory, and it is always possible to boot it from the micro SD card, so even corruption of files on the internal flash will not "brick" the system. There are no buttons or switches on the camera and the camera should be instructed to change the boot source. Always booting from micro SD is not practical - in that case it would not be possible to leave a non-bootable card (intended just for image/video storage) in the camera slot.
-There are two ways to switch camera to the micro SD boot mode. One requires camera to be connected to the host computer with the USB cable (micro USB socket under the network jack - marked "console" on the picture). There is an internal USB-to-serial converter in the camera (CP2103) that offers 4 additional GPIO signals in addition to just the serial connection. One of these signals selects the boot source (GPIO0 - 0 - MMC, 1 - NAND), another (GPIO3 - 0 reset, 1 - normal operation). Unfortunately GPIO control of the CP2103 is not in a mainline cp210x Linux driver so this functionality requires a modified version (see instructions below).
-
-Another way to "tell" the camera to boot from the μSD card instead of the internal NAND flash is to use a mechanically modified card or card adapter (such cards are provided with the camera). Standard specifies two alternative ways for detection of the card presence - one is a mechanical switch (closed when the card is inserted), another is a pull-up resistor on a data line. Camera uses both signals at boot time to determine the boot source:
-* Switch not closed, pull-up resistor not detected -> no card present, boot from the internal NAND flash
-* Switch closed -> data (non-bootable) card present, boot from the internal NAND flash
-* Switch not closed, pull-up resistor is detected -> bootable card present, boot from the MMC card
-
-* [default behavior] on power-on the camera boots from NAND flash: u-boot, device tree and kernel.
-devicetree has "chosen = ...root=/dev/mmcblk0p2..." - rootfs is on the micro SD card second partition. Thus, the μSD card must be inserted.
-* boot from μSD card only options:
-** A modified card that doesn't lock the mechanical CD pin in the slot - it's done by carefully filing off the corner (see Fig.2) - most cards have circuitry there and get damaged.
-** μUSB-to-USB cable: in Linux compile [https://sourceforge.net/p/elphel/cp210x_gpio/ci/master/tree/ this driver], connect camera to PC, reload the driver then type:
- ./cp210x_gpio.py 0x6;
- ./cp210x_gpio.py 0xe;
-{|
-|[[File:Recover mmc.jpeg|130px|thumb|Fig.2 Recovery μSD card ('cut' corner) - enforces the system board to boot from it]]
-|}
==<font color="blue">Command line access</font>== ==<font color="blue">Command line access</font>==
Oleg
Boot options 393
Other boot options:
New page
==<font color="blue">Description</font>==Normally camera boots from the internal NAND flash memory, and it is always possible to boot it from the micro SD card, so even corruption of files on the internal flash will not "brick" the system. There are no buttons or switches on the camera - it should be instructed to change the boot source. Always booting from micro SD is not practical - in that case it would not be possible to leave a non-bootable card (intended just for image/video storage) in the camera slot.
There are two ways to switch camera to the micro SD boot mode.
One requires camera to be connected to the host computer with the USB cable (micro USB socket under the network jack - marked "console" on the picture). There is an internal USB-to-serial converter in the camera (CP2103) that offers 4 additional GPIO signals in addition to just the serial connection. One of these signals selects the boot source (GPIO0 - 0 - MMC, 1 - NAND), another (GPIO3 - 0 reset, 1 - normal operation). Unfortunately GPIO control of the CP2103 is not in a mainline cp210x Linux driver so this functionality requires a modified version (see instructions below).
Another way to "tell" the camera to boot from the μSD card instead of the internal NAND flash is to use a mechanically modified card or card adapter (such cards are provided with the camera). Standard specifies two alternative ways for detection of the card presence - one is a mechanical switch (closed when the card is inserted), another is a pull-up resistor on a data line. Camera uses both signals at boot time to determine the boot source:
* Switch not closed, pull-up resistor not detected -> no card present, boot from the internal NAND flash
* Switch closed -> data (non-bootable) card present, boot from the internal NAND flash
* Switch not closed, pull-up resistor is detected -> bootable card present, boot from the MMC card
{|
|[[File:Recover mmc.jpeg|130px|thumb|Fig.1 Recovery μSD card ('cut' corner) - forces the system board to boot from it]]
|}
==<font color="blue">Boot instructions</font>==
===Internal NAND flash (default)===
* Make sure the recovery card is not inserted
* Power on
===Recovery micro SD card===
Requirements:
* A modified card that doesn't lock the mechanical CD pin in the slot - it's done by carefully filing off the corner (see Fig.1) - most cards have circuitry there and get damaged. Use the one that came with the camera or order a new one.
Instructions:
* insert the card, power on
===Regular micro SD card===
Requirements:
* μUSB-to-USB cable
* Linux: compile [https://sourceforge.net/p/elphel/cp210x_gpio/ci/master/tree/ cp210x driver]
Instructions:
* Power on
* Connect the camera's console port (see Fig.2, right under the μSD slot) to PC using μUSB-to-USB cable
{|
|[[File:NC393-CS marked ports.jpeg|thumb|200px|Fig.2 10393 camera ports]]
|}
* Reload the cp210x driver:
** unplug the μUSB-to-USB cable
** In the terminal from the directory where the driver was built, run:
sudo rmmod cp210x
sudo insmod cp210x.ko
** plug the cable back (the driver will stay loaded until the PC is rebooted).
* In the terminal from the directory where the driver was built, run:
./cp210x_gpio.py 0x6;
./cp210x_gpio.py 0xe;
* To reboot back to NAND flash w/o power cycling:
./cp210x_gpio.py 0x7;
./cp210x_gpio.py 0xf;
===Other boot options===
The instructions are defined by the 3 options above.
They define where the camera will load the u-boot, device tree and kernel from: μSD card or NAND flash. The location of rootfs ("/") is set in the device tree. Available locations for rootfs:
* '''any μSD card partition'''. The default device tree parameter is:
bootargs = "cma=336M console=ttyPS0,115200 root=/dev/mmcblk0p2 rw ip=192.168.0.9 earlyprintk rootwait rootfstype=ext4";
* '''any internal NAND flash partition'''. The default parameter is:
bootargs = "cma=336M console=ttyPS0,115200 root=ubi0:elphel393-rootfs rw ip=192.168.0.9 earlyprintk rootwait rootfstype=ubifs ubi.mtd=4,2048";
* '''any internal SSD''' (if installed) partition. There is no default device tree.
* '''RAM''' - unpack an archive from a μSD card FAT32 partition into RAM but it was tested a while ago:
bootargs = "cma=336M console=ttyPS0,115200 root=/dev/ram rw ip=192.168.0.9 earlyprintk ramdisk_size=262144";
'''To build a custom device tree''', see [http://wiki.elphel.com/index.php?title=Poky_2.0_manual SDK manual]'''
==<font color="blue">cp210x_gpio.py -h</font>==
$./cp210x_gpio.py -h
usage: cp210x_gpio.py [-h] [-d DEVICE] [-m MASK] [gpio_value]
positional arguments:
gpio_value hex value for GPIO. Example (GPIO[3:0]): 0xf - all
1's, 0x0 - all 0's. If not specified - read GPIO only
optional arguments:
-h, --help show this help message and exit
-d DEVICE, --device DEVICE
USB device. Default: /dev/ttyUSB0
-m MASK, --mask MASK hex value for masking out GPIO bits: 1 - enable
rewrite, 0 - disable. Example (GPIO[3:0]): -m 0xf
[[Category:393]] Oleg
Boot options 393
New page
==<font color="blue">Description</font>==Normally camera boots from the internal NAND flash memory, and it is always possible to boot it from the micro SD card, so even corruption of files on the internal flash will not "brick" the system. There are no buttons or switches on the camera - it should be instructed to change the boot source. Always booting from micro SD is not practical - in that case it would not be possible to leave a non-bootable card (intended just for image/video storage) in the camera slot.
There are two ways to switch camera to the micro SD boot mode.
One requires camera to be connected to the host computer with the USB cable (micro USB socket under the network jack - marked "console" on the picture). There is an internal USB-to-serial converter in the camera (CP2103) that offers 4 additional GPIO signals in addition to just the serial connection. One of these signals selects the boot source (GPIO0 - 0 - MMC, 1 - NAND), another (GPIO3 - 0 reset, 1 - normal operation). Unfortunately GPIO control of the CP2103 is not in a mainline cp210x Linux driver so this functionality requires a modified version (see instructions below).
Another way to "tell" the camera to boot from the μSD card instead of the internal NAND flash is to use a mechanically modified card or card adapter (such cards are provided with the camera). Standard specifies two alternative ways for detection of the card presence - one is a mechanical switch (closed when the card is inserted), another is a pull-up resistor on a data line. Camera uses both signals at boot time to determine the boot source:
* Switch not closed, pull-up resistor not detected -> no card present, boot from the internal NAND flash
* Switch closed -> data (non-bootable) card present, boot from the internal NAND flash
* Switch not closed, pull-up resistor is detected -> bootable card present, boot from the MMC card
{|
|[[File:Recover mmc.jpeg|130px|thumb|Fig.1 Recovery μSD card ('cut' corner) - forces the system board to boot from it]]
|}
==<font color="blue">Boot instructions</font>==
===Internal NAND flash (default)===
* Make sure the recovery card is not inserted
* Power on
===Recovery micro SD card===
Requirements:
* A modified card that doesn't lock the mechanical CD pin in the slot - it's done by carefully filing off the corner (see Fig.1) - most cards have circuitry there and get damaged. Use the one that came with the camera or order a new one.
Instructions:
* insert the card, power on
===Regular micro SD card===
Requirements:
* μUSB-to-USB cable
* Linux: compile [https://sourceforge.net/p/elphel/cp210x_gpio/ci/master/tree/ cp210x driver]
Instructions:
* Power on
* Connect the camera's console port (see Fig.2, right under the μSD slot) to PC using μUSB-to-USB cable
{|
|[[File:NC393-CS marked ports.jpeg|thumb|200px|Fig.2 10393 camera ports]]
|}
* Reload the cp210x driver:
** unplug the μUSB-to-USB cable
** In the terminal from the directory where the driver was built, run:
sudo rmmod cp210x
sudo insmod cp210x.ko
** plug the cable back (the driver will stay loaded until the PC is rebooted).
* In the terminal from the directory where the driver was built, run:
./cp210x_gpio.py 0x6;
./cp210x_gpio.py 0xe;
==<font color="blue">cp210x_gpio.py -h</font>==
$./cp210x_gpio.py -h
usage: cp210x_gpio.py [-h] [-d DEVICE] [-m MASK] [gpio_value]
positional arguments:
gpio_value hex value for GPIO. Example (GPIO[3:0]): 0xf - all
1's, 0x0 - all 0's. If not specified - read GPIO only
optional arguments:
-h, --help show this help message and exit
-d DEVICE, --device DEVICE
USB device. Default: /dev/ttyUSB0
-m MASK, --mask MASK hex value for masking out GPIO bits: 1 - enable
rewrite, 0 - disable. Example (GPIO[3:0]): -m 0xf
[[Category:393]] Oleg
Tmp manual
← Older revision
Revision as of 00:48, 16 December 2016
(6 intermediate revisions not shown)Line 1:
Line 1:
+==<font color="blue">In the package</font>==
+* 10393 system
+{|
+|[[File:NC393-CS marked ports.jpeg|thumb|200px]]
+|}
+* Power supply wall adapter (48V)
+* CAT6 network cable
+* μUSB-to-USB cable
+* Recovery μSD card
+
+==<font color="blue">Power on</font>==
+* Plug in the power supply
+* Connect to LAN using the network cable
+
+NOTE: the boot time is ~30s
+
==<font color="blue">Connections</font>== ==<font color="blue">Connections</font>==
* Connect [[FPC_cables|sensors to system board]] - FPC cables are not symmetrical * Connect [[FPC_cables|sensors to system board]] - FPC cables are not symmetrical
Line 6:
Line 22:
|} |}
* [[10393_power|Power supply]] * [[10393_power|Power supply]]
+
+==<font color="blue">Important Notes</font>==
+* As of 2016/12/15, the software supports only 5MPix sensors, for 14MPix, please see:
+**[http://wiki.elphel.com/index.php?title=Tmp_manual&oldid=14676 older version of this manual with links to older software images]
==<font color="blue">Defaults</font>== ==<font color="blue">Defaults</font>==
-IP addr: <b>192.168.0.9</b> (old: 192.168.0.8)
-user / pwd: root / <empty>+{| class="wikitable"
+|-
+! IP Address
+| 192.168.0.9
+|-
+! User
+| root
+|-
+! Password
+| pass
+|}
-* (current) The address is set in the ''/etc/init_elphel393.sh'' in rootfs.+* The IP address is set in the ''/etc/elphel393/init_elphel393.py'' in the currenly mounted rootfs ("/").
-* (old) The address is set in the ''init_elphel393.sh'' script on the card's FAT32 partition.+
-==<font color="blue">init_elphel393.sh</font>==+==<font color="blue">init_elphel393.py</font>==
-* ''/etc/init_elphel393.sh''+* /etc/elphel393/init_elphel393.py
-* Change SENSOR_TYPE (boots but no images if incorrectly set):+
-** SENSOR_TYPE=5 - for 5MPix sensors+
-** SENSOR_TYPE=14 - for 14MPix+
-<b>NOTE: 5 & 14 MPix sensors cannot be mixed - require different bitstreams.</b>+
-* Change the default IP address+
==<font color="blue">Boot</font>== ==<font color="blue">Boot</font>==
Oleg
Tmp manual
← Older revision
Revision as of 00:21, 16 December 2016
(5 intermediate revisions not shown)Line 6:
Line 6:
|} |}
* [[10393_power|Power supply]] * [[10393_power|Power supply]]
+
+==<font color="blue">Important Notes</font>==
+* As of 2016/12/15, the software supports only 5MPix sensors, for 14MPix, please see:
+**[http://wiki.elphel.com/index.php?title=Tmp_manual&oldid=14676 older version of this manual with links to older software images]
==<font color="blue">Defaults</font>== ==<font color="blue">Defaults</font>==
-IP addr: <b>192.168.0.9</b> (old: 192.168.0.8)
-user / pwd: root / <empty>+{| class="wikitable"
+|-
+! IP Address
+| 192.168.0.9
+|-
+! User
+| root
+|-
+! Password
+| pass
+|}
-* (current) The address is set in the ''/etc/init_elphel393.sh'' in rootfs.+* The IP address is set in the ''/etc/elphel393/init_elphel393.py'' in the currenly mounted rootfs ("/").
-* (old) The address is set in the ''init_elphel393.sh'' script on the card's FAT32 partition.+
-==<font color="blue">init_elphel393.sh</font>==+==<font color="blue">init_elphel393.py</font>==
-* ''/etc/init_elphel393.sh''+* /etc/elphel393/init_elphel393.py
-* Change SENSOR_TYPE (boots but no images if incorrectly set):+
-** SENSOR_TYPE=5 - for 5MPix sensors+
-** SENSOR_TYPE=14 - for 14MPix+
-<b>NOTE: 5 & 14 MPix sensors cannot be mixed - require different bitstreams.</b>+
-* Change the default IP address+
==<font color="blue">Boot</font>== ==<font color="blue">Boot</font>==
Oleg
10393 power
← Older revision
Revision as of 23:58, 15 December 2016
(One intermediate revision not shown)Line 5:
Line 5:
* camera's DC-DC converter installed: TRACO POWER THD 12-4810WI, IN 18-75V, OUT 3.3V/3500mA * camera's DC-DC converter installed: TRACO POWER THD 12-4810WI, IN 18-75V, OUT 3.3V/3500mA
===Notes=== ===Notes===
-* For 48V the recommended connector is '''J3'''+* For 48V the recommended connector is '''J3''' (accessible from the back panel)
==9-36V (12V)== ==9-36V (12V)==
Line 11:
Line 11:
===Notes=== ===Notes===
-* <font color='red'>For 12V the recommended connector is '''J4''' - bypassing diodes reduces voltage drop and the chances of not hitting the lower voltage limit are better.</font>+* <font color='red'>For 12V the recommended connector is '''J4''' - bypassing diodes reduces voltage drop and the chances of not hitting the lower voltage limit are higher.</font>
* For 18+ V the recommended connector is '''J3''' * For 18+ V the recommended connector is '''J3'''
Oleg
File:10385 18-75V top sm.png
uploaded a new version of "[[File:10385 18-75V top sm.png]]"
Oleg
File:10385 bottom sm.png
uploaded a new version of "[[File:10385 bottom sm.png]]"
Oleg
File:10385 18-75V top.png
uploaded a new version of "[[File:10385 18-75V top.png]]"
Oleg
File:10385 9-36V top.png
uploaded a new version of "[[File:10385 9-36V top.png]]"
Oleg
File:10385 bottom.png
uploaded a new version of "[[File:10385 bottom.png]]"
Oleg