Difference between revisions of "Development for 10393"
From ElphelWiki
| Line 70: | Line 70: | ||
* change branch: ''edit elphel393/poky/build/conf/local.conf'' | * change branch: ''edit elphel393/poky/build/conf/local.conf'' | ||
ELPHEL393_branches += "elphel-apps-camogm:framepars" | ELPHEL393_branches += "elphel-apps-camogm:framepars" | ||
| + | |||
| + | ===Add new application project to environment=== | ||
| + | The best reference projects are in ''elphel393/rootfs-elphel/'' | ||
| + | * Place project files to ''elphel393/rootfs-elphel/'' | ||
| + | * Create a recipe in ''elphel393/meta/meta-elphel393/.../'' | ||
| + | * 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 | ||
===Kernel=== | ===Kernel=== | ||
Revision as of 16:00, 29 March 2017
Contents
Setup environment
Get sources and build default images: Instructions
setup.py
- clones all projects
- rerun to update all repositories - then rebuild with bitbake
- creates a working copy of projects-default.json - projects.json
check_versions.py
- compares software versions on the 10393 vs current sources
~$ ./check_versions.py root@192.168.0.9
Flash vs micro SD
- micro SD cards work best for development
- replaceable
- changes get written to the card, no extra sync required
- flash works best for a production system:
- non-replaceable
- limited write cycles
- because of overlayfs changes need an extra sync (overlay_sync) and a proper reboot to get written to the flash.
Environment tree
elphel393
├── bootable-images -> poky/build/tmp/deploy/images/elphel393/ - poky generated boot images
├── fpga-elphel - fpga projects, matching recipes are in meta/meta-elphel393/recipes-core/
│ ├── x359
│ ├── x393
│ └── x393_sata
├── linux-elphel - kernel - a kernel tree with Elphel's sources only - it is merged with the full kernel tree
├── meta - extra recipe layers for poky
│ ├── meta-elphel393 - Elphel's recipes: fpga, device tree, kernel and applications, lots of bbappends
│ ├── meta-ezynq - Elphel's recipes for u-boot
│ ├── meta-openembedded - recipes (like PHP) that were not included in poky 2.0
│ ├── meta-swupdate - swupdate recipes (not yet used)
│ └── meta-xilinx - Xilinx's recipes, help to build kernel and device tree
├── poky - poky tree
│ ├── build
│ │ └── conf
│ │ ├── bblayers.conf - paths to extra layers (generated by setup.py)
│ │ └── local.conf - have a look inside, local configuration (generated by setup.py)
│ └── meta - poky's recipes
├── rootfs-elphel - user applicatons projects and init scripts, matching recipes are found in meta/meta-elphel393/recipes-core/
│ ├── elphel-apps-autocampars - camera parameters manager - setup, store/restore, set default
│ ├── elphel-apps-autoexposure - autoexposure daemon
│ ├── elphel-apps-camogm - recorder program
│ ├── elphel-apps-editconf
│ ├── elphel-apps-gps - gps receiver application
│ ├── elphel-apps-histograms - histograms
│ ├── elphel-apps-imgsrv - image server
│ ├── elphel-apps-php-extension - php functions, compiled as a php extension (part of php recipe)
│ ├── elphel-apps-tempmon - temperature monitor
│ ├── elphel-init - system init script
│ ├── elphel-udev-rules - udev rules: drive automount
│ ├── elphel-web-393 - web GUIs
│ ├── elphel-web-camvc - main control GUI, ported from 353
│ └── elphel-web-hwmon - hardware monitor
└── tools
└── elphel-tools-update - useful scripts, e.g. create bootable mmc
Change repository address, branch, hash
- change uri: edit elphel393/projects.json
- change hash: edit elphel393/projects.json:
"elphel-apps-camogm":[ "https://git.elphel.com/Elphel/elphel-apps-camogm.git", "master","" <- leave empty to get the latest, add hash to freeze ],
- change branch: edit elphel393/poky/build/conf/local.conf
ELPHEL393_branches += "elphel-apps-camogm:framepars"
Add new application project to environment
The best reference projects are in elphel393/rootfs-elphel/
- Place project files to elphel393/rootfs-elphel/
- Create a recipe in elphel393/meta/meta-elphel393/.../
- 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
