June 2010 - U-Boot

[U-Boot] [PATCH 1/4 v2] musb: Use name based initialization for musb_config
by Ajay Kumar Gupta 10 Jun '10

10 Jun '10

Changed musb_config initialization for omap3.c, davinci.c and da8xx.c using name of structure fields. This would cause the uninitialized field to be null by default and thus would help in avoiding to init some flags required to be set only for a few selected platforms. CC: Remy Bohmer <linux(a)bohmer.net> Signed-off-by: Ajay Kumar Gupta <ajay.gupta(a)ti.com> --- drivers/usb/musb/da8xx.c | 6 +++--- drivers/usb/musb/davinci.c | 6 +++--- drivers/usb/musb/omap3.c | 6 +++--- 3 files changed, 9 insertions(+), 9 deletions(-) diff --git a/drivers/usb/musb/da8xx.c b/drivers/usb/musb/da8xx.c index 40bfe44..617d88e 100644 --- a/drivers/usb/musb/da8xx.c +++ b/drivers/usb/musb/da8xx.c @@ -27,9 +27,9 @@ /* MUSB platform configuration */ struct musb_config musb_cfg = { - (struct musb_regs *)DA8XX_USB_OTG_CORE_BASE, - DA8XX_USB_OTG_TIMEOUT, - 0 + .regs = (struct musb_regs *)DA8XX_USB_OTG_CORE_BASE, + .timeout = DA8XX_USB_OTG_TIMEOUT, + .musb_speed = 0, }; /* diff --git a/drivers/usb/musb/davinci.c b/drivers/usb/musb/davinci.c index 8fbadc9..f56f2df 100644 --- a/drivers/usb/musb/davinci.c +++ b/drivers/usb/musb/davinci.c @@ -28,9 +28,9 @@ /* MUSB platform configuration */ struct musb_config musb_cfg = { - (struct musb_regs *)MENTOR_USB0_BASE, - DAVINCI_USB_TIMEOUT, - 0 + .regs = (struct musb_regs *)MENTOR_USB0_BASE, + .timeout = DAVINCI_USB_TIMEOUT, + .musb_speed = 0, }; /* MUSB module register overlay */ diff --git a/drivers/usb/musb/omap3.c b/drivers/usb/musb/omap3.c index 3bfd0a0..785629c 100644 --- a/drivers/usb/musb/omap3.c +++ b/drivers/usb/musb/omap3.c @@ -36,9 +36,9 @@ static int platform_needs_initialization = 1; struct musb_config musb_cfg = { - (struct musb_regs *)MENTOR_USB0_BASE, - OMAP3_USB_TIMEOUT, - 0 + .regs = (struct musb_regs *)MENTOR_USB0_BASE, + .timeout = OMAP3_USB_TIMEOUT, + .musb_speed = 0, }; /* -- 1.6.2.4

3 5

[U-Boot] [PATCH 0/4] Support for board Calao USB A9263
by Thomas Petazzoni 09 Jun '10

09 Jun '10

Hello, This patchset implements the support for the Calao USB A9263 board (patch 4). The first three patches are preliminary work, to convert the Atmel Dataflash SPI driver to the new C struct accessors introduced a few months ago for AT91 support in U-Boot. Thanks, Thomas Thomas Petazzoni (4): Atmel Dataflash: convert to C struct accessors at91_spi: remove register offsets at91sam9263: add new style definition for SPI0_BASE Support for Calao USB A9263 board based on AT91SAM9263 CPU MAINTAINERS | 4 + MAKEALL | 1 + Makefile | 3 + arch/arm/include/asm/arch-at91/at91_spi.h | 152 +++++++++------------ arch/arm/include/asm/arch-at91/at91sam9263.h | 1 + board/calao/usb-a9263/Makefile | 58 ++++++++ board/calao/usb-a9263/config.mk | 24 ++++ board/calao/usb-a9263/partition.c | 38 ++++++ board/calao/usb-a9263/usb-a9263.c | 186 ++++++++++++++++++++++++++ drivers/spi/atmel_dataflash_spi.c | 73 ++++++----- include/configs/usb-a9263.h | 182 +++++++++++++++++++++++++ 11 files changed, 598 insertions(+), 124 deletions(-) create mode 100644 board/calao/usb-a9263/Makefile create mode 100644 board/calao/usb-a9263/config.mk create mode 100644 board/calao/usb-a9263/partition.c create mode 100644 board/calao/usb-a9263/usb-a9263.c create mode 100644 include/configs/usb-a9263.h

3 15

[U-Boot] [PATCH V7 2/3] Add Orion5x support to 16550 device driver
by Albert Aribaud 09 Jun '10

09 Jun '10

This patch provides access to the 16550-compatible serial device of the Orion5x SoC. Signed-off-by: Albert Aribaud <albert.aribaud(a)free.fr> --- drivers/serial/serial.c | 3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) diff --git a/drivers/serial/serial.c b/drivers/serial/serial.c index 8eda95c..1073ac0 100644 --- a/drivers/serial/serial.c +++ b/drivers/serial/serial.c @@ -30,6 +30,9 @@ #ifdef CONFIG_KIRKWOOD #include <asm/arch/kirkwood.h> #endif +#ifdef CONFIG_ORION5X +#include <asm/arch/orion5x.h> +#endif #if defined (CONFIG_SERIAL_MULTI) #include <serial.h> -- 1.6.4.4

2 1

[U-Boot] [PATCH V7 2/3] Add Orion5x support to 16550 device driver
by Albert Aribaud 09 Jun '10

09 Jun '10

This patch provides access to the 16550-compatible serial device of the Orion5x SoC. Signed-off-by: Albert Aribaud <albert.aribaud(a)free.fr> --- drivers/serial/serial.c | 3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) diff --git a/drivers/serial/serial.c b/drivers/serial/serial.c index 8eda95c..1073ac0 100644 --- a/drivers/serial/serial.c +++ b/drivers/serial/serial.c @@ -30,6 +30,9 @@ #ifdef CONFIG_KIRKWOOD #include <asm/arch/kirkwood.h> #endif +#ifdef CONFIG_ORION5X +#include <asm/arch/orion5x.h> +#endif #if defined (CONFIG_SERIAL_MULTI) #include <serial.h> -- 1.6.4.4

1 0

[U-Boot] Fw:Re: Fw:Re: Fw:How can I use yaffs2 in uboot
by jackfriend 09 Jun '10

09 Jun '10

> And how are your MTD partitions set up in Linux? [*] MTD partitioning support < > RedBoot partition table parsing [*] Command line partition table parsing < > TI AR7 partitioning support static struct mtd_partition mini2440_default_nand_part[] __initdata = { [0] = { .name = "u-boot", .size = SZ_256K + SZ_128K, .offset = 0, }, [1] = { .name = "u-boot-env", .size = SZ_128K, .offset = SZ_256K + SZ_128K, }, [2] = { .name = "kernel", /* 5 megabytes, for a kernel with no modules * or a uImage with a ramdisk attached */ .size = 0x00500000, .offset = SZ_512K, }, [3] = { .name = "root", .offset = SZ_512K + 0x00500000, .size = MTDPART_SIZ_FULL, }, }; in /uboot/fs/yaffs2/yaffscfg.c flashDev->startBlock =44; flashDev->endBlock = 800;

1 0

[U-Boot] DRAM error when enable #define CONFIG_SPLASH_SCREEN
by Tommy Agustianto 09 Jun '10

09 Jun '10

for enabling splash screen on my board (mpx8349) I enabled the splash screen config in file configuration. the binary was succesfully flashed to the board but when I start the uboot, I got this message : U-Boot 2009.01-dirty (Jun 09 2010 - 10:19:28) MPC83XX Reset Status: CPU: e300c1, MPC8349EA, Rev: 3.0 at 396 MHz, CSB: 264 MHz Board: MPX8349 PCI1: 32 bit, 33 MHz SRAM: 1 MB I2C: ready DRAM: *** failed *** ### ERROR ### Please RESET the board ### and I'd like to know, what the meaning of 'dirty' on the U-Boot title. what more that I must configure to enabling splash screen or bitmap support? like memory init..etc.. Thanks -- "success isn't a destination but its a journey" ---------------------------- Tommy Agustianto Electronics Engineer. ---------------------------- http://xsatria.wordpress.com

2 1

[U-Boot] BDI2000 Procedure
by Mark Maestas 09 Jun '10

09 Jun '10

Hi Does anyone have a procedure to restore u-boot on a AMCC Canyonlands board using the BDI2000? I have the bdisetup utility and the firmware/logic files for ppc4xx. I also found the config files for BDI2000 but there is not a procedure to program it. I have not used our BDI programmer before so this may be a stupid question but I need to restore the image on a couple of boards now. Thanks Mark Maestas

2 1

[U-Boot] Unable to mount Root File System , initramdisk or initramfs
by Gurumurthy G M 09 Jun '10

09 Jun '10

Hi All, I am using MIPS32 AU1350 processor board with 2MB of NOR Flash, I have programmed u-boot and Linux kernel in NOR Flash. U-boot is working able to boot linux kernel but not able to mount root filesystem from SDRAM. I tried both initramdisk and initramfs. please let me know more info about this. I have created uRamdisk and also passed boot arguments. Below is the error log. let me know whether I am missing something. U-Boot 2010.03 (May 28 2010 - 21:01:02) Linux Advanced AVN Platform CPU: Au1350 660MHz, id: 0x80, rev: 0x01 DRAM: 256 MB Flash: 2 MB *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial LinuxAVN=> loadb 0x81000000 ## Ready for binary (kermit) download to 0x81000000 at 0 bps... (Back at localhost) ---------------------------------------------------- (/home/gurumurthy/Downloads/kermit/) C-Kermit>send /tftpboot/rdImage (/home/gurumurthy/Downloads/kermit/) C-Kermit>\c Connecting to /dev/ttyS0, speed 115200 Escape character: Ctrl-\ (ASCII 28, FS): enabled Type the escape character followed by C to get back, or followed by ? to see other options. ---------------------------------------------------- ## Total Size = 0x002ed937 = 3070263 Bytes ## Start Addr = 0x81000000 LinuxAVN=> imls Legacy Image at BFC50000: Image Name: Linux-2.6.28.1 Created: 2010-06-02 11:38:32 UTC Image Type: MIPS Linux Kernel Image (gzip compressed) Data Size: 1134559 Bytes = 1.1 MB Load Address: 80100000 Entry Point: 80104730 Verifying Checksum ... OK LinuxAVN=> iminfo 0x81000000 ## Checking Image at 81000000 ... Legacy image found Image Name: Created: 2010-06-02 11:11:16 UTC Image Type: MIPS Linux RAMDisk Image (gzip compressed) Data Size: 3070199 Bytes = 2.9 MB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK LinuxAVN=> setenv bootargs console=ttyS0,115200 root=/dev/ram0 rw LinuxAVN=> printenv baudrate=115200 stdin=serial stdout=serial stderr=serial filesize=2ED937 bootargs=console=ttyS0,115200 root=/dev/ram0 rw Environment size: 121/65532 bytes LinuxAVN=> baudrate=115200 stdin=serial stdout=serial stderr=serial filesize=2ED937 bootargs=console=ttyS0,115200 root=/dev/ram0 rw Environment size: 121/65532 bytes LinuxAVN=> baudrate=115200 stdin=serial stdout=serial stderr=serial filesize=2ED937 bootargs=console=ttyS0,115200 root=/dev/ram0 rw Environment size: 121/65532 bytes LinuxAVN=> baudrate=115200 stdin=serial stdout=serial stderr=serial filesize=2ED937 bootargs=console=ttyS0,115200 root=/dev/ram0 rw Environment size: 121/65532 bytes LinuxAVN=> bootm ## Booting kernel from Legacy Image at 81000000 ... Image Name: Created: 2010-06-02 11:11:16 UTC Image Type: MIPS Linux RAMDisk Image (gzip compressed) Data Size: 3070199 Bytes = 2.9 MB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Wrong Image Type for bootm command ERROR: can't get kernel image! LinuxAVN=> LinuxAVN=> LinuxAVN=> bootm 0xbfc50000 0x81000000 ## Booting kernel from Legacy Image at bfc50000 ... Image Name: Linux-2.6.28.1 Created: 2010-06-02 11:38:32 UTC Image Type: MIPS Linux Kernel Image (gzip compressed) Data Size: 1134559 Bytes = 1.1 MB Load Address: 80100000 Entry Point: 80104730 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 81000000 ... Image Name: Created: 2010-06-02 11:11:16 UTC Image Type: MIPS Linux RAMDisk Image (gzip compressed) Data Size: 3070199 Bytes = 2.9 MB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Uncompressing Kernel Image ... OK Starting kernel ... Linux version 2.6.29.4-rmi-126-DB1350 (root@gurumurthy) (gcc version 4.2.4) #31 Wed Jun 2 17:05:36 IST 2010 console [early0] enabled CPU revision is: 800c8001 (Au13xx) (PRId 800c8001) @ 660.00 MHz RMI DBAu1300 Development Board Determined physical RAM map: memory: 01800000 @ 00000000 (usable) memory: 0c800000 @ 01800000 (reserved) memory: 02000000 @ 0e000000 (usable) Initrd not found or empty - disabling initrd Zone PFN ranges: Normal 0x00000000 -> 0x00010000 HighMem 0x00010000 -> 0x00010000 Movable zone start PFN for each node early_node_map[1] active PFN ranges 0: 0x00000000 -> 0x00010000 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024 Kernel command line: console=ttyS0,115200 root=/dev/ram0 rw video=au1200fb:panel:bs Primary instruction cache 16kB, VIPT, 4-way, linesize 32 bytes. Primary data cache 16kB, 4-way, VIPT, no aliases, linesize 32 bytes PID hash table entries: 1024 (order: 10, 4096 bytes) Alchemy clocksource installed Console: colour dummy device 80x25 Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) Memory: 51012k/57344k available (1899k kernel code, 5988k reserved, 490k data, 152k init, 0k highmem) Calibrating delay loop... 658.63 BogoMIPS (lpj=3293184) Mount-cache hash table entries: 512 Hooking cpu_wait bio: create slab <bio-0> at 0 SCSI subsystem initialized Creating sysfs entry for board Alchemy MEMPOOL initializing Alchemy MEMPOOL registered at major 235 Available memory pools: LCD: 40 MB @ phys 0x01800000, free BSA: 64 MB @ phys 0x04000000, free MPE: 32 MB @ phys 0x08000000, free OGL: 64 MB @ phys 0x0a000000, free squashfs: version 4.0 (2009/01/31) Phillip Lougher msgmni has been set to 100 alg: No test for stdrng (krng) io scheduler noop registered (default) io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled )console handover: boot [early0] -> real [ttyS0]) is a 8250 brd: module loaded Driver 'sd' needs updating - please use bus_type methods Driver 'sr' needs updating - please use bus_type methods List of all partitions: No filesystem could mount root, tried: ext3 ext2 cramfs squashfs vfat msdos Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0) With Regards, Gurumurthy

2 1

[U-Boot] Linux kernel only reporting 16M / 128M
by Kristoffer Ericson 09 Jun '10

09 Jun '10

Greetings, My flashing issues are now gone and will adress this later on. Anyhow, I noticed that linux kernel only reports 16M total memory while the board got 128M. Was just wondering where to start looking? Everything works fine inside u-boot so its not passed correctly or something, not sure how the linux kernel detects that. Any thoughts are helpful. Best wishes Kristoffer

2 3

Re: [U-Boot] Rescue /alternative boot
by Arno Steffen 09 Jun '10

09 Jun '10

Dear Albert, 2010/6/9 Albert ARIBAUD <albert.aribaud(a)free.fr>: > If the user is able to do something stupid then you should avoid it, e.g. > not give the user the ability to alter the u-boot environment by making it In fact, the normal user doesn't have access to change it. But even I can make faults. > You should consider accessibility to the bootloader prompt as a critical > requirement before considering resiliency -- actually, access to U-boot is a > last-resort, but good, response to the resiliency requirement. I am not free to change this anymore. So I have to find another way via network. > Why can you not trust the u-boot environment? Maybe hardening the system > against user-induced environment changes would help avoid the condition in > the first place. The system must be ready for updates - and they might go wrong, even by a typo. >> - howto handle boot/kernel parameters? I only know the way via >> environment variables > > As Wolfgang pointed out, read the manual: passing parameters does not depend > on how you got the image in the first place, and works the same whether you > use TFTP, flash or hard disks. In manual I just can see how to set commandline parameters. Everything ( I understand until now) is controled via environment. I have to put some code (before the environment is read) into uboot source to force a tftpboot with in-compiled parameters. And I don't have a clue howto and where to do this. It is not enough to set some default environment, as this becomes active only if CRC is failed. This will not help against a typo in the setting. Best regards Arno

2 1