July 2017 - U-Boot

[U-Boot] [PATCH v2 0/6] AM43xx OP-TEE support
by Andrew F. Davis 25 Jul '17

25 Jul '17

Hello all, This series brings our firewall and OP-TEE support from DRA7xx/AM57xx family devices to the AM43xx class devices. We do this by factoring out code common code from omap5/ into common mach-omap2/ sources. Then add the hooks for the AM43xx boards. Thanks, Andrew Changes from v1: - Stop format-patch from thinking the first patch is a rename - Rebase on latest master Andrew F. Davis (6): arm: mach-omap2: Move omap5/sec-fxns.c into sec-common.c arm: mach-omap2: Factor out common FDT fixup suport arm: mach-omap2: fdt-common: Add OP-TEE node when firmware node is defined arm: mach-omap2: am33xx: Add FDT fixup suport for AM33xx/AM43xx boards board: ti: am43xx: Add TEE loading and firewall setup board: ti: am43xx: Add FDT fixup for HS devices arch/arm/include/asm/omap_common.h | 5 + arch/arm/include/asm/omap_sec_common.h | 6 + arch/arm/mach-omap2/Kconfig | 26 ++++ arch/arm/mach-omap2/Makefile | 2 + arch/arm/mach-omap2/am33xx/Makefile | 1 + arch/arm/mach-omap2/am33xx/fdt.c | 43 ++++++ arch/arm/mach-omap2/fdt-common.c | 168 +++++++++++++++++++++++ arch/arm/mach-omap2/omap5/Kconfig | 26 ---- arch/arm/mach-omap2/omap5/Makefile | 1 - arch/arm/mach-omap2/omap5/fdt.c | 119 ----------------- arch/arm/mach-omap2/omap5/sec-fxns.c | 234 --------------------------------- arch/arm/mach-omap2/sec-common.c | 226 ++++++++++++++++++++++++++++++- board/ti/am43xx/board.c | 16 +++ configs/am43xx_hs_evm_defconfig | 4 + 14 files changed, 496 insertions(+), 381 deletions(-) create mode 100644 arch/arm/mach-omap2/am33xx/fdt.c create mode 100644 arch/arm/mach-omap2/fdt-common.c delete mode 100644 arch/arm/mach-omap2/omap5/sec-fxns.c -- 2.13.0

2 13

[U-Boot] [PATCH] Makefile: add dependencies to regenerate u-boot.cfg when lost
by Philipp Tomsich 25 Jul '17

25 Jul '17

When running a 'make clean' or carelessly removing u-boot.cfg, all future make invocations (until autoconf is regenerated) will print an error for a missing u-boot.cfg due to missing rules and dependencies. This commit adds (i) an explicit rule dependency from all (which will invokes the configuration checker) to cfg, and (b) adds a rule to invoke scripts/Makefile.autoconf to regenerate u-boot.cfg. Signed-off-by: Philipp Tomsich <philipp.tomsich(a)theobroma-systems.com> --- Makefile | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/Makefile b/Makefile index 07dbd9f..9db5ab0 100644 --- a/Makefile +++ b/Makefile @@ -516,6 +516,9 @@ include/config/%.conf: $(KCONFIG_CONFIG) include/config/auto.conf.cmd @# Otherwise, 'make silentoldconfig' would be invoked twice. $(Q)touch include/config/auto.conf +u-boot.cfg spl/u-boot.cfg tpl/u-boot.cfg: include/config.h FORCE + $(Q)$(MAKE) -f $(srctree)/scripts/Makefile.autoconf $(@) + -include include/autoconf.mk -include include/autoconf.mk.dep @@ -851,7 +854,7 @@ quiet_cmd_cfgcheck = CFGCHK $2 cmd_cfgcheck = $(srctree)/scripts/check-config.sh $2 \ $(srctree)/scripts/config_whitelist.txt $(srctree) -all: $(ALL-y) +all: $(ALL-y) cfg ifeq ($(CONFIG_DM_I2C_COMPAT)$(CONFIG_SANDBOX),y) @echo "===================== WARNING ======================" @echo "This board uses CONFIG_DM_I2C_COMPAT. Please remove" -- 2.1.4

4 3

[U-Boot] [PATCH] dtc: mkimage: Add the possibility to specify DTC
by Emmanuel Vadot 25 Jul '17

25 Jul '17

FreeBSD recently switch to it's BSDL dtc. While it support most of the features of the GPL one it still lacks the incbin directive. Add the possibility to specify which dtc we want to use for compiling dts and generating fit image. Signed-off-by: Emmanuel Vadot <manu(a)bidouilliste.com> --- Makefile | 2 +- tools/Makefile | 2 ++ tools/mkimage.h | 1 - 3 files changed, 3 insertions(+), 2 deletions(-) diff --git a/Makefile b/Makefile index 2385285bb8..358f062f83 100644 --- a/Makefile +++ b/Makefile @@ -349,7 +349,7 @@ OBJDUMP = $(CROSS_COMPILE)objdump AWK = awk PERL = perl PYTHON ?= python -DTC = dtc +DTC ?= dtc CHECK = sparse CHECKFLAGS := -D__linux__ -Dlinux -D__STDC__ -Dunix -D__unix__ \ diff --git a/tools/Makefile b/tools/Makefile index cb1683e153..62a7921e43 100644 --- a/tools/Makefile +++ b/tools/Makefile @@ -175,6 +175,8 @@ HOSTCFLAGS_rsa-sign.o += -Wno-deprecated-declarations endif endif +HOSTCFLAGS_fit_image.o += -DMKIMAGE_DTC=\"$(DTC)\" + HOSTLOADLIBES_dumpimage := $(HOSTLOADLIBES_mkimage) HOSTLOADLIBES_fit_info := $(HOSTLOADLIBES_mkimage) HOSTLOADLIBES_fit_check_sign := $(HOSTLOADLIBES_mkimage) diff --git a/tools/mkimage.h b/tools/mkimage.h index 3f369b748e..baee866665 100644 --- a/tools/mkimage.h +++ b/tools/mkimage.h @@ -44,6 +44,5 @@ static inline ulong map_to_sysmem(void *ptr) #define MKIMAGE_MAX_TMPFILE_LEN 256 #define MKIMAGE_DEFAULT_DTC_OPTIONS "-I dts -O dtb -p 500" #define MKIMAGE_MAX_DTC_CMDLINE_LEN 512 -#define MKIMAGE_DTC "dtc" /* assume dtc is in $PATH */ #endif /* _MKIIMAGE_H_ */ -- 2.13.1

3 2

[U-Boot] [RFC 1/1] meson-gx: reserved memory regions
by Heinrich＠lists.denx.de 25 Jul '17

25 Jul '17

From: Heinrich Schuchardt <xypron.glpk(a)gmx.de> The Odroid C2 has two GiB of memory with two reserved regions. reg = <0x0 0x0 0x0 0x1000000>; reg = <0x0 0x10000000 0x0 0x200000>; The description has been created with the following patches: Patch bfcef28ae4cf (arm: add initial support for Amlogic Meson and ODROID-C2) defined the available memory in arch/arm/dts/meson-gxbb-odroidc2.dts as reg = <0x0 0x0 0x0 0x80000000> and the number of RAM banks as #define CONFIG_NR_DRAM_BANKS 1. Patch 4b3ab59d21ef (configs: gxbb: Introduce a common config header file) moved the number of RAM banks to include/configs/meson-gxbb-common.h. Patch a3b02a1d4926 (arm: dts: update Meson GXBB / Odroid-C2 DT with recent) defined two reserved memory regions in arch/arm/dts/meson-gx.dtsi. U-Boot does not support the concept of reserved memory regions. Amongst other mishaps this leads to a wrong memory configuration when calling bootefi which may cause a memory violation. The easiest way to correct this is to define multiple memory banks. In the long run fdt support for reserved-memory might be implemented. Signed-off-by: Heinrich Schuchardt <xypron.glpk(a)gmx.de> --- arch/arm/dts/meson-gxbb-odroidc2.dts | 7 ++++++- include/configs/meson-gxbb-common.h | 2 +- 2 files changed, 7 insertions(+), 2 deletions(-) diff --git a/arch/arm/dts/meson-gxbb-odroidc2.dts b/arch/arm/dts/meson-gxbb-odroidc2.dts index c737183a29..35b8300e23 100644 --- a/arch/arm/dts/meson-gxbb-odroidc2.dts +++ b/arch/arm/dts/meson-gxbb-odroidc2.dts @@ -61,7 +61,12 @@ memory@0 { device_type = "memory"; - reg = <0x0 0x0 0x0 0x80000000>; + reg =<0x0 0x1000000 0x0 0xf000000>; + }; + + memory@1 { + device_type = "memory"; + reg = <0x0 0x10200000 0x0 0x6fe00000>; }; usb_otg_pwr: regulator-usb-pwrs { diff --git a/include/configs/meson-gxbb-common.h b/include/configs/meson-gxbb-common.h index 89e3807a14..ed55f441a4 100644 --- a/include/configs/meson-gxbb-common.h +++ b/include/configs/meson-gxbb-common.h @@ -10,7 +10,7 @@ #define CONFIG_CPU_ARMV8 #define CONFIG_REMAKE_ELF -#define CONFIG_NR_DRAM_BANKS 1 +#define CONFIG_NR_DRAM_BANKS 2 #define CONFIG_ENV_IS_NOWHERE 1 #define CONFIG_ENV_SIZE 0x2000 #define CONFIG_SYS_MAXARGS 32 -- 2.11.0

4 4

[U-Boot] [PATCH 0/3] env: Add support for environments on arbitrary filesystems
by Fiach Antaw 25 Jul '17

25 Jul '17

This patch series consolidates the redundancy implementations used by env_nand, env_mmc and env_ubi, and adds support for a generic env_fs (also using the same redundancy implementation) that supports all filesystems supported by the filesystem code. env_fs should be able to replace env_fat and env_ext4 in all cases, since it implements the same functionality. Unfortunately, I am unable to verify the changes to env_nand, env_mmc and env_ubi on real hardware, though I have verified that they do compile. Fiach Antaw (3): env: Add generic redundant environment implementation env: Switch env_nand, env_mmc and env_ubi to env_import_redund env: Add support for FS environment README | 22 ++++++++ cmd/nvedit.c | 1 + common/Makefile | 1 + common/env_common.c | 51 ++++++++++++++++++ common/env_fs.c | 126 +++++++++++++++++++++++++++++++++++++++++++ common/env_mmc.c | 42 +++------------ common/env_nand.c | 45 +++------------- common/env_ubi.c | 39 +------------- include/environment.h | 21 ++++++++ scripts/config_whitelist.txt | 5 ++ 10 files changed, 243 insertions(+), 110 deletions(-) create mode 100644 common/env_fs.c -- 2.7.4

2 8

[U-Boot] [PATCH] tests: test_dfu.py: Add example udev rule for host_usb_dev_node
by Tom Rini 25 Jul '17

25 Jul '17

If one does not already have a rule to create a custom device node when a given device enumerates it can be useful to have udev create a bus path based node to the entry in /dev/bus/usb that was just enumerated. Given that DFU itself does not require a /dev entry it is a good idea to provide a rule that will generate one. Signed-off-by: Tom Rini <trini(a)konsulko.com> --- test/py/tests/test_dfu.py | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/test/py/tests/test_dfu.py b/test/py/tests/test_dfu.py index 585e6b29d7f8..fba67d585b9f 100644 --- a/test/py/tests/test_dfu.py +++ b/test/py/tests/test_dfu.py @@ -80,6 +80,13 @@ ACTION=="add", SUBSYSTEM=="block", SUBSYSTEMS=="usb", KERNELS=="3-13", MODE:="66 (You may wish to change the group ID instead of setting the permissions wide open. All that matters is that the user ID running the test can access the device.) + +c) An optional udev rule to give you a persistent value to use in +host_usb_dev_node. For example: + +IMPORT{builtin}="path_id" +ENV{ID_PATH}=="?*", ENV{.ID_PORT}=="", SYMLINK+="bus/usb/by-path/$env{ID_PATH}" +ENV{ID_PATH}=="?*", ENV{.ID_PORT}=="?*", SYMLINK+="bus/usb/by-path/$env{ID_PATH}-port$env{.ID_PORT}" """ # The set of file sizes to test. These values trigger various edge-cases such -- 1.9.1

1 1

[U-Boot] [PATCH] tools/fw_env: use fsync to ensure that data is physically stored
by Michael Heimpold 25 Jul '17

25 Jul '17

Closing a file descriptor does not guarantee that the data has been successfully saved to disk, as the kernel might defer the write. Signed-off-by: Michael Heimpold <mhei(a)heimpold.de> --- tools/env/fw_env.c | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/tools/env/fw_env.c b/tools/env/fw_env.c index 428e374..0420495 100644 --- a/tools/env/fw_env.c +++ b/tools/env/fw_env.c @@ -1033,7 +1033,19 @@ static int flash_io (int mode) rc = flash_write (fd_current, fd_target, dev_target); + if (fsync (fd_current)) { + fprintf (stderr, + "fsync failed on %s: %s\n", + DEVNAME (dev_current), strerror (errno)); + } + if (HaveRedundEnv) { + if (fsync (fd_target)) { + fprintf (stderr, + "fsync failed on %s: %s\n", + DEVNAME (dev_current), strerror (errno)); + } + if (close (fd_target)) { fprintf (stderr, "I/O error on %s: %s\n", -- 1.7.10.4

5 6

[U-Boot] Enc: Uboot compatible with board Tegra124-nyan-big (ChromeBook G3 HP 14")
by Alexandre N. Perfeito 25 Jul '17

25 Jul '17

Hi, I resend the e-mail as you asked ! Can help in this tip . Best Regards Perfeito,Alexander ________________________________ De: sjg(a)google.com <sjg(a)google.com> em nome de Simon Glass <sjg(a)chromium.org> Enviado: segunda-feira, 17 de julho de 2017 19:50 Para: Alexandre N. Perfeito Assunto: Re: Uboot compatible with board Tegra124-nyan-big (ChromeBook G3 HP 14") Hi, On 17 July 2017 at 10:33, Alexandre N. Perfeito <perfeitoan(a)hotmail.com<mailto:perfeitoan@hotmail.com>> wrote: Simon, Hi , My Name is Alexander and i need some tip information about U-boot Board Nyan-Big to runinng Linux v4.4.x.x. Can you please resend this to the U-Boot mailing list and cc me? Thanks, Simon I compiled source 4.4.0.70 Ubuntu distribution in chroot environment in my chormebook Tegra Tk1. After compilation the generated files were the following: [aperfeito@alarm boot]$ ls -l total 24992 -rw-r--r-- 1 root root 98874 Jul 13 14:54 config-4.4.70-ARCH -rw-r--r-- 1 root root 8277506 Jul 13 14:54 initrd.img-4.4.70-ARCH -rw-r--r-- 1 root root 2033244 Jul 13 14:54 System.map-4.4.70-ARCH -rw-r--r-- 1 root root 15175680 Jul 13 14:54 vmlinuz-4.4.70-ARCH I also compiled the u-boot-tegra in the same environment in chroot Ubuntu Xenial distribution these were compiled according to the email of Tom Warren send before Make 'nyan-big_defconfig' and everything ok as you see below the generated files: [aperfeito@alarm u-boot-tegra]$ ls *.bin u-boot.bin u-boot-dtb-tegra.bin u-boot-nodtb-tegra.bin u-boot-dtb.bin u-boot-nodtb.bin u-boot-tegra.bin Now is the tip I'm asking you: I have two suggestions on how to put this in the KERNEL partition of my USB. My USB has two partitions To 1st. KERNEL Name with 16 megabytes of space dev / sda6 A 2st. ROOFS Name approximately 29 Gigabytes of space where I worked to compile the UbuntuXenial and Uboot-Tegra srcs kernel as you see in the email. Sugestion : 1 mkimage -D "-I dts -O dtb -p 2048" -f kernel.its vmlinux.uimg dd if=/dev/zero of=bootloader.bin bs=512 count=1 vbutil_kernel \ --pack vmlinux.kpart \ --version 1 \ --vmlinuz vmlinux.uimg \ --arch arm \ --keyblock kernel.keyblock \ --> How I do This if necessary --signprivate kernel_data_key.vbprivk \ --> How I do This if necessary --config cmdline \ --> TXT file whit this config below --bootloader bootloader.bin * kernel.its adjust to files below as given to te src kernel 4.4.0-70 ./arch/arm/boot/dts/tegra124-nyan-blaze.dtb ./arch/arm/boot/dts/tegra124-nyan-big.dtb * ___________________________________________________TXT CONFIG FILE __________________________________________________ * console=tty1 init=/sbin/init root=PARTUUID=%U/PARTNROFF=1 rootwait rw noinitrd lsm.module_locking=0 ## OR ### * initrd=/boot/initrd.img-4.4.0-ARCH console=ttyS0,115200n8 console=tty1 ignore_loglevel earlyprintk cgroup_enable=memory root=/dev/sda7 ### For config line need your sugestion with is the best. Sugestion: 2 I have to copy the kernel, generated initramfs, and dtb to the SDA6 partition and added the following kernel config to /dev/sda7/roofsparttion :/boot/extlinux/extlinux.conf LABEL UbuntuXenial MENU LABEL UbuntuXenial on sda7 with 4.4 kernel LINUX /boot/vmlinuz-4.4.0 FDT /boot/dtb/tegra124-nyan-big.dtb APPEND initrd=/boot/initrd.img-4.4.0-ARCH console=ttyS0,115200n8 console=tty1 ignore_loglevel earlyprintk cgroup_enable=memory root=/dev/sda7 How to make U-boot-Tegra now Work with Kernel 4.4.x.x as v3.10.x.x Kernels booting on USB. Best Regards Perfeito Alexander ________________________________ De: Tom Warren <TWarren(a)nvidia.com<mailto:TWarren@nvidia.com>> Enviado: segunda-feira, 17 de julho de 2017 10:48 Para: Alexandre N. Perfeito Cc: Simon Glass Assunto: RE: Uboot compatible with board Tegra124-nyan-big (ChromeBook G3 HP 14") See ‘nyan-big_defconfig’. Added Simon to CC as he’s used this build quite a lot. HTH, Tom From: Alexandre N. Perfeito [mailto:perfeitoan@hotmail.com<mailto:perfeitoan@hotmail.com>] Sent: Wednesday, July 12, 2017 11:02 AM To: Tom Warren <TWarren(a)nvidia.com<mailto:TWarren@nvidia.com>> Subject: Uboot compatible with board Tegra124-nyan-big (ChromeBook G3 HP 14") Tom, Hi, I woud like to know if exist u-boot/configs/defconfig-for-this-board , to build a Das-U-boot to running Mainline Kernel 4.4 Thanks Best Regards Perfeito,Alexander ________________________________ This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. ________________________________

3 3

[U-Boot] How to update Espressobin (U-Boot) firmware?
by Andre Przywara 24 Jul '17

24 Jul '17

Hi, I wanted to exploit U-Boot's EFI support on the Espressobin board, to use off-the-shelf arm64 distribution installer images. This should work with current U-Boot, which has support for the Espressobin board (and for UEFI). The firmware my board ships with seems to be built from older and non-upstream sources - and, in contrast to the Macchiatobin board - I cannot find either proper sources for all components (mv-ddr, ATF) nor *any* kind of instructions how to (re-)build and update the firmware. So I was wondering if there are any instructions or documentation I missed on how to update at least U-Boot? I see some hints that people are apparently chain-loading mainline U-Boot, is this the only way? I dumped the SPI flash and could identify the ATF FIP image on it, but I am a bit wary of bricking the board by just squashing a freshly built u-boot.bin into that - which I guess wouldn't work that easily anyway. And to allow experimentation: Are the boot selection jumpers actually working? Setting them to SD card (111) doesn't seem to make a difference (it still booted off the SPI flash, apparently). Or does it fall back to SPI flash in case the SD image is not valid (I put the dumped image at sector 1)? I see that selecting "UART" (110) gives me that "E" prompt, apparently waiting for some data to be fed, but again can't tell what to do from here? I take it that mkimage/kwboot won't work as is, as it needs ATF? I found some mentioning of a Windows binary, but hope that's not the only way to use this mode? I'd be very grateful for any insight into this! Cheers, Andre.

5 11

[U-Boot] [PATCH v2 00/12] efi_loader: protocol services
by Heinrich Schuchardt 24 Jul '17

24 Jul '17

Currently only a small fraction of the UEFI specification is implemented in U-Boot. It is sufficient to load grub but it fails on iPXE. With this patch series all EFI protocol services are implemented that are needed to reach the console prompt of the bin-<ARCH>-efi/snponly.efi target of iPXE. Futher patches for event services are needed to use the iPXE console. These will be provided in a separate patch series. The 1st patch refactors efi_open_protocol to enable the implementation of InstallProtocolInterface. This patch eliminates the open protocol functions in efi_disk, efi_gop, and efi_net. The 2nd patch adds missing parameter checks to efi_open_protocol. The 3rd patch implements InstallProtocolInteface. The 4th patch partially implements UninstallProtocolInterface. The 5th patch refactors efi_install_protocol_interface to make it callable internally. The 6th patch refactors efi_uninstall_protocol_interface to make it callable internally. The 7th patch implements InstallMultipleProtocolInterfaces by calling efi_install_protocol_interface. The 8th patch refactors efi_locate_handle to make it callable internally. The 9th patch implements LocateHandleBuffer. The 10th patch increases the number of protocols per handle. The 11th patch reimplements efi_locate_protocol. The 12th patch implements the device path to text protocol. Signed-off-by: Heinrich Schuchardt <xypron.glpk(a)gmx.de> --- v2 Remove implementation of efi_return_handle in 1st patch. Correctly check GUIDs in 3rd patch. Check if protocol != NULL to avoid illegal memory access in 4th patch. Add patches 10-12. --- Heinrich Schuchardt (12): efi_loader: refactor efi_open_protocol efi_loader: efi_open_protocol: parameter checks efi_loader: implement InstallProtocolInterface efi_loader: implement UninstallProtocolInterface efi_loader: refactor efi_install_protocol_interface efi_loader: refactor efi_uninstall_protocol_interface efi_loader: implement InstallMultipleProtocolInterfaces efi_loader: refactor efi_locate_handle efi_loader: implement LocateHandleBuffer efi_loader: provide a sufficient number of protocols efi_loader: reimplement efi_locate_protocol efi_loader: implement EFI_DEVICE_PATH_TO_TEXT_PROTOCOL cmd/bootefi.c | 24 +-- include/efi_api.h | 26 ++- include/efi_loader.h | 33 +--- lib/efi_loader/Makefile | 2 +- lib/efi_loader/efi_boottime.c | 261 +++++++++++++++++++++++++++---- lib/efi_loader/efi_device_path_to_text.c | 68 ++++++++ lib/efi_loader/efi_disk.c | 29 +--- lib/efi_loader/efi_gop.c | 2 +- lib/efi_loader/efi_image_loader.c | 8 - lib/efi_loader/efi_net.c | 30 +--- 10 files changed, 350 insertions(+), 133 deletions(-) create mode 100644 lib/efi_loader/efi_device_path_to_text.c -- 2.11.0

3 20