| /rk3399_rockchip-uboot/doc/ |
| H A D | README.console | 15 relocates itself to RAM, all console drivers are initialized (they
16 will register all detected console devices to the system for further
20 to the 'stdin' file, the first output one to 'stdout' and 'stderr'.
22 You can use the command "coninfo" to see all registered console
24 stdout or stderr) to any device you see in that list simply by
25 assigning its name to the corresponding environment variable. For
31 Do a simple "saveenv" to save the console settings in the environment
37 You can use the following functions to access the console:
40 putc (to put a char to stdout)
41 puts (to put a string to stdout)
[all …]
|
| H A D | README.log | 8 setting up the board to displaying a start-up screen to loading an Operating
15 a problem it is often useful to see what U-Boot is doing in more detail than
18 U-Boot's logging feature aims to satisfy this goal for both users and
43 has a category which is intended to allow messages to be filtered according to
49 UCLASS_... - Related to a particular uclass (e.g. UCLASS_USB)
50 LOGC_ARCH - Related to architecture-specific code
51 LOGC_BOARD - Related to board-specific code
52 LOGC_CORE - Related to core driver-model support
53 LOGC_DT - Related to device tree control
59 The following options are used to enable logging at compile time:
[all …]
|
| H A D | README.atmel_pmecc | 1 How to enable PMECC(Programmable Multibit ECC) for nand on Atmel SoCs
7 can be used to support both SLC and MLC NAND Flash devices. It supports to
8 generate ECC to correct 2, 4, 8, 12 or 24 bits of error per sector (512 or
17 To use PMECC in this driver, the user needs to set:
30 How to enable PMECC header for direct programmable boot.bin
34 The usual way to program SPL into NAND flash is to use the SAM-BA Atmel tool.
35 This however is often not usable when doing field updates. To be able to
36 program a SPL binary into NAND flash we need to add the PMECC header to the
38 sama5d3 SoC spec (as of 03. April 2014) defines how this PMECC header has to
39 look like. In order to do so we have a new image type added to mkimage to
[all …]
|
| H A D | README.mxc_hab | 4 required to set the proper configuration for the target board. This
9 In addition, the U-Boot image to be programmed into the
10 boot media needs to be properly constructed, i.e. it must contain a
13 The Initial Vector Table contains a pointer to the CSF. Please see
14 doc/README.imximage for how to prepare u-boot.imx.
19 which can be used in the Freescale tooling to authenticate U-Boot
36 (1) Size of area in file u-boot.imx to sign
39 (2) Start of area in u-boot.imx to sign
40 (3) Start of area in RAM to authenticate
43 'hab_status' in U-Boot to retrieve the HAB status and events. This
[all …]
|
| H A D | README.unaligned-memory-access.txt | 8 when it comes to memory access. This document presents some details about
9 unaligned accesses, why you need to write code that doesn't cause them,
10 and how to write such code!
16 Unaligned memory accesses occur when you try to read N bytes of data starting
24 or write a number of bytes to or from memory (e.g. movb, movw, movl in x86
25 assembly). As will become clear, it is relatively easy to spot C statements
26 which will compile to multiple-byte memory access instructions, namely when
33 The rule mentioned above forms what we refer to as natural alignment:
43 to achieve full portability.
50 to architecture. It would be easy to write a whole document on the differences
[all …]
|
| H A D | README.NetConsole | 5 'stdout' environment variables. To switch to the networked console,
6 set either of these variables to "nc". Input and output can be
11 We use an environment variable 'ncip' to set the IP address and the
14 broadcast address and port 6666 are used. If it is set to an IP
15 address of 0 (or 0.0.0.0) then no messages are sent to the network.
28 On the host side, please use this script to access the console:
32 The script uses netcat to talk to the board over UDP. It requires you to
41 It turns out that 'netcat' cannot be used to listen to broadcast
43 listens to broadcast packets on a given port and dumps them to the
49 Minimally, the host IP address needs to be specified. This can be
[all …]
|
| H A D | README.trace | 11 to be collected and sent to a host machine for analysis. At present the
12 main use for this is to profile boot time.
18 The trace feature uses GCC's instrument-functions feature to trace all
20 The memory buffer can be saved to the host over a network link using
21 tftpput or by writing to an attached memory device such as MMC.
36 Add the following to include/configs/sandbox.h (if not already there)
50 Run sandbox, wait for a bit of trace information to appear, and then capture
72 66,491 calls not traced due to depth
77 950,490 traced function calls (333217 dropped due to overflow)
80 1,275,767 calls not traced due to depth
[all …]
|
| H A D | README.video | 11 The 'video-mode' environment variable can be used to enable and configure
18 <xres> The X resolution (in pixels) to use.
19 <yres> The Y resolution (in pixels) to use.
20 <depth> The color depth (in bits) to use.
21 <freq> The frequency (in Hz) to use.
39 requires the CONFIG_VIDEO_LCD_MODE Kconfig value to be set.
43 - monitor=[none|dvi|hdmi|lcd|vga|composite-*] - Select the video output to use
47 lcd: Selects video output to a LCD screen.
52 Defaults to monitor=dvi.
56 1: Enabled. Fallback to the lcd / vga / none in that order (if available)
[all …]
|
| H A D | README.LED | 8 The first step is to enable CONFIG_LED_STATUS in menuconfig:
14 Status LEDS 0 to 5 are enabled by the following configurations at menuconfig:
23 CONFIG_STATUS_LED_BIT is passed into the __led_* functions to identify which LED
24 is being acted on. As such, the value choose must be unique with with respect to
25 the other CONFIG_STATUS_LED_BIT's. Mapping the value to a physical LED is the
28 CONFIG_STATUS_LED_STATE is the initial state of the LED. It should be set to one
32 Values range from 2 to 10.
37 CONFIG_STATUS_LED_BOOT is the LED to light when the board is booting.
40 CONFIG_STATUS_LED_RED is the red LED. It is used to signal errors. This must be
48 __led_init is called once to initialize the LED to CONFIG_STATUS_LED_STATE.
[all …]
|
| H A D | README.malta | 3 How to flash using a MIPS Navigator Probe:
6 be unable to flash your Malta using a Navigator Probe.
8 - Connect Navigator Console to your probe and Malta as usual.
12 source /path/to/u-boot/board/imgtec/malta/flash-malta-boot.tcl
14 flash-boot /path/to/u-boot/u-boot.bin
16 - You should now be able to reboot your Malta to a U-Boot shell.
|
| H A D | README.falcon | 7 This document provides an overview of how to add support for Falcon Mode
8 to a board.
10 Falcon Mode is introduced to speed up the booting process, allowing
11 to boot a Linux kernel (or whatever image) without a full blown U-Boot.
13 Falcon Mode relies on the SPL framework. In fact, to make booting faster,
15 image. In most implementations, SPL is used to start U-Boot when booting from
17 and can generally be seen as a way to start an image performing the minimum
21 The Falcon Mode extends this way allowing to start the Linux kernel directly
22 from SPL. A new command is added to U-Boot to prepare the parameters that SPL
23 must pass to the kernel, using ATAGS or Device Tree.
[all …]
|
| H A D | README.pxe | 8 the PXELINUX boot loader. This allows U-Boot based systems to be controlled
24 'pxe get' requires two environment variables to be set:
26 pxefile_addr_r - should be set to a location in RAM large enough to hold
27 pxe files while they're being processed. Up to 16 config files may be
33 handler, and correspond to fields in the DHCP response.
38 'pxe get' uses it to look for a configuration file specific to a system's
43 it to look for a configuration file based on the system's UUID.
47 'pxe get' repeatedly tries to download config files until it either
48 successfully downloads one or runs out of paths to try. The order and
65 There are some environment variables that may need to be set, depending
[all …]
|
| H A D | README.watchdog | 4 This enables hw_watchdog_reset to be called during various loops,
13 Can be used to change the timeout for i.mx31/35/5x/6x.
14 If not given, will default to maximum timeout. This would
18 Available for AT91SAM9 to service the watchdog.
21 Available for FTWDT010 to service the watchdog.
24 Can be used to change the timeout for FTWDT010.
27 Available for i.mx31/35/5x/6x to service the watchdog. This is not
28 automatically set because some boards (vision2) still need to define
33 Available for Xilinx Axi platforms to service timebase watchdog timer.
36 Available for bf5xx and bf6xx to service the watchdog.
|
| /rk3399_rockchip-uboot/doc/SPL/ |
| H A D | README.am335x-network | 5 how to setup network booting and then optionally use this support to flash
9 1. You have to enable generic SPL configuration options (see
12 CONFIG_SPL_LIBCOMMON_SUPPORT in your board configuration file to build
13 SPL with support for booting over the network. Also you have to enable
16 If you want SPL to use some Vendor Class Identifier (VCI) you can set
19 2. Define CONFIG_BOOTCOMMAND for your board to load and run debrick
30 You will need u-boot.img and spl/u-boot.bin images to perform
31 network boot. Copy them to u-boot-restore.img and
32 u-boot-spl-restore.bin respectively to distinguish this version
37 - Install DHCP server and setup it to listen on the interface you
[all …]
|
| /rk3399_rockchip-uboot/drivers/video/rk_eink/ |
| H A D | Kconfig | 5 Choose this option to enable support for EBC TCON controller
11 Choose this option to enable support for TPS65185, which is
12 used to supply power for eink panel.
18 Choose this option to enable support for eink display, which is
19 used to display uboot/charging/lowerpower logo, and also used to
20 load kernel logo to ram, which can pass to kernel to display.
28 Choose this option to enable support for FP9931 PMIC.
36 Choose this option to enable support for SY7636A PMIC.
|
| /rk3399_rockchip-uboot/drivers/video/bridge/ |
| H A D | Kconfig | 5 Some platforms use video bridges to convert from one output to
7 requires LVDS, an eDP->LVDS bridge chip can be used to provide the
14 The Parade PS8622 and PS8625 are DisplayPort-to-LVDS (Low voltage
16 to be connected to an eDP output device such as an SoC that lacks
17 LVDS capability, or where LVDS requires too many signals to route
24 The NXP PTN3460 is a DisplayPort-to-LVDS (Low voltage differential
25 signalling) converter. It enables an LVDS LCD panel to be connected
26 to an eDP output device such as an SoC that lacks LVDS capability,
27 or where LVDS requires too many signals to route on the PCB.
34 The Analogix ANX6345 is RGB-to-DP converter. It enables an eDP LCD
[all …]
|
| /rk3399_rockchip-uboot/tools/patman/ |
| H A D | README | 14 - Optionally emails them out to selected people
16 It is intended to automate patch creation and make it a less
22 once, and keep the settings with each branch rather than having to
26 Series-to: fred.blogs@napier.co.nz
31 patches automatically (unless you use -m to disable this).
34 How to use this tool
41 - Add tags into the commits within each branch to indicate where the
43 normally in the top commit so it is easy to change them with 'git
47 - Check out a branch, and run this script to create and send out your
52 How to configure it
[all …]
|
| /rk3399_rockchip-uboot/drivers/power/ |
| H A D | Kconfig | 43 Select this to enable support for the axp152 pmic found on most
51 Select this to enable support for the axp209 pmic found on most
59 Select this to enable support for the axp221/axp223 pmic found on most
67 Say y here to enable support for the axp809 pmic found on A80 boards.
74 Say y here to enable support for the axp818 pmic found on
81 Select this to enable support for the SY8106A pmic found on some
107 Set the voltage (mV) to program the axp pmic dcdc1 at, set to 0 to
110 sdcard interfaces, etc. On most boards dcdc1 is undervolted to 3.0V to
124 Set the voltage (mV) to program the axp pmic dcdc2 at, set to 0 to
142 Set the voltage (mV) to program the axp pmic dcdc3 at, set to 0 to
[all …]
|
| /rk3399_rockchip-uboot/test/py/ |
| H A D | README.md | 5 This tool aims to test U-Boot by executing U-Boot shell commands using the
6 console interface. A single top-level script exists to execute or attach to the
12 - There is no need to write or embed test-related code into U-Boot itself.
15 - It is reasonably simple to interact with U-Boot in this way.
21 need to implement various "hook" scripts that are called by the test suite at
36 - Executing an external "hook" scripts to flash a U-Boot binary onto a
37 physical board, attach to the board's console stream, and reset the board.
40 ### Using `virtualenv` to provide requirements
43 packages, or may provide versions that are too old to run the test suite. One
44 can use the Python `virtualenv` script to locally install more up-to-date
[all …]
|
| /rk3399_rockchip-uboot/board/davinci/da8xxevm/ |
| H A D | README.da850 | 10 controller (such as SPI or NAND) to continue the boot process by loading
13 predefined location in persistent storage to DDR and jumps to the u-boot
16 AIS is an image format defined by TI for the images that are to be loaded
17 to memory by the RBL. The image is divided into a series of sections and
19 like the target address the section is to be copied to and the size of the
20 section, which is used by the RBL to load the image. At the end of the
21 image the RBL jumps to the image entry point. The AIS format allows for
35 u-boot.ais file that needs to be written to the correct persistent
39 Flashing the images to SPI
41 The AIS image can be written to SPI flash using the following commands.
[all …]
|
| /rk3399_rockchip-uboot/drivers/serial/ |
| H A D | Kconfig | 24 during serial port initialization (default y). Set this to n on
80 The size of the RX buffer (needs to be power of 2)
105 The debug UART is intended for use very early in U-Boot to debug
111 - Enable the CONFIG for your UART to tell it to provide this interface
115 - Call debug_uart_putc() to output a character
117 Depending on your platform it may be possible to use this UART before
122 it is preferred to use no stack.
136 Select this to enable a debug UART using the altera_jtag_uart driver.
137 You will need to provide parameters to make this work. The driver will
143 Select this to enable a debug UART using the altera_uart driver.
[all …]
|
| /rk3399_rockchip-uboot/board/freescale/mpc8536ds/ |
| H A D | README | 12 call 4K NAND loader and a second stage image. The former is appended to
13 the latter to produce u-boot-nand.bin.
16 configure the L2SRAM, then copy the second stage image to L2SRAM and jump
17 to it. The second stage image is to configure all the hardware and boot up
18 to U-Boot command line.
22 is mainly used to shrink the code size to the 4K size limitation.
24 The macro CONFIG_SYS_RAMBOOT is used to control the code to produce the
49 and boot from eSPI. When power on, the porcessor excutes the ROM code to
51 the memory device that interfaced to the controller, such as the SDCard or
52 SPI EEPROM, to the target memory, e.g. SDRAM or L2SRAM, then boot from it.
[all …]
|
| /rk3399_rockchip-uboot/Licenses/ |
| H A D | gpl-2.0.txt | 6 Everyone is permitted to copy and distribute verbatim copies
11 The licenses for most software are designed to take away your
12 freedom to share and change it. By contrast, the GNU General Public
13 License is intended to guarantee your freedom to share and change free
14 software--to make sure the software is free for all its users. This
15 General Public License applies to most of the Free Software
16 Foundation's software and to any other program whose authors commit to
18 the GNU Lesser General Public License instead.) You can apply it to
21 When we speak of free software, we are referring to freedom, not
22 price. Our General Public Licenses are designed to make sure that you
[all …]
|
| /rk3399_rockchip-uboot/doc/driver-model/ |
| H A D | fdt-fixup.txt | 9 4. Work to be done
14 In certain markets, it is beneficial for manufacturers of embedded devices to
20 To realize this in hardware, one method is to have a motherboard, and several
21 possible daughter boards that can be attached to this mother board. Different
23 addition of the daughter board to the device realizes the "extension" of
24 functionality to the device described previously.
26 For the software, we obviously want to reuse components for all these
27 variations of the device. This means that the software somehow needs to cope
29 system, depending on which daughter boards are connected to the motherboard.
31 In the Linux kernel, one possible solution to this problem is to employ the
[all …]
|
| /rk3399_rockchip-uboot/drivers/dfu/ |
| H A D | Kconfig | 18 This option enables using DFU to read and write to MMC based storage.
23 This option enables using DFU to read and write to NAND based
29 This option enables using DFU to read and write to MTD based
35 This option enables using DFU to read and write RAM on the target.
40 This option enables using DFU to read and write to SPI flash based
|