June 2017 - U-Boot

[U-Boot] [PULL] u-boot-usb/master
by Marek Vasut 20 Jun '17

20 Jun '17

The following changes since commit b9f7d8817424bb328d5eac9b16196a1189b8b6f5: powerpc, 5xx: remove some "5xx" remains (2017-06-16 10:14:56 -0400) are available in the git repository at: git://git.denx.de/u-boot-usb.git master for you to fetch changes up to b9203429a04402bd03c48fa87670686ef7e7891d: cmd: usb_mass_storage: Staticize do_usb_mass_storage() (2017-06-18 21:11:10 +0200) ---------------------------------------------------------------- Alexey Brodkin (1): drivers/usb/ehci: Use platform-specific accessors Fabio Estevam (2): cmd: usb_mass_storage: Use NULL for pointer cmd: usb_mass_storage: Staticize do_usb_mass_storage() Meng Dongyang (1): usb: dwc2: force to host mode if not support HNP/SRP Tom Rini (1): at91_udc.c: Fix unused variable warning cmd/usb_mass_storage.c | 4 ++-- drivers/usb/gadget/at91_udc.c | 10 ---------- drivers/usb/host/dwc2.c | 19 ++++++++++++++++--- drivers/usb/host/ehci.h | 10 ++++------ 4 files changed, 22 insertions(+), 21 deletions(-)

2 1

[U-Boot] Use u-boot to recover bricked NVIDIA SHIELD TV.
by Matthew Gorski 19 Jun '17

19 Jun '17

I am curious if there is a possibility to recover a wrongly flashed NVIDIA SHIELD TV device by flashing u-boot instead of cboot and mounting the emmc in uboot to do some repairs. If I lose keys for widevine I won't care I just would like to know if this or any remedy is possible when stuck in APX mode after a wrongly flashed system. My device is past the warranty date so an RMA is not an option. Even if I could possibly flash linux4tegra it would still be better than having a bricked device stuck in an unusable state. Any help is immensely appreciated. Please help u-boot community and or anyone at NVIDIA. Tried APX flashing the same as I flash my Jetson TX1 devkit. Log below. sudo ./tegraflash.py --bl cboot.bin --bct bct_e2530.cfg --odmdata 0x84000 --bldtb tegra210-foster-e-p2530-0930-e02-00.dtb --applet nvtboot_recovery.bin --cmd "flash;reboot" --cfg flash_t210_android_sdmmc.xml --chip 0x21 Welcome to Tegra Flash version 1.0.0 Type ? or help for help and q or quit to exit Use ! to execute system commands [ 0.0000 ] Generating RCM messages [ 0.0017 ] tegrarcm --listrcm rcm_list.xml --chip 0x21 --download rcm nvtboot_recovery.bin 0 0 [ 0.0033 ] RCM 0 is saved as rcm_0.rcm [ 0.0043 ] RCM 1 is saved as rcm_1.rcm [ 0.0043 ] List of rcm files are saved in rcm_list.xml [ 0.0044 ] [ 0.0044 ] Signing RCM messages [ 0.0060 ] tegrasign --key None --list rcm_list.xml --pubkeyhash pub_key.key [ 0.0076 ] Assuming zero filled SBK key [ 0.0255 ] [ 0.0256 ] Copying signature to RCM mesages [ 0.0273 ] tegrarcm --chip 0x21 --updatesig rcm_list_signed.xml [ 0.0299 ] [ 0.0299 ] Parsing partition layout [ 0.0317 ] tegraparser --pt flash_t210_android_sdmmc.xml [ 0.0341 ] [ 0.0341 ] Creating list of images to be signed [ 0.0358 ] tegrahost --chip 0x21 --partitionlayout flash_t210_android_sdmmc.bin --list images_list.xml [ 0.0444 ] [ 0.0445 ] Generating signatures [ 0.0460 ] tegrasign --key None --list images_list.xml --pubkeyhash pub_key.key [ 0.0477 ] Assuming zero filled SBK key [ 0.4273 ] [ 0.4291 ] tegrabct --bct bct_e2530.cfg --chip 0x21 [ 0.4308 ] Copying Sdram info from 0 to 1 set [ 0.4339 ] Copying Sdram info from 1 to 2 set [ 0.4339 ] Copying Sdram info from 2 to 3 set [ 0.4339 ] [ 0.4340 ] Updating boot device parameters [ 0.4356 ] tegrabct --bct bct_e2530.bct --chip 0x21 --updatedevparam flash_t210_android_sdmmc.bin [ 0.4371 ] Warning: No sdram params [ 0.4374 ] [ 0.4374 ] Updating bl info [ 0.4391 ] tegrabct --bct bct_e2530.bct --chip 0x21 --updateblinfo flash_t210_android_sdmmc.bin --updatesig images_list_signed.xml [ 0.4418 ] [ 0.4419 ] Updating secondary storage information into bct [ 0.4435 ] tegraparser --pt flash_t210_android_sdmmc.bin --chip 0x21 --updatecustinfo bct_e2530.bct [ 0.4453 ] [ 0.4454 ] Updating Odmdata [ 0.4469 ] tegrabct --bct bct_e2530.bct --chip 0x21 --updatefields Odmdata = 0x84000 [ 0.4484 ] Warning: No sdram params [ 0.4486 ] [ 0.4487 ] Get Signed section bct [ 0.4502 ] tegrabct --bct bct_e2530.bct --chip 0x21 --listbct bct_list.xml [ 0.4520 ] [ 0.4520 ] Signing BCT [ 0.4536 ] tegrasign --key None --list bct_list.xml --pubkeyhash pub_key.key [ 0.4551 ] Assuming zero filled SBK key [ 0.4563 ] [ 0.4563 ] Updating BCT with signature [ 0.4578 ] tegrabct --bct bct_e2530.bct --chip 0x21 --updatesig bct_list_signed.xml [ 0.4597 ] [ 0.4598 ] Copying signatures [ 0.4613 ] tegrahost --chip 0x21 --partitionlayout flash_t210_android_sdmmc.bin --updatesig images_list_signed.xml [ 0.4628 ] Run tegrabct to update tboot signature in bct [ 0.4639 ] Run tegrabct to update tboot signature in bct [ 0.4811 ] [ 0.4811 ] Updating BFS information [ 0.4829 ] tegrabct --bct bct_e2530.bct --chip 0x21 --updatebfsinfo flash_t210_android_sdmmc.bin [ 0.4848 ] [ 0.4849 ] Boot Rom communication [ 0.4864 ] tegrarcm --chip 0x21 --rcm rcm_list_signed.xml [ 0.4880 ] BR_CID: 0x621010015c6561861800000010fd8140 [ 0.4890 ] RCM version 0X13 [ 0.4890 ] Boot Rom communication failed [ 0.4890 ] Error: Return value 3 Command tegrarcm --chip 0x21 --rcm rcm_list_signed.xml

4 7

[U-Boot] Driver model u-boot 2017
by Christine Gharzuzi 19 Jun '17

19 Jun '17

Hi Simon, I need an early binding in order to print information about the CPU frequency using a driver I implemented using driver model. u-boot starts binding all the devices at once? I don't understand why the printing is performed during the binding (I have only 1 CPU) also it's performed right after the root driver bind. Thanks, Christine ---------------------------------------------------------------------- Hi Christine, On 14 June 2017 at 10:18, Christine Gharzuzi <chrisg(a)marvell.com<mailto:chrisg@marvell.com>> wrote: > Hi, > > I Need an early binding for a device right after the root driver is binding. > By doing a simple debug I see that after binding the root driver > there's an attempt to bind > > all the devices (nodes) from the device tree to their suitable driver, > the device I want to bind to its drivers is also a part of my device > tree but I need it > > to be right after the root driver binding and not according to the > nodes sequence in the device tree. > > I hope there's a way to do so. Why do you need this? Regards, Simon

2 1

[U-Boot] [PATCH v8 0/7] Add Intel Arria 10 SoC FPGA driver
by tien.fong.chee＠intel.com 19 Jun '17

19 Jun '17

From: Tien Fong Chee <tien.fong.chee(a)intel.com> This is the 8th version of patchset to adds support for Intel Arria 10 SoC FPGA driver. This version mainly resolved comments from Marek in [v7] and pulling in the Intel related FPGA Kconfig conversion patch into this patchset. This series is working on top of u-boot-socfpga.git - http://git.denx.de/u-boot-socfpga.git [v7]: https://www.mail-archive.com/u-boot@lists.denx.de/msg251213.html v7 -> v8 changes: ----------------- - Pull in the Intel related FPGA Kconfig convertion patch into this patchset - Changed SPL_FPGA_SUPPORT Macro config header into Kconfig - Improved the git commit message on patch 5, which has explanation why FPGA build must be enabled in SPL before applying patch 6 to avoid build failed when the expected functions in driver/fpga/ is not availabled in SPL. Patchset history ---------------- [v1]: https://www.mail-archive.com/u-boot@lists.denx.de/msg247788.html [v2]: https://www.mail-archive.com/u-boot@lists.denx.de/msg248541.html [v3]: https://www.mail-archive.com/u-boot@lists.denx.de/msg249160.html [v4]: https://www.mail-archive.com/u-boot@lists.denx.de/msg250149.html [v5]: https://www.mail-archive.com/u-boot@lists.denx.de/msg250517.html [v6]: https://www.mail-archive.com/u-boot@lists.denx.de/msg250687.html Tien Fong Chee (7): arm: socfpga: Remove unused passing parameter of socfpga_bridges_reset arm: socfpga: Restructure FPGA driver in the preparation to support A10 arm: socfpga: Convert all Intel related FPGA configuration to Kconfig arm: socfpga: Enable FPGA driver on SPL drivers: Enable FPGA driver build on SPL arm: socfpga: Move FPGA manager driver to FPGA driver arm: socfpga: Add FPGA driver support for Arria 10 arch/arm/mach-socfpga/Makefile | 1 - arch/arm/mach-socfpga/fpga_manager.c | 78 ---- arch/arm/mach-socfpga/include/mach/fpga_manager.h | 70 +-- .../include/mach/fpga_manager_arria10.h | 100 +++++ .../mach/{fpga_manager.h => fpga_manager_gen5.h} | 69 ++- .../include/mach/reset_manager_arria10.h | 2 +- arch/arm/mach-socfpga/reset_manager_arria10.c | 4 +- configs/astro_mcf5373l_defconfig | 1 + configs/socfpga_arria10_defconfig | 2 + configs/socfpga_arria5_defconfig | 2 + configs/socfpga_cyclone5_defconfig | 2 + configs/socfpga_de0_nano_soc_defconfig | 2 + configs/socfpga_de10_nano_defconfig | 2 + configs/socfpga_de1_soc_defconfig | 2 + configs/socfpga_is1_defconfig | 2 + configs/socfpga_mcvevk_defconfig | 2 + configs/socfpga_sockit_defconfig | 2 + configs/socfpga_socrates_defconfig | 2 + configs/socfpga_sr1500_defconfig | 2 + configs/socfpga_vining_fpga_defconfig | 2 + configs/theadorable_debug_defconfig | 1 + configs/theadorable_defconfig | 1 + drivers/Makefile | 1 + drivers/fpga/Kconfig | 8 + drivers/fpga/Makefile | 2 + drivers/fpga/socfpga.c | 241 +---------- drivers/fpga/socfpga_arria10.c | 479 +++++++++++++++++++++ drivers/fpga/{socfpga.c => socfpga_gen5.c} | 98 ++--- include/configs/astro_mcf5373l.h | 2 - include/configs/socfpga_common.h | 6 +- include/configs/theadorable.h | 2 - 31 files changed, 719 insertions(+), 471 deletions(-) delete mode 100644 arch/arm/mach-socfpga/fpga_manager.c create mode 100644 arch/arm/mach-socfpga/include/mach/fpga_manager_arria10.h copy arch/arm/mach-socfpga/include/mach/{fpga_manager.h => fpga_manager_gen5.h} (57%) create mode 100644 drivers/fpga/socfpga_arria10.c copy drivers/fpga/{socfpga.c => socfpga_gen5.c} (85%) -- 2.2.0

4 41

[U-Boot] [PATCH 1/2] rpi: Change load addresses to make more room for the kernel
by Tuomas Tynkkynen 19 Jun '17

19 Jun '17

According to the comment in rpi.h, the current kernel load address is picked such that the compressed kernel and the uncompressed kernel don't overlap in memory to avoid unnecessary relocation of the compressed image in the decompressor stub. However, as is evident from the kernel boot log snipped below, a full-blown ARMv7 distro kernel (v4.11.3) can use as much as 17063 kB uncompressed. That is larger than the current 16M reservation which means that the relocation indeed is happening. [ 0.000000] Virtual kernel memory layout: .text : 0xc0208000 - 0xc0f00000 (13280 kB) .init : 0xc1500000 - 0xc1700000 (2048 kB) .data : 0xc1700000 - 0xc18b1978 (1735 kB) Additionally, on AArch64 the kernel images are much larger than on ARM. A full-blown 4.11.3 distro kernel takes 24M, which with the current load addresses (reserving only 17M) stomps over the initrd, breaking the boot of such large kernels. Fix both of these problems by tweaking the load addresses as appropriate depending on the CPU architecture. To make things simpler, pxefile_addr_r is moved from low memory next to scriptaddr. After this patch we end up with this memory map on ARM (assuming the most conservative CPU-GPU memory split of 128M for the CPU): 0x00000100 - 0x00008000 ( 31 kB): fdt_addr_r - decompressed_kernel_start 0x00008000 - 0x03000000 ( 49120 kB): decompressed_kernel - kernel_addr_r 0x03000000 - 0x04000000 ( 16384 kB): kernel_addr_r - scriptaddr 0x04000000 - 0x04100000 ( 1024 kB): scriptaddr - pxefile_addr_r 0x04100000 - 0x04200000 ( 1024 kB): pxefile_addr_r - ramdisk_addr_r 0x04200000 - 0x08000000 ( 63488 kB): ramdisk_addr_r - top_of_ram And this for AArch64: 0x00000100 - 0x00080000 ( 511 kB): fdt_addr_r - kernel_addr_r 0x00080000 - 0x04000000 ( 65024 kB): kernel_addr_r - scriptaddr 0x04000000 - 0x04100000 ( 1024 kB): scriptaddr - pxefile_addr_r 0x04100000 - 0x04200000 ( 1024 kB): pxefile_addr_r - ramdisk_addr_r 0x04200000 - 0x08000000 ( 63488 kB): ramdisk_addr_r - top_of_ram Signed-off-by: Tuomas Tynkkynen <tuomas.tynkkynen(a)iki.fi> --- This has been tested on: - RPi 1 booting the RPi Foundation downstream kernel - RPi 3 booting a distro multi_v7_defconfig in 32-bit mode - RPi 3 booting a AArch64 distro defconfig in 64-bit mode --- include/configs/rpi.h | 36 +++++++++++++++++++++++++----------- 1 file changed, 25 insertions(+), 11 deletions(-) diff --git a/include/configs/rpi.h b/include/configs/rpi.h index d715eaad14..a2d82a9146 100644 --- a/include/configs/rpi.h +++ b/include/configs/rpi.h @@ -131,32 +131,46 @@ * U-Boot (and scripts it executes) typicaly ignore the DT loaded by the FW * and loads its own DT from disk (triggered by boot.scr or extlinux.conf). * - * pxefile_addr_r can be pretty much anywhere that doesn't conflict with - * something else. Put it low in memory to avoid conflicts. + * kernel_addr_r has different constraints on ARM and Aarch64. + * For Aarch64, the kernel image is uncompressed and must be loaded at + * text_offset bytes (specified in the header of the Image) into a + * 2MB boundary. As Linux uses a default text_offset of 0x80000, load + * the kernel at 0x80000 so that the 'booti' command does not need + * to perform any relocation of the Image in the typical case. * - * kernel_addr_r must be within the first 128M of RAM in order for the + * For 32-bit ARM, it must be within the first 128M of RAM in order for the * kernel's CONFIG_AUTO_ZRELADDR option to work. Since the kernel will * decompress itself to 0x8000 after the start of RAM, kernel_addr_r * should not overlap that area, or the kernel will have to copy itself * somewhere else before decompression. Similarly, the address of any other * data passed to the kernel shouldn't overlap the start of RAM. Pushing - * this up to 16M allows for a sizable kernel to be decompressed below the + * this up to 48M allows for a sizable kernel to be decompressed below the * compressed load address. * * scriptaddr can be pretty much anywhere that doesn't conflict with something - * else. Choosing 32M allows for the compressed kernel to be up to 16M. + * else. Choosing 64M allows for the compressed kernel to be up to 16M on + * 32-bit ARM and roughly 64M for the uncompressed kernel on Aarch64. + * + * pxefile_addr_r can be pretty much anywhere that doesn't conflict with + * something else. Choosing 65M allows for any boot script to be up to 1M, + * which is hopefully plenty. * - * ramdisk_addr_r simply shouldn't overlap anything else. Choosing 33M allows - * for any boot script to be up to 1M, which is hopefully plenty. + * ramdisk_addr_r simply shouldn't overlap anything else. Choosing 66M allows + * for any PXE configuration file to be up to 1M, which is hopefully plenty. */ +#ifdef CONFIG_ARM64 +# define KERNEL_ADDR_R "0x00080000" +#else +# define KERNEL_ADDR_R "0x03000000" +#endif #define ENV_MEM_LAYOUT_SETTINGS \ "fdt_high=ffffffff\0" \ "initrd_high=ffffffff\0" \ "fdt_addr_r=0x00000100\0" \ - "pxefile_addr_r=0x00100000\0" \ - "kernel_addr_r=0x01000000\0" \ - "scriptaddr=0x02000000\0" \ - "ramdisk_addr_r=0x02100000\0" \ + "kernel_addr_r=" KERNEL_ADDR_R "\0" \ + "scriptaddr=0x04000000\0" \ + "pxefile_addr_r=0x04100000\0" \ + "ramdisk_addr_r=0x04200000\0" \ #define BOOT_TARGET_DEVICES(func) \ func(MMC, mmc, 0) \ -- 2.13.0

2 2

[U-Boot] Getting splash screen to work
by Sergey Borovkov 19 Jun '17

19 Jun '17

Hello, I am trying to get splash screen work in the uboot but have no luck so far. Anyone can help me with what I might be doing wrong? I have following code right now: fatload ${devtype} ${devnum}:${bootpart} 0x00200000 /splash.bmp && bmp display 0x00200000; I can see that image is actually loaded into the RAM. I can read it back with bmp info. bmp display does nothing though. I tried putting an image with incorrect color depth on the SD card and at that time bmp display actually complained about incorrect color depth. So it's actually called and can read the image. Setting splashimage variable made no difference as well unfortunately.

1 0

[U-Boot] [PATCH] SECURE_BOOT: Unify memory map for Layerscape based platforms
by Sumit Garg 19 Jun '17

19 Jun '17

Unify memory map for Layerscape based platforms as per DASH SDK memory map. This patch includes changes in bootscript, bootscript header and PPA header addresses change as per unified memory map. Signed-off-by: Sumit Garg <sumit.garg(a)nxp.com> Tested-by: Vinitha Pillai <vinitha.pillai(a)nxp.com> --- arch/arm/cpu/armv8/fsl-layerscape/Kconfig | 12 +++---- arch/arm/include/asm/fsl_secure_boot.h | 54 +++++++++++++------------------ 2 files changed, 28 insertions(+), 38 deletions(-) diff --git a/arch/arm/cpu/armv8/fsl-layerscape/Kconfig b/arch/arm/cpu/armv8/fsl-layerscape/Kconfig index 8270431..c849c05 100644 --- a/arch/arm/cpu/armv8/fsl-layerscape/Kconfig +++ b/arch/arm/cpu/armv8/fsl-layerscape/Kconfig @@ -206,12 +206,12 @@ config SYS_LS_PPA_FW_ADDR config SYS_LS_PPA_ESBC_ADDR hex "hdr address of PPA firmware loading from" depends on FSL_LS_PPA && CHAIN_OF_TRUST - default 0x600c0000 if SYS_LS_PPA_FW_IN_XIP && ARCH_LS1043A - default 0x40740000 if SYS_LS_PPA_FW_IN_XIP && ARCH_LS1046A - default 0x40480000 if SYS_LS_PPA_FW_IN_XIP && ARCH_LS1012A - default 0x580c40000 if SYS_LS_PPA_FW_IN_XIP && FSL_LSCH3 - default 0x700000 if SYS_LS_PPA_FW_IN_MMC - default 0x700000 if SYS_LS_PPA_FW_IN_NAND + default 0x60680000 if SYS_LS_PPA_FW_IN_XIP && ARCH_LS1043A + default 0x40680000 if SYS_LS_PPA_FW_IN_XIP && ARCH_LS1046A + default 0x40680000 if SYS_LS_PPA_FW_IN_XIP && ARCH_LS1012A + default 0x580680000 if SYS_LS_PPA_FW_IN_XIP && FSL_LSCH3 + default 0x680000 if SYS_LS_PPA_FW_IN_MMC + default 0x680000 if SYS_LS_PPA_FW_IN_NAND help If the PPA header firmware locate at XIP flash, such as NOR or QSPI flash, this address is a directly memory-mapped. diff --git a/arch/arm/include/asm/fsl_secure_boot.h b/arch/arm/include/asm/fsl_secure_boot.h index 7bff8b7..42ae4e2 100644 --- a/arch/arm/include/asm/fsl_secure_boot.h +++ b/arch/arm/include/asm/fsl_secure_boot.h @@ -1,5 +1,6 @@ /* * Copyright 2015 Freescale Semiconductor, Inc. + * Copyright 2017 NXP * * SPDX-License-Identifier: GPL-2.0+ */ @@ -77,55 +78,44 @@ * DDR memory map */ #ifdef CONFIG_FSL_LSCH3 -#define CONFIG_BS_HDR_ADDR_DEVICE 0x580d00000 -#define CONFIG_BS_ADDR_DEVICE 0x580e00000 -#define CONFIG_BS_HDR_ADDR_RAM 0xa0d00000 -#define CONFIG_BS_ADDR_RAM 0xa0e00000 -#define CONFIG_BS_HDR_SIZE 0x00002000 +#define CONFIG_BS_ADDR_DEVICE 0x580600000 +#define CONFIG_BS_HDR_ADDR_DEVICE 0x580640000 #define CONFIG_BS_SIZE 0x00001000 +#define CONFIG_BS_HDR_SIZE 0x00004000 +#define CONFIG_BS_ADDR_RAM 0xa0600000 +#define CONFIG_BS_HDR_ADDR_RAM 0xa0640000 #else #ifdef CONFIG_SD_BOOT /* For SD boot address and size are assigned in terms of sector * offset and no. of sectors respectively. */ -#if defined(CONFIG_LS1043A) || defined(CONFIG_ARCH_LS1046A) -#define CONFIG_BS_HDR_ADDR_DEVICE 0x00000920 -#else -#define CONFIG_BS_HDR_ADDR_DEVICE 0x00000900 -#endif -#define CONFIG_BS_ADDR_DEVICE 0x00000940 -#define CONFIG_BS_HDR_SIZE 0x00000010 +#define CONFIG_BS_ADDR_DEVICE 0x00003000 +#define CONFIG_BS_HDR_ADDR_DEVICE 0x00003200 #define CONFIG_BS_SIZE 0x00000008 +#define CONFIG_BS_HDR_SIZE 0x00000010 #elif defined(CONFIG_NAND_BOOT) -#define CONFIG_BS_HDR_ADDR_DEVICE 0x00800000 -#define CONFIG_BS_ADDR_DEVICE 0x00802000 -#define CONFIG_BS_HDR_SIZE 0x00002000 -#define CONFIG_BS_SIZE 0x00001000 -#elif defined(CONFIG_QSPI_BOOT) -#ifdef CONFIG_ARCH_LS1046A -#define CONFIG_BS_HDR_ADDR_DEVICE 0x40780000 -#define CONFIG_BS_ADDR_DEVICE 0x40800000 -#elif defined(CONFIG_ARCH_LS1012A) -#define CONFIG_BS_HDR_ADDR_DEVICE 0x400c0000 -#define CONFIG_BS_ADDR_DEVICE 0x40060000 -#else -#error "Platform not supported" -#endif +#define CONFIG_BS_ADDR_DEVICE 0x00600000 +#define CONFIG_BS_HDR_ADDR_DEVICE 0x00640000 +#define CONFIG_BS_SIZE 0x00001000 #define CONFIG_BS_HDR_SIZE 0x00002000 +#elif defined(CONFIG_QSPI_BOOT) +#define CONFIG_BS_ADDR_DEVICE 0x40600000 +#define CONFIG_BS_HDR_ADDR_DEVICE 0x40640000 #define CONFIG_BS_SIZE 0x00001000 -#else /* Default NOR Boot */ -#define CONFIG_BS_HDR_ADDR_DEVICE 0x600a0000 -#define CONFIG_BS_ADDR_DEVICE 0x60060000 #define CONFIG_BS_HDR_SIZE 0x00002000 +#else /* Default NOR Boot */ +#define CONFIG_BS_ADDR_DEVICE 0x60600000 +#define CONFIG_BS_HDR_ADDR_DEVICE 0x60640000 #define CONFIG_BS_SIZE 0x00001000 +#define CONFIG_BS_HDR_SIZE 0x00002000 #endif -#define CONFIG_BS_HDR_ADDR_RAM 0x81000000 -#define CONFIG_BS_ADDR_RAM 0x81020000 +#define CONFIG_BS_ADDR_RAM 0x81000000 +#define CONFIG_BS_HDR_ADDR_RAM 0x81020000 #endif #ifdef CONFIG_BOOTSCRIPT_COPY_RAM -#define CONFIG_BOOTSCRIPT_HDR_ADDR CONFIG_BS_HDR_ADDR_RAM #define CONFIG_BOOTSCRIPT_ADDR CONFIG_BS_ADDR_RAM +#define CONFIG_BOOTSCRIPT_HDR_ADDR CONFIG_BS_HDR_ADDR_RAM #else #define CONFIG_BOOTSCRIPT_HDR_ADDR CONFIG_BS_HDR_ADDR_DEVICE /* BOOTSCRIPT_ADDR is not required */ -- 1.9.1

2 5

[U-Boot] [GIT] Pull request: u-boot-dfu
by Lukasz Majewski 18 Jun '17

18 Jun '17

Dear Marek, Please find pull request for dfu repository: The following changes since commit 9000eddbae0d292331ef403b0a1ff7ec7a983a79: drivers/usb/ehci: Use platform-specific accessors (2017-06-17 17:59:03 +0200) are available in the git repository at: git://git.denx.de/u-boot-dfu.git for you to fetch changes up to b9203429a04402bd03c48fa87670686ef7e7891d: cmd: usb_mass_storage: Staticize do_usb_mass_storage() (2017-06-18 21:11:10 +0200) ---------------------------------------------------------------- Fabio Estevam (2): cmd: usb_mass_storage: Use NULL for pointer cmd: usb_mass_storage: Staticize do_usb_mass_storage() Tom Rini (1): at91_udc.c: Fix unused variable warning cmd/usb_mass_storage.c | 4 ++-- drivers/usb/gadget/at91_udc.c | 10 ---------- 2 files changed, 2 insertions(+), 12 deletions(-) Best regards, Lukasz Majewski -- DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd(a)denx.de

2 1

[U-Boot] [PATCH] ARM: rmobile: salvator-x: Enable CMD_MMC
by Marek Vasut 17 Jun '17

17 Jun '17

The CONFIG_CMD_MMC is not automatically enabled, explicitly add it into the default configuration files. Signed-off-by: Marek Vasut <marek.vasut+renesas(a)gmail.com> Cc: Nobuhiro Iwamatsu <iwamatsu(a)nigauri.org> --- configs/r8a7795_salvator-x_defconfig | 1 + configs/r8a7796_salvator-x_defconfig | 1 + 2 files changed, 2 insertions(+) diff --git a/configs/r8a7795_salvator-x_defconfig b/configs/r8a7795_salvator-x_defconfig index 1eba299242..2424f69ff8 100644 --- a/configs/r8a7795_salvator-x_defconfig +++ b/configs/r8a7795_salvator-x_defconfig @@ -15,6 +15,7 @@ CONFIG_CMD_SAVEENV=y CONFIG_CMD_NET=y CONFIG_CMD_NFS=y CONFIG_CMD_MII=y +CONFIG_CMD_MMC=y CONFIG_CMD_PING=y CONFIG_CMD_FAT=y CONFIG_CMD_DHCP=y diff --git a/configs/r8a7796_salvator-x_defconfig b/configs/r8a7796_salvator-x_defconfig index 5bd762da79..eb29cc1029 100644 --- a/configs/r8a7796_salvator-x_defconfig +++ b/configs/r8a7796_salvator-x_defconfig @@ -15,6 +15,7 @@ CONFIG_CMD_SAVEENV=y CONFIG_CMD_NET=y CONFIG_CMD_NFS=y CONFIG_CMD_MII=y +CONFIG_CMD_MMC=y CONFIG_CMD_PING=y CONFIG_CMD_FAT=y CONFIG_CMD_DHCP=y -- 2.11.0

1 0

[U-Boot] [PATCH] ARM: rmobile: Increase console buffer sizes
by Marek Vasut 17 Jun '17

17 Jun '17

Allow pasting extra long lines into the U-Boot console on RCar Gen3. This is OK since we have plenty of resources and it's convenient. Signed-off-by: Marek Vasut <marek.vasut+renesas(a)gmail.com> Cc: Nobuhiro Iwamatsu <iwamatsu(a)nigauri.org> --- include/configs/rcar-gen3-common.h | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/include/configs/rcar-gen3-common.h b/include/configs/rcar-gen3-common.h index 8da3e7a235..6c23249861 100644 --- a/include/configs/rcar-gen3-common.h +++ b/include/configs/rcar-gen3-common.h @@ -39,12 +39,12 @@ #define CONFIG_SH_GPIO_PFC /* console */ - +#define CONFIG_SYS_CBSIZE 2048 +#define CONFIG_SYS_PBSIZE \ + (CONFIG_SYS_CBSIZE + sizeof(CONFIG_SYS_PROMPT) + 16) +#define CONFIG_SYS_BARGSIZE CONFIG_SYS_CBSIZE #define CONFIG_SYS_LONGHELP -#define CONFIG_SYS_CBSIZE 256 -#define CONFIG_SYS_PBSIZE 256 -#define CONFIG_SYS_MAXARGS 16 -#define CONFIG_SYS_BARGSIZE 512 +#define CONFIG_SYS_MAXARGS 64 #define CONFIG_SYS_BAUDRATE_TABLE { 115200, 38400 } /* MEMORY */ -- 2.11.0

1 0