[U-Boot] [PATCH V2 4/7] test/py: test the md/mw commands

[Michal Simek <monstr@monstr.eu>]

On 2.12.2015 23:18, Stephen Warren wrote:
> This tests whether md/mw work, and affect each-other.
> 
> Command repeat is also tested.
> 
> test/cmd_repeat.sh is removed, since the new Python-based test does
> everything it used to.
> 
> Signed-off-by: Stephen Warren <swarren@wwwdotorg.org>
> Signed-off-by: Stephen Warren <swarren@nvidia.com>
> ---
>  test/cmd_repeat.sh | 29 -----------------------------
>  test/py/test_md.py | 29 +++++++++++++++++++++++++++++
>  2 files changed, 29 insertions(+), 29 deletions(-)
>  delete mode 100755 test/cmd_repeat.sh
>  create mode 100644 test/py/test_md.py
> 
> diff --git a/test/cmd_repeat.sh b/test/cmd_repeat.sh
> deleted file mode 100755
> index 990e79900f47..000000000000
> --- a/test/cmd_repeat.sh
> +++ /dev/null
> @@ -1,29 +0,0 @@
> -#!/bin/sh
> -
> -# Test for U-Boot cli including command repeat
> -
> -BASE="$(dirname $0)"
> -. $BASE/common.sh
> -
> -run_test() {
> -	./${OUTPUT_DIR}/u-boot <<END
> -setenv ctrlc_ignore y
> -md 0
> -
> -reset
> -END
> -}
> -check_results() {
> -	echo "Check results"
> -
> -	grep -q 00000100 ${tmp} || fail "Command did not repeat"
> -}
> -
> -echo "Test CLI repeat"
> -echo
> -tmp="$(tempfile)"
> -build_uboot
> -run_test >${tmp}
> -check_results ${tmp}
> -rm ${tmp}
> -echo "Test passed"
> diff --git a/test/py/test_md.py b/test/py/test_md.py
> new file mode 100644
> index 000000000000..2e67ed0a1de2
> --- /dev/null
> +++ b/test/py/test_md.py
> @@ -0,0 +1,29 @@
> +# Copyright (c) 2015 Stephen Warren
> +# Copyright (c) 2015, NVIDIA CORPORATION. All rights reserved.
> +#
> +# SPDX-License-Identifier: GPL-2.0
> +
> +import pytest
> +
> + at pytest.mark.buildconfigspec("cmd_memory")
> +def test_md(uboot_console):
> +    ram_base = uboot_console.find_ram_base()
> +    addr = "%08x" % ram_base
> +    val = "a5f09876"
> +    expected_response = addr + ": " + val

I would add this here.
uboot_console.run_command("mw " + addr + " 0 10")

The reason is that with jtag I don't need to do board reset and DDR is
in the same state. Also I expect some board can have just cpu reset pin
and origin values can stay in memory. That's why clearing before test
will be good.

Thanks,
Michal

-- 
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20151218/19f2daa1/attachment.sig>