Hello,

I would like to boot the OMAP5912 board from u-boot. Memory layout is : FLASH : Starts from 0x0000 0000 (32MB) SDRAM: 0x1000 0000 to 0x1200 0000 (32 MB)

I used the kernel Image with DHCP Support = ON.

I copied the uImage at 0x0001 0000 and uRamdisk at 0x0010 0000

*********************LOG***************************** OMAP5912 OSK # tftp 10000000 uImage OMAP5912 OSK # cp.b 10000000 100000 b67e4 OMAP5912 OSK # imi 100000 ## Checking Image at 00100000 ... Image Name: Linux-2.4.20_mvl31-omap5912_osk Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 747428 Bytes = 729.9 kB Load Address: 10008000 Entry Point: 10008000 Verifying Checksum ... OK

OMAP5912 OSK # tftp 10000000 uRamdisk OMAP5912 OSK # cp.b 10000000 1000000 16f4eb OMAP5912 OSK # imi 1000000 ## Checking Image at 01000000 ... Image Name: Test Ramdisk Image Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 1504427 Bytes = 1.4 MB Load Address: 11000000 Entry Point: 11000000 Verifying Checksum ... OK

OMAP5912 OSK # setenv bootargs mem=32M console=ttyS0,115200n8 root=/dev/rd/0 ramdisk_start=1000000

OMAP5912 OSK # print

baudrate=115200 ethaddr=00:0E:99:02:06:7D bootdelay=10 bootfile=/tftpboot/omap/dhcp_uImage hostname=tqm stdin=serial stdout=serial stderr=serial filesize=16f4eb fileaddr=10000000 gatewayip=172.18.19.253 netmask=255.255.248.0 ipaddr=172.18.20.198 serverip=172.18.20.141 bootargs=mem=32M console=ttyS0,115200n8 root=/dev/rd/0 ramdisk_start=1000000

Environment size: 346/131068 bytes OMAP5912 OSK # bootm 100000

## Booting image at 00100000 ... Image Name: Linux-2.4.20_mvl31-omap5912_osk Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 747428 Bytes = 729.9 kB Load Address: 10008000 Entry Point: 10008000 Verifying Checksum ... OK OK

Starting kernel ...

Uncompressing Linux................................................... ...... ..... Backtrace: Function entered at [<c00c0fa8>] from [<c0049fc0>] r7 = 00000000 r6 = FFFFFFEA r5 = C03FA120 r4 = C03FA140 Function entered at [<c0049ef0>] from [<c0008ecc>] Function entered at [<c0008e68>] from [<c0009094>] r8 = 00000001 r7 = C018BD54 r6 = 00000000 r5 = C01874D4 r4 = 00000000 Function entered at [<c0009020>] from [<c001829c>] Function entered at [<c00181dc>] from [<c0018040>] r6 = C01B6728 r5 = C0176000 r4 = 00000000 Function entered at [<c001802c>] from [<c001bcac>] Code: 1a00002c e2522004 4282c004 4a00001b (e4913004) Kernel panic: Attempted to kill init!

**************************LOG END***********************************

I also tried with => setenv bootargs root=/dev/ram rw => bootm 100000 1000000 But it also does not work,

I think I made some mistake by passing the correct kernel parameter. What might be the correct bootargs value? The same uImage and uRamdisk works fine if the ramdisk image is mounted by NFS with the bootargs (setenv bootargs console=ttyS0,115200n8 noinitrd rw ip=dhcp root=/dev/nfs nfsroot=172.18.22.125:/mnt, nolock mem=30M)

What am I missing?

Now I tried with uImage without DHCP support which gives the following log

******LOG WITHOUT DHCP ************** OMAP5912 OSK # bootm 100000 1000000 ...... OMAP flash: using static partition definition Creating 5 MTD partitions on "omap-flash": 0x00000000-0x00020000 : "BootLoader" 0x00020000-0x00040000 : "Params" 0x00040000-0x00240000 : "Kernel" 0x00240000-0x01000000 : "Flash0 FileSys" 0x01000000-0x02000000 : "Flash1 FileSys" Linux Kernel Card Services 3.1.22 options: none 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 2048 bind 4096) IP-Config: Incomplete network configuration information. NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. 802.1Q VLAN Support v1.7 Ben Greear greearb@candelatech.com All bugs added by David S. Miller davem@redhat.com NetWinder Floating Point Emulator V0.95 (c) 1998-1999 Rebel.com Root-NFS: No NFS server available, giving up. VFS: Unable to mount root fs via NFS, trying floppy. VFS: Cannot open root device "nfs" or 02:00 Please append a correct "root=" boot option Kernel panic: VFS: Unable to mount root fs on 02:00 ********************END***********************

What is the general rule to set bootargs?

Batsayan Das Tata Consultancy Services Limited Mailto: batsayan.das@tcs.com Website: http://www.tcs.com

Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you