civilinfrastructureplatform:cipsystembuildhowto
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
civilinfrastructureplatform:cipsystembuildhowto [2018/02/16 15:04] rajmarshall |
civilinfrastructureplatform:cipsystembuildhowto [2018/11/21 16:06] (current) rajmarshall better line spacing |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Build the CIP System and Artifacts (4/5) ====== | ====== Build the CIP System and Artifacts (4/5) ====== | ||
| - | This set of instructions assumes you have already Setup and Configured the B@D Virtual Machine. If that is not the case please go back to the [[beagleboneblackboard | Beaglebone Black Setup & Configuration]]. | + | This set of instructions assumes you have already Setup and Configured the B@D Virtual Machine. If that is not the case please go back to the [[beagleboneblackboard | Beaglebone Black Setup & Configuration]] or the [[renesasboard| IWG20M Setup & Configuration]] depending on which board you are using. |
| - | ===== Creating an initramfs with BusyBox for the Beaglebone Black ===== | + | ===== Creating an initramfs with BusyBox for the board ===== |
| BusyBox combines tiny versions of many common UNIX utilities into a single small executable. It provides replacements for most of the utilities you usually find in GNU fileutils, shellutils, etc. BusyBox provides a fairly complete environment from which to boot any embedded system. | BusyBox combines tiny versions of many common UNIX utilities into a single small executable. It provides replacements for most of the utilities you usually find in GNU fileutils, shellutils, etc. BusyBox provides a fairly complete environment from which to boot any embedded system. | ||
| Line 11: | Line 11: | ||
| **Prerequisites:** | **Prerequisites:** | ||
| - | You must have the CIP Board-at-Desk Single-Developer (B@D) v1.0 Virtual Machine set up with make, gcc and the arm cross compilers. | + | You must have the CIP Board-at-Desk Single-Developer (B@D) Virtual Machine set up with make, gcc and the arm cross compilers. |
| 1. Connect to the B@D Virtual Machine. | 1. Connect to the B@D Virtual Machine. | ||
| Line 75: | Line 75: | ||
| - | **Make it available for the Beaglebone Black:** | + | **Make it available for the LAVA testing environment:** |
| 13. Copy the ''initramfs.cpio.gz'' to the ''initramfs'' directory where it can be retrieved by LAVA. | 13. Copy the ''initramfs.cpio.gz'' to the ''initramfs'' directory where it can be retrieved by LAVA. | ||
| Line 89: | Line 89: | ||
| ==== Prerequisites: ==== | ==== Prerequisites: ==== | ||
| - | * A working CIP Board-at-Desk Single-Developer (B@D) v1.0 Virtual Machine | + | * A working CIP Board-at-Desk Single-Developer (B@D) Virtual Machine |
| ==== Procedure: ==== | ==== Procedure: ==== | ||
| Line 109: | Line 109: | ||
| '' vagrant@guest:~/git-repos$ **git clone [[git://git.kernel.org/pub/scm/linux/kernel/git/bwh/linux-cip.git]]** '' | '' vagrant@guest:~/git-repos$ **git clone [[git://git.kernel.org/pub/scm/linux/kernel/git/bwh/linux-cip.git]]** '' | ||
| - | 4. Find the branch of the kernel version you want (We will use '4.4.69-cip4' for this example) | + | 4. Find the branch of the kernel version you want (We will use '4.4.83-cip8' for this example) |
| '' vagrant@guest:~/git-repos$ **cd linux-cip** '' | '' vagrant@guest:~/git-repos$ **cd linux-cip** '' | ||
| Line 139: | Line 139: | ||
| //Note: Don't forget the dash (-) at the end of the ''CROSS_COMPILE'' line!// | //Note: Don't forget the dash (-) at the end of the ''CROSS_COMPILE'' line!// | ||
| - | 7. Execute the ''build.py'' command, passing in the Beaglebone Black configuration. | + | 7. If using the Beaglebone Black execute the ''build.py'' command, passing in the Beaglebone Black configuration. |
| ''vagrant@guest:~/git-repos/linux-cip$ **~/kernelci-build/build.py -c omap2plus_defconfig -p CIP-KernelCI**'' | ''vagrant@guest:~/git-repos/linux-cip$ **~/kernelci-build/build.py -c omap2plus_defconfig -p CIP-KernelCI**'' | ||
| Line 154: | Line 154: | ||
| 202 | 202 | ||
| - | 8. Start the Kernel CI web server | + | 8. If using the Renesas IWG20M execute the ''build.py'' command, passing in the IWG20M configuration. |
| + | |||
| + | ''vagrant@guest:~/git-repos/linux-cip$ **~/kernelci-build/build.py -c shmobile_defconfig -p CIP-KernelCI**'' | ||
| + | |||
| + | make -j4 -k -s ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- O=build-arm shmobile_defconfig | ||
| + | make -j4 -k -s ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- O=build-arm | ||
| + | INFO: published artifacts | ||
| + | |||
| + | ... | ||
| + | cip-example/cip4.4.126/v4.4.126-cip22/arm/shmobile_defconfig/dtbs/r8a7743-iwg20d-q7.dtb | ||
| + | ... | ||
| + | INFO: triggering build | ||
| + | 202 | ||
| + | |||
| + | 9. Start the Kernel CI web server | ||
| ''vagrant@guest:**/vagrant/scripts/start_webserver.sh &**'' | ''vagrant@guest:**/vagrant/scripts/start_webserver.sh &**'' | ||
| - | 9. On your host machine, open a web browser and enter the following in the address box: | + | 10. On your host machine, open a web browser and enter the following in the address box: |
| ''**<nowiki>http://localhost:5000</nowiki>**'' | ''**<nowiki>http://localhost:5000</nowiki>**'' | ||
| - | // Note that if you are using Windows 10 as a host you will need to use either Chrome or Firefox as a browser as the Windows browsers do not work with the KernelCI webserver. // | ||
| - | 10. You will see the KernelCI Website home page from which you can navigate to the different builds and Trees that you've created (see the **Example Builds** section below). | + | //Note that if you are using Windows 10 as a host you will need to use either Chrome or Firefox as a browser for the Windows browsers do not work with the KernelCI webserver.// |
| + | |||
| + | 11. You will see the KernelCI Website home page from which you can navigate to the different builds and Trees that you've created (see the **Example Builds** section below). | ||
| - | 11. Click on the **Jobs** button at the top of the page and you will see all of the available Trees | + | 12. Click on the **Jobs** button at the top of the page and you will see all of the available Trees |
| - | 12. Click on the **Tree name** (cip-example) and you will see the list of available builds, or kernel versions for that tree. | + | 13. Click on the **Tree name** (cip-example) and you will see the list of available builds, or kernel versions for that tree. |
| - | 13. Click on the (for example) **v4.4.83** kernel and you will see the list of build configurations (omap2plus). | + | 14. Click on the (for example) **v4.4.83** kernel and you will see the list of build configurations (for example omap2plus). |
| - | 14. The files that resulted from the build are available in the KernelCI website by navigating to the Tree Name, Kernel version, and Configuration. They are stored on the hard drive at: | + | 15. The files that resulted from the build are available in the KernelCI website by navigating to the Tree Name, Kernel version, and Configuration. They are stored on the hard drive at: |
| ''/var/www/images/kernel-ci/TREE_NAME/KERNEL_VERSION/BRANCH/ARCH/CONFIG'' | ''/var/www/images/kernel-ci/TREE_NAME/KERNEL_VERSION/BRANCH/ARCH/CONFIG'' | ||
| Line 177: | Line 192: | ||
| === Example Builds === | === Example Builds === | ||
| - | 15. For instance, for the build with the following parameters: | + | 16. For instance, for the build with the following parameters: |
| * TREE_NAME: **cip-example** | * TREE_NAME: **cip-example** | ||
| Line 189: | Line 204: | ||
| ''/var/www/images/kernel-ci/cip-example/v4.4.83-cip8/cip_v4.4.83/arm/omap2plus'' | ''/var/www/images/kernel-ci/cip-example/v4.4.83-cip8/cip_v4.4.83/arm/omap2plus'' | ||
| - | 16. Kernel CI generates the following files. Make a note of the ones in **bold**. They will be needed for testing the CIP Kernel: | + | 17. Kernel CI generates the following files. Make a note of the ones in **bold**. They will be needed for testing the CIP Kernel: |
| * ''build.log'' shows the output of the build process to help track down any issues in compilation. | * ''build.log'' shows the output of the build process to help track down any issues in compilation. | ||
| Line 203: | Line 218: | ||
| * ''**dtbs**'' directory which holds all of the generated Device Tree Binary's. | * ''**dtbs**'' directory which holds all of the generated Device Tree Binary's. | ||
| - | 17. Check the [[civilinfrastructureplatform/ciptestingreferencetestcases|reference test cases]] and try them as reference examples. | + | 18. Check the [[civilinfrastructureplatform/ciptestingreferencetestcases|reference test cases]] and try them as reference examples. |
civilinfrastructureplatform/cipsystembuildhowto.1518793493.txt.gz · Last modified: 2018/02/16 15:04 by rajmarshall
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
