October 2006 - U-Boot

[U-Boot-Users] Linux Hangs After Uncompressing Kernel
by wenwen 07 Oct '06

07 Oct '06

i download a 6M Byte kernel(28M bytes uncompressed) to SDRAM(0x4000000), it hangs after uncompressing kernel. when i use standalone downlod the kernel, i found the text section which offset is 8M bytes is not the same as the objdump file of the elf file. is there any limited size about kernel ? i used amcc ppc440 sequoia board

3 3

[U-Boot-Users] howto use diskboot with ppcboot?
by Gerald Dachs 07 Oct '06

07 Oct '06

The following mail I sent some days ago is still unanswered. The author of the sources I refere to is one of the most active posters on the list, so I believe the answers to my questions are know. I assume that it got unanswered, because it is answered already somewhere else. I would be glad to get any pointer or link that help me with this, because the searches I did before I wrote the first mail didn't help me. Yes, I have read "How to ask smart questions", but maybe I didn't learn from it, and I am not whining :) Thanks Hi, I want to boot an alternative kernel on my NAS with minimal changes to the flash. I suppose this could be possible by using diskboot. My problem is now that I am very new to the bootloader problematic and the documentation for ppcboot is rather short and the documentation for uboot seems not to fit. From the sources of the diskboot command I understand that it expects a dos partition and reads continuous blocks from this partition. Does this mean I need a dos partition and have to write the kernel image with dd to it? It doesn't look like it supports the dos filesystem, or is the dos fs really so simple? But if it is not using the dos fs, why has the partition to be of type dos? Hopefully I didn't make myself a fool and overlooked the obvious. Gerald

3 4

[U-Boot-Users] Re : MV64460 Burst reads from BootCS
by joe secund 06 Oct '06

06 Oct '06

Hi Roel I've seen similar behavior using a MV64560 and power PC processor using a Windriver ICE. Basically I could not read the MV internal registers correctly when I did not plug in a bootrom (leaving empty socket). Was reading zeroes anywhere in memory. Somehow putting in even an empty Flash device allowed me to initialize the processor correctly and read/write MV registers and burn the flash via ICE. - Wim > ------------------------------ > > Message: 5 > Date: Sun, 1 Oct 2006 20:19:12 +0200 > From: "Roel Loeffen" <roel.loeffen@pr...> > Subject: [U-Boot-Users] MV64460 Burst reads from BootCS > To: <u-boot-users@li...> > Message-ID: > <7826EB01AD927140A1DCF898FE63325D0D91B1@Ex...> > Content-Type: text/plain; charset="iso-8859-1" > > Hi all, > > We discover some serious problems accessing flash at BootCS > of the Marvell MV64460. It looks like burst reads make the > whole bridge hang. >From inside U-Boot as well as using only > the BDI2000 debugger. > > Reading the flash with bursts enabled (which is default), > makes it sometimes impossible to access any > registers/dram/devices anymore, only zeros can be read. > > It also freezes the CPU somehow the debugger cannot halt it > anymore with a normal halt (COP halt), it has to use COP > freeze to take over control again. > > I cannot say this problem does not occur accessing other > spaces, so it can also be a problem at the PPC60x bus. > > Has anyone over excpirianced this before? > > Thanks in advance! > > Roel __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 0

[U-Boot-Users] What's the status on erasing a nand flash with bad blocks?
by mitsy 06 Oct '06

06 Oct '06

Hello list, There was a discussion on how to handle the bad blocks when erasing entire nand flash few month ago. I was curious to know what you all decided on how to handle the issue. Now I got a nand flash (Samsung) with 2 bad blocks and I can erase and program it from kernel using flash_eraseall and nandwrite just fine. However, from u-boot (I'm using a newer nand driver, btw) the erase stops at the first bad block, as you know. I'm little hesitant to just fix the code to skip the bad blocks during erase/write since like it was discussed on the earlier thread, kernel's mtd driver do it that way as well... Any comments/update on this issue will be very helpful! Thanks.

4 5

[U-Boot-Users] nand flash controller on 440ep/epx
by Jeff Mann 06 Oct '06

06 Oct '06

It appears that the nand flash controller support recently added to u-boot for the ppc400ep/epx only supports the use of a single nand chip. The nand flash controller supports up to four devices using chip selects 0-3. I am working on making two devices work right now for my use, but I would like to update the flash-controller support. I am open for comments on this. What I think I need to do is add an #config CFG_440_USENANDCONTROLLER option and an entry into the nand_chip struct for holding the chip select numbers for each chip. Then in addition to configuring an array of nand bases {CFG_NAND_BASE} (which would all be the same address because it is the address of the nand controller), the chip selects are put in a configured array and put into the nand_chip nand struct. The read and write functions would then need to be updated to enable the right chip select in the nand controller config register too. Comments? Suggestions? What am I missing? -Jeff

2 1

[U-Boot-Users] ML403 Uboot Linux Boot Error
by alayrac christophe 06 Oct '06

06 Oct '06

I'm coming back to the comunitee with good news , especially for me !-) I succeed to start linux (2-4.26) from u-boot 1.1.4 on ML403. When U-boot start I press enter to stop autostart. Then I type the following commands : => setenv bootargs => fatload ace 0 400000 linux/vmlinux.uboot => bootm 400000 In fact the first command is the reason of hang up after #Uncompressing Kernel Image .... Ok My goal was to preserve command line set up in the Kernel configuration (using NFS) If I type only the last two commands, the Kernel start properly on the root file system of the Compact Flash (due to u-boot default bootargs). I did not succeed to run under emulator to try to figure out what's going wrong. I do not succeed to activate break points with the command (under gdb) monitor bps do_bootm hw Is this U-boot behaviour normal? A second question is : What is the starting point to have I2C EEPROM available on that ML403 board under U-boot to save environnement and us autostart? Kinds regards Chris

2 1

[U-Boot-Users] Converting uboot.bin file to uboot.raw file
by Raju S N 06 Oct '06

06 Oct '06

Hi all, I have uboot.bin and uboot.out files. I need to generate <<< uboot.raw >>>> file. Iam new to these file formats. It may be simple one also. Please help me about the procedure to do this. I tried objcopy options and my << objdump -i >> command returned following BFD formats only BFD header file version 2.15.90.0.1.1 20040303 (SuSE Linux) elf32-i386 (header little endian, data little endian) i386 a.out-i386-linux (header little endian, data little endian) i386 efi-app-ia32 (header little endian, data little endian) i386 elf32-little (header little endian, data little endian) i386 elf32-big (header big endian, data big endian) i386 elf64-x86-64 (header little endian, data little endian) i386 elf64-little (header little endian, data little endian) i386 elf64-big (header big endian, data big endian) i386 srec (header endianness unknown, data endianness unknown) i386 symbolsrec (header endianness unknown, data endianness unknown) i386 tekhex (header endianness unknown, data endianness unknown) i386 binary (header endianness unknown, data endianness unknown) i386 ihex (header endianness unknown, data endianness unknown) i386 trad-core (header endianness unknown, data endianness unknown) Thanx Raju

2 1

[U-Boot-Users] Booting linux on i386 processor from u-boot.
by mushtaq khan 06 Oct '06

06 Oct '06

Hi, I have configured the u-boot to sc520_cdp board.I am trying to boot linux on x86 platform.But, i am facing a problem, u-boot is crashing when entering in to the realmode_enter(in file lib_i386/realmode_switch.S) routine.The image i am trying to boot is bzImage .I have changed the u-boot.lds file according to our system requirement(i have attach the lds file).I have changed macro BZIMAGE_LOAD_ADDR 0x100000 to 0x1000000, since my u-boot is setting at addr 0x100000. I went through the realmode_enter routine, i didn't get the point where there is jump to linux code. Can anyone guide me in this regard? Thanks, Mushtaq Khan. --------------------------------- Find out what India is talking about on - Yahoo! Answers India Send FREE SMS to your friend's mobile from Yahoo! Messenger Version 8. Get it NOW /* * (C) Copyright 2002 * Daniel Engström, Omicron Ceti AB, daniel(a)omicron.se. * * See file CREDITS for list of people who contributed to this * project. * * This program is free software; you can redistribute it and/or * modify it under the terms of the GNU General Public License as * published by the Free Software Foundation; either version 2 of * the License, or (at your option) any later version. * * This program is distributed in the hope that it will be useful, * but WITHOUT ANY WARRANTY; without even the implied warranty of * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the * GNU General Public License for more details. * * You should have received a copy of the GNU General Public License * along with this program; if not, write to the Free Software * Foundation, Inc., 59 Temple Place, Suite 330, Boston, * MA 02111-1307 USA */ OUTPUT_FORMAT("elf32-i386", "elf32-i386", "elf32-i386") OUTPUT_ARCH(i386) ENTRY(_start) SECTIONS { /* AMI's boot code copies 0xfff80000-0xfff9ffff to 0x40000-0x5ffff. It puts CS to 0x4000 and jumps to real mode at 0x40000 (= 0x4000:0000). Therefore, so as far as this script goes, it thinks LOADADDR starts at 0x40000. */ /* 16 bit */ /* Only the offset of IP here. CS=0x4000 */ . = 0x0000; .start16 : AT(0x40000) { *(.start16); } .realmode 0x7c0 : AT( LOADADDR(.start16) + SIZEOF(.start16) ) { *(.realmode) } /* check this */ _i386boot_realmode = LOADADDR(.realmode); _i386boot_realmode_size = SIZEOF(.realmode); .bios : AT ( LOADADDR(.realmode) + SIZEOF(.realmode) ) { *(.bios) } /* not needed ?*/ _i386boot_bios = LOADADDR(.bios); _i386boot_bios_size = SIZEOF(.bios); /* . = 0xfff0; */ /*check this*/ .reset : AT ( LOADADDR(.bios) + SIZEOF(.bios) ) { *(.reset); } _i386boot_end = (LOADADDR(.reset) + SIZEOF(.reset) ); /* 32 bit */ /* Assumption: ROM image above is < 4K. */ /* The VMA below has to matche the #define TEXTBASE in config.mk*/ . = 0x00041000; .text : { *(.text); } .rodata ALIGN(4) : { *(.rodata) *(.rodata.str1.1) *(.rodata.str1.32) } _i386boot_romdata_dest = ABSOLUTE(.); .data : { *(.data) } _i386boot_romdata_start = LOADADDR(.data); .got ALIGN(4) : { *(.got) } _i386boot_romdata_size = SIZEOF(.data) + SIZEOF(.got); __u_boot_cmd_start = .; .u_boot_cmd ALIGN(4) : { *(.u_boot_cmd) } __u_boot_cmd_end = .; .start32 ALIGN(4) : { *(.start32); } _i386boot_bss_start = ABSOLUTE(.); .bss ALIGN(4) : { * (.bss) } .atp_load_space ALIGN(0x10000) (NOLOAD) : {* (.atp_load_space)} _i386boot_bss_end = .; _i386boot_bss_size = _i386boot_bss_end - _i386boot_bss_start; }

1 0

[U-Boot-Users] 2Gbits NAND flash
by Srinivasa Hebbar 06 Oct '06

06 Oct '06

Hello, I am using the latest u-boot (1.1.4) code and it doesn't have 2Gbits (256 MBytes) NAND flash support. I appreciate if some one can point me in the right direction to use the 2Gbits NAND flash from U-boot. (Chip: Micron MT29F2Gxxxxx) I want to boot the linux kernel from the NAND flash. Thanks, Hebbar.

4 3

Re: [U-Boot-Users] [DNX#2006100642000014] Hi
by U-Boot patch tracking system 06 Oct '06

06 Oct '06

Dear Mr. U. Boot, thank you for your contribution to the U-Boot project. Your e-mail was registered at our system under the ticket number [DNX#2006100642000014]. Please keep this ticket ID string in the subject line of any e-mail replies!!! Your U-Boot support team Powered by OTRS (http://otrs.org/)

1 0