board/sandbox/README.sandbox

7 Native Execution of U-Boot
10 The 'sandbox' architecture is designed to allow U-Boot to run under Linux on
11 almost any hardware. To achieve this it builds U-Boot (so far as possible)
14 All of U-Boot's architecture-specific code therefore cannot be built as part
15 of the sandbox U-Boot. The purpose of running U-Boot under Linux is to test
33 To run sandbox U-Boot use something like:
51 U-Boot will start on your computer, showing a sandbox emulation of the serial
55 U-Boot 2014.04 (Mar 20 2014 - 19:06:00)
79 This will start U-Boot with a window showing the contents of the LCD. If
93 press Ctrl-C, U-Boot will exit instead of handling this as a keypress.
95 Other options are 'raw' (so Ctrl-C is handled within U-Boot) and 'cooked'
102 (it is stored at arch/sandbox/dts/sandbox.dts) you must rebuild U-Boot to
107 U-Boot. Be careful with quoting as the shall will normally process and
108 swallow quotes. When -c is used, U-Boot exists after the command is complete,
118 test runs. You can tell U-Boot to remove the memory file after it is read
121 To access U-Boot's emulated memory within the code, use map_sysmem(). This
122 function is used throughout U-Boot to ensure that emulated memory is used
123 rather than the U-Boot application memory. This provides memory starting
132 preserved across U-Boot runs. This is particularly useful for testing. For
134 U-Boot exits.
138 make U-Boot read the state on start-up (otherwise it starts empty) and -w
140 changes U-Boot made will be lost). You can also use -n to tell U-Boot to
152 Since there is no machine architecture, sandbox U-Boot cannot actually boot
157 When 'bootm' runs a kernel, sandbox will exit, as U-Boot does on a real
160 It is also possible to tell U-Boot that it has jumped from a temporary
161 previous U-Boot binary, with the -j option. That binary is automatically
162 removed by the U-Boot that gets the -j option. This allows you to write
163 tests which emulate the action of chain-loading U-Boot, typically used in
164 a situation where a second 'updatable' U-Boot is stored on your board. It
165 is very risky to overwrite or upgrade the only U-Boot on a board, since a
173 U-Boot sandbox supports these emulations:
178 - Host filesystem (access files on the host from within U-Boot)
199 stack and the RAW sockets API in Linux. This allows much of the U-Boot network
204 means that all of the Ethernet frame is included. This allows the U-Boot network
207 responses to packets sent from U-Boot the network interface has to be set to
326 U-Boot can use raw disk images for block device emulation. To e.g. list
354 To access U-Boot's emulated memory, use map_sysmem() as mentioned above.
369 U-Boot sandbox can be used to run various tests, mostly in the test/
375      - Unit tests for U-Boot's compression algorithms, useful for
391 coverage in U-Boot is limited, as we need to work to improve it.