From 4f6fb8c3620aa2aca2132fa793e9eaf69bf289af Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Fri, 18 Apr 2014 09:08:55 -0700 Subject: dev-manual: Updates to "Performing Automated Runtime Testing" Fixes [YOCTO #5554] I worked with Stefan here to update the section on running tests. We are good now with it all. (From yocto-docs rev: 806a89f1ddd3efc39d15d3f7e1a01e8fd69af7c1) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- .../dev-manual/dev-manual-common-tasks.xml | 74 ++++++++++++++++++++-- 1 file changed, 69 insertions(+), 5 deletions(-) (limited to 'documentation/dev-manual') diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml index 08237ea9ac..01cfd92222 100644 --- a/documentation/dev-manual/dev-manual-common-tasks.xml +++ b/documentation/dev-manual/dev-manual-common-tasks.xml @@ -5801,13 +5801,31 @@ (or something similar) is installed. Also, your hardware under test must be in a DHCP-enabled network that gives it the same IP - address for each reboot. + address for each reboot. + If you choose "GummibootTarget", there are + additional requirements and considerations. + See the + "Selecting GummibootTarget" + section, which follows, for more information. + + +
+ Selecting GummibootTarget + + + If you did not set TEST_TARGET to + "GummibootTarget", then you do not need any information + in this section. + You can skip down to the + "Running Tests" + section. + - If you set TEST_TARGET to + If you did set TEST_TARGET to "GummibootTarget", you also need to perform a one-time setup of your master image by doing the following: @@ -5821,11 +5839,57 @@ Build the master image: Build the core-image-testmaster image. + The core-image-testmaster + recipe is provided as an example for a + "master" image and you can customize the image + recipe as you would any other recipe. + + Here are the image recipe requirements: + + Inherits + core-image + so that kernel modules are installed. + + Installs normal linux utilities + not busybox ones (e.g. + bash, + coreutils, + tar, + gzip, and + kmod). + + Uses a custom + initramfs image with a custom installer. + A normal image that you can install usually + creates a single rootfs partition. + This image uses another installer that + creates a specific partition layout. + Not all Board Support Packages (BSPs) + can use an installer. + For such cases, you need to manually create + the following partition layout on the + target: + + First partition mounted + under /boot, + labeled "boot". + + The main rootfs + partition where this image gets + installed, which is mounted under + /. + + Another partition + labeled "testrootfs" where test + images get deployed. + + + + Install image: - Install the image on the target system. - <Need some clarification here from Stefan, - partition layout, etc.> + Install the image that you just built on the target + system. -- cgit v1.2.3-54-g00ecf