summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMilosz Wasilewski <milosz.wasilewski@linaro.org>2015-12-16 15:29:07 +0000
committerMilosz Wasilewski <milosz.wasilewski@linaro.org>2015-12-16 15:29:07 +0000
commit35c4e6047d7011fbc3c0c55242494a3c01a7ee28 (patch)
tree77378eff4244c00a633198ce49c416eb12ef8080
parentc28dfe4d248f7e7082e63c056b3af5e154b601b0 (diff)
Android: Linux: serial console test case unification
Change-Id: If1825f91667468fe09980ac201590790c449a753 Signed-off-by: Milosz Wasilewski <milosz.wasilewski@linaro.org>
-rw-r--r--generic/android/serial-console.yaml39
-rw-r--r--generic/linux/serial-console.yaml37
-rw-r--r--generic/serial-console.yaml41
3 files changed, 41 insertions, 76 deletions
diff --git a/generic/android/serial-console.yaml b/generic/android/serial-console.yaml
deleted file mode 100644
index 97ea267..0000000
--- a/generic/android/serial-console.yaml
+++ /dev/null
@@ -1,39 +0,0 @@
-metadata:
- name: andriod-serial-console
- format: "Manual Test Definition 1.0"
- description: "Test if the serial connection to the board works well"
- maintainer:
- - amit.khare@linaro.org
- os:
- - android
- scope:
- - functional
- devices:
- - panda
- - panda-es
- - vexpress-a9
- - vexpress-tc2
- - arndale
- - hikey
- environment:
- - manual-test
-
-run:
- steps:
- - Connect the serial cable.
- - Install minicom on host PC.
- - "$ sudo apt-get install minicom"
- - Launch minicom run "$ sudo minicom -s"
- - Set data transfer speed to "115200 8N1". For ARM Versatile Express board, it is "38400 8N1"
- - Save and exit minicom.
- - Re-launch minicom and run "$sudo minicom"
- - Power on and boot the board under test.
- - For Hikey board, If the 4 pin jumper block for UART0 is installed, attach a serial terminal and
- ensure the console is displayed on the serial terminal. If a mezzanine board is available for UART1,
- install it, attach a serial terminal and ensure the console is displayed on the serial terminal.
-
-
- expected:
- - "Verify that the output looks good."
- - "Verify that you can type in serial console."
-
diff --git a/generic/linux/serial-console.yaml b/generic/linux/serial-console.yaml
deleted file mode 100644
index cf90059..0000000
--- a/generic/linux/serial-console.yaml
+++ /dev/null
@@ -1,37 +0,0 @@
-metadata:
- name: serial-console
- format: "Manual Test Definition 1.0"
- description: "Test if the serial connection to the board works"
- maintainer:
- - amit.khare@linaro.org
- os:
- - ubuntu
- - openembedded
- scope:
- - functional
- devices:
- - panda
- - panda-es
- - vexpress-a9
- - vexpress-tc2
- - arndale
- - ifc6410
- - hikey
- environment:
- - manual-test
-
-run:
- steps:
- - Connect the Serial Cable.
- - Launch minicom in terminal of host PC.
- - "$ minicom -D /dev/ttyUSB0 -w -C minicom_log.txt"
- - "$ sudo screen /dev/ttyUSB0 115200"
- - Boot the board.
- - After boot sequence is complete run
- - "$ ls -l"
-
- expected:
- - "Boot log should be shown in serial console after powering the board"
- - "The boot log and command line prompt at the end should look like this: root@linaro-developer:~#"
- - "Input by keyboard in serial console should work and characters should be echoed back and displayed in minicom"
-
diff --git a/generic/serial-console.yaml b/generic/serial-console.yaml
new file mode 100644
index 0000000..7b1f29b
--- /dev/null
+++ b/generic/serial-console.yaml
@@ -0,0 +1,41 @@
+metadata:
+ name: serial-console
+ format: "Manual Test Definition 1.0"
+ description: "Test if the serial connection to the board works"
+ maintainer:
+ - amit.khare@linaro.org
+ os:
+ - android
+ - ubuntu
+ - openembedded
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - vexpress-a9
+ - vexpress-tc2
+ - juno
+ - arndale
+ - ifc6410
+ - hi6220-hikey
+ - apq8016-sbc
+ environment:
+ - manual-test
+
+run:
+ steps:
+ # depending on the board, the serial cable might be UART or symmetric serial
+ - Connect the serial cable to the device under test
+ - Launch minicom in terminal of host PC.
+ # correct tty should be used. /dev/ttyUSB0 is just an example
+ - "$ minicom -D /dev/ttyUSB0 -w -C minicom_log.txt"
+ - Power the device under test
+ - After boot sequence is complete run the following command in the console
+ - "$ ls -l"
+
+ expected:
+ - Boot log is displayed in minicom after powering the device under test
+ - Command line prompt is displayed after successful boot.
+ - Input by keyboard in works and characters are echoed back and displayed in minicom
+