u-boot/test/dfu
Stephen Warren 54ce79c8a5 test: dfu: add some more test cases
On Tegra, the DFU buffer size is 1M. Consequently, the 8M test always
fails. Add tests for the 1M size, and one byte less as a corner case,
so that some large tests are executed and expected to pass.

Signed-off-by: Stephen Warren <swarren@nvidia.com>
2014-08-09 11:17:00 -04:00
..
dfu_gadget_test.sh test: dfu: cleanup before execution 2014-08-09 11:17:00 -04:00
dfu_gadget_test_init.sh test: dfu: add some more test cases 2014-08-09 11:17:00 -04:00
README test:dfu: README file update 2014-08-09 11:17:00 -04:00

DFU TEST CASE DESCRIPTION:

The prerequisites for running this script are assured by
dfu_gadget_test_init.sh, which is automatically invoked by dfu_gadget_test.sh.
In this file user is able to generate their own set of test files by altering
the default set of TEST_FILES_SIZES variable.
The dfu_gadget_test_init.sh would generate test images only if they are not
already generated.

On the target device, environment variable "dfu_alt_info" must contain at
least:

    dfu_test.bin fat 0 6;dfudummy.bin fat 0 6

Depending on your device, you may need to replace "fat" with
"ext4", and "6" with the relevant partition number. For reference please
consult the config file for TRATS/TRATS2 devices
(../../include/configs/trats{2}.h)

One can use fat, ext4 or any other supported file system supported by U-Boot.
These can be created by exporting storage devices via UMS (ums 0 mmc 0) and
using standard tools on host (like mkfs.ext4).

Example usage:
1. On the target:
   setenv dfu_alt_info dfu_test.bin fat 0 6\;dfudummy.bin fat 0 6
   dfu 0 mmc 0
2. On the host:
   test/dfu/dfu_gadget_test.sh X Y  [test file name]
   e.g. test/dfu/dfu_gadget_test.sh 0 1
   or
   e.g. test/dfu/dfu_gadget_test.sh 0 1 ./dat_960.img

... where X and Y are dfu_test.bin's and dfudummy.bin's alt setting numbers.
They can be obtained from dfu-util -l or $dfu_alt_info.
It is also possible to pass optional [test file name] to force the script to
test one particular file.