July 2005 - U-Boot

[U-Boot-Users] (no subject)
by prabhu 20 Jul '05

20 Jul '05

1 0

[U-Boot-Users] CF 5282 fec.c
by Zachary Landau 20 Jul '05

20 Jul '05

> I'm new on U-Boot and work on a MCF5282 port. I have modify the cvs > source and U-Boot runs on my own MCF5282 board (I get a promt on serial > line). But i get "Tx not ready" and "Tx Timeout" messages for each > ethernet access. > I discover the fec.c, and find out that only 10MBit haft duplex is use. > Is there in implementation for full 100MBit use? Jens, Search the mailing list archives. There are multiple posts about 5282 ports, and some specifically about the fec. -- Zachary P. Landau <kapheine(a)gmail.com>

2 1

[U-Boot-Users] starting an initrd
by Greg Lindberg 20 Jul '05

20 Jul '05

I realize that this may be off-topic here, but I'm hoping that someone has some insight that will help me to figure out what the problem is. I'm running u-boot on a PXA255 based board, I've loaded u-boot in ram at 0xa1500000, the Linux kernel at 0xa0100000, compiled for 0xc0010000 (phy ram addresses get mapped from 0xa0000000 to 0xc0000000), and the ramdisk at 0xa1600000 to moved to 0xa1800000. I haven't tried to set up an environment yet, the board I'm working on is a temporary development board and that portion is going to change on the final board. The bootm command defaults to: bootm 0xa0100000 0xa1600000 Also, here is the command line that I'm passing to the Linux kernel: console=ttyS0,38400 initrd=0xa1800000,4096k root=/dev/ram init=/bin/sh Here is the output from running u-boot: U-Boot 1.1.3 (Jul 19 2005 - 10:37:00) U-Boot code: A1500000 -> A1513E40 BSS: -> A1515894 RAM Configuration: Bank #0: a0000000 32 MB Bank #1: a4000000 0 kB Bank #2: a8000000 0 kB Bank #3: ac000000 0 kB Flash: 32 MB *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Hit any key to stop autoboot: 0 ## Booting image at a0100000 ... Image Name: ARM-Linux-2.6 Image Type: ARM Linux Kernel Image (gzip compressed) Data Size: 662900 Bytes = 647.4 kB Load Address: a0010000 Entry Point: a0010000 Verifying Checksum ... OK Uncompressing GZip'd Kernel Image ... OK ## Loading Ramdisk Image at a1600000 ... Image Name: ARM-Linux-2.6.initrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 1000261 Bytes = 976.8 kB Load Address: a1800000 Entry Point: a1800000 Verifying Checksum ... OK Starting kernel ... Linux version 2.6.12-RC4-InHand2 (greg@rh9dev) (gcc version 3.3.4) #62 Tue Jul 19 10:42:15 PDT 2005 CPU: XScale-PXA255 [69052d06] revision 6 (ARMv5TE) CPU0: D VIVT undefined 5 cache CPU0: I cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets CPU0: D cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets Machine: InHand Electronics Fingertip3 initrd (0xa1800000 - 0xa1c00000) extends beyond physical memory - disabling initrd Memory policy: ECC disabled, Data cache writeback Memory clock: 99.53MHz (*27) Run Mode clock: 199.07MHz (*2) Turbo Mode clock: 199.07MHz (*1.0, inactive) Built 1 zonelists Kernel command line: console=ttyS0,38400 initrd=0xa1800000,4096k root=/dev/ram init=/bin/sh PID hash table entries: 128 (order: 7, 2048 bytes) Console: colour dummy device 80x30 Dentry cache hash table entries: 4096 (order: 2, 16384 bytes) Inode-cache hash table entries: 2048 (order: 1, 8192 bytes) Memory: 16MB = 16MB total Memory: 14720KB available (1110K code, 277K data, 68K init) Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok Linux NoNET1.0 for Linux 2.6 JFFS2 version 2.2. (NAND) (C) 2001-2003 Red Hat, Inc. JFFS2: default compression mode: priority ttyS0 at MMIO 0x40100000 (irq = 15) is a FFUART ttyS1 at MMIO 0x40200000 (irq = 14) is a BTUART ttyS2 at MMIO 0x40700000 (irq = 13) is a STUART io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered RAMDISK driver initialized: 4 RAM disks of 4096K size 1024 blocksize physmap flash device: 2000000 at 0 phys_mapped_flash: Found 1 x16 devices at 0x0 in 16-bit bank Intel/Sharp Extended Query Table at 0x0031 Using buffer write method cfi_cmdset_0001: Erase suspend on write enabled RedBoot partition parsing not available mtd: Giving out device 0 to phys_mapped_flash mice: PS/2 mouse device common for all mice i2c /dev entries driver Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0) Any help anyone can give me to point out to me what is happening and/or what I'm doing wrong would be greatly appreciated. Greg Wilson-Lindberg

2 2

[U-Boot-Users] Kernel Panic
by Will Haines 19 Jul '05

19 Jul '05

I am currently trying to boot an kernel with inital ramdisk using u-boot on an EP885C, but I am running into the following problem when I try to boot the kernel: Linux version 2.4.22 (wdhaine@prod-pci) (gcc version 3.3.3) #1 Mon Jul 18 12:45:35 EDT 2005 On node 0 totalpages: 16384 zone(0): 16384 pages. zone(1): 0 pages. zone(2): 0 pages. Kernel command line: console=ttyS0,9600 console=ttyS0 root=/dev/ram0 init=/linuxrc rw ... RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize loop: loaded (max 8 devices) ... RAMDISK: Compressed image found at block 0 Freeing initrd memory: 466k freed Kernel panic: VFS: Unable to mount root fs on 01:00 I would think that this is purely a kernel problem; however, it did not crop up until I started using u-boot. As shown above, I have ramdisk support built into the kernel, and I am passing it a root device in the kernel command line, so this doesn't seem to be an FAQ type of problem. In order to get the kernel to run, I had to copy the ppcboot.h bd_t struct into my linux port and change the IMAP_ADDR to get the kernel to boot. I am thinking that somehow the bd_t struct changes could make the it impossible to use /dev/ram0 correctly. Other than that, I am stumped. Any help would be greatly apprectiated. Will Haines

4 9

Re: [U-Boot-Users] 2.6.12 with u-boot-1.1.2 on versatile
by Peter Pearse 19 Jul '05

19 Jul '05

Wolfgang Denk wrote: > In message <20050719073213.49786.qmail(a)web30712.mail.mud.yahoo.com> > you wrote: >> >> Thanks to Wolfgang Denk, Catalin Marinas, and Peter Pearse, I now >> have >> 2.6.12-rmk1 running with base.cramfs on the PB-ARM926EJ-S. The >> following documentation is for reference: > ... >> 4. Copy the uImage from flash to SDRAM: >> >> cp 0xbbccddee 0x7fc0 0x123456 > ... >> 6. Bootup >> >> bootm 0x7fc0 > > The "cp" step (4.) is redundant. Instead, just type "bootm > 0xbbccddee". > Not on Versatile, where we have not yet implemented CONFIG_HAS_DATAFLASH correctly. At present one must copy the kernel image into the load address before using bootm. I have this on my list of patches to make.... Peter

1 0

[U-Boot-Users] SDRAM initialization sequence!
by junping feng 19 Jul '05

19 Jul '05

Hi,I have a little problem with the uboot startup,the BDI2000 can program u-boot.bin into FLASH .My board is like the board MPC8260ADS.CPU is ppc8250. Board information can print through serial interface after the first initialization of board now. But when it run to the function relocate_code(in the /cpu/mpc8260/start.s),it don't run continually. Through LED on the board ,I find that it stops at the code below: in_ram: My SDRAM is samsang k4s643232f-tc60, total 16MBytes,two chips.Each is organzied as 4*512K*32bits. The link address is the SDRAM data sheet! http://www.samsung.com/Products/Semiconductor/DRAM/SDRAM/SDRAMcomponent/64M… Please check whether my SDRAM initialization sequence is correct! Thanks in advance! /* init sdram dimm */ printf("Now init 60x sdram dimm ...\n"); ramaddr = (uchar *)CFG_SDRAM_BASE; memctl->memc_mptpr = 0x1900; memctl->memc_psrt = 0x10; immap->im_memctl.memc_or2 = 0xFF003080; immap->im_memctl.memc_br2 = 0x00000041; memctl->memc_psdmr = 0x2869a452; *ramaddr = c; memctl->memc_psdmr = 0x0869a452; for (i = 0; i < 8; i++) *ramaddr = c; memctl->memc_psdmr = 0x1869a452; *ramaddr = c; memctl->memc_psdmr = 0x4069a452; *ramaddr = c; __________________________________________________ 赶快注册雅虎超大容量免费邮箱? http://cn.mail.yahoo.com

2 1

[U-Boot-Users] Mac Address communication to Linux
by Stage Iup - Fabrice & Frederic 19 Jul '05

19 Jul '05

Hi all i'm wondering something, i don't understand how can U-Boot communicate to an Embedded Linux. Can someone explain it to me please? -- With regards Frédéric Kwiatkowski -- IFOTEC Tél : 04 76 67 53 53

2 3

RE: [U-Boot-Users] 2.6.12 with u-boot-1.1.2 on versatile
by Shakthi Kannan 19 Jul '05

19 Jul '05

Hi, Thanks for your replies Peter Pearse and Catalin Marinas. 1. --- Peter Pearse <Peter.Pearse(a)arm.com> wrote: > I use > > <U-Boot dir>/tools/mkimage -A arm -O linux -T kernel > -C none -a 0x7fc0 > -e 0x8000 -n u-linux -d <Kernel dir>/arch/arm/Image > u-linux Worked like a charm! I then had to copy the kernel to SDRAM 0x7fc0 and boot it using: cp 0x36000000 0x7fc0 <kernel_size> bootm 0x7fc0 2. I then tried to use the base.cramfs filesystem provided in arm.com: http://www.arm.com/linux/linux_download.html I used mkimage to append a header and flashed it at 0x36200000. Copied the same to SDRAM, 0x04000000. I changed the bootargs values using setenv, but, was not sure as to what values I need to give. setenv bootargs root=/dev/mtdblock0 mtdparts=versatile:0x65d050@0x04000000(cramfs) ip=none mem=128M console=ttyAMA0 video=vc:1-2clcdfb: I then tried to boot the kernel with the ramdisk: bootm 0x7fc0 0x04000000 I got the following output: http://www.shakthimaan.com/downloads/session.log Why is it trying the floppy? Is it trying the external memory card? I did check the boot log to the 2.4.19-rmk6 kernel provided in the NOR flash, and it loaded ramdisk drivers etc. I have used the config-versatile-pb file as provided in arm.com site, which does not have support for ramdisk by default. I did try enabling ramdisk support, but, I ended up with the same output as above. The ramdisk by default is 4 MB in the kernel, but base.cramfs given in arm.com is 6 MB. I even tried changing the ramdisk size in kernel CONFIG to 8 MB, but, no change in the output. I'd appreciate any feedback for the above, and any help in getting the filesystem mounted, so I can start playing with the shell. Board: Versatile-PB-ARM926EJ-S Cross_compiler: 3.4.3 Kernel: 2.6.12 Thanks again for your help, K Shakthi -- proudly anti-micro$oft ------------------------------------------------------------ Shakthi Kannan, MS Software Engineer, Specsoft (Hexaware Technologies) [E]: shaks(a)shakthimaan.com [M]: (91) 98407-87007 [W]: http://www.shakthimaan.com [L]: Chennai, India ------------------------------------------------------------ ____________________________________________________ Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs

2 3

[U-Boot-Users] Undelivered Mail Returned to Sender
by MAILER-DAEMON＠glw.com 19 Jul '05

19 Jul '05

This is the Postfix program at host mail.glw.com. I'm sorry to have to inform you that the message returned below could not be delivered to one or more destinations. For further assistance, please send mail to <postmaster> If you do so, please include this problem report. You can delete your own text from the message returned below. The Postfix program <".aarons"@glw.com>: host public/lmtp[public/lmtp] said: 550-Mailbox unknown. Either there is no mailbox associated with this 550-name or you do not have authorization to see it. 550 5.1.1 User unknown

1 0

[U-Boot-Users] flash erase problem for Intel TE28F640J3C
by me 19 Jul '05

19 Jul '05

Hi, I have a ATMEL AT91RM9200 board with u-boot 1.1.2 and Intel TE28F640J3C flash. I can burn u-boot image to flash when the board is booted from internal ROM. But I can't erase sector 1 of the flash when it is booted from external flash. Strangely, other sectors can be erased sucessfully expect the sector 1 which u-boot image will be located. I am sure that I unportect the sector 1 and I still get an erase timeout. BTW, I use CFI driver for Intel flash. Someone, can give me some light ?? Eric 憟單祥蝬脰楝餉店隞颱

1 0