July 2013 - U-Boot

[U-Boot] [PATCH 0/2] add support for LaCie CloudBox
by Frederic Leroy 05 Jul '13

05 Jul '13

These patches add support for the network storage LaCie CloudBox. The device shares one sata hardrive via a gigabit ethernet port. It is based on a Marvell Kirkwood 6702 soc.

8 27

[U-Boot] Fwd: U-Boot 2013.04: himport_r: can't insert "..."into hash table
by Thomas O'Hara 05 Jul '13

05 Jul '13

Hi, I am using u-Boot 2013.04 to boot an AT91SAM9263-based board. I use a GCC/uClibc cross compiler which I updated to use GCC-4.7.3 and came across a strange problem (see attached log files). uBoot_GCC-4.7.1.log - Bootstrap built with GCC-4.7.3 - uBoot built with cross-compiler based on GCC-4.7.1 - Kernel built with GCC-4.7.3 uBoot_GCC-4.7.3a.log - Bootstrap built with GCC-4.7.3 - uBoot is built with GCC-4.7.3 and throws the hash table error shown - Kernel built with GCC-4.7.3 uBoot_GCC-4.7.3b.log - Bootstrap built with GCC-4.7.3 - uBoot is built with GCC-4.7.3 and halts after the "using default environment" message shown - Kernel built with GCC-4.7.3 The uBoot source code is the same for all builds. The hash-tables problem seems to have occurred in the past with uBoot-2010.12. I tested the builds on 10 different boards and 8 resulted in the uBoot_GCC-4.7.3b log while 2 resulted in the uBoot_GCC-4.7.3a log. All 10 boards worked correctly when uBoot was built with the GCC-4.7.1 based cross compiler. Initially I assumed that the fault was with the compiler but both the bootstrap and the kernel compile and run fine, only uBoot fails. I did some further investigation and discovered that when the GCC/uClibc cross-compiler is built with the following sources, uBoot builds and runs correctly. binutils-2.22 gcc-4.7.1 gmp-5.0.5 linux-3.6.11 mpc-1.0 mpfr-3.1.1 uClibc-0.9.33.2 When the GCC/uClibc cross-compiler is built with the following sources, uBoot builds without error but does not run. binutils-2.23 gcc-4.7.2 gmp-5.0.5 linux-3.6.11 mpc-1.0.1 mpfr-3.1.1 uClibc-0.9.33.2 I'm continuing to narrow this down but I was wondering if anyone has already come across this and could help me resolve it more quickly. Cheers, Tom -- Life, liberty and...

1 0

[U-Boot] [PATCH 0/2] Update Falcon Mode docs
by Tom Rini 05 Jul '13

05 Jul '13

Hey all, The following 2 patches update docs for falcon mode, and am335x_evm. The first adds a quick general note about how failure is decided in falcon mode and we drop back to U-Boot. The second adds a README for am335x_evm which provides examples for eMMC or raw SD cards, FAT SD cards and NAND for setting up falcon mode. This also updates the DFU info to be able to write these areas and corrects a small bug in the NAND configuration for falcon mode. I did this in part because while I found doc/README.falcon helpful we still want to provide board-specific examples when possible I believe. And, as has been pointed out to me on IRC, this isn't a huge boot time win (and may be a loss) until we have dcache configured correctly. This is on my TODO list, but a separate patch. -- Tom

3 7

[U-Boot] Ethernet support on mx6slevk board
by Shawn Guo 05 Jul '13

05 Jul '13

Hi, I'm running U-Boot 2013.07-rc2 and seeing Ethernet is failed to initialize. Is it a known issue or something not supported yet? It's unlikely my setup problem, since I have a vendor U-Boot running the board just fine. Shawn

3 5

[U-Boot] [PATCH] power:bat:trats: Break battery charging with ctrl+C
by Lukasz Majewski 05 Jul '13

05 Jul '13

Add support for disabling battery charging with ctrl+C keyboard combination pressed. Moreover the battery update is done more frequently. Signed-off-by: Lukasz Majewski <l.majewski(a)samsung.com> Cc: Tom Rini <trini(a)ti.com> --- drivers/power/battery/bat_trats.c | 13 +++++++++---- drivers/power/power_core.c | 3 ++- 2 files changed, 11 insertions(+), 5 deletions(-) diff --git a/drivers/power/battery/bat_trats.c b/drivers/power/battery/bat_trats.c index ca0d214..97a9661 100644 --- a/drivers/power/battery/bat_trats.c +++ b/drivers/power/battery/bat_trats.c @@ -41,18 +41,23 @@ static int power_battery_charge(struct pmic *bat) for (k = 0; bat->chrg->chrg_bat_present(p_bat->chrg) && bat->chrg->chrg_type(p_bat->muic) && battery->state_of_chrg < 100; k++) { - udelay(10000000); - puts("."); + udelay(2000000); + if (!(k % 5)) + puts("."); bat->fg->fg_battery_update(p_bat->fg, bat); - if (k == 100) { + if (k == 200) { debug(" %d [V]", battery->voltage_uV); puts("\n"); k = 0; } + if (ctrlc()) { + printf("\nCharging disabled on request.\n"); + goto exit; + } } - + exit: bat->chrg->chrg_state(p_bat->chrg, CHARGER_DISABLE, 0); return 0; diff --git a/drivers/power/power_core.c b/drivers/power/power_core.c index 90df2c5..f16b9dc 100644 --- a/drivers/power/power_core.c +++ b/drivers/power/power_core.c @@ -205,7 +205,8 @@ int do_pmic(cmd_tbl_t *cmdtp, int flag, int argc, char * const argv[]) if (strcmp(argv[3], "charge") == 0) { if (p->pbat) { - printf("PRINT BAT charge %s\n", p->name); + printf("BAT: %s charging (ctrl+c to break)\n", + p->name); if (p->low_power_mode) p->low_power_mode(); if (p->pbat->battery_charge) -- 1.7.10.4

2 1

[U-Boot] [PATCH] arm:trats: Increase malloc pool size (for DFU ext4 transfers)
by Lukasz Majewski 05 Jul '13

05 Jul '13

Commit: dfu: make data buffer size configurable SHA1: 89a72b2e0e141042c9109185e02d39b2107ffc62 replaced statically allocated buffers with one allocated with memalign. Malloc pool size of 1MiB was too small, since we needed bigger buffer to transfer for example uImage. Signed-off-by: Lukasz Majewski <l.majewski(a)samsung.com> Cc: Minkyu Kang <mk7.kang(a)samsung.com> --- include/configs/trats.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/configs/trats.h b/include/configs/trats.h index 53fcf79..90562c4 100644 --- a/include/configs/trats.h +++ b/include/configs/trats.h @@ -66,7 +66,7 @@ #define CONFIG_MACH_TYPE MACH_TYPE_TRATS /* Size of malloc() pool */ -#define CONFIG_SYS_MALLOC_LEN (CONFIG_ENV_SIZE + (1 << 20)) +#define CONFIG_SYS_MALLOC_LEN (CONFIG_ENV_SIZE + (16 << 20)) /* select serial console configuration */ #define CONFIG_SERIAL2 /* use SERIAL 2 */ -- 1.7.10.4

2 1

[U-Boot] [U-boot] DFU tools copyright
by TigerLiu＠viatech.com.cn 05 Jul '13

05 Jul '13

Hi, experts: I found DFU tool code had been put in drivers/dfu directory. Previously, it was owned by Samsung Electronics. Because it has been merged into uboot library. So, it could be used or released by every ARM SOC vendor? Best wishes,

3 8

[U-Boot] [PATCH 0/4 V4]EXYNOS: Convert Assembly code to c and make it common
by Rajeshwari Shinde 05 Jul '13

05 Jul '13

Convert the assembly code in board/samsung to c and move the same to arch/arm. lds file made common across SMDKV310, Origen and SMDK5250. Add the power reset and exit wakeup api for exynos. Initialise GPIO for uart in Origen and SMDKV310 using pinmux. Changes in V2: - Rebased on latest u-boot-samsung tree. - Incorporated review comments from Simon glass and Minkyu Kang. Changes in V3: - Optimised the mem_ctrl_init function for exynos4. - Removed magic numbers. Changes in V4: - Used samsung_get_base api instead of hardcoding base address. Rajeshwari Shinde (4): EXYNOS: Add API for power reset and exit wakeup EXYNOS: LDS file move to common EXYNOS4210: Configure GPIO for uart EXYNOS: Move files from board/samsung to arch/arm arch/arm/cpu/armv7/exynos/Makefile | 17 +- .../arm/cpu/armv7/exynos}/clock_init.h | 0 arch/arm/cpu/armv7/exynos/clock_init_exynos4.c | 95 +++++ .../arm/cpu/armv7/exynos/clock_init_exynos5.c | 56 ++-- arch/arm/cpu/armv7/exynos/common_setup.h | 45 ++ .../arm/cpu/armv7/exynos}/dmc_common.c | 7 +- .../arm/cpu/armv7/exynos}/dmc_init_ddr3.c | 27 +- arch/arm/cpu/armv7/exynos/dmc_init_exynos4.c | 213 ++++++++++ .../arm/cpu/armv7/exynos/exynos4_setup.h | 397 +++++++++---------- .../arm/cpu/armv7/exynos/exynos5_setup.h | 28 +- arch/arm/cpu/armv7/exynos/lowlevel_init.c | 73 ++++ arch/arm/cpu/armv7/exynos/pinmux.c | 40 ++ arch/arm/cpu/armv7/exynos/power.c | 50 +++ .../arm/cpu/armv7/exynos}/spl_boot.c | 74 +++- arch/arm/include/asm/arch-exynos/cpu.h | 13 +- arch/arm/include/asm/arch-exynos/power.h | 12 + .../exynos-uboot-spl.lds} | 0 board/samsung/origen/Makefile | 11 +- board/samsung/origen/lowlevel_init.S | 357 ----------------- board/samsung/origen/mem_setup.S | 421 -------------------- board/samsung/origen/mmc_boot.c | 58 --- board/samsung/origen/origen.c | 46 +++ board/samsung/smdk5250/Makefile | 14 +- board/samsung/smdkv310/Makefile | 10 +- board/samsung/smdkv310/lowlevel_init.S | 414 ------------------- board/samsung/smdkv310/mem_setup.S | 365 ----------------- board/samsung/smdkv310/mmc_boot.c | 60 --- board/samsung/smdkv310/smdkv310.c | 46 +++ include/configs/exynos5250-dt.h | 10 +- include/configs/origen.h | 9 +- include/configs/smdkv310.h | 8 +- 31 files changed, 985 insertions(+), 1991 deletions(-) rename {board/samsung/smdk5250 => arch/arm/cpu/armv7/exynos}/clock_init.h (100%) create mode 100644 arch/arm/cpu/armv7/exynos/clock_init_exynos4.c rename board/samsung/smdk5250/clock_init.c => arch/arm/cpu/armv7/exynos/clock_init_exynos5.c (94%) create mode 100644 arch/arm/cpu/armv7/exynos/common_setup.h rename {board/samsung/smdk5250 => arch/arm/cpu/armv7/exynos}/dmc_common.c (97%) rename {board/samsung/smdk5250 => arch/arm/cpu/armv7/exynos}/dmc_init_ddr3.c (92%) create mode 100644 arch/arm/cpu/armv7/exynos/dmc_init_exynos4.c rename board/samsung/origen/origen_setup.h => arch/arm/cpu/armv7/exynos/exynos4_setup.h (65%) rename board/samsung/smdk5250/setup.h => arch/arm/cpu/armv7/exynos/exynos5_setup.h (96%) create mode 100644 arch/arm/cpu/armv7/exynos/lowlevel_init.c rename {board/samsung/smdk5250 => arch/arm/cpu/armv7/exynos}/spl_boot.c (74%) rename board/samsung/{smdk5250/smdk5250-uboot-spl.lds => common/exynos-uboot-spl.lds} (100%) delete mode 100644 board/samsung/origen/lowlevel_init.S delete mode 100644 board/samsung/origen/mem_setup.S delete mode 100644 board/samsung/origen/mmc_boot.c delete mode 100644 board/samsung/smdkv310/lowlevel_init.S delete mode 100644 board/samsung/smdkv310/mem_setup.S delete mode 100644 board/samsung/smdkv310/mmc_boot.c -- 1.7.4.4

2 5

[U-Boot] : MACB TX timeout
by Jagan Teki 05 Jul '13

05 Jul '13

Hi, Did anyone find this TX timeout issue on macb(gmac)? I observed this issue when i enable d-cache. Log: ---- zynq-uboot> ping 10.10.70.101 gmac0: PHY present at 7 gmac0: link up, 1000Mbps full-duplex (lpa: 0x3800) Using gmac0 device gmac0: TX timeout gmac0: TX timeout ping failed; host 10.10.70.101 is not alive Any help.! -- Thanks, Jagan.

2 3

[U-Boot] [PATCH 1/3] bootm: Handle errors consistently
by Simon Glass 04 Jul '13

04 Jul '13

A recent bootm fix left the error path incomplete. Reinstate this so that failures in bootm stages are handled properly. Signed-off-by: Simon Glass <sjg(a)chromium.org> --- common/cmd_bootm.c | 4 ---- 1 file changed, 4 deletions(-) diff --git a/common/cmd_bootm.c b/common/cmd_bootm.c index 02a5013..f4df0a0 100644 --- a/common/cmd_bootm.c +++ b/common/cmd_bootm.c @@ -684,12 +684,8 @@ static int do_bootm_states(cmd_tbl_t *cmdtp, int flag, int argc, if (!ret && (states & BOOTM_STATE_OS_GO)) { ret = boot_selected_os(argc, argv, BOOTM_STATE_OS_GO, images, boot_fn); - if (ret) - goto err; } - return ret; - /* Deal with any fallout */ err: if (iflag) -- 1.8.3

2 6