January 2013 - U-Boot

[U-Boot] [PATCH v2] mx53loco: Add support for SEIKO 4.3'' WVGA panel
by Fabio Estevam 02 Jan '13

02 Jan '13

From: Fabio Estevam <fabio.estevam(a)freescale.com> Add support for the Seiko 4.3'' WVGA panel on mx53loco. By default, the CLAA WVGA panel is selected. In order to support the Seiko panel, the enviroment variable 'panel' must be set to 'seiko'. Signed-off-by: Fabio Estevam <fabio.estevam(a)freescale.com> --- Changes since v1: - Allow a single binary to support both CLAA and Seiko panels board/freescale/mx53loco/mx53loco.c | 2 -- board/freescale/mx53loco/mx53loco_video.c | 53 ++++++++++++++++++++++++++--- 2 files changed, 49 insertions(+), 6 deletions(-) diff --git a/board/freescale/mx53loco/mx53loco.c b/board/freescale/mx53loco/mx53loco.c index 63a4f8b..9635e62 100644 --- a/board/freescale/mx53loco/mx53loco.c +++ b/board/freescale/mx53loco/mx53loco.c @@ -463,8 +463,6 @@ int board_init(void) mxc_set_sata_internal_clock(); setup_iomux_i2c(); - lcd_enable(); - return 0; } diff --git a/board/freescale/mx53loco/mx53loco_video.c b/board/freescale/mx53loco/mx53loco_video.c index 69991e8..f02c0e5 100644 --- a/board/freescale/mx53loco/mx53loco_video.c +++ b/board/freescale/mx53loco/mx53loco_video.c @@ -46,6 +46,21 @@ static struct fb_videomode const claa_wvga = { .vmode = FB_VMODE_NONINTERLACED }; +static struct fb_videomode const seiko_wvga = { + .name = "Seiko-43WVF1G", + .refresh = 60, + .xres = 800, + .yres = 480, + .pixclock = 29851, /* picosecond (33.5 MHz) */ + .left_margin = 89, + .right_margin = 164, + .upper_margin = 23, + .lower_margin = 10, + .hsync_len = 10, + .vsync_len = 10, + .sync = 0, +}; + void setup_iomux_lcd(void) { mxc_request_iomux(MX53_PIN_DI0_DISP_CLK, IOMUX_CONFIG_ALT0); @@ -86,9 +101,39 @@ void setup_iomux_lcd(void) gpio_direction_output(IOMUX_TO_GPIO(MX53_PIN_GPIO_1), 1); } -void lcd_enable(void) +int board_video_skip(void) { - int ret = ipuv3_fb_init(&claa_wvga, 0, IPU_PIX_FMT_RGB565); - if (ret) - printf("LCD cannot be configured: %d\n", ret); + int ret; + char const *e = getenv("panel"); + + if (!e) { + /* 'panel' env variable not found. Default to 'claa' lcd */ + ret = ipuv3_fb_init(&claa_wvga, 0, IPU_PIX_FMT_RGB565); + if (ret) + printf("LCD cannot be configured: %d\n", ret); + return ret; + + } else { /* 'panel' env variable is found */ + if (strcmp(e, "claa") == 0) { + ret = ipuv3_fb_init(&claa_wvga, 0, IPU_PIX_FMT_RGB565); + if (ret) + printf("LCD cannot be configured: %d\n", ret); + return ret; + } + + if (strcmp(e, "seiko") == 0) { + ret = ipuv3_fb_init(&seiko_wvga, 0, IPU_PIX_FMT_RGB24); + if (ret) + printf("LCD cannot be configured: %d\n", ret); + return ret; + } + /* + * If 'panel' variable has a value different then + * 'claa' or 'seiko' then setup as 'claa' lcd by default + */ + ret = ipuv3_fb_init(&claa_wvga, 0, IPU_PIX_FMT_RGB565); + if (ret) + printf("LCD cannot be configured: %d\n", ret); + return ret; + } } -- 1.7.9.5

1 0

[U-Boot] [PATCH 0/3] Add I2C driver for Tegra30 Cardhu
by Tom Warren 02 Jan '13

02 Jan '13

Add/update clock tables and enable I2C driver support for the Tegra30 Cardhu board. This uses the standard Tegra I2C driver. 5 controllers are supported, although all may not have devices behind them on every board. Tom Warren (3): Tegra30: clocks: Fix clock tables for I2C and other periphs Tegra30: fdt: Update DT files with I2C info for T30/Cardhu Tegra30: I2C: Enable I2C driver on Cardhu arch/arm/cpu/tegra30-common/clock.c | 78 ++++++++++++---------- arch/arm/dts/tegra30.dtsi | 61 +++++++++++++++++ arch/arm/include/asm/arch-tegra30/clock-tables.h | 4 + board/nvidia/dts/tegra30-cardhu.dts | 41 +++++++++++ include/configs/cardhu.h | 9 +++ include/configs/tegra30-common.h | 3 + 6 files changed, 162 insertions(+), 34 deletions(-)

2 9

[U-Boot] Bricked when trying to attach UBI
by Luca Ceresoli 02 Jan '13

02 Jan '13

Hi all, I am facing a problem with some boards that do not boot after some weeks or months of normal usage, being unable to attach UBI. They do not boot anymore event after a power cycle, in other words they are totally bricked. I don't know exactly what problem UBI has, but it is recoverable by Linux, but apparently not by U-Boot. The boards are DIG297 (dig297 board in mainline U-Boot), based on OMAP3530 and equipped with a NAND flash (Micron MT29F2G16ABBEAHC) as their unique permanent storage. U-Boot v2012.04.01 starts correctly. The bootcmd tries to load the kernel from UBI, starting with the following commands: echo Booting from nand ... setenv bootargs console=ttyO2,115200n8 mtdparts=omap2-nand.0:768k(uboot),128k(reserved),128k(uboot-env),-(ubi) ubi.mtd=3 root=ubi0:rootfs ro rootfstype=ubifs ip=.... ubi part nand0,3 ... On "bricked" devices the output of the "ubi part nand0,3" command is: Creating 1 MTD partitions on "nand0": 0x000000100000-0x000010000000 : "mtd=3" UBI: attaching mtd1 to ubi0 UBI: physical eraseblock size: 131072 bytes (128 KiB) UBI: logical eraseblock size: 129024 bytes UBI: smallest flash I/O unit: 2048 UBI: sub-page size: 512 UBI: VID header offset: 512 (aligned 512) UBI: data offset: 2048 UBI error: ubi_wl_init_scan: no enough physical eraseblocks (0, need 1) Now the device is totally blocked, and power cycling does not change the result. The interesting thing is that if I load Linux (2.6.37 + OMAP patches + board support patches) via TFTP and boot it with bootm, it correctly attaches UBI (fixing any problem it may have) and boots correctly. After that the board is unbricked: U-Boot can boot again normally from NAND. Without the ambition of understanding all UBI internals, I tried to visually inspect the UBI code around the line where the error is produced and compare it to the corresponding Linux sources. They looked extremely similar, so I haven't and obvious hint of why U-Boot and Linux produce different results. I also tried with an updated U-Boot master, but the error is still there. Obviously I have changed nothing in the UBI and MTD code, both in U-Boot and in Linux. Can you suggest a proper way to track the root of the problem, or to bypass it? Big thanks in advance, Luca

5 11

[U-Boot] [PATCH 0/4] SMDK5250: Convert lowlevel_init.S to .c and set PMIC values
by Rajeshwari Shinde 02 Jan '13

02 Jan '13

This patch converts lowlevel_init.S to lowlevel_init_c.c. Add PMIC MAX77686 voltage settings for SMDK5250. Rajeshwari Shinde (4): SMDK5250: Convert lowlevel_init.S to lowlevel_init_c.c EXYNOS: Add functions for power initialisation SMDK5250: Add PMIC voltage settings SMDK5250: Modify IRAM stack pointer address arch/arm/cpu/armv7/exynos/power.c | 34 ++++++++++++++ arch/arm/include/asm/arch-exynos/power.h | 5 ++ board/samsung/smdk5250/Makefile | 1 + board/samsung/smdk5250/dmc_common.c | 4 +- board/samsung/smdk5250/dmc_init_ddr3.c | 6 ++- board/samsung/smdk5250/lowlevel_init.S | 69 ++--------------------------- board/samsung/smdk5250/lowlevel_init_c.c | 70 ++++++++++++++++++++++++++++++ board/samsung/smdk5250/setup.h | 17 ++++++- board/samsung/smdk5250/smdk5250.c | 68 ++++++++++++++++++++++++++++- board/samsung/smdk5250/spl_boot.c | 52 ++++++++++++++++++---- include/configs/exynos5250-dt.h | 7 ++- include/power/max77686_pmic.h | 15 ++++++ spl/Makefile | 4 ++ 13 files changed, 266 insertions(+), 86 deletions(-) create mode 100644 board/samsung/smdk5250/lowlevel_init_c.c -- 1.7.4.4

4 14

[U-Boot] How to generate the exceptions in U-boot
by VISWANADHULA BALAJI 02 Jan '13

02 Jan '13

Dear all, For knowing the exception handler functionality in the U-boot, instead of running the stand alone applications i included the code(which generates the data abort)in the u-boot. When i run board gets hanged. I included the code after enable_interrupts( ) function. I am able to see the handler functionality when i run the stand alone applications but not with the data abort generated code. Can you guide me how to come out from this. Thanks balaji.V

1 0