February 2005 - U-Boot

[U-Boot-Users] i2c compiling and/or linking problem
by Peter Asemann 13 Feb '05

13 Feb '05

Well, I wanted to compile u-boot with i2c support. So I just added an #include <i2c.h> in to my boards board.c, put #define CFG_HARD_I2C in the include-file and thought that'd be enough. Well... apparently that's not enough as compiling (make distclean done before) stops in the linking process with a lot of complaints like this: common/libcommon.a(cmd_i2c.o)(.text+0x128): In function `do_i2c_md': /opt/asemann/u-boot/common/cmd_i2c.c:188: undefined reference to `i2c_read' and the error common/libcommon.a(exports.o)(.got2+0x24):/opt/asemann/u-boot/common/exports.c:14: undefined reference to `i2c_read' So... any suggestions where to add some references so it find all the stuff? I tried to figure out what other boards that use i2c do, but couldn't find any hints that I missed some Makefile or config, got lost in the build-system. Peter Asemann

4 8

[U-Boot-Users] My first embedded project
by Benjamin D Boicourt 12 Feb '05

12 Feb '05

Hi, I'm new to the world of embedded linux and have a few questions. First some back ground on my current project. I am the software guy on an embedded firmware project. We are using a Virtex II Pro P50 with one PowerPC 405 core. We will have 512MB Compactflash and 64MB SRAM. We want to use U-boot and the latest kernel of linux as our bootlaoder and OS. The firmware package that will be running on the OS will be C/C++ programs. 1. Is there a way to use U-boot without an EEPROM. Can we use U-boot with its environmental variables on the Compactflash card? 2. Is there a doc that details the boot processes of the boot loader and the linux kernel? 3. Is there a doc detailing the process of downloading, configuring and porting an open source kernel to the VII Pro? I greatly appreciate any help. Thank you very much, Ben

4 6

[U-Boot-Users] at45 dataflash
by Z.N. 12 Feb '05

12 Feb '05

Hi! I'm running u-boot 1.1.2 on an AT91 compatible board, however I have no NAND flash, only serial dataflash. As far as I've looked at the sources, there is a configuration option that I can store environment variables on the dataflash, however how can I load the kernel image & ramdisk image from dataflash into SDRAM? (I've found no commands to do this, maybe I overlooked it somewhere..) If there is no way to do this, what if I load the kernel image together with u-boot into sdram on startup, can u-boot start this "pre-loaded" kernel image? Thank you for you answers! Best Regards, Zoli

3 4

[U-Boot-Users] decrease boot time
by Konstantin Kletschke 12 Feb '05

12 Feb '05

Hi Folks! I am trying to improve boot time of my linux system on my motorola i.MX system as much as possible. Therefore I tried to omit the copying and decompressing the linux kernel image ba using XIP, but the code runs slower in the (slower) flash and boot time increased. I wonder how to make use of sync burst mode with u-boot in conjunction eith linux. Today I switched on CFG_CMD_CACHE (I use u-boot-1.1.1) but I wonder if u-boot knows that it should cache the area above 0x10000000. Hm... I think the way the linux kernel starts itself is not making use of any implementation of burst mode of the flash device. It copies a small amount of bytes and decompresses them. Could it be possible to make use of burst mode by copying the compressed image into RAM by u-boot (i.e. bursting) and start the kernel in RAM then? The decompressing and copying would be faster then... How do I disable serial support in u-boot? My u-boot is currently 60k big, in my opinion a simple bootloader which does something like memsetup and starting kernel afterwards should not be much bigger than 10k. Or is that wrong? I tried to disable serial support but several functions in common/ (serial_get* for example) are calling functions in cpu/arm920t/imx_serial.c. Do I have to "#ifdef" any occurences of these functions? REgards, Konsti -- GPG KeyID EF62FCEF Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF

3 2

[U-Boot-Users] Environment in flash rather than EEProm
by Andy Hawkins 11 Feb '05

11 Feb '05

Hi all I'm using a PPChameleonEVB, and am trying to move the u-boot environment into flash. I've modified the include/configs/PPChameleon.h file as follows: #define CFG_ENV_IS_IN_FLASH 1 #define CFG_ENV_ADDR 0xFFFFA000 #define CFG_ENV_OFFSET (CFG_ENV_ADDR - 0xFFFC0000) #define CFG_ENV_SIZE 0x2000 I've added some debugging into the section where it reads the environment, and I'm seeing the following: U-Boot 1.0.2-adh-2004/03/29 (Mar 30 2004 - 13:40:38) CPU: IBM PowerPC 405EP Rev. B at 133.333 MHz (PLB=133, OPB=66, EBC=33 MHz) IIC Boot EEPROM disabled PCI async ext clock used, internal PCI arbiter enabled 16 kB I-Cache 16 kB D-Cache Board: ### No HW ID - assuming PPChameleonEVB I2C: ready DRAM: 32 MB Top of RAM usable for U-Boot at: 02000000 Reserving 189k for U-Boot at: 01fd0000 Reserving 256k for malloc() at: 01f90000 Reserving 128 Bytes for Board Info at: 01f8ff80 Reserving 48 Bytes for Global Data at: 01f8ff50 Stack Pointer at: 01f8ff38 New Stack Pointer is: 01f8ff38 Now running in RAM - U-Boot at: 01fd0000 FLASH: 4 MB env_relocate[204] offset = 0x2010000 env_relocate[216] embedded ENV (before reloc) at fffd9474 env_relocate[218] embedded ENV (after reloc) at 01fe9474 U-Boot relocated to 01fd0000 NAND:Probing at 0xff000000 32 MB ### main_loop entered: bootdelay=5 ### main_loop: bootcmd="<UNDEFINED>" => As you can see, the address of the environment before relocation is 0xfffd9474. Shouldn't this be 0xFFFFA000? Is there anything else I need to do to force the location of the environment into the required place? It looks like the address of the environment is based on the location of the 'environment' variable in common/environment.c. Do I need to change the LD script to force this variable to a certain location? If so, can anyone help with what I need to do (I'm not familiar with LD scripts yet). Many thanks. Andy

3 7

[U-Boot-Users] Upload from U-Boot to serial-client?
by Martin Egholm Nielsen 11 Feb '05

11 Feb '05

Hi there, I know this was up a couple of years ago :-) (PPCBoot related), but is there a way (besides dumping with "md") to upload data to a client using the serial-/ethernet-connection? Best regards, Martin

2 2

[U-Boot-Users] error while loading image with fatload.
by Sharad P. Katti 11 Feb '05

11 Feb '05

Hi, We are using u-boot-1.1.1, and trying to load the uImage from the FAT partition, The board has a 20GB harddisk, and we have created 3 partitions in that, using fdisk, and the 3rd partition is of type FAT, we have copied the uImage and the Ramdisk image on the FAT partition, and while trying to load the uImage from the same, we are getting the following error, the fat partition type is showing as c (win95 FAT(LBA)) $ fatload ide 0:3 0xa0100000 uimage reading uimage FAT32, fatlength: 8568 Rootdir begins at sector: 17168, offset: 862000, size: 32 Data begins at: 17104 Cluster size: 32 Rootvfatname: |bcm | RootMismatch: |au|bcm | Rootvfatname: |uimage| RootName: uimage~1, start: 0x3, size: 0xc4d60 Filesize: 806240 bytes Reading: 806240 bytes gc - clustnum: 3, startsect: 17200 curclust: 0xfff0004 Invalid FAT entry Size: 806240, got: 16384 We are able to list the contents using the fatls command, what could be the reason for the above error..? regards, -- Sharad P.Katti "GOD is real, unless declared as an int"

2 2

[U-Boot-Users] MPC8540ADS CONFIG_HAS_FEC patch
by Jon Loeliger 10 Feb '05

10 Feb '05

Wolfgang, Here is a simple patch that introduces the CONFIG_HAS_FEC option to the MPC8540 ADS board. Thanks, jdl * Patch by Jon Loeliger, 2005-Feb-10 Add config option CONFIG_HAS_FEC calling out 8540 FEC features. diff -r --exclude=CVS -u u-boot/doc/README.mpc85xxads u-boot-pq3/doc/README.mpc85xxads --- u-boot/doc/README.mpc85xxads 2005-02-09 14:49:14.000000000 -0600 +++ u-boot-pq3/doc/README.mpc85xxads 2005-02-10 12:20:35.998989000 -0600 @@ -143,6 +143,7 @@ CONFIG_DDR_ECC only for ECC DDR module CONFIG_DDR_DLL DLL fix on some ADS boards needed for more stability. + CONFIG_HAS_FEC If an FEC is on chip, set to 1, else 0. Other than the above definitions, the rest in the config files are straightforward. diff -r --exclude=CVS -u u-boot/include/configs/MPC8540ADS.h u-boot-pq3/include/configs/MPC8540ADS.h --- u-boot/include/configs/MPC8540ADS.h 2005-01-09 11:12:34.000000000 -0600 +++ u-boot-pq3/include/configs/MPC8540ADS.h 2005-02-10 12:19:35.502593000 -0600 @@ -41,6 +41,10 @@ #define CONFIG_MPC8540 1 /* MPC8540 specific */ #define CONFIG_MPC8540ADS 1 /* MPC8540ADS board specific */ +#ifndef CONFIG_HAS_FEC +#define CONFIG_HAS_FEC 1 /* 8540 has FEC */ +#endif + #define CONFIG_PCI #define CONFIG_TSEC_ENET /* tsec ethernet support */ #define CONFIG_ENV_OVERWRITE @@ -344,9 +348,12 @@ #define TSEC1_PHYIDX 0 #define TSEC2_PHYIDX 0 + +#if CONFIG_HAS_FEC #define CONFIG_MPC85XX_FEC 1 -#define FEC_PHY_ADDR 3 +#define FEC_PHY_ADDR 3 #define FEC_PHYIDX 0 +#endif #define CONFIG_ETHPRIME "MOTO ENET0"

1 0

[U-Boot-Users] Re: u-boot and linux-2.6.9
by Peter Pearse 10 Feb '05

10 Feb '05

Alan Try setting the CP switch S2[1] ON (down) so that U-Boot is run after the ARM Boot Monitor. - either by hand or automatically. If your kernel then boots OK the problem is the failure to remap. This is solved by my multicore patch:- [Patch]IntegratorAP & CP multi core module support 2005-02-02 08:43 If your kernel does not boot with switch S2[1] ON then IMHO, the problem lies in your kernel, Peter ------------------------ Peter.Pearse(a)arm.com -------------------------

1 0

[U-Boot-Users] Booting problems for Integrator/CP+ARM920T
by Alan Casey 10 Feb '05

10 Feb '05

Hi, I have an ARM Integrator/CP board(s) which contains an ARM920T macrocell. I have been trying to use U-Boot(1.1.2) to boot linux2.6.9 (with a patch applied from ARM's website) on this system. As i understand it, U-Boot only supports the ARM926EJS macrocell as the default configuration with the Integrator/CP but i was hoping the same boot process would work with the ARM920T macrocell?? The default kernel command string i use when compiling/building/installing the kernel is: CONFIG_CMDLINE="root=/dev/ram0 video=vc:1-2clcdfb console=ttyAMA0 mem=128M ramdisk_size=17408 initrd=0x24500000,6980391" I then generate the kernel image using: arm-linux-objcopy -O binary -R .note -R .comment -S vmlinux linux-2.6.9.bin mkimage -n '2.6.9 Kernel Image' -A arm -O linux -T kernel -C none -a 0x7fc0 -e 0x7fc0 -d linux-2.6.9.bin linux-2.6.9.img I also generate a RAMDisk image in a similar way. I load the U-Boot, kernel and RAMDisk images into FLASH at the following addresses: U-Boot image: 0x24000000 kernel image: 0x242C0000 ramdisk image: 0x24500000 Using U-Boot i set the bootargs variable as: setenv bootargs root=/dev/ram0 However when i try to boot the kernel using 'bootm 242c0000 24500000' i get the following message: ## Booting image at 242c0000 ... ... Load Address: 00007fc0 Entry Point: 00007fc0 OK ## Loading Ramdisk Image at 24500000 ... ... ... Load Address: 00000000 Entry Point: 00000000 Starting Kernel ... Then nothing - the boot process freezes. Does anybody know what i am doing wrong?? I have tried numerous things such as copying the kernel image to RAM and booting from there but i always get the same message as above. Do i have to configure and build U-Boot to support the ARM920T macrocell with the Integrator/CP?? Any information greatly appreciated, Regards, Alan.

3 5