- Nov 10, 2017
-
-
Goldschmidt Simon authored
The U-Boot location has been moved to block 16384. This is 8MB, not 4MB. Signed-off-by:
Simon Goldschmidt <sgoldschmidt@de.pepperl-fuchs.com> Reviewed-by:
Jagan Teki <jagan@openedev.com> Acked-by:
Philipp Tomsich <philipp.tomsich@theobroma-systems.com> Reviewed-by:
Philipp Tomsich <philipp.tomsich@theobroma-systems.com>
-
- Nov 09, 2017
-
-
git://git.denx.de/u-boot-sunxiTom Rini authored
-
git://www.denx.de/git/u-boot-imxTom Rini authored
-
Lukasz Majewski authored
Signed-off-by:
Lukasz Majewski <lukma@denx.de>
-
Lukasz Majewski authored
Signed-off-by:
Lukasz Majewski <lukma@denx.de>
-
Lukasz Majewski authored
Signed-off-by:
Lukasz Majewski <lukma@denx.de>
-
Lukasz Majewski authored
This commit provides support for LWN's IMX6Q based DISPLAY5 board. Signed-off-by:
Lukasz Majewski <lukma@denx.de>
-
Lukasz Majewski authored
This commit provides generic function to set the RGMII/HSIC IO voltage level on iMX6 devices. Signed-off-by:
Lukasz Majewski <lukma@denx.de>
-
Lukasz Majewski authored
The sys_proto.h file has been included earlier in this file. Signed-off-by:
Lukasz Majewski <lukma@denx.de>
-
Artturi Alm authored
due misnaming of CONFIG_SUN4I_EMAC in include/configs/sunxi-common.h, likely missed in: commit 3146f0c0 ("Move PHYLIB to Kconfig") Signed-off-by:
Artturi Alm <artturi.alm@gmail.com> Reviewed-by:
Jagan Teki <jagan@openedev.com>
-
Artturi Alm authored
fixes CONFIG_SUNXI_EMAC references from drivers/net/Makefile and include/configs/sunxi-common.h likely forgotten in: commit abc3e4df ("sunxi: Convert SUNXI_EMAC to Kconfig") Signed-off-by:
Artturi Alm <artturi.alm@gmail.com> Reviewed-by:
Jagan Teki <jagan@openedev.com>
-
- Nov 07, 2017
-
-
Benoît Thébaudeau authored
The following error has been observed on i.MX25 with a high-speed SDSC card: Data Write Failed in PIO Mode. It was caused by the timeout set on PRSSTAT.BWEN, which was triggered because this bit takes 15 ms to be set after writing the first block to DATPORT with this card. Without this timeout, all the blocks are properly written. This timeout was implemented by decrementing a variable, so it was depending on the CPU frequency. Fix this issue by setting this timeout to a long enough absolute duration (500 ms). Signed-off-by:
Benoît Thébaudeau <benoit.thebaudeau.dev@gmail.com> Cc: Stefano Babic <sbabic@denx.de> Cc: Fabio Estevam <fabio.estevam@nxp.com> Cc: Jaehoon Chung <jh80.chung@samsung.com> Reviewed-by:
Fabio Estevam <fabio.estevam@nxp.com> Reviewed-by:
Jagan Teki <jagan@openedev.com>
-
Jagan Teki authored
- Update newly added include/configs file in MAINTAINERS - Update newly added defconfig file in README Signed-off-by:
Jagan Teki <jagan@amarulasolutions.com>
-
Fabio Estevam authored
When a high speed card is connected to mx51evk the following error is seen: U-Boot 2017.11-rc2 (Oct 18 2017 - 13:49:26 -0200) CPU: Freescale i.MX51 rev3.0 at 800 MHz Reset cause: POR Board: MX51EVK DRAM: 512 MiB MMC: FSL_SDHC: 0, FSL_SDHC: 1 *** Warning - read failed, using default environment In: serial Out: serial Err: serial Net: FEC Hit any key to stop autoboot: 0 => saveenv Saving Environment to MMC... Writing to MMC(0)... failed The root cause for the failure is the eSDHC-A001 erratum: "eSDHC-A001 : Data timeout counter (SYSCTL[DTOCV]) is not reliable for values of 0x4,0x8, and 0xC" that is listed on some PowerArchitecture chips: https://www.nxp.com/files-static/32bit/doc/errata/MPC8379ECE.pdf Even though eSDHC-A001 is not documented on the i.MX51 errata document, I have confirmed with the NXP design team that this erratum does affect i.MX51, so fix the problem by selecting SYS_FSL_ERRATUM_ESDHC_A001 at SoC level. The i.MX51 ts4800 board already selects this option, but it is better to move this selection to the i.MX51 SoC level instead. Successfully tested with a high speed SD card on a mx51evk board. Signed-off-by:
Fabio Estevam <fabio.estevam@nxp.com> Acked-by:
Sebastien Bourdelin <sebastien.bourdelin@savoirfairelinux.com>
-
Fabio Estevam authored
When a high speed card is connected to mx25 the following error is seen: U-Boot 2017.11-rc2-00104-gb79372a (Oct 31 2017 - 11:02:22 -0200) CPU: Freescale i.MX25 rev1.2 at 399 MHz Reset cause: POR Board: MX25PDK I2C: ready DRAM: 64 MiB No arch specific invalidate_icache_all available! MMC: FSL_SDHC: 0 *** Warning - read failed, using default environment In: serial Out: serial Err: serial Net: FEC Hit any key to stop autoboot: 0 => saveenv Saving Environment to MMC... Writing to MMC(0)... failed , which prevents any usage of the SD card. The root cause for the failure is the eSDHC-A001 erratum: "eSDHC-A001 : Data timeout counter (SYSCTL[DTOCV]) is not reliable for values of 0x4,0x8, and 0xC" that is listed on some PowerArchitecture chips: https://www.nxp.com/files-static/32bit/doc/errata/MPC8379ECE.pdf Even though eSDHC-A001 is not documented on the i.MX25 errata document, I have confirmed with the NXP design team that this erratum does affect i.MX25, so fix the problem by selecting SYS_FSL_ERRATUM_ESDHC_A001 at SoC level. Successfully tested with a high speed SD card on a mx25pdk board. Suggested-by:
Benoît Thébaudeau <benoit@wsystem.com> Signed-off-by:
Fabio Estevam <fabio.estevam@nxp.com> Acked-by:
Sebastien Bourdelin <sebastien.bourdelin@savoirfairelinux.com> Acked-by:
Otavio Salvador <otavio@ossystems.com.br> Tested-by: Otavio Salvador <otavio@ossystems.com.br> # mx25pdk
-
Fabio Estevam authored
The motivation for moving MX25 selection to Kconfig is to be able to better handle MX25 specific errata, so that an errata option can be selected at SoC level instead of board level. This selection method also aligns with the way other i.MX SoCs are selected in U-Boot. Signed-off-by:
Fabio Estevam <fabio.estevam@nxp.com> Acked-by:
Sebastien Bourdelin <sebastien.bourdelin@savoirfairelinux.com> Reviewed-by:
Benoît Thébaudeau <benoit.thebaudeau.dev@gmail.com>
-
Kever Yang authored
Use default value 0x4000 for SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR instead of define a new one. Signed-off-by:
Kever Yang <kever.yang@rock-chips.com> Acked-by:
Philipp Tomsich <philipp.tomsich@theobroma-systems.com> Reviewed-by:
Philipp Tomsich <philipp.tomsich@theobroma-systems.com>
-
Kever Yang authored
Update rockchip U-Boot location to 0x4000/16384. Signed-off-by:
Kever Yang <kever.yang@rock-chips.com> Acked-by:
Philipp Tomsich <philipp.tomsich@theobroma-systems.com> Reviewed-by:
Philipp Tomsich <philipp.tomsich@theobroma-systems.com>
-
Kever Yang authored
Rockchip use a 'loader2' partition for U-Boot, so u-boot.bin or u-boot.itb load by SPL need to locate at0x4000. Detail here: http://opensource.rock-chips.com/wiki_Boot_option Signed-off-by:
Kever Yang <kever.yang@rock-chips.com> Acked-by:
Philipp Tomsich <philipp.tomsich@theobroma-systems.com> Reviewed-by:
Philipp Tomsich <philipp.tomsich@theobroma-systems.com>
-
Klaus Goger authored
The environment storage location is selectable via Kconfig. We support eMMC, SD and SPI-NOR as location for U-Boot. This adds support to store the environment in the SPI-NOR additional to the default eMMC location. Signed-off-by:
Klaus Goger <klaus.goger@theobroma-systems.com> Signed-off-by:
Philipp Tomsich <philipp.tomsich@theobroma-systems.com>
-
Klaus Goger authored
The VCC_SD and VCC_SDIO rail should only be powered up to 3.0V on RK3399 platforms. Signed-off-by:
Klaus Goger <klaus.goger@theobroma-systems.com> Signed-off-by:
Philipp Tomsich <philipp.tomsich@theobroma-systems.com>
-
Klaus Goger authored
pinctrl/rockchip.h provides defines that map pin numbers to pin names. Use them to make the dts more human readable. Signed-off-by:
Klaus Goger <klaus.goger@theobroma-systems.com> Signed-off-by:
Philipp Tomsich <philipp.tomsich@theobroma-systems.com>
-
Philipp Tomsich authored
This change updates the USB configuration for the RK3399-Q7 in the DTS: * fixes the OTG board configuration by enabling it ('okay') * improves the speed of 'usb start' by disabling the unused EHCI/OHCI controllers Signed-off-by:
Philipp Tomsich <philipp.tomsich@theobroma-systems.com> Tested-by:
Klaus Goger <klaus.goger@theobroma-systems.com>
-
Philipp Tomsich authored
To correctly model the usbhub_enable regulator for U-Boot, we need to change the settings to: * the GPIO polarity is GPIO_ACTIVE_LOW * should be set to inactive (enable-active-low) when boot-on settings are applied * it can be changed at runtime (i.e. remove the always-on) Signed-off-by:
Philipp Tomsich <philipp.tomsich@theobroma-systems.com> Tested-by:
Klaus Goger <klaus.goger@theobroma-systems.com>
-
Philipp Tomsich authored
The fixed regulator for overriding BIOS_DISABLE had been modelling backwards (i.e. the GPIO polarity and the enable-active-low/high property had both been inverted), causing the 'regulator' command to always print/expect 'disabled'/'enabled' backwards. This fixes the mix-up and models it correctly: * the GPIO is low-active * the regulator should be enabled (enable-active-high) during boot-on initialisation Signed-off-by:
Philipp Tomsich <philipp.tomsich@theobroma-systems.com> Tested-by:
Klaus Goger <klaus.goger@theobroma-systems.com>
-
Kever Yang authored
All Rockchip SoCs use 32KB as CONFIG_ENV_SIZE. Signed-off-by:
Kever Yang <kever.yang@rock-chips.com> Acked-by:
Philipp Tomsich <philipp.tomsich@theobroma-systems.com> Reviewed-by:
Philipp Tomsich <philipp.tomsich@theobroma-systems.com>
-
Kever Yang authored
Using the ENV offset from rockchip legacy U-Boot for all SoCs, the offset is 4MB-32KB Signed-off-by:
Kever Yang <kever.yang@rock-chips.com> Acked-by:
Philipp Tomsich <philipp.tomsich@theobroma-systems.com> Reviewed-by:
Philipp Tomsich <philipp.tomsich@theobroma-systems.com>
-
Kever Yang authored
We use the same default ENV setting in rockchip_common.h for all SoC. Signed-off-by:
Kever Yang <kever.yang@rock-chips.com> Acked-by:
Philipp Tomsich <philipp.tomsich@theobroma-systems.com> Reviewed-by:
Philipp Tomsich <philipp.tomsich@theobroma-systems.com>
-
- Nov 06, 2017
-
-
Tom Rini authored
Signed-off-by:
Tom Rini <trini@konsulko.com>
-
Chris Brandt authored
Renesas was spelled wrong. Signed-off-by:
Chris Brandt <chris.brandt@renesas.com>
-
Jan Kundrát authored
U-Boot bundles a patched copy of libfdt, so it's wrong to attempt to include it <like/this>. This breaks the build for me when I have dtc fully installed in my host -- as happened earlier tonight with Buildroot, for example. There are several other occurrences throughout the code where '<libfdt' matches. I'm not modifying these because I have no clue why the <systemwide> include style is being used -- IMHO wrongly. Signed-off-by:
Jan Kundrát <jan.kundrat@cesnet.cz>
-
Angelo Dureghello authored
Update m68k documentation to reflect the current ColdFire architecture support status. Signed-off-by:
Angelo Dureghello <angelo@sysam.it>
-
Shawn Guo authored
The check in part_get_info_extended() for a successful partition searching misses a condition for extended partition. In case of (ext_part_sector == 0), we should anyway mark the partition as found, even if it's an extended partition, i.e. (is_extended(pt->sys_ind) == 0). Otherwise, the extended partition (type 0x0f) will never be identified, and the following recursive call to part_get_info_extended() will get a wrong 'part_num' and 'which_part' parameter. In the end, all those partitions in extended table will not be identified. Let's add the missing OR condition of (ext_part_sector == 0) for is_extended() check to fix the problem. The issue is discovered by running fastboot flash to an extended partition on eMMC. $ fastboot flash mmcsda5 cache.img target reported max download size of 536870912 bytes sending 'mmcsda5' (18796 KB)... OKAY [ 2.144s] writing 'mmcsda5'... FAILED (remote: cannot find partition) finished. total time: 2.261s Signed-off-by:
Shawn Guo <shawn.guo@linaro.org>
-
Lukasz Majewski authored
Before this patch one could receive following errors when executing "gpt write" command on machine with cache enabled: display5 factory > gpt write mmc ${mmcdev} ${partitions} Writing GPT: CACHE: Misaligned operation at range [4ef8f7f0, 4ef8f9f0] CACHE: Misaligned operation at range [4ef8f9f8, 4ef939f8] CACHE: Misaligned operation at range [4ef8f9f8, 4ef939f8] CACHE: Misaligned operation at range [4ef8f7f0, 4ef8f9f0] success! To alleviate this problem - the calloc()s have been replaced with malloc_cache_aligned() and memset(). After those changes the buffers are properly aligned (with both start address and size) to SoC cache line. Signed-off-by:
Lukasz Majewski <lukma@denx.de>
-
Masahiro Yamada authored
This function is called when signing configuration nodes. Adjust the error message. I do not know why we do not need to show the error message in case of ENOSPC. Remove the if-conditional that seems unnecessary. Signed-off-by:
Masahiro Yamada <yamada.masahiro@socionext.com>
-
Masahiro Yamada authored
If -K option is missing when you sign image nodes, it fails with an unclear error message: tools/mkimage Can't add hashes to FIT blob: -1 It is hard to figure out the cause of the failure. In contrast, when you sign configuration nodes, -K is optional because fit_config_process_sig() returns successfully if keydest is unset. Probably this is a preferred behavior when you want to update FIT with the same key; you do not have to update the public key in this case. So, this commit changes fit_image_process_sig() to continue signing without keydest. If ->add_verify_data() fails, show a clearer error message, which has been borrowed from fit_config_process_sig(). Signed-off-by:
Masahiro Yamada <yamada.masahiro@socionext.com>
-
Masahiro Yamada authored
The "algo_name" points to a property in a blob being edited. The pointer becomes stale when fit_image_write_sig() inserts signatures. Then crypto->add_verify_data() writes wrong data to the public key destination. Signed-off-by:
Masahiro Yamada <yamada.masahiro@socionext.com>
-
Stephen Warren authored
test_gpt generates a persistent disk image which can be re-used across multiple test runs. Currently, if the Python code that generates the disk image change, the image is not regenerated, which could cause test failures e.g. if a test was updated to expect some new partition name or size, yet the persistent disk image contained the old name or size. This change introduces functionality to regenerate the disk image if the instructions to generate the image have changed. Signed-off-by:
Stephen Warren <swarren@nvidia.com>
-
Stefan Agner authored
The fw_env utility family has a default environment compiled in which ties it quite strongly to the U-Boot source/config it has been built with. Allow to display the U-Boot version it has been built with using the -v/--version argument. Signed-off-by:
Stefan Agner <stefan.agner@toradex.com> Reviewed-by:
Lukasz Majewski <lukma@denx.de>
-
Masahiro Yamada authored
Designated initializers are more readable because we do not have to check the order in the struct definitions. Signed-off-by:
Masahiro Yamada <yamada.masahiro@socionext.com> Reviewed-by:
Simon Glass <sjg@chromium.org>
-