April 2014 - U-Boot

[U-Boot] Latest u-boot release on BeagleBone Black for FreeBSD
by Xuebing Wang 07 May '14

07 May '14

Hi u-boot community, I am trying to port u-boot (release u-boot-2014.04-rc3.tar.bz2) to FreeBSD on BeagleBone Black. In FreeBSD, there is a u-boot loader (named ubldr), which can call u-boot API to get fdt (Flat Device Tree) data. I have to comment out below 3 lines, in order to get correct fdt data in FreeBSD ubldr from u-boot. Would you please advice what is the best way to fix this? In file common/env_common.c: const uchar *env_get_addr(int index) { // if (gd->env_valid) // return (uchar *)(gd->env_addr + index); // else return &default_environment[index]; } -- Thanks, Xuebing Wang

4 5

[U-Boot] [PATCHv2] ARM: exynos: remove the unused code
by Jaehoon Chung 07 May '14

07 May '14

"mmc boot" command didn't use anywhere. It can be replace "mmc dev" command. Signed-off-by: Jaehoon Chung <jh80.chung(a)samsung.com> --- Changelog v2: - Fixed the different address for loading and uploading. include/configs/s5pc210_universal.h | 7 ++----- include/configs/trats.h | 7 ++----- include/configs/trats2.h | 11 +++-------- 3 files changed, 7 insertions(+), 18 deletions(-) diff --git a/include/configs/s5pc210_universal.h b/include/configs/s5pc210_universal.h index 2da8871..db5561a 100644 --- a/include/configs/s5pc210_universal.h +++ b/include/configs/s5pc210_universal.h @@ -111,12 +111,9 @@ "onenand write 0x41008000 0xc00000 0x500000\0" \ "bootk=" \ "run loaduimage; bootm 0x40007FC0\0" \ - "updatemmc=" \ - "mmc boot 0 1 1 1; mmc write 0 0x42008000 0 0x200;" \ - "mmc boot 0 1 1 0\0" \ "updatebackup=" \ - "mmc boot 0 1 1 2; mmc write 0 0x42100000 0 0x200;" \ - "mmc boot 0 1 1 0\0" \ + "mmc dev 0 2; mmc write 0 0x42100000 0 0x200;" \ + "mmc dev 0 0\0" \ "updatebootb=" \ "mmc read 0 0x42100000 0x80 0x200; run updatebackup\0" \ "lpj=lpj=3981312\0" \ diff --git a/include/configs/trats.h b/include/configs/trats.h index 5d8bd60..694c29c 100644 --- a/include/configs/trats.h +++ b/include/configs/trats.h @@ -121,12 +121,9 @@ "bootm 0x40007FC0 - ${fdtaddr};" \ "fi;" \ "bootm 0x40007FC0;\0" \ - "updatemmc=" \ - "mmc boot 0 1 1 1; mmc write 0 0x42008000 0 0x200;" \ - "mmc boot 0 1 1 0\0" \ "updatebackup=" \ - "mmc boot 0 1 1 2; mmc write 0 0x42100000 0 0x200;" \ - "mmc boot 0 1 1 0\0" \ + "mmc dev 0 2; mmc write 0 0x42100000 0 0x200;" \ + "mmc dev 0 0\0" \ "updatebootb=" \ "mmc read 0 0x42100000 0x80 0x200; run updatebackup\0" \ "lpj=lpj=3981312\0" \ diff --git a/include/configs/trats2.h b/include/configs/trats2.h index 53d449c..165663e 100644 --- a/include/configs/trats2.h +++ b/include/configs/trats2.h @@ -111,16 +111,11 @@ "bootm 0x40007FC0 - ${fdtaddr};" \ "fi;" \ "bootm 0x40007FC0;\0" \ - "updatemmc=" \ - "mmc boot 0 1 1 1; mmc write 0x42008000 0 0x200;" \ - "mmc boot 0 1 1 0\0" \ "updatebackup=" \ - "mmc boot 0 1 1 2; mmc write 0x42100000 0 0x200;" \ - " mmc boot 0 1 1 0\0" \ + "mmc dev 0 2; mmc write 0x51000000 0 0x800;" \ + " mmc dev 0 0\0" \ "updatebootb=" \ - "mmc read 0x51000000 0x80 0x200; run updatebackup\0" \ - "updateuboot=" \ - "mmc write 0x50000000 0x80 0x400\0" \ + "mmc read 0x51000000 0x80 0x800; run updatebackup\0" \ "mmcboot=" \ "setenv bootargs root=/dev/mmcblk${mmcdev}p${mmcrootpart} " \ "${lpj} rootwait ${console} ${meminfo} ${opts} ${lcdinfo}; " \ -- 1.7.9.5

2 1

[U-Boot] [PATCH] trats2: config: fix: Set default console to ttySAC2
by Lukasz Majewski 07 May '14

07 May '14

During providing device tree support for Exynos4 based boards, a tiny mistake has creeped in the 1ecab0f commit. This commit restores proper setting of default console for the trats2 board. Signed-off-by: Lukasz Majewski <l.majewski(a)samsung.com> Cc: Minkyu Kang <mk7.kang(a)samsung.com> --- include/configs/trats2.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/configs/trats2.h b/include/configs/trats2.h index aee9ee2..0760309 100644 --- a/include/configs/trats2.h +++ b/include/configs/trats2.h @@ -53,7 +53,7 @@ #define CONFIG_BOOTARGS "Please use defined boot" #define CONFIG_BOOTCOMMAND "run mmcboot" -#define CONFIG_DEFAULT_CONSOLE "console=ttySAC1,115200n8\0" +#define CONFIG_DEFAULT_CONSOLE "console=ttySAC2,115200n8\0" #define CONFIG_SYS_INIT_SP_ADDR (CONFIG_SYS_LOAD_ADDR \ - GENERATED_GBL_DATA_SIZE) -- 1.7.10.4

2 5

[U-Boot] [PATCH v3 0/5] Android Fastboot support
by Rob Herring 07 May '14

07 May '14

From: Rob Herring <robh(a)kernel.org> I'm reviving the Android Fastboot support after 2+ years since the last posting[1]. The previous postings had some questions about licensing and source of some code. I believe I've traced the history sufficiently that the copyrights and source information are complete and correct. The Android code used or referenced is BSD 2-clause license. This was originally raised by Wolfgang that it was not compatible with GPLv2+. I believe that has since been demonstrated and agreed that the BSD 2-clause license is compatible with u-boot. As far as the history of the code, I have traced that back. The u-boot code started in 2008/2009 by Tom Rix @ Windriver. This initial support was then adopted and extended by TI (eMMC support primarily, not included here) in their OMAP u-boot tree[2]. In 2011, the TI code was used as a basis for upstream patches by Sebastian Siewior @ Linutronix. The code has been rearranged quite a bit since the original, but the content is pretty much the same. Some of the re-arranging left stale or missing copyrights in the v2 version which I have corrected. I've reworked the previous version to make enabling board support more simple including re-using the existing settings for image loading address. I've tested this series on a BeagleBoard. Rob [1] http://lists.denx.de/pipermail/u-boot/2011-November/110557.html [2] http://git.omapzoom.org/?p=repo/u-boot.git;a=commit;h=601ff71c8d46b5e90e136… Rob Herring (3): common: introduce maximum load size usb: handle NULL table in usb_gadget_get_string arm: beagle: enable Android fastboot support Sebastian Siewior (2): image: add support for Android's boot image format usb/gadget: add the fastboot gadget README | 3 + common/Makefile | 3 + common/board_r.c | 1 + common/cmd_bootm.c | 23 +- common/cmd_fastboot.c | 36 +++ common/image-android.c | 84 ++++++ common/image.c | 37 ++- doc/README.android-fastboot | 86 ++++++ doc/README.android-fastboot-protocol | 170 +++++++++++ drivers/usb/gadget/Makefile | 1 + drivers/usb/gadget/f_fastboot.c | 535 +++++++++++++++++++++++++++++++++++ drivers/usb/gadget/g_fastboot.h | 15 + drivers/usb/gadget/u_fastboot.c | 260 +++++++++++++++++ drivers/usb/gadget/usbstring.c | 3 + include/android_image.h | 69 +++++ include/common.h | 1 + include/config_fallbacks.h | 4 + include/configs/omap3_beagle.h | 5 + include/image.h | 13 + include/usb/fastboot.h | 36 +++ 20 files changed, 1379 insertions(+), 6 deletions(-) create mode 100644 common/cmd_fastboot.c create mode 100644 common/image-android.c create mode 100644 doc/README.android-fastboot create mode 100644 doc/README.android-fastboot-protocol create mode 100644 drivers/usb/gadget/f_fastboot.c create mode 100644 drivers/usb/gadget/g_fastboot.h create mode 100644 drivers/usb/gadget/u_fastboot.c create mode 100644 include/android_image.h create mode 100644 include/usb/fastboot.h -- 1.9.1

8 58

[U-Boot] [Question] Linux Boot with u-boot 2014.04 on Zynq board
by Masahiro Yamada 07 May '14

07 May '14

Hi Michal, I am a user of Zynq ZC-706 board. On u-boot 2014.01 release, I put Kernel Image, Device Tree, Ramdisk into "fit.itb" and I could successfully boot Linux Kernel. But I don't know how to boot Kernel on u-boot 2014.04 release. Please help! The default boot sequence of Zynq on the u-boot-2014.04 release is Falcon boot, right? I am trying to boot Linux with - U-boot 2014.04 - Linux Kernel 3.14 - SD boot mode - ZC706 board What I did is roughly like this: ## U-Boot ## [1] Build u-boot [2] Convert spl/u-boot-spl.bin into boot.bin with BootGen tool [3] Copy "boot.bin" to FAT-fomatted SD card. ##Kernel ## [1] Build kernel with multi_v7_defconfig setting [2] Copy uImage to the SD card [3] Rename zynq-zc706.dtb into system.dtb and copy to SD card Kernel boot failed to mount the root device. My question is, how to pass an init ramdisk? In which file-name should I copy init ramdisk into SD card? How should I load the init ramdisk from the SD card? Best Regards Masahiro Yamada

3 7

[U-Boot] [RFC] Kconfig: MAINTAINERS file or not?
by Masahiro Yamada 06 May '14

06 May '14

Hi. Before I send Kconfig series v2, please let me cofirm our approach of maintainers info. When I posted the RFC series in March, I put maintainers info and board status into defconfig of each board. But this idea was rejected. Instead, MAINTAINERS file as in Linux Kernel was proposed. (And the patch series by Daniel is already on Patchwork.) http://patchwork.ozlabs.org/patch/340546/ But Wolfgang (and Albert) disagreed with it. In Kconfig v1 series, I put maintainers info and board status in board/*/*/Kconfig as non-user-editable settings: http://patchwork.ozlabs.org/patch/342089/ But I am not sure if this is a good idea. (At least, it is dirty.) In v2, I will drop maintainers info and board status from Kconfig and leave them to Daniel's patch. Any furthur comments about this? Best Regards Masahiro Yamada

5 7

[U-Boot] [PATCH] i2c: zynq: Fixed compilation errors when using DEBUG
by Michal Simek 06 May '14

06 May '14

From: "Jesper B. Christensen" <jesper.christensen(a)cobham.com> Signed-off-by: Jesper B. Christensen <jesper.christensen(a)cobham.com> Signed-off-by: Michal Simek <michal.simek(a)xilinx.com> --- drivers/i2c/zynq_i2c.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/i2c/zynq_i2c.c b/drivers/i2c/zynq_i2c.c index f1f6513..b3264af 100644 --- a/drivers/i2c/zynq_i2c.c +++ b/drivers/i2c/zynq_i2c.c @@ -142,7 +142,7 @@ static u32 zynq_i2c_wait(struct zynq_i2c_registers *zynq_i2c, u32 mask) break; } #ifdef DEBUG - zynq_i2c_debug_status(zynq_i2c)); + zynq_i2c_debug_status(zynq_i2c); #endif /* Clear interrupt status flags */ writel(int_status & mask, &zynq_i2c->interrupt_status); @@ -235,7 +235,7 @@ static int zynq_i2c_read(struct i2c_adapter *adap, u8 dev, uint addr, clrbits_le32(&zynq_i2c->control, ZYNQ_I2C_CONTROL_HOLD); #ifdef DEBUG - zynq_i2c_debug_status(); + zynq_i2c_debug_status(zynq_i2c); #endif return 0; } -- 1.8.2.3

3 2

[U-Boot] [PATCH v2] Exynos5: config: Enable FIT
by Akshay Saraswat 06 May '14

06 May '14

Adding two configs: * CONFIG_FIT - Enable FIT image support. * CONFIG_FIT_BEST_MATCH - Enable fetching correct DTB from FIT image by comparing compatibles. Change in V2: - Added "Acked-by". Signed-off-by: Akshay Saraswat <akshay.s(a)samsung.com> Acked-by: Simon Glass <sjg(a)chromium.org> --- include/configs/exynos5-dt.h | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/include/configs/exynos5-dt.h b/include/configs/exynos5-dt.h index 414db42..dee53e9 100644 --- a/include/configs/exynos5-dt.h +++ b/include/configs/exynos5-dt.h @@ -288,4 +288,8 @@ #define CONFIG_CMD_BOOTZ +/* Enable FIT support and comparison */ +#define CONFIG_FIT +#define CONFIG_FIT_BEST_MATCH + #endif /* __CONFIG_H */ -- 1.8.3.2

2 1

[U-Boot] [PATCH] disk: part_efi: add support for the Alternate GPT
by Steve Rae 05 May '14

05 May '14

Check the Alternate GPT table if the Primary GPT table is invalid. Signed-off-by: Steve Rae <srae(a)broadcom.com> --- disk/part_efi.c | 20 ++++++++++++++++++-- 1 file changed, 18 insertions(+), 2 deletions(-) diff --git a/disk/part_efi.c b/disk/part_efi.c index 216a292..ad899fa 100644 --- a/disk/part_efi.c +++ b/disk/part_efi.c @@ -93,7 +93,15 @@ void print_part_efi(block_dev_desc_t * dev_desc) if (is_gpt_valid(dev_desc, GPT_PRIMARY_PARTITION_TABLE_LBA, gpt_head, &gpt_pte) != 1) { printf("%s: *** ERROR: Invalid GPT ***\n", __func__); - return; + if (is_gpt_valid(dev_desc, (dev_desc->lba - 1), + gpt_head, &gpt_pte) != 1) { + printf("%s: *** ERROR: Invalid Alternate GPT ***\n", + __func__); + return; + } else { + printf("%s: *** Using Alternate GPT ***\n", + __func__); + } } debug("%s: gpt-entry at %p\n", __func__, gpt_pte); @@ -142,7 +150,15 @@ int get_partition_info_efi(block_dev_desc_t * dev_desc, int part, if (is_gpt_valid(dev_desc, GPT_PRIMARY_PARTITION_TABLE_LBA, gpt_head, &gpt_pte) != 1) { printf("%s: *** ERROR: Invalid GPT ***\n", __func__); - return -1; + if (is_gpt_valid(dev_desc, (dev_desc->lba - 1), + gpt_head, &gpt_pte) != 1) { + printf("%s: *** ERROR: Invalid Alternate GPT ***\n", + __func__); + return -1; + } else { + printf("%s: *** Using Alternate GPT ***\n", + __func__); + } } if (part > le32_to_cpu(gpt_head->num_partition_entries) || -- 1.8.5

3 7

[U-Boot] MMC: proposal to support multiple physical partitions
by Steve Rae 05 May '14

05 May '14

In addition to using the MMC "user area" (the device's physical partition), I am also using the "first MMC boot partition" and the "second MMC boot partition"... As a result, I am currently using the following code snippet in a number of places: err = -1; if (mmc->part_num != part_num) { if (mmc_switch_part(dev_num, part_num)) { printf("%s: MMC partition switch to %d failed\n", __func__, part_num); err = 0; } } if (err != 0) { err = mmc->block_dev.block_read(dev_num, start, blkcnt, buffer); } if (mmc->part_num != part_num) { if (mmc_switch_part(dev_num, mmc->part_num)) { printf("%s: MMC partition switching back from %d failed\n", __func__, part_num); } } I have two different proposals: 1) overload the "int dev_num" argument with encoded "dev_num" and "part_num" fields - the dev_num in the [15:0] bits, - the part_num in the [30:16] bits, - a flag to indicate this encoding in [31] bit. - and modify mmc_bread() to handle this encoded argument, and implement the above code... 2) create a wrapper function to perform the above code, with an added argument "int part_num", possibly named: - mmc_block_dev_block_read() -- so that it is similar to the original calling convention [mmc->block_dev.block_read], or - mmc_pbread() [PartitionBlockRead] -- so that it is similar to the mmc_bread() [which is the implementation of the callback function] Also, would implement this solution for mmc->block_dev.block_write() and mmc->block_dev.block_erase() too. Either proposals would affect: include/mmc.h drivers/mmc/mmc.c drivers/mmc/mmc_write.c Would either of these proposals be acceptable to upstream? Thanks in advance, Steve

2 3