diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index 9565b1b950..0123d84e69 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -7742,8 +7742,7 @@ Gateways via their Web Interfaces"
TEST_TARGET to an appropriate value.
For QEMU, you do not have to change anything, the default
value is "QemuTarget".
- For running tests on hardware, two options exist:
- "SimpleRemoteTarget" and "GummibootTarget".
+ For running tests on hardware, the following options exist:
"SimpleRemoteTarget":
Choose "SimpleRemoteTarget" if you are going to
@@ -7770,6 +7769,45 @@ Gateways via their Web Interfaces"
"Selecting GummibootTarget"
section, which follows, for more information.
+ "BeagleBoneTarget":
+ Choose "BeagleBoneTarget" if you are deploying
+ images and running tests on the BeagleBone
+ "Black" or original "White" hardware.
+ For information on how to use these tests, see the
+ comments at the top of the BeagleBoneTarget
+ meta-yocto-bsp/lib/oeqa/controllers/beaglebonetarget.py
+ file.
+
+ "EdgeRouterTarget":
+ Choose "EdgeRouterTarget" is you are deploying
+ images and running tests on the Ubiquiti Networks
+ EdgeRouter Lite.
+ For information on how to use these tests, see the
+ comments at the top of the EdgeRouterTarget
+ meta-yocto-bsp/lib/oeqa/controllers/edgeroutertarget.py
+ file.
+
+ "GrubTarget":
+ Choose the "supports deploying images and running
+ tests on any generic PC that boots using GRUB.
+ For information on how to use these tests, see the
+ comments at the top of the GrubTarget
+ meta-yocto-bsp/lib/oeqa/controllers/grubtarget.py
+ file.
+
+ "your-target":
+ Create your own custom target if you want to run
+ tests when you are deploying images and running
+ tests on a custom machine within your BSP layer.
+ To do this, you need to add a Python unit that
+ defines the target class under
+ lib/oeqa/controllers/ within
+ your layer.
+ You must also provide an empty
+ __init__.py.
+ For examples, see files in
+ meta-yocto-bsp/lib/oeqa/controllers/.
+
@@ -7880,10 +7918,14 @@ Gateways via their Web Interfaces"
+
+
+
+ Power Control
- Here is some additional information regarding running
- "GummibootTarget" as your test target:
+ For most hardware targets other than SimpleRemoteTarget,
+ you can control power:
You can use
@@ -7928,6 +7970,63 @@ Gateways via their Web Interfaces"
some manual interaction is okay from time to time.
+ If you have no hardware to automatically perform power
+ control but still wish to experiment with automated
+ hardware testing, you can use the dialog-power-control
+ script that shows a dialog prompting you to perform the
+ required power action.
+ This script requires either KDialog or Zenity to be
+ installed.
+ To use this script, set the
+ TEST_POWERCONTROL_CMD
+ variable as follows:
+
+ TEST_POWERCONTROL_CMD = "${COREBASE}/scripts/contrib/dialog-power-control"
+
+
+
+
+
+ Serial Console Connection
+
+
+ For test target classes requiring a serial console
+ to interact with the bootloader (e.g. BeagleBoneTarget,
+ EdgeRouterTarget, and GrubTarget), you need to
+ specify a command to use to connect to the serial console
+ of the target machine by using the
+ TEST_POWERCONTROL_CMD
+ variable and optionally the
+ TEST_SERIALCONTROL_EXTRA_ARGS
+ variable.
+
+
+
+ These cases could be a serial terminal program if the
+ machine is connected to a local serial port, or a
+ telnet or
+ ssh command connecting to a remote
+ console server.
+ Regardless of the case, the command simply needs to
+ connect to the serial console and forward that connection
+ to standard input and output as any normal terminal
+ program does.
+ For example, to use the picocom terminal program on
+ serial device /dev/ttyUSB0
+ at 115200bps, you would set the variable as follows:
+
+ TEST_SERIALCONTROL_CMD = "picocom /dev/ttyUSB0 -b 115200"
+
+ For local devices where the serial port device disappears
+ when the device reboots, an additional "serdevtry" wrapper
+ script is provided.
+ To use this wrapper, simply prefix the terminal command
+ with
+ ${COREBASE}/scripts/contrib/serdevtry:
+
+ TEST_SERIALCONTROL_CMD = "${COREBASE}/scripts/contrib/serdevtry picocom -b
+115200 /dev/ttyUSB0"
+