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/04/27 10:41] rajmarshall [Procedure:] renumber sections |
civilinfrastructureplatform:cipsystembuildhowto [2018/11/21 16:06] (current) rajmarshall better line spacing |
||
|---|---|---|---|
| Line 4: | Line 4: | ||
| - | ===== 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 159: | Line 159: | ||
| 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 shmobile_defconfig | ||
| - | make -j4 -k -s ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- O=build-arm | + | make -j4 -k -s ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- O=build-arm |
| - | make -j4 -k -s ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- O=build-arm modules | + | |
| - | make -j4 -k -s ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- O=build-arm modules_install | + | |
| INFO: published artifacts | INFO: published artifacts | ||
| + | |||
| ... | ... | ||
| - | //cip-example/cip_v4.4.83/v4.4.83-cip8/arm/omap2plus_defconfig/dtbs/am335x-boneblack.dtb - fix!! // | + | cip-example/cip4.4.126/v4.4.126-cip22/arm/shmobile_defconfig/dtbs/r8a7743-iwg20d-q7.dtb |
| ... | ... | ||
| INFO: triggering build | INFO: triggering build | ||
| Line 176: | Line 175: | ||
| ''**<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. // | + | |
| + | //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. 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). | ||
| Line 184: | Line 184: | ||
| 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 **Tree name** (cip-example) and you will see the list of available builds, or kernel versions for that tree. | ||
| - | 14. 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). |
| 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: | 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: | ||
civilinfrastructureplatform/cipsystembuildhowto.1524825695.txt.gz · Last modified: 2018/04/27 10:41 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
