Re: [U-Boot-Users] Replacing AT91 u-boot
Sorry, I missed this. Remove the initrd= and mem= part. U-Boot passes correct ATAGS to the kernel.
Thank you again. I followed your suggestions:
U-Boot> printenv bootdelay=3 baudrate=115200 ethaddr=00:02:a5:6e:3f:fd filesize=3638c0 fileaddr=21140000 netmask=255.255.255.0 ipaddr=192.168.0.184 serverip=192.168.0.11 bootargs=root=/dev/ram rw ramdisk_size=15360 console=ttyS0,115200 stdin=serial stdout=serial stderr=serial
U-Boot> tftp 21100000 ramdisk TFTP from server 192.168.0.11; our IP address is 192.168.0.184 Filename 'ramdisk'. Load address: 0x21100000 Loading: ### .snip. ######## done Bytes transferred = 3553472 (3638c0 hex)
U-Boot> tftp 21000000 uImage TFTP from server 192.168.0.11; our IP address is 192.168.0.184 Filename 'uImage'. Load address: 0x21000000 Loading: ############################################## ####################################### done Bytes transferred = 646841 (9deb9 hex)
U-Boot> bootm ## Booting image at 21000000 ... Image Name: Image Type: ARM Linux Kernel Image (gzip compressed) Data Size: 646777 Bytes = 631.6 kB Load Address: 20008000 Entry Point: 20008000 Verifying Checksum ... OK Uncompressing Kernel Image ...
[here is still freezed]
Every test I do I'm more confused. Please apologize my question, but did you ever used an AT91RM9200DK board with u-boot (reading help and your site seems that you are a PPC expert but there is no examples using AT91) ? Why Atmel give out and say to use boot.bin as pre-bootloader and you say not ? Why the u-boot-1.1.3 default configuration for this board don't work ? Maybe there is something missing or wrong ? TIA
In message INQMN6$BA1EA9D7C1AEB9F5F48178400D2F533D@libero.it you wrote:
Every test I do I'm more confused. Please apologize my question, but did you ever used an AT91RM9200DK board with u-boot (reading help and your site seems that you are a PPC expert but there is no examples using AT91) ?
My own ARM knowledge is indeed limited, but there are other engineers in our team who know exactly what they are doing; DENX supports PowerPC, ARM and MIPS.
And yes, I did. Here is an example (not exactly the AT91RM9200DK board but the CMC_PU2, but there is no difference between these two boards relevant to this discussion):
U-Boot 1.1.3 (Apr 6 2005 - 15:40:24)
U-Boot code: 20F00000 -> 20F18A38 BSS: -> 20F1D23C RAM Configuration: Bank #0: 20000000 16 MB Board: CMC-PU2 (Rittal GmbH) Flash: 8 MB In: serial Out: serial Err: serial ... => tftp 20800000 /tftpboot/cmcpu2/uImage TFTP from server 192.168.1.1; our IP address is 192.168.20.1 Filename '/tftpboot/cmcpu2/uImage'. Load address: 0x20800000 Loading: ################################################################# ################################################################# ######## done Bytes transferred = 702805 (ab955 hex) => tftp 20900000 /tftpboot/cmcpu2/uRamdisk TFTP from server 192.168.1.1; our IP address is 192.168.20.1 Filename '/tftpboot/cmcpu2/uRamdisk'. Load address: 0x20900000 Loading: ################################################################# ################################################################# ################################################################# ################################################################# ################################## done Bytes transferred = 1502281 (16ec49 hex) => print bootargs bootargs=root=/dev/ram rw ip=192.168.20.1:192.168.1.1:192.168.1.254:255.255.0.0:cmcpu2:eth0:off panic=1 => bootm 20800000 20900000 ## Booting image at 20800000 ... Image Name: ARM Linux-2.4.27 Created: 2005-07-11 15:13:23 UTC Image Type: ARM Linux Kernel Image (gzip compressed) Data Size: 702741 Bytes = 686.3 kB Load Address: 20008000 Entry Point: 20008000 Verifying Checksum ... OK Uncompressing Kernel Image ... OK ## Loading Ramdisk Image at 20900000 ... Image Name: Simple Embedded Linux Framework Created: 2004-11-10 0:35:20 UTC Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 1502217 Bytes = 1.4 MB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK
Starting kernel ...
Linux version 2.4.27-vrs1-mk1 (mk@pollux) (gcc version 3.3.3 (DENX ELDK 3.1.1 3.3.3-9)) #1 Mon Jul 11 17:10:44 MEST 2005 CPU: Arm920Tid(wb) revision 0 Machine: ATMEL AT91RM9200 On node 0 totalpages: 4096 zone(0): 4096 pages. zone(1): 0 pages. zone(2): 0 pages. Kernel command line: root=/dev/ram rw ip=192.168.20.1:192.168.1.1:192.168.1.254:255.255.0.0:cmcpu2:eth0:off panic=1 Calibrating delay loop... 34.50 BogoMIPS Memory: 16MB = 16MB total Memory: 13068KB available (1299K code, 277K data, 56K init) Dentry cache hash table entries: 2048 (order: 2, 16384 bytes) Inode cache hash table entries: 1024 (order: 1, 8192 bytes) Mount cache hash table entries: 512 (order: 0, 4096 bytes) Buffer cache hash table entries: 1024 (order: 0, 4096 bytes) Page-cache hash table entries: 4096 (order: 2, 16384 bytes) CPU: Testing write buffer: pass POSIX conformance testing by UNIFIX Linux NET4.0 for Linux 2.4 Based upon Swansea University Computer Society NET3.039 Initializing RT netlink socket Starting kswapd Installing knfsd (copyright (C) 1996 okir@monad.swb.de). JFFS2 version 2.1. (C) 2001 Red Hat, Inc., designed by Axis Communications AB. RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize Amd/Fujitsu Extended Query Table v1.3 at 0x0040 number of CFI chips: 1 cfi_cmdset_0002: Disabling fast programming due to code brokenness. Creating 5 MTD partitions on "CMC PU2 flash": 0x00000000-0x00020000 : "Firmware" 0x00020000-0x00030000 : "Environment" 0x00030000-0x000f0000 : "Kernel" 0x000f0000-0x00780000 : "Filesystem 1" 0x00780000-0x00800000 : "Filesystem 2" i2c-core.o: i2c core module version 2.6.1 (20010830) i2c-dev.o: i2c /dev entries driver module version 2.6.1 (20010830) ttyS0 at MMIO 0xfefc0000 (irq = 6) is a AT91_SERIAL ttyS1 at MMIO 0xfefc4000 (irq = 7) is a AT91_SERIAL ttyS2 at MMIO 0xfefc8000 (irq = 8) is a AT91_SERIAL ttyS3 at MMIO 0xfefcc000 (irq = 9) is a AT91_SERIAL ttyS4 at MMIO 0xfefff200 (irq = 1) is a AT91_SERIAL eth0: Link now 100-FullDuplex eth0: AT91 ethernet at 0xfefbc000 int=24 100-FullDuplex (f6:70:1d:61:b5:9d) eth0: Davicom 9196 PHY (Copper) AT91 Watchdog Timer enabled (5 seconds) Found AT91 i2c I2C: RS5C372 RTC driver successfully loaded CMC buzzer driver $Revision: 0.2 $ CMC digital IO driver $Revision: 0.2 $ Serial driver version 0.03 (2004-12-17) with no serial options enabled ttyS5 at 0xc2084000 (irq = 29) is a TI16752 ttyS6 at 0xc2086000 (irq = 30) is a TI16752 NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP IP: routing cache hash table of 512 buckets, 4Kbytes TCP: Hash tables configured (established 1024 bind 2048) eth0: Link now 100-FullDuplex IP-Config: Complete: device=eth0, addr=192.168.20.1, mask=255.255.0.0, gw=192.168.1.254, host=cmcpu2, domain=, nis-domain=(none), bootserver=192.168.1.1, rootserver=192.168.1.1, rootpath= NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. NetWinder Floating Point Emulator V0.97 (double precision) RAMDISK: Compressed image found at block 0 Freeing initrd memory: 1467K VFS: Mounted root (ext2 filesystem). Freeing init memory: 56K
BusyBox v0.60.5 (2004.11.10-00:31+0000) Built-in shell (msh) Enter 'help' for a list of built-in commands.
# cat /proc/cpuinfo Processor : Arm920Tid(wb) rev 0 (v4l) BogoMIPS : 34.50 Features : swp half thumb
Hardware : ATMEL AT91RM9200 Revision : 0000 Serial : 0000000000000000 #
Why Atmel give out and say to use boot.bin as pre-bootloader and you say not ?
There are several reasons. For example, Atmel supports booting from dataflash, too, where a minimal bootstrap loader is necessary.
Why the u-boot-1.1.3 default configuration for this board don't work ?
Why do you think so? From your postings it's clear that U-Boot works - you can even load and start your kernel. It's just that your Linux kernel is not working.
Maybe there is something missing or wrong ?
Seems to be some problem with your kernel. Check the typical problems on ARM systems, like if you're using a correct machine ID. Attach a debugger and check where the kernel is hanging, and why. Etc. But this actually is off topic here as it is unrelated to U-Boot.
The messages you showed make it clear that U-Boot *is* running fine on your board.
Best regards,
Wolfgang Denk
participants (2)
-
kentropy -
Wolfgang Denk