X-Git-Url: https://gerrit.automotivelinux.org/gerrit/gitweb?a=blobdiff_plain;f=README.md;h=dd08bc21dc809bb2276c1546b117a7188a3ec4e3;hb=2ef3a253290cee25348b37d536a1c8580d420da4;hp=4b97f74275b4d0cec81bd3e171709551439999a5;hpb=0ef8a183969cc9c3c51feb7dca5025e5773840f5;p=AGL%2Fmeta-agl-demo.git diff --git a/README.md b/README.md index 4b97f7427..dd08bc21d 100644 --- a/README.md +++ b/README.md @@ -29,7 +29,7 @@ URI: git://git.yoctoproject.org/poky > revision: df87cb27efeaea1455f20692f9f1397c6fcab254 URI: git://git.openembedded.org/meta-openembedded -> layer: meta-oe +> layer: meta-oe, meta-multimedia, meta-ruby > branch: dizzy > revision: 9efaed99125b1c4324663d9a1b2d3319c74e7278 @@ -39,7 +39,7 @@ URI: https://gerrit.automotivelinux.org/gerrit/AGL/meta-agl > (or later) URI: https://github.com/meta-qt5/meta-qt5.git -> branch: dizzy +> branch: jethro (b/c of qt-5.5.x) > revision: adeca0db212d61a933d7952ad44ea1064cfca747 ## The Renesas R-Car Gen2 (Porter) board depends in addition on: ## @@ -72,18 +72,18 @@ These packagegroups contains packages for application framework of AGL Distro. Subsystem should maintain ``packagegroup-agl-appfw-[subsystem].bb`` which should hold sufficient packages for application framework of AGL Distro. -Subsystems also can maintain thier own packagegroups under appropriate +Subsystems also can maintain their own packagegroups under appropriate ``recipes-*/``. For example, Qt5 has 2 packagegroups in ``meta-agl-demo``, -``packagegroup-agl-appfw-native-qt5`` and ``pacakgegroup-agl-demo-qt-examples`` +``packagegroup-agl-appfw-native-qt5`` and ``packagegroup-agl-demo-qt-examples`` which are under ``recipes-qt/``. The ``packagegroup-agl-appfw-native-qt5`` is included by -``pacakgegroup-agl-appfw-native`` because Qt5 belongs to native application +``packagegroup-agl-appfw-native`` because Qt5 belongs to native application framework of AGL Distro. -The ``pacakgegroup-agl-demo-qt-examples`` is added to local.conf if needed +The ``packagegroup-agl-demo-qt-examples`` is added to local.conf if needed because they are not mandatory for AGL application framework and AGL Demo Platform. @@ -151,6 +151,16 @@ You can build a QEMU image using the following steps: 2. Build the full image of AGL Demo Platform and applications $ bitbake agl-demo-platform + 2a. If you want to run QEMU directly as VM in Virtual Box or your other favorite VM software then add this line to your "conf/local.conf" file. +IMAGE_FSTYPES += "vmdk" + + 2b. The Weston IVI-Shell always gets built ; it will not be started, however, unless you specify the following in your "conf/local.conf" file : + +IMAGE_INSTALL_append = " \ + weston-ivi-shell-config \ + " + or you manually overwrite the "/etc/xdg/weston/weston.ini" file with a correct one. + 3. Run the emulator. The path for the emulator (runqemu) was added during the envsetup. $ cd tmp/deploy/images/qemex86-64 $ runqemu bzImage-qemux86-64.bin agl-demo-platform-qemux86-64.ext3 @@ -159,7 +169,20 @@ You can build a QEMU image using the following steps: $ runqemu bzImage-qemux86-64.bin agl-demo-platform-qemux86-64.ext3 \ bootparams="uvesafb.mode_option=1280x720-32" -5. Some weston samples are available from weston terminal. + To extend the amount of memory, add to runqemu: + qemuparams="-m 512" + + To separate console from VGA screen (to avoid corrupt screen while booting), + add to runqemu: + serial + + or use the virtual disk in Virtual Box from this location: + tmp/deploy/images/qemux86-64/agl-demo-platform-qemux86-64.vmdk + +4. Some weston samples are available from weston terminal. + + + Build a R-Car M2 (porter) image ------------------------------- @@ -251,7 +274,7 @@ NOTE: These instructions are based on GENIVI wiki, [here](http://wiki.projects.g 4. After the copy finished, unmount SD-Card and insert it into the SD-Card slot of the porter board. -#### Instructions on the host +#### Instructions on the target board NOTE: There is details about porter board [here](http://elinux.org/R-Car/Boards/Porter). @@ -316,3 +339,76 @@ NOTE: To boot weston on porter board, we need keyboard and mouse. (USB2.0 can be queue ! omxh264dec no-copy=true ! v4l2sink device=/dev/video1 \ io-mode=userptr d. ! queue ! faad ! alsasink device=hw:0,0 +### Deployment (TFTP/NFS) + +NOTE: These instructions are based on Embedded Linux Wiki, [here](http://www.elinux.org/R-Car/Boards/Yocto#Loading_kernel_via_TFTP_and_rootfs_via_NFS). And a Debian (wheezy, ip: 192.168.30.70) is used as the host for this instructions. + +#### Instructions on the host +1. Setup a TFTP server + 1. Install necessary packages + $ sudo apt-get install tftp tftpd-hpa + 2. Go to build directory, and copy kernel and DTB into TFTP server root (default server dir: /srv/tftp) + $ cd $AGL_TOP/build/tmp/deploy/images/porter + $ sudo cp uImage uImage-r8a7791-porter.dtb /srv/tftp + 3. Verify TFTP server is working + $ ls uImage + ls: cannot access uImage: No such file or directory + $ cd /tmp/ + $ tftp 192.168.30.70 + tftp> get uImage + Received 3583604 bytes in 0.2 seconds + tftp> q + $ ls uImage + uImage + +2. set NFS server + 1. Install necessary packages + $ sudo apt-get install nfs-kernel-server nfs-common + 2. Go to build directory, and extract the root file system into a dedicated directory (here we use /nfs/porter) + $ cd $AGL_TOP/build/tmp/deploy/images/porter + $ sudo mkdir -p /nfs/porter + $ sudo tar --extract --numeric-owner --preserve-permissions --preserve-order \ + --totals --directory=/nfs/porter --file=agl-demo-platform-porter.tar.bz2 + 3. Edit /etc/exports + $ sudo vi /etc/exports + Add + /nfs/porter *(rw,no_subtree_check,sync,no_root_squash,no_all_squash) + Save the file and exit. + 4. Restart nfs service + $ sudo service nfs-kernel-server restart + 5. Verify NFS server is working + $ sudo mount -t nfs 192.168.30.70:/nfs/porter /tmp/ + $ ls /tmp + bin boot dev etc home lib media mnt proc run sbin sh-thd-430987335390 sys tmp usr var + +#### Instructions on the target board + +NOTE: There is details about porter board [here](http://elinux.org/R-Car/Boards/Porter). + +NOTE: To boot weston on porter board, we need keyboard and mouse. (USB2.0 can be use for this) + +##### Change U-Boot parameters to boot from TFTP/NFS + +1. Power up the board and, using your preferred terminal emulator, stop the board's autoboot by hitting any key. + + > Debug serial settings are 38400 8N1. Any standard terminal emulator program can be used. + +2. Set the follow environment variables and save them + => setenv ipaddr + => setenv serverip + => setenv bootargs_console console=ttySC6,${baudrate} + => setenv bootargs_video vmalloc=384M video=HDMI-A-1:1024x768-32@60 + => setenv bootcmd_net 'tftp 0x40007fc0 uImage; tftp 0x40f00000 uImage-r8a7791-porter.dtb' + => setenv bootcmd 'setenv bootargs ${bootargs_console} ${bootargs_video} ip=${ipaddr} root=/dev/nfs nfsroot=${serverip}:/nfs/porter,vers=3;run bootcmd_net;bootm 0x40007fc0 - 0x40f00000' + => saveenv + + Replace with a proper IP address for the board, like 192.168.30.60. + Replace with the IP address of the host, here we use 192.168.30.70. + +##### Boot from TFTP/NFS + +1. After board reset, U-Boot is started and after a countdown, ... + Linux boot message should be displayed. Please wait a moment. +2. Then weston is booted automatically, and weston-terminal appears. + +3. Have fun! :)