- Nov 07, 2022
-
-
Simon Glass authored
Document the 'host' command and also the internals of how it is implemented. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
- Oct 31, 2022
-
-
The current name is inconsistent with SPL which uses CONFIG_SPL_TEXT_BASE and this makes it imposible to use CONFIG_VAL(). Rename it to resolve this problem. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
- May 28, 2022
-
-
This documents some additional options which can be used with valgrind, as well as directions for future work. It also fixes up inline literals to actually be inline literals (and not italics). The content of this documentation is primarily adapted from [1]. [1] https://lore.kernel.org/u-boot/57cb4b49-fa30-1194-9ac3-faa53e8033bd@gmail.com/ Signed-off-by:
Sean Anderson <seanga2@gmail.com> Reviewed-by:
Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
-
Image created by LTO is not friendly to debugger, let's document this. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com> Mention CONFIG_CC_OPTIMIZE_FOR_DEBUG and LLDB. Reviewed-by:
Heinrich Schuchardt <xypron.glpk@gmx.de>
-
It should be CONFIG_SANDBOX_RAM_SIZE_MB. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com> Reviewed-by:
Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
-
- May 02, 2022
-
-
Add an initial VPL build for sandbox. This includes the flow: TPL (with of-platdata) -> VPL -> SPL -> U-Boot To run it: ./tpl/u-boot-tpl -D The -D is needed to get the default device tree, which includes the serial console info. Add a Makefile check for OF_HOSTFILE which is the option that enables devicetree control on sandbox. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
- Apr 11, 2022
-
-
This documents how to get more detailed results from valgrind made possible by the last two commits. Signed-off-by:
Sean Anderson <seanga2@gmail.com> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
- Jul 28, 2021
-
-
These are out of date. Update them and point to the existing build instructions to avoid duplication. Add a few that are missing. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
- Jul 21, 2021
-
-
Simon Glass authored
Move this down to provide more space for the bloblist. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
- Mar 27, 2021
-
-
Simon Glass authored
At present when a file is bound to a host device it is always marked as removeable. Arguably the device is removeable, since it can be unbound at will. However while it is bound, it is not considered removable by the user. Also it is useful to be able to model both fixed and removeable devices for code that distinguishes them. Add a -r flag to the 'host bind' command and plumb it through to provide this feature. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
- Mar 13, 2021
-
-
The 'reset' command now resets sandbox but does not quit it. Fix the instructions. Fixes: 329dccc0 ("sandbox: implement reset") Signed-off-by:
Simon Glass <sjg@chromium.org>
-
- Mar 12, 2021
-
-
At present some of the documentation about running sandbox tests is in the sandbox docs. It makes more sense to put it in with the other testing docs, with a link there from sandbox. Update the documentation accordingly. Also add a paragraph explaining why sandbox exists and the test philosophy that it uses. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
As an example of an SPL test, add a new test for loading a FIT within SPL. This runs on sandbox_spl. For this to work, the text base is adjusted so that there is plenty of space available. While we are here, document struct spl_load_info properly, since this is currently ambiguous. This test only verifies the logic path. It does not actually check that the image is loaded correctly. It is not possible for sandbox's SPL to actually run u-boot.img since it currently includes u-boot.bin rather than u-boot. Further work could expand the test in that direction. The need for this was noted at: http://patchwork.ozlabs.org/project/uboot/patch/20201216000944.2832585-3-mr.nuke.me@gmail.com/ Signed-off-by:
Simon Glass <sjg@chromium.org>
-
- Jan 30, 2021
-
-
The UEFI Self Certification Test (SCT) checks the SetTime() service with the following steps: * set date * reset * check date matches To be compliant the sandbox should keep the offset to the host RTC during resets. The implementation uses the environment variable UBOOT_SB_TIME_OFFSET to persist the offset. Signed-off-by:
Heinrich Schuchardt <xypron.glpk@gmx.de> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
Show the command line options in bold. Signed-off-by:
Heinrich Schuchardt <xypron.glpk@gmx.de> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
- Oct 06, 2020
-
-
Reformat the command line options chapter so that the command line options clearly stand out. Signed-off-by:
Heinrich Schuchardt <xypron.glpk@gmx.de> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
- May 30, 2020
-
-
Since the commit 1289e967 ("sandbox: spi: Drop command-line SPI option"), "--spi_sf" command line option is no longer supported. So update the following documents to sync them up with the change. doc/arch/sandbox.rst doc/SPI/README.sandbox-spi Signed-off-by:
AKASHI Takahiro <takahiro.akashi@linaro.org> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
- Apr 11, 2020
-
-
Quite a few packages are used by sandbox or tools. Add a list of these to help people setting up for the first time. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
- Feb 06, 2020
-
-
Simon Glass authored
Sandbox currently uses SDL1.2. SDL2 has been around for quite a while and is widely supported. It has a number of useful features. It seems appropriate to move sandbox over. Update the code to use SDL2 instead of SDL1.2. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
- Oct 11, 2019
-
-
Tom Rini authored
At this point, all drivers that do not use CONFIG_BLK are past their migration deadlines, so remove this config as it's no longer helpful and hinders enhancing block drivers. Reviewed-by:
Simon Glass <sjg@chromium.org> Signed-off-by:
Tom Rini <trini@konsulko.com>
-
- Oct 08, 2019
-
-
U-Boot already supports using -D to indicate that it should use the normal device tree. It is sometimes useful to run with the test device tree, e.g. when running a test. Add a -T option for this along with some documentation. It can be used like this: /tmp/b/sandbox/u-boot -T -c "ut dm pci_busdev" (this will use /tmp/b/sandbox/arch/sandbox/dts/test.dtb as the DT) Signed-off-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Bin Meng <bmeng.cn@gmail.com> Tested-by:
Bin Meng <bmeng.cn@gmail.com>
-
- Jul 24, 2019
-
-
Convert plain text documentation to reStructuredText format and add it to Sphinx TOC tree. No essential content change. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com>
-
- Jul 10, 2019
-
-
Simon Glass authored
U-Boot sandbox can run with valgrind to check memory allocations. Add documentation on how to do this. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
When cross-compiling, sometimes sdl-config must come from a different path from the default. Add a way to override it, by adding SDL_CONFIG to the environment before building U-Boot. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
- Apr 24, 2019
-
-
Simon Glass authored
These two buffers currently conflict if tracing is enabled. Move the pre-console buffer and update the documentation. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
At present if one of the initcalls fails on sandbox the address printing is not help, e.g.: initcall sequence 0000557678967c80 failed at call 00005576709dfe1f (err=-96) This is because U-Boot gets relocated high into memory and the relocation offset (gd->reloc_off) does not work correctly for sandbox. Add support for finding the base address of the text region (at least on Linux) and use that to set the relocation offset. This makes the output better: initcall sequence 0000560775957c80 failed at call 0000000000048134 (err=-96) Then you use can use grep to see which init call failed, e.g.: $ grep 0000000000048134 u-boot.map stdio_add_devices Of course another option is to run it with a debugger such as gdb: $ gdb u-boot ... (gdb) br initcall.h:41 Breakpoint 1 at 0x4db9d: initcall.h:41. (2 locations) Note that two locations are reported, since this function is used in both board_init_f() and board_init_r(). (gdb) r Starting program: /tmp/b/sandbox/u-boot [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". U-Boot 2018.09-00264-ge0c2ba9814-dirty (Sep 22 2018 - 12:21:46 -0600) DRAM: 128 MiB MMC: Breakpoint 1, initcall_run_list (init_sequence=0x5555559619e0 <init_sequence_f>) at /scratch/sglass/cosarm/src/third_party/u-boot/files/include/initcall.h:41 41 printf("initcall sequence %p failed at call %p (err=%d)\n", (gdb) print *init_fnc_ptr $1 = (const init_fnc_t) 0x55555559c114 <stdio_add_devices> (gdb) Signed-off-by:
Simon Glass <sjg@chromium.org>
-
- Nov 26, 2018
-
-
We have a few things in the memory map now, so add documentation for this to avoid confusion. Also note that it is possible to run all tests now. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
- Nov 21, 2018
-
-
If we want to control which network interface is actually used, we have to issue 'setenv ethrotate no'. If ethrotate is not set any interface may be used. Signed-off-by:
Heinrich Schuchardt <xypron.glpk@gmx.de> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
The command to set environment variables is setenv. Signed-off-by:
Heinrich Schuchardt <xypron.glpk@gmx.de> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
- Sep 29, 2018
-
-
Simon Glass authored
There are quite a few builds of sandbox now. Add information about these to the README. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
- May 07, 2018
-
-
Tom Rini authored
When U-Boot started using SPDX tags we were among the early adopters and there weren't a lot of other examples to borrow from. So we picked the area of the file that usually had a full license text and replaced it with an appropriate SPDX-License-Identifier: entry. Since then, the Linux Kernel has adopted SPDX tags and they place it as the very first line in a file (except where shebangs are used, then it's second line) and with slightly different comment styles than us. In part due to community overlap, in part due to better tag visibility and in part for other minor reasons, switch over to that style. This commit changes all instances where we have a single declared license in the tag as both the before and after are identical in tag contents. There's also a few places where I found we did not have a tag and have introduced one. Signed-off-by:
Tom Rini <trini@konsulko.com>
-
- May 06, 2018
-
-
Signed-off-by:
Trevor Woerner <twoerner@gmail.com>
-
- Feb 18, 2018
-
-
To debug device tree issues involving 32- and 64-bit platforms, it is useful to have a generic 64-bit platform available. Add a version of the sandbox that uses 64-bit integers for its physical addresses as well as a modified device tree. Signed-off-by:
Mario Six <mario.six@gdsys.cc> Added CONFIG_SYS_TEXT_BASE to configs/sandbox64_defconfig Signed-off-by:
Simon Glass <sjg@chromium.org>
-
- Sep 15, 2017
-
-
Provide a Python function that creates a small block device for the purpose of testing the cmd/gpt.c or cmd/part.c functions in the u-boot sandbox. Signed-off-by:
Alison Chaiken <alison@peloton-tech.com> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
- Sep 12, 2017
-
-
Convert SANDBOX_BITS_PER_LONG to Kconfig and assign it a correct number depending on which host we are going to build and run. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
- Jul 11, 2017
-
-
The instructions for creating a disk image that are presently in README.sandbox fail because sfdisk doesn't know about GPT. Signed-off-by:
Alison Chaiken <alison@peloton-tech.com> Reviewed-by:
Simon Glass <sjg@chromium.org> Tested-by:
Simon Glass <sjg@chromium.org>
-
- Sep 19, 2016
-
-
Signed-off-by:
Stefan Brüns <stefan.bruens@rwth-aachen.de> Acked-by:
Simon Glass <sjg@chromium.org> Changed 'Sandbox' to 'sandbox' in subject: Signed-off-by:
Simon Glass <sjg@chromium.org>
-
- Jul 25, 2016
-
-
Sandbox is built with 64-bit ints by default. This doesn't work properly on 32-bit machines. Signed-off-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Tom Rini <trini@konsulko.com>
-
- May 27, 2016
-
-
Remove the warning from the Makefile, since boards that do not use generic board will no longer build. Also update documentation. Signed-off-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Andreas Bießmann <andreas@biessmann.org>
-
- Apr 14, 2016
-
-
Update dm test command with pytest instead of ./test/dm/test-dm.sh Cc: Tom Rini <trini@konsulko.com> Cc: Simon Glass <sjg@chromium.org> Acked-by:
Stephen Warren <swarren@nvidia.com> Signed-off-by:
Jagan Teki <jteki@openedev.com>
-