rk3399_rockchip-uboot/doc/README.POST

16       The framework shall allow adding/removing/replacing POST tests.
17       Also, standalone POST tests shall be supported.
22       of tests running on normal/power-fail booting.
26       The framework shall support manual running of the POST tests.
28 2) The results of tests shall be saved so that it will be possible to
31 3) The following POST tests shall be developed for MPC823E-based
52 tests and developing such tests for particular hardware.
57 tests and collect their results at boot time. Also, U-Boot will
58 support running POST tests manually at any time by executing a
61 The list of available POST tests will be configured at U-Boot build
63 tests. All POST tests will be divided into the following groups:
67      This group will contain those tests that run only once on
72      This group will contain those tests that do not take much
77      This group will contain POST tests that consume much time
80   4) Manually executed tests
82      This group will contain those tests that can be run manually.
84 If necessary, some tests may belong to several groups simultaneously.
90 Also, all tests will be discriminated by the moment they run at.
95      These tests will run immediately after initializing RAM
97      contents. Basically, this group will contain memory tests
102      These tests will run immediately before entering the main
105 The POST layer will also distinguish a special group of tests that
106 may cause system rebooting (e.g. watchdog test). For such tests, the
131      This routine will run the test (or the group of tests) specified
134      otherwise all tests running in ROM/RAM (depending on the flag
148      This routine will print the list of all POST tests that can be
154      This routine will be called from POST tests to log their
171      tests.
177      power-on long-running tests shall be executed or not ("normal"
180 The list of available POST tests be kept in the post_tests array
195      used in logs and on listing POST tests (e.g. CPU test).
229 The lists of the POST tests that should be run at power-on/normal/
236 The results of tests will be collected by the POST layer. The POST
247 Basically, the results of tests will be printed to stderr. This
257 POST tests for the board. The macro will have the format of array
284 tests. Each POST test in this directory will be placed into a
285 separate file (it will be needed for building standalone tests). Some
286 POST tests (mainly those for testing peripheral devices) will be
290 2.1.4. Standalone tests
292 The POST framework will allow to develop and run standalone tests. A
294 functions to standalone tests.
299 used for listing all available hardware tests, getting detailed
300 descriptions of them and running these tests.
303 print the list of all available hardware tests:
306 Available hardware tests:
311 Use 'diag run [<test1> [<test2>]] ... ' to run tests.
315 descriptions of the specified tests will be printed:
324 If the first argument to diag is 'run', the specified tests will be
325 executed. If no tests are specified, all available tests will be
328 It will be prohibited to execute tests running in ROM manually. The
329 'diag' command will not display such tests and/or run them.
346 executing all hardware tests.
348 2.1.7. Hazardous tests
350 Some tests may cause system rebooting during their execution. For
351 some tests, this will indicate a failure, while for the Watchdog
354 In order to support such tests, the following scheme will be
355 implemented. All the tests that may cause system rebooting will have
357 post_test structure. Before starting tests marked with this bit flag,
360 this variable and if it is set will skip over the tests preceding the
399 This project will also develop a set of POST tests for MPC8xx- based
403 2.2.1. Generic PPC tests
405 The following generic POST tests will be developed:
653 2.2.2. Common tests
655 This section describes tests that are not based on any hardware
656 peculiarities and use common U-Boot interfaces only. These tests do
679 section "Hazardous tests") will be used. Namely, this test will be
704 2.2.3. MPC8xx peripherals tests
706 This project will develop a set of tests verifying the peripheral
714 2.2.3.1. Ethernet tests (SCC)
718 packets will be transmitted. These tests may be enhanced in future to
722 The test routines for the SCC ethernet tests will be located in
725 2.2.3.2. UART tests (SMC/SCC)
727 To perform these tests the internal (local) loopback mode will be
730 will be transmitted. These tests may be enhanced to make to perform
734 The test routine for the SMC/SCC UART tests will be located in