Development for 10393 - Revision history

Oleg: /* after building */

2020-09-16T19:07:23Z

after building

← Older revision		Revision as of 19:07, 16 September 2020
Line 125:		Line 125:
	=====after building=====		=====after building=====
	rootfs-elphel/elphel-init/		rootfs-elphel/elphel-init/
	├── <font color='green'>bitbake-logs -> /.../elphel393/poky/build/tmp/work/~~cortexa9~~-neon-poky-linux-gnueabi/init/1_0-60/temp</font>		├── <font color='green'>bitbake-logs -> /.../elphel393/poky/build/tmp/work/cortexa9t2hf-neon-poky-linux-gnueabi/init/1_0-69/temp</font>
	├── eclipse_project_setup		├── eclipse_project_setup
	├── <font color='green'>image -> /.../elphel393/poky/build/tmp/work/~~cortexa9~~-neon-poky-linux-gnueabi/init/1_0-60/image</font>		├── <font color='green'>image -> /.../elphel393/poky/build/tmp/work/cortexa9t2hf-neon-poky-linux-gnueabi/init/1_0-69/image</font>
	├── LICENSE		├── LICENSE
	├── Makefile		├── Makefile
Line 139:		Line 139:
	│ ├── init_eyesis_bottom2.sh		│ ├── init_eyesis_bottom2.sh
	│ └── Makefile		│ └── Makefile
	├── <font color='green'>sysroots -> /~~home~~/~~oleg~~/~~GIT~~/~~elphel393_fixold~~/poky/~~build~~/~~tmp~~/~~sysroots~~</font>		├── <font color='green'>sysroots -> /.../elphel393/poky/build/tmp/work/cortexa9t2hf-neon-poky-linux-gnueabi/init/1_0-69/recipe-sysroot</font>
	└── VERSION		└── VERSION

Oleg: /* after building */

2018-12-13T01:25:15Z

after building

← Older revision		Revision as of 01:25, 13 December 2018
Line 144:		Line 144:
	</font>		</font>

			At some point when building from command line the sysroots link will be created. After '''sysroots''' link is there the project can be build from Eclipse IDE

	[[Category:393]]		[[Category:393]]

Andrey.filippov: /* Flash vs micro SD */

2018-10-25T01:27:00Z

Flash vs micro SD

← Older revision		Revision as of 01:27, 25 October 2018
Line 33:		Line 33:
	** provisions are made to limit write cycles and to prevent inadvertent file system changes		** provisions are made to limit write cycles and to prevent inadvertent file system changes
	** overlayfs file system merges nonvolatile (flash) and volatile (ram disk) file systems, power-cycling discards all file modifications made during the last session		** overlayfs file system merges nonvolatile (flash) and volatile (ram disk) file systems, power-cycling discards all file modifications made during the last session
	** an extra sync command (overlay_sync) and a proper reboot is required to commit file system changes to the system flash memory (see [[10393_manual#Change_default_ip_address]]).		** an extra sync command (overlay_sync) and a proper reboot is required to commit file system changes to the system flash memory (see overlay_syn usage example [[10393_manual#Change_default_ip_address]]).

	===Environment tree===		===Environment tree===

Andrey.filippov: /* Flash vs micro SD */

2018-10-25T01:25:30Z

Flash vs micro SD

← Older revision		Revision as of 01:25, 25 October 2018
Line 33:		Line 33:
	** provisions are made to limit write cycles and to prevent inadvertent file system changes		** provisions are made to limit write cycles and to prevent inadvertent file system changes
	** overlayfs file system merges nonvolatile (flash) and volatile (ram disk) file systems, power-cycling discards all file modifications made during the last session		** overlayfs file system merges nonvolatile (flash) and volatile (ram disk) file systems, power-cycling discards all file modifications made during the last session
	** an extra sync command (overlay_sync) and a proper reboot is required to commit file system changes to the system flash memory.		** an extra sync command (overlay_sync) and a proper reboot is required to commit file system changes to the system flash memory (see [[10393_manual#Change_default_ip_address]]).

	===Environment tree===		===Environment tree===

Andrey.filippov: /* Flash vs micro SD */

2018-10-25T01:23:35Z

Flash vs micro SD

← Older revision		Revision as of 01:23, 25 October 2018
Line 31:		Line 31:
	* flash works best for a production system:		* flash works best for a production system:
	** non-replaceable		** non-replaceable
	** ~~limited~~ write cycles		** provisions are made to limit write cycles and to prevent inadvertent file system changes
	** ~~because of~~ overlayfs ~~changes need~~ an extra sync (overlay_sync) and a proper reboot to ~~get written~~ to the flash.		** overlayfs file system merges nonvolatile (flash) and volatile (ram disk) file systems, power-cycling discards all file modifications made during the last session
			** an extra sync command (overlay_sync) and a proper reboot is required to commit file system changes to the system flash memory.

	===Environment tree===		===Environment tree===

Oleg at 00:18, 30 March 2017

2017-03-30T00:18:02Z

← Older revision		Revision as of 00:18, 30 March 2017
Line 2:		Line 2:
	Get sources and build default images: [[Poky_2.0_manual#Setup\|Instructions]]		Get sources and build default images: [[Poky_2.0_manual#Setup\|Instructions]]

	====~~setup.py~~====		====top project====
	* ~~clones all projects~~		* [https://git.elphel.com/Elphel/elphel393.git elphel393.git]
	* rerun to update all repositories - then rebuild with bitbake
	* creates a working copy of projects-default.~~json - projects~~.~~json~~

	=~~===check_versions~~.py~~====~~		{\| class='wikitable'
	* ~~compares software versions on~~ the 10393 ~~vs current sources~~		!file
	~~~$ ./~~check_versions.py ~~root@192.168.0.9~~		!description
			\|-
			\| '''projects-default.json'''
			\|
			* list of cloned repositories and tree structure
			* copy of this file makes a working copy - '''projects.json'''
			\|-
			\| '''setup.py'''
			\|
			* creates a working copy from default and parses the contents
			* rerun to update all repositories - then rebuild using bitbake
			* generates a default ''local.conf'' for poky pre-configured for 10393
			\|-
			\| '''check_versions.py'''
			\| local repository vs running on target hardware version checker
			\|}

	===Flash vs micro SD===		===Flash vs micro SD===

Oleg: /* create new project */

2017-03-30T00:12:52Z

create new project

← Older revision		Revision as of 00:12, 30 March 2017
Line 80:		Line 80:

	===Applications===		===Applications===
	====~~create~~ new project====		====Create new project====
	The best reference projects are in ''elphel393/rootfs-elphel/''		The best reference projects are in ''elphel393/rootfs-elphel/''
	* Place project files to ''elphel393/rootfs-elphel/''		* Place project files to ''elphel393/rootfs-elphel/''

Oleg at 00:12, 30 March 2017

2017-03-30T00:12:35Z

← Older revision		Revision as of 00:12, 30 March 2017
Line 87:		Line 87:
	* bitbake core-image-elphel393		* bitbake core-image-elphel393

	===Project structure===		====Project structure====
	====recipe====		=====recipe=====
	elphel393/meta/meta-elphel393/recipes-core/init/init_1.0.bb		elphel393/meta/meta-elphel393/recipes-core/init/init_1.0.bb

	'''Note:''' The recipe and the project sources are in different repos		'''Note:''' The recipe and the project sources are in different repos

	====in repository====		=====in repository=====
	rootfs-elphel/elphel-init/		rootfs-elphel/elphel-init/
	├── eclipse_project_setup		├── eclipse_project_setup
Line 109:		Line 109:
	└── VERSION		└── VERSION

	====after building====		=====after building=====
	rootfs-elphel/elphel-init/		rootfs-elphel/elphel-init/
	├── <font color='green'>bitbake-logs -> /.../elphel393/poky/build/tmp/work/cortexa9-neon-poky-linux-gnueabi/init/1_0-60/temp</font>		├── <font color='green'>bitbake-logs -> /.../elphel393/poky/build/tmp/work/cortexa9-neon-poky-linux-gnueabi/init/1_0-60/temp</font>

Oleg: /* Projects structure */

2017-03-30T00:11:41Z

Projects structure

@@ Line 87: / Line 87: @@
 * bitbake core-image-elphel393
-===Projects structure===
+===Project structure===
 [[Category:393]]

Oleg at 00:10, 30 March 2017

2017-03-30T00:10:40Z

← Older revision		Revision as of 00:10, 30 March 2017
Line 71:		Line 71:
	ELPHEL393_branches += "elphel-apps-camogm:framepars"		ELPHEL393_branches += "elphel-apps-camogm:framepars"

	===Add new ~~application~~ project ~~to environment~~===
			===Kernel===
			====Add new driver====
			* examples in ''elphel393/linux-elphel/src''
			** add new files to the tree
			** do not forget KConfig and Makefiles
			** change kernel config in ''elphel393_fixold/meta/meta-elphel393/recipes-kernel/linux/config/elphel393.cfg'' - clean then rebuild the kernel. The cfg file gets copied to the poky's kernel build directory.

			===Applications===
			====create new project====
	The best reference projects are in ''elphel393/rootfs-elphel/''		The best reference projects are in ''elphel393/rootfs-elphel/''
	* Place project files to ''elphel393/rootfs-elphel/''		* Place project files to ''elphel393/rootfs-elphel/''
Line 77:		Line 86:
	* In the recipe set package name - it will go to the rootfs recipe ''elphel393/meta/meta-elphel393/recipes-core/images/'''''core-image-elphel393.bb'''		* In the recipe set package name - it will go to the rootfs recipe ''elphel393/meta/meta-elphel393/recipes-core/images/'''''core-image-elphel393.bb'''
	* bitbake core-image-elphel393		* bitbake core-image-elphel393

	~~===Kernel===~~

	~~===Applications===~~

	===Projects structure===		===Projects structure===