- Feb 06, 2023
-
-
Add a command to load SEAMA (Seattle Image), a NAND flash on-flash storage format. This type of flash image is found in some D-Link routers such as DIR-645, DIR-842, DIR-859, DIR-860L, DIR-885L, DIR890L and DCH-M225, as well as in WD and NEC routers on the ath79 (MIPS), Broadcom BCM53xx, and RAMIPS platforms. This U-Boot command will read and decode a SEAMA image from raw NAND flash on any platform. As it is always using big endian format for the data decoding is always necessary on platforms such as ARM. The command is needed to read a SEAMA-encoded boot image on the D-Link DIR-890L router for boot from NAND flash in an upcoming port of U-Boot to the Broadcom Northstar (BCM4709, BCM53xx) architecture. A basic test and documentation is added as well. The test must be run on a target with NAND flash support and at least one resident SEAMA image in flash. Cc: Rafał Miłecki <rafal@milecki.pl> Signed-off-by:Linus Walleij <linus.walleij@linaro.org>
-
Fix the issue in commit 46c9016b ("env: mcc: Drop unnecessary #ifdefs") If CONFIG_SYS_REDUNDAND_ENVIRONMENT is not defined, the offset value becomes undetermined, so write env to unexpected offset. Signed-off-by:
Ye Li <ye.li@nxp.com> Reviewed-by:
Jaehoon Chung <jh80.chung@samsung.com>
-
Set my new current personal email. Signed-off-by:
Angelo Dureghello <angelo@kernel-space.org> -
If image file is stored on flash partition then it contains padding, which is not part of the image itself. Image data size is stored in the image header. So use image size from the header instead of expecting that total image file size is size of the header plus size of the image data. This allows dumpimage to parse image files with padding (e.g. dumped from flash partition). Signed-off-by:
Pali Rohár <pali@kernel.org> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
Before reading image header, verify that image size is at least size of the image header. Signed-off-by:
-
gpimage type requires only that two first 32-bit words of data file are non-zero. So basically every random data file can be guessed and verified as gpimage. So completely skip gpimage type from image autodetection code to prevent lot of false positive results. Data file with gpimage type can be still verified and parsed by explicitly specifying -T gpimage. Signed-off-by:
-
Signed-off-by: -
Signed-off-by: -
These are only used in one place, so move them there. Signed-off-by: -
Use the new environment format so we can drop most of the config.h file. Signed-off-by: -
Drop use of the distro scripts and use standard boot instead. Enable BOOTDEV_FULL just for convenience, although this does add quite a bit to the size. Signed-off-by: -
This supports reading a kernel and ramdisk from qfw, then loading it with either the booti or bootz commands. For now this uses the existing booti and bootz commands, rather than trying to call that functionality directly (e.g. do_bootm_states()). It does not require the HUSH parser though, which helps a little with size. Signed-off-by: -
Add a bootdev device for qfw so that it can be used with standard boot. This simply checks for the correct method and then does the read. Most of the other logic is handed in a new bootmeth driver. Signed-off-by: -
This is currently in the cmd/ file but we want to call it from a driver. Move it into a common place. Tidy up the header-file order while we are here. Signed-off-by: -
This uses casts all over the place. Use the correct type so that these can be avoided, as is done with other commands. Also simplify a few conditionals. Signed-off-by: -
We need to support a basic set of filesystems for booting to work in most cases. Add these in via a new option, letting the board disable them individually (for space reasons) if desired. This enables the filesystem commands as well as the actual functionality, even though bootstd is quite happy to use ext4 without the ext4 command. Further work would be needed to disintangle this and reduce code size. Add several other options as well, providing sensible defaults. We cannot enable this by default, since it expands the size of many boards quite a lot. Signed-off-by: -
At present virtio tries to attach QEMU services to a bootdev device, which cannot work. Add a check for this. Also use bootdev_setup_sibling_blk() to create the bootdev device, since it allows the correct name to be used and bootdev_get_sibling_blk() to work as expected. The bootdev is not created on sandbox since it does have a real virtio device and it is not possible to read blocks. Signed-off-by:
Ilias Apalodimas <ilias.apalodimas@linaro.org>
-
In some cases the block device is obtained but is not probed, since it is a sibling of the bootdev. Make sure it is probed, so it can be used without any trouble. This fixes a bug with virtio, where the device is accessed before it has been set up by the virtio uclass. Signed-off-by:
-
It is sometimes useful to have one without the other, e.g. on a device without a display, since at present the expo feature requires CONFIG_VIDEO to be enabled. Update the Makefile and bootflow command to support this, as well as the EXPO dependency. Signed-off-by: -
When QEMU does not respond for some reason, it is helpful to have debugging info to show. Add some. Signed-off-by: -
Sometimes it is useful to log things related to filesystems. Add a new category and place it at the top of one of the FAT files. Signed-off-by: -
am335x_evm_defconfig is used for BeagleBone Black, popular single board computer with wide extension support. Enable CONFIG_CMD_EXTENSION by default since extension detection is already implemented for am335x. Also run make savedefconfig for am335x_evm_defconfig Signed-off-by:Matwey V. Kornilov <matwey.kornilov@gmail.com>
-
Tom Rini authored
This family of platforms typically has a USB port, and so attempting to boot from it, and making it first, will provide a better overall user experience. Signed-off-by:Tom Rini <trini@konsulko.com>
-
allow only to boot signed fitimages (and signed u-boot scripts). Signed-off-by:Heiko Schocher <hs@denx.de>
-
enable protected Environment on socrates board. Signed-off-by: -
add autoboot delay string for socrates board. use sha256 for abort autoboot, use "ao" to abort. Signed-off-by: -
add support for i2c eeprom on address 0x51. Signed-off-by: -
add boot retry feature and reboot after 120 seconds. Signed-off-by: -
drop second flash bank, as not used anymore. Signed-off-by: -
we need to set initrd_high to get fitimage booting. Without, U-Boot drops when booting fitimage: ERROR: Failed to allocate 0x59a0b6 bytes below 0x800000. ramdisk - allocation error bootm - boot application image from memory Signed-off-by: -
setup MTD partitioning through mtdparts variable and set it to: mtdparts=fe0000000.nor:13312k(system1),13312k(system2),5120k(data),128k(env),128k(env-red),768k(u-boot) and pass this to linux per kernel commandline. Signed-off-by: -
include common e500v2_power_isa.dtsi and rearrange some nodes. Signed-off-by: -
convert socrates board to use MPC85XX_HAVE_RESET_VECTOR and disable CONFIG_OF_BOARD and use common u-boot.dtsi for creating u-boot-dtb.bin. Signed-off-by: -
U-Boot build process for socrates board produces final U-Boot binary in file u-boot-socrates.bin (by binman) And as a bonus it produces two unusable broken binaries u-boot-dtb.bin and u-boot.bin (by Makefile). Clean this up, so final U-Boot binary is in u-boot-dtb.bin Signed-off-by:
-
current mainline does not work on socrates board. To get it back up working, there are some updates needed in socrates_defconfig. Signed-off-by:
-
This was added by mistake and renders the function useless. Fix it. Signed-off-by:
Stefan Herbrechtsmeier <stefan.herbrechtsmeier-oss@weidmueller.com> Reviewed-by:
Oleksandr Suvorov <oleksandr.suvorov@foundries.io>
-
As MDIO driver does not support Driver Model, the pinctrl settings in the MDIO node will not be applied resulting in PHY not being detected. To workaround this we add the MDIO pinctrl in the CPSW3G node in the -u-boot.dtsi file. Add the missing MDIO and RGMII pinctrl nodes in k3-am642-r5-evm.dts Signed-off-by:
Roger Quadros <rogerq@kernel.org> Reviewed-by:
-
We need to enable i2c0 so u-boot can read from EEPROM. Signed-off-by:
-
Sync AM64 DT files with Linux v6.2-rc4 Signed-off-by:
-
There are no differences for the different 832x targets we have in the header defined with SYS_CONFIG_NAME. So we can join the five headers to a single file. Signed-off-by:Holger Brunck <holger.brunck@hitachienergy.com>
-
