Lines Matching refs:script
8 console interface. A single top-level script exists to execute or attach to the
9 U-Boot console, run the entire script of tests against it, and summarize the
12 - Testing is performed in the same way a user or script would interact with
59 The test script supports either:
73 root has this privilege. You can add a script /etc/initramfs-tools/hooks/vmlinuz
82 The script should be chmod 755. It will be invoked whenever the initial RAM file
117 running the test script.
119 The test script will attach to U-Boot, execute all valid tests for the board,
225 test script in any way, but rather is simply passed to the hook scripts
229 indicates that the test script should compile U-Boot itself before running
252 test.py script passes all command-line arguments directly to `pytest` for
304 This script provides access to the U-Boot console. The script's stdin/stdout
306 indefinitely, until killed. The test suite will run this script in parallel
309 This script may be implemented e.g. by executing `cu`, `kermit`, `conmux`, etc.
313 you would likely spawn that simulator from this script. However, note that
314 `u-boot-test-reset` may be called multiple times per test script run, and must
326 suite calls this hook script for that purpose.
328 This script should perform the entire flashing process synchronously; the
329 script should only exit once flashing is complete, and a board reset will
332 It is conceivable that this script will do nothing. This might be useful in
340 required. If this feature is used, the `u-boot-test-reset` script should
345 hook script appropriately.
347 This script will typically be implemented by calling out to some SoC- or
353 Whenever the test suite needs to reset the target board, this script is
356 this script again to restore U-Boot to an operational state before running the
359 This script will likely be implemented by communicating with some form of
362 The semantics of this script require that when it is executed, U-Boot will
364 to flash, pulsing the board's reset signal is likely all this script needs to
365 do. However, in some scenarios, this script may perform other actions. For
386 to provide board-specific information to the test script. Any global value
398 machine running the test script.
402 board-specific and board-identity-specific information to the test script. Any
407 should set `$PYTHONPATH` prior to running the test script to allow these
441 then you would likely invoke the test script as follows:
451 If you want the test script to compile U-Boot for you too, then you likely
452 need to set `$CROSS_COMPILE` to allow this, and invoke the test script as