March 2006 - U-Boot

[U-Boot-Users] does someone add YAFFS2 support in uboot?
by zhuzhenhua 06 Mar '06

06 Mar '06

i want to boot the kernel under the dir /boot/ of a yaffs2 filesystem, does someone succeed on it? thanks for any hints. Best Regards zhuzhenhua

3 5

[U-Boot-Users] Re: IMPORTANT NOTE to all maintainers with NAND flash and DoC
by Wolfgang Denk 06 Mar '06

06 Mar '06

Hello, this is a "heads up" note to all maintainers of boards with NAND flash and Disk-on-Chip support: As mentioned before, we merged the "testing-NAND" branch back in to the main tree, with the intention to drop support for the old NAND flash code ASAP. Quote from doc/README.nand: We now use a complete rewrite of the NAND code based on what is in 2.6.12 Linux kernel. The old NAND handling code has been re-factored and is now confined to only board-specific files and - unfortunately - to the DoC code (see below). A new configuration variable has been introduced: CFG_NAND_LEGACY, which has to be defined in the board config file if that board uses legacy code. If CFG_NAND_LEGACY is defined, the board specific config.mk file should also have "BOARDLIBS = drivers/nand_legacy/libnand_legacy.a". For boards using the new NAND approach (PPChameleon and netstar at the moment) no variable is necessary, but the config.mk should have "BOARDLIBS = drivers/nand/libnand.a". The necessary changes have been made to all affected boards, and no build breakage has been introduced, except for NETTA and NETTA_ISDN targets from MAKEALL. This is due to the fact that these two boards use JFFS, which has been adopted to use the new NAND, and at the same time use NAND in legacy mode. The breakage will disappear when the board-specific code is changed to the new NAND. As mentioned above, the legacy code is still used by the DoC subsystem. The consequence of this is that the legacy NAND can't be removed from the tree until the DoC is ported to use the new NAND support (or boards with DoC will break). Best regards, Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd(a)denx.de A Chairman was as necessary to a Board planet as the zero was in mathematics, but being a zero had big disadvantages... - Terry Pratchett, _The Dark Side of the Sun_

1 0

[U-Boot-Users] Uboot image size reduction
by Vijayakumar 06 Mar '06

06 Mar '06

Hi all, I am trying to build a uboot image of size 90k. My full image having all the functionality has a size of 169k. Till now i am able to reduce its size to 106k. Things i did to reduce it to 106k are -- disabled all the commands except (loadb,saveenv,setenv,help,printenv,protect) which are not used to load the kernel image. -- disabled the longhelp macro. Is there any possibility to compress some parts of uboot and decompress into the memory when needed? Also i am open to any suggestions which can help me to redue the image size close to 90k Thanks in advance. Vijayakumar

2 1

[U-Boot-Users] Patch queue outlook?
by bbosch＠iphase.com 03 Mar '06

03 Mar '06

Wolfgang, I see there has been some promising commit activity in your U-Boot git tree over the past couple of weeks, tho it is not always clear to me what drives the choice of patches being applied. I know you are very busy [answering silly questions among other things, judging by traffic on this list :-) ] and I'm sure we all greatly appreciate your constant help and leadership, but... Can you give us some statistics on the state of your patch queue and perhaps an idea about when you might get to the bulk of the patches submitted during the last quarter of last year (and earlier)? If you don't reject a patch immediately on submission is it likely it will be committed some day? Should I wait to submit patches which depend on patches already submitted by others or just assume the previous patches will be committed eventually? Thanks! --Brad Bosch

2 1

[U-Boot-Users] Squashfs
by Brian Johnson 02 Mar '06

02 Mar '06

Just getting started with this stuff so I hope I don't ask too many newbie questions I've read that squashfs is supposed to be an improvement over cramfs but I couldn't find any info about squashfs in the terrific U-Boot info at http://www.denx.de/wiki/view/DULG Is it basically the same setup as for a cramfs root? How would it rank in the table shown at http://www.denx.de/wiki/view/DULG/RootFileSystemSelection ?

3 2

[U-Boot-Users] Target hangs during relocate_code() call
by Rick Nardone 02 Mar '06

02 Mar '06

Target: SBC8540 - Wind River Systems Arch: PPC CPU: MPC85xx Board: sbc8560 ELDK 4.0 Host: SUSE Linux 9.3 on x86 U-Boot 1.1.4 Problem: I am trying to get a clean build of U-Boot to run on the WRS SBC8540 board. I think I have the latest versions of ELDK and U-Boot. The system executes through board_init_f( ) without any problems, but never gets into board_init_r( ). The console output is as follows: U-Boot 1.1.4 (Mar 2 2006 - 10:27:01) CPU: 8540, Version: 1.0, (0x80300010) Core: E500, Version: 1.0, (0x80200010) Clock Configuration: CPU: 396 MHz, CCB: 132 MHz, DDR: 66 MHz, LBC: 66 MHz L1: D-cache 32 kB enabled I-cache 32 kB enabled Board: Wind River SBC8540 Board CPU: 396 MHz CCB: 132 MHz DDR: 66 MHz LBC: 66 MHz CPM: 132 Mhz L1 D-cache 32KB, L1 I-cache 32KB enabled. I2C: ready DRAM: 512 MB RN Testing 1 Top of RAM usable for U-Boot at: 20000000 Reserving 163k for U-Boot at: 1ffd0000 Reserving 136k for malloc() at: 1ffae000 Reserving 88 Bytes for Board Info at: 1ffadfa8 Reserving 72 Bytes for Global Data at: 1ffadf60 Stack Pointer at: 1ffadf48 New Stack Pointer is: 1ffadf48 Memcpy call to relocate_code() Dest Addr =0x1FFADF48, Src Addr = 0x1FFADF60, size = 536674304 bytes I am a U-Boot newbie. Any diagnostic suggestions are appreciated. Thanks in advance, Richard Nardone Richard.Nardone at cyclone dot com

4 3

[U-Boot-Users] New Board and New CPU
by CoDeBrEaKeR 02 Mar '06

02 Mar '06

i have a new board and new CPU to be ported to U Boot. since this is completely new to me, i wish i cud get some help from the ppl here. first of all i need to know what are the necessary information that i have to gather regarding the board and the cpu. second, as far as i have the information, the CPU that i have matches m68k. third, since the board is designed in house, i am not sure which ref code to use for the development. pls do need me the inputs so that i can get back with the necessary information for further development. thanks --------------------------------- Brings words and photos together (easily) with PhotoMail - it's free and works with Yahoo! Mail.

2 1

RE: [U-Boot-Users] cfi_flash.c
by Spinelli, Claudio (Claudio) 02 Mar '06

02 Mar '06

Hi Wolfgang, Yes, I should have been more specific. How do you find out if a flash is compatible with CFI interface? I have: AMD AM29F040 28F256J3C Do you know if the above flashes are compatible with CFI? Thanks Claudio -----Original Message----- From: wd(a)denx.de To: claudio123 Cc: u-boot-users(a)lists.sourceforge.net Sent: 3/1/06 2:54 AM Subject: Re: [U-Boot-Users] cfi_flash.c In message <3176526.post(a)talk.nabble.com> you wrote: > > I am looking for a flash driver that would work with both the new flash part > (J3D)supported by cfi_flash.c and the old flash (28F256J3C), or better yet a > driver that would support the flash parts supported by new cfi_flash .c as > well as the old parts supported by flash.c and flash64.c You should be a bit more specific. Which "flash.c"? There are nearly 200 files by that name in the U-Boot tree! In general, you should use the CFI driver and fix any problems / add any code that might be missing there. Best regards, Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd(a)denx.de They weren't that important. They were merely at the top. The people who really run organizations are usually found several levels down, where it's still possible to get things done. - Terry Pratchett, _Small Gods_

3 2

[U-Boot-Users] Re: transferring control to linux
by Josef Angermeier 02 Mar '06

02 Mar '06

> Hi all, Hello > we are porting u-boot/linux to a custom board based on mpc8280. > After having made u-boot-1.1.4 work, we tried booting some > test-configured linux 2.6.15 kernels. > If we start u-boot using Trace32 (lauterbach) all goes well and linux > gets loaded, but if we do the same steps disconnecting Trace32, u-boot > seems to work properly, but as soon as the control is transferred to > linux all seems to be hanged, and the last words visible on the serial are: > [...] > ## Loading RAMDisk Image at 00400000 ... > Image Name: Test Ramdisk Image > Image Type: PowerPC Linux RAMDisk Image (gzip compressed) > Data Size: 1374924 Bytes = 1.3 MB > Load Address: 00000000 > Entry Point: 00000000 > Verifying Checksum ... OK > ## initrd at 0x00400040 ... 0x0054FB0B (len=1374924=0x14FACC) > Loading Ramdisk to 07e4e000, end 07f9dacc ... OK > ## Transferring control to Linux (at address 00000000) ... > We are wondering if this is an issue involving u-boot or if this is > related to linux config (in this case sorry for being off-topic). Had the same problem. Make sure your board-specific include defines the correct IMMR-address etc. and the bd_info structure is the same in u-boot and in linux. After having checked that you should compile a minimal kernel, check the logbuffer for output (see DENX FAQ) and debug the kernel. In my case it hang in some console output function so that i had to fix the serial debug output the same way i had to fix u-boot before. Then the kernel just worked great :-) > Thanks for any help!! > Ciao, > Alberto ciao josef

1 0

RE: Need help with IDE/PCI config on unknown board(was: [U-Boot-Users] (no subject))
by Jerry K. Schieffer 02 Mar '06

02 Mar '06

Thank you for your help. In answer to your questions: >>>Can you "see" the PCI IDE controller at this address? What's the output of: >>>=> md.b e80001f0 10 I believe not because => md.b e8000000 10 e8000000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ >>>What's the output of: >>>=> pci long => pci long Scanning PCI devices on bus 0 Found PCI device 00.00.00: vendor ID = 0x1014 device ID = 0x0156 command register = 0x0006 status register = 0x2210 revision ID = 0x01 class code = 0x06 (Bridge device) sub class code = 0x00 programming interface = 0x00 cache line = 0x00 latency time = 0x07 header type = 0x00 BIST = 0x00 base address 0 = 0x00000000 base address 1 = 0x00000008 base address 2 = 0x00000000 base address 3 = 0x00000000 base address 4 = 0x00000000 base address 5 = 0x00000000 cardBus CIS pointer = 0x00000000 sub system vendor ID = 0x10e8 sub system ID = 0xcafe expansion ROM base address = 0x00000000 interrupt line = 0x00 interrupt pin = 0x01 min Grant = 0x00 max Latency = 0x00 Found PCI device 00.04.00: vendor ID = 0x105a device ID = 0x0d30 command register = 0x0004 status register = 0x0210 revision ID = 0x02 class code = 0x01 (Mass storage controller) sub class code = 0x01 programming interface = 0x8a cache line = 0x00 latency time = 0x40 header type = 0x00 BIST = 0x00 base address 0 = 0x000001f1 base address 1 = 0x000003f5 base address 2 = 0x00000171 base address 3 = 0x00000375 base address 4 = 0x00006801 base address 5 = 0x00000000 cardBus CIS pointer = 0x00000000 sub system vendor ID = 0x105a sub system ID = 0x4d33 expansion ROM base address = 0x000dc000 interrupt line = 0x1d interrupt pin = 0x01 min Grant = 0x00 max Latency = 0x00 => I suppose that the oxFF bytes are not correct for the contents of the ide controller registers. What should I look for? I used 0xE8000000 (apparently incorrectly) because it was reported in the following messages when initializing with the PPBBoot firmware: PCI_Scan:Device 4 is present Bus Func 2000 ClassCode 101 IDE device found: PCI_Config_Device:Read Base Addr Reg 0 = 0x000001f1 ***PCI I/O space = 0x10 bytes 0 IDE-Just Set CFG_ATA_BASE_ADDR to e8000000^M PCI_Config_Device:Read Base Addr Reg 1 = 0x000003f5 ***PCI I/O space = 0x4 bytes 10 PCI_Config_Device:Read Base Addr Reg 2 = 0x00000171 ***PCI I/O space = 0x10 bytes 20 PCI_Config_Device:Read Base Addr Reg 3 = 0x00000375 ***PCI I/O space = 0x4 bytes 30 PCI_Config_Device:Read Base Addr Reg 4 = 0xffffffc1 ***PCI I/O space = 0x40 bytes 40 PCI_Config_Device:Read Base Addr Reg 5 = 0xfffe0000 ***PCI Memory space = 0x20000 bytes Hardcode address e80001f0 >>>PS: Please use a subject next time! Done - see subject.

2 1