September 2004 - U-Boot

[U-Boot-Users] Booting in IPv6
by philipv＠cam.org 02 Sep '04

02 Sep '04

Is there any support planned or in progress for booting in an IPv6 network? Philip

1 0

RE: [U-Boot-Users] M-Systems Disk on Chip and U-boot
by Woodruff, Richard 02 Sep '04

02 Sep '04

There are some MDOC drivers in the kernel MTD system at present. Putting them in u-boot wouldn't be so much of a stretch. How you use the single part in u-boot will depend on how big xip region is and its attributes. You might get away with folding it right in, or you might need a sub loader like we used for our TI NAND boots for OMAP processors. The OMAP 16xx/17xx/24xx processor allow for booting from a RAW NAND devices and can be made to work with u-boot. In there case they have microcode in the cpu which reads some blocks of nand into onchip SRAM and executes it. Regards, Richard W. > -----Original Message----- > From: u-boot-users-admin(a)lists.sourceforge.net [mailto:u-boot-users- > admin(a)lists.sourceforge.net] On Behalf Of Herb Radford > Sent: Thursday, September 02, 2004 6:37 AM > To: u-boot-users(a)lists.sourceforge.net > Subject: [U-Boot-Users] M-Systems Disk on Chip and U-boot > > We're looking at using a DoC on our next product and I was wondering how > the drivers (obviously supplied by M-Systems) are merged into U-Boot code? > > One of the newer P3 chips has an IPL section which is "execute in place" > and would contain early initialization code for the cpu/board/SDRAM and > then copy the body of the code into SDRAM. This idea sounds good for cost > reasons (one device) but seems like an ugly hack to the structure of > U-Boot. Any comments? > > Regards, Herb > > > > ------------------------------------------------------- > This SF.Net email is sponsored by BEA Weblogic Workshop > FREE Java Enterprise J2EE developer tools! > Get your free copy of BEA WebLogic Workshop 8.1 today. > http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click > _______________________________________________ > U-Boot-Users mailing list > U-Boot-Users(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/u-boot-users

1 0

[U-Boot-Users] Patch for Cirrus Logic EDB93xx
by llandre 02 Sep '04

02 Sep '04

Here http://www.dave-tech.it/download/misc/sw/edb93xx/u-boot-edb93xx-1 is available for download the patch for EDB93xx. It has been tested on EDB9312. Tha patch includes Steven Scholz's patch for ARM9-based SoCs. It seems that two builds (lpd7a400 and trab) got broken, but it is not clear why (see below). Any suggestions? *** lpd7a400 *** lib_arm/libarm.a(board.o)(.data+0x20): In function `mem_malloc_init': /home/llandre/devel/zephyr/sw/u-boot/u-boot/lib_arm/board.c:82: undefined reference to `checkcpu' make: *** [u-boot] Error 1 *** trab *** arm-linux-ld: ERROR: /usr/local/arm/3.3.2/lib/gcc-lib/arm-linux/3.3.2/libgcc.a(_udivsi3.oS) uses hardware FP, whereas trab_fkt uses software FP Success: failed to merge target specific data of file /usr/local/arm/3.3.2/lib/gcc-lib/arm-linux/3.3.2/libgcc.a(_udivsi3.oS) arm-linux-ld: ERROR: /usr/local/arm/3.3.2/lib/gcc-lib/arm-linux/3.3.2/libgcc.a(_umodsi3.oS) uses hardware FP, whereas trab_fkt uses software FP Success: failed to merge target specific data of file /usr/local/arm/3.3.2/lib/gcc-lib/arm-linux/3.3.2/libgcc.a(_umodsi3.oS) arm-linux-ld: ERROR: /usr/local/arm/3.3.2/lib/gcc-lib/arm-linux/3.3.2/libgcc.a(_dvmd_lnx.oS) uses hardware FP, whereas trab_fkt uses software FP Success: failed to merge target specific data of file /usr/local/arm/3.3.2/lib/gcc-lib/arm-linux/3.3.2/libgcc.a(_dvmd_lnx.oS) arm-linux-ld: ERROR: /usr/local/arm/3.3.2/lib/gcc-lib/arm-linux/3.3.2/libgcc.a(_udivdi3.oS) uses hardware FP, whereas trab_fkt uses software FP Success: failed to merge target specific data of file /usr/local/arm/3.3.2/lib/gcc-lib/arm-linux/3.3.2/libgcc.a(_udivdi3.oS) arm-linux-ld: ERROR: /usr/local/arm/3.3.2/lib/gcc-lib/arm-linux/3.3.2/libgcc.a(_clz.oS) uses hardware FP, whereas trab_fkt uses software FP Success: failed to merge target specific data of file /usr/local/arm/3.3.2/lib/gcc-lib/arm-linux/3.3.2/libgcc.a(_clz.oS) make[1]: *** [trab_fkt.srec] Error 1 make: *** [board/trab/libtrab.a] Error 2 Regards, llandre DAVE Electronics System House - R&D Department web: http://www.dave-tech.it email: r&d2(a)dave-tech.it

3 5

RE: [U-Boot-Users] Booting kernel with initrd
by Zhang, Jian 01 Sep '04

01 Sep '04

Make a uImage from bootpImage instead of zImage so you won't need separate files for kernel and compressed ram disk image. Bootm automatically detects ram disk and passes its address to kernel through ATAG. Of course you need fatload to load this uImage to RAM first. Regards, Jian > -----Original Message----- > From: u-boot-users-admin(a)lists.sourceforge.net [mailto:u-boot-users- > admin(a)lists.sourceforge.net] On Behalf Of Rainer Brestan (VI/SEA) > Sent: Wednesday, September 01, 2004 2:53 AM > To: 'U-Boot-Users(a)lists.sourceforge.net' > Cc: 'wd(a)denx.de' > Subject: RE: [U-Boot-Users] Booting kernel with initrd > > Seems to be misunderstood. > > I dont want to create the root filesystem on FAT. > I want to have it like the configuration with loadlin, where you have the > four files on the FAT filesystem, the kernel, the initrd image, the root > filesystem image (ext2) and a swap image. When the kernel boots the > initrd, this mounts the root filesystem through the loopback device > (root=/dev/loop0), this is described various times on the net. > > I have read the manuals about uboot i have found (DLUG). > > The bootm command describes how the images (kernel and initrd) are > processed, when they are in flash and copied out in memeory. But that not > what i need in this case. They must be loaded from filesystem into RAM. It > makes no sense to load the images into RAM with another command and then > run bootm, which copies them from one position in RAM to another. > > The reply from fumin showed a way to do this. Looking at the kernel source > for the parameter parsing for initrd parameter assumes > initrd=0x00800000,16M to be correct (first start address and then size). I > dont understood > your reply. > > >> u can load image to 0x00800000 and type command to set bootargs like > below: > >> setenv bootargs root=/dev/ram0 mem=128M initrd=0x00800000,16M > > > >This is only needed for broken (Linux) ports. Normally U-Boot will > >directly pass the ramdisk address top the Linux kernel. > > Maybe i have completly misunderstood something, but for me the boot > sequency is to load the kernel from filesystem (probable fatload, but > where is the documentation for that command), then the initrd, and then > starting the kernel with go with bootargs set to root=/dev/loop0 > initrd=start,size. > > Is this wrong ? > Should i use other commands ? > Should i use another way to get the kernel and initrd from FAT filesystem > ? > > Regards, Rainer > > > ------------------------------------------------------- > This SF.Net email is sponsored by BEA Weblogic Workshop > FREE Java Enterprise J2EE developer tools! > Get your free copy of BEA WebLogic Workshop 8.1 today. > http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click > _______________________________________________ > U-Boot-Users mailing list > U-Boot-Users(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/u-boot-users

1 0

[U-Boot-Users] u-boot-1.1.1 ml300 compile problem
by Der Herr Hofrat 01 Sep '04

01 Sep '04

----- Forwarded message (env-from root) ----- >From root Sun Aug 29 16:10:11 2004 Subject: u-boot-1.1.1 ml300 compile problem To: u-boot-users(a)lists-sourceforge.net Date: Sun, 29 Aug 2004 16:10:11 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL60 (25)] HI ! The mails in the archive on ml300 I found say to "compile u-boot first" or state that it compiles successfully, the problem I have is that this step fails. Platform: Debian Xilinx: EDK 6.2 Procedure: copied boot.o crt0.o and libc.a to examples export CROSS_COMPILE=powerpc-eabi- make ml300_config make IT failes with an undefined reference to main As I just ran this on the unmodified download version of u-boot to check the procedure before making any modifications for my board, I asume I'm doing somthing wrong in the procedure/setup - any hint to what I'm doing wrong or what the proper procedure would be ? make[1]: Entering directory `/root/u-boot-1.1.1/tools' make[1]: `.depend' is up to date. make[1]: Leaving directory `/root/u-boot-1.1.1/tools' make[1]: Entering directory `/root/u-boot-1.1.1/examples' make[1]: `.depend' is up to date. make[1]: Leaving directory `/root/u-boot-1.1.1/examples' make[1]: Entering directory `/root/u-boot-1.1.1/post' make[1]: `.depend' is up to date. make[1]: Leaving directory `/root/u-boot-1.1.1/post' make[1]: Entering directory `/root/u-boot-1.1.1/post/cpu' make[1]: `.depend' is up to date. make[1]: Leaving directory `/root/u-boot-1.1.1/post/cpu' make -C tools all make[1]: Entering directory `/root/u-boot-1.1.1/tools' make[1]: Leaving directory `/root/u-boot-1.1.1/tools' make -C examples all make[1]: Entering directory `/root/u-boot-1.1.1/examples' powerpc-eabi-ld -g -Ttext 0x40000 \ -o hello_world -e hello_world hello_world.o libstubs.a \ -L/root/EDK/gnu/powerpc-eabi/lin/bin/../lib/gcc-lib/powerpc-eabi/2.95.3-4 -lgcc powerpc-eabi-objcopy -O srec hello_world hello_world.srec 2>/dev/null powerpc-eabi-gcc -g -Os -fPIC -ffixed-r14 -meabi -D__KERNEL__ -DTEXT_BASE=0x04000000 -I/root/u-boot-1.1.1/include -fno-builtin -ffreestanding -nostdinc -isystem /root/EDK/gnu/powerpc-eabi/lin/bin/../lib/gcc-lib/powerpc-eabi/2.95.3-4/include -pipe -DCONFIG_PPC -D__powerpc__ -DCONFIG_4xx -ffixed-r2 -ffixed-r29 -mstring -Wa,-m405 -mcpu=405 -msoft-float -Wall -Wstrict-prototypes -c -o sched.o sched.c powerpc-eabi-ld -g -Ttext 0x40000 \ -o sched -e sched sched.o libstubs.a \ -L/root/EDK/gnu/powerpc-eabi/lin/bin/../lib/gcc-lib/powerpc-eabi/2.95.3-4 -lgcc libxil.a(crt0.o): In function `_start': crt0.o(.text+0x78): undefined reference to `main' make[1]: *** [sched] Error 1 make[1]: Leaving directory `/root/u-boot-1.1.1/examples' make: *** [examples] Error 2 thx ! hofrat

2 3

[U-Boot-Users] Big endian-ness - Config option?
by David Snowdon 01 Sep '04

01 Sep '04

G'Day, Feel free to harsh me if I've got this wrong. (I'm writing this so I don't get harshed when I submit my patch). I've just borrowed the code from the sixnet board for talking to 28F320C3 flash chips (advanced boot sector, yada, yada) which was written by Wolfgang at some point. Its dropped in very nicely and works very well (once I'd worked out what i was doing). I've had two problems. The first has been that that the code uses the get_timer(x) function, which is not implemented properly on ARM. (It just returns the value of the OS counter, ignoring the value passed to it. I had to replace the get_timer stuff with get_timer_masked and reset_timer_masked. I could try fixing the arm implementation of get_timer, but figured you guys wouldn't want me touching that bit of code since other bits and pieces now depend on it. Is there some way of doing this nicely? The second was that one part of the code munges some bytes into a word to get them ready for writing. This is broken with respect to endian-ness, and breaks on my XScale running in little-endian mode. Is it possible (or appropriate?) to add a CFG_LITTLE_ENDIAN (or something similar)? Is there a better way of switching between the two? It would be nice if this code could be re-used without these sorts of problems. Cheers, Dave. - David Snowdon PhD Student National ICT Australia (NICTA) Phone: 9385 7355 Email: daves(a)cse.unsw.edu.au

3 3

[U-Boot-Users] porting to new board: what to do next?
by Benjamin Collar 01 Sep '04

01 Sep '04

Greetings We're porting U-Boot to a new board. We've followed the plan given in the README and have written board.c, flash.c, configs/board.h. We've flashed it and ... well, nothing happens. Nothing at all. Now, I know you'll need more information from me, but I'm not sure exactly what you'll want to know, so for the moment, we'll leave it like that. What I need to know is, how do I find out what U-Boot is up to? Is there a way to debug it from the beginning? I've got it connected serially (unfortunately, our debugger works under windows, so we've got to use HyperTerminal) but nothing shows up at all. Thanks for any help Ben -- Benjamin Collar Siemens AG CT SE 2 Embedded Linux 089-636-53711

2 3

[U-Boot-Users] Returned mail: User unknown
by Mail Delivery Subsystem 01 Sep '04

01 Sep '04

The original message was received at Wed, 1 Sep 2004 18:49:04 +0300 (IDT) from diup-203-16.inter.net.il [213.8.203.16] ----- The following addresses had permanent delivery errors ----- <igldservicess(a)zahav.net.il>

1 0

RE: [U-Boot-Users] Booting kernel with initrd
by Rainer Brestan (VI/SEA) 01 Sep '04

01 Sep '04

Seems to be misunderstood. I dont want to create the root filesystem on FAT. I want to have it like the configuration with loadlin, where you have the four files on the FAT filesystem, the kernel, the initrd image, the root filesystem image (ext2) and a swap image. When the kernel boots the initrd, this mounts the root filesystem through the loopback device (root=/dev/loop0), this is described various times on the net. I have read the manuals about uboot i have found (DLUG). The bootm command describes how the images (kernel and initrd) are processed, when they are in flash and copied out in memeory. But that not what i need in this case. They must be loaded from filesystem into RAM. It makes no sense to load the images into RAM with another command and then run bootm, which copies them from one position in RAM to another. The reply from fumin showed a way to do this. Looking at the kernel source for the parameter parsing for initrd parameter assumes initrd=0x00800000,16M to be correct (first start address and then size). I dont understood your reply. >> u can load image to 0x00800000 and type command to set bootargs like below: >> setenv bootargs root=/dev/ram0 mem=128M initrd=0x00800000,16M > >This is only needed for broken (Linux) ports. Normally U-Boot will >directly pass the ramdisk address top the Linux kernel. Maybe i have completly misunderstood something, but for me the boot sequency is to load the kernel from filesystem (probable fatload, but where is the documentation for that command), then the initrd, and then starting the kernel with go with bootargs set to root=/dev/loop0 initrd=start,size. Is this wrong ? Should i use other commands ? Should i use another way to get the kernel and initrd from FAT filesystem ? Regards, Rainer

2 1

[U-Boot-Users] MDaemon Warning - Virus Found
by postmaster＠sovtek.com 01 Sep '04

01 Sep '04

The following message had attachment(s) which contained viruses: >From : u-boot-users(a)lists.sourceforge.net To : Poster(a)sovtek.com Subject : ***SPAM*** Score/Req: 05.53/05.00 - Re: important details Date : Tue, 31 Aug 2004 20:37:00 -0700 Message-ID: Attachment Virus name Action taken ------------------------------------------------------------------------------ details_sales.exe I-Worm.NetSky.q Message Quarantined

1 0