<br><font size=2 face="sans-serif">Hello</font>
<br>
<br><font size=2 face="sans-serif">I am trying to boot kernel version 2.6.9-rc1-omap1
on my OMAP P2 730 target board, but am facing problems in the kernel boot
process. I am using u-boot version 1.0.1, which has been burnt to the target's
NOR flash.</font>
<br>
<br><font size=2 face="sans-serif">u-boot 1.0.1 is up and running on the
target, and I use the command 'loadb 0x(addr)' along with triggering a
send file (protocol->kermit) on the hyperterminal to download the kernel
image 'uImage' on to the target's RAM. 'uImage' is created using a utility
'mkimage' which is created by u-boot build process. I specified the load
address & entry point as 0x10008000 while creating the uImage.</font>
<br>
<br><font size=2 face="sans-serif">I also made sure that I properly specify
the environment variables for u-boot, the most important one being 'bootargs'.
The following command was given at the u-boot prompt to specify 'bootargs'.</font>
<br>
<br><font size=2 face="sans-serif">OMAP730 P2 #<i> setenv bootargs mem=32M
console=ttyS0,115200n8 root=/dev/ram0 rw initrd=0x10400000,1M devfs=mount</i></font>
<br>
<br><font size=2 face="sans-serif">The ramdisk image was then downloaded
to the target's RAM over the serial line at the 'initrd' address - 0x10400000.
Having done everything by the book, I now issue the following command to
boot the kernel:</font>
<br>
<br><font size=2 face="sans-serif">OMAP730 P2 #<i> bootm 0x10008000 0x10400000</i></font>
<br>
<br><font size=2 face="sans-serif">The traces received on the hyperterminal
are:</font>
<br>
<br>
<br><font size=2 face="sans-serif"><i>## Booting image at 10008000 ...</i></font>
<br><font size=2 face="sans-serif"><i> Image Name: Linux-2.6.9-rc1-omap1</i></font>
<br><font size=2 face="sans-serif"><i> Image Type: ARM
Linux Kernel Image (uncompressed)</i></font>
<br><font size=2 face="sans-serif"><i> Data Size: 864600
Bytes = 844.3 kB</i></font>
<br><font size=2 face="sans-serif"><i> Load Address: 10008000</i></font>
<br><font size=2 face="sans-serif"><i> Entry Point: 10008000</i></font>
<br><font size=2 face="sans-serif"><i> Verifying Checksum ...
OK</i></font>
<br><font size=2 face="sans-serif"><i> XIP Kernel Image ...
OK</i></font>
<br>
<br><font size=2 face="sans-serif"><i>Starting kernel ... </i></font>
<br>
<br><font size=2 face="sans-serif"><i>
-----> </i><b>and the execution stucks
beyond this point. The system freezes right after u-boot finishes uncompressing
the image for startup. Nothing is output after that & there are no
responses to any input from the terminal.</b></font>
<br>
<br><font size=2 face="sans-serif">I am not very sure if there is any missing
step which is needed to make the kernel boot or maybe I am giving the load-address/entry-point
wrongly while building the kernel images. </font>
<br>
<br><font size=2 face="sans-serif">Also, I tried changing the filed <i>textaddr-y
</i>in the kernel makefile while building the kernel zImage. Does any one
have any idea that what does this address signify & does it effect
the kernel images created by the build process. The original entry against
the <i>textaddr-y </i>field in the kernel Makefile was 0xC0008000 which
was changed to 0x10008000 by me as the former address looked a bit obscure
& did not relate to the target's memory map.</font>
<br>
<br><font size=2 face="sans-serif">Please help me if anyone has faced the
similar problem before or if anyone can make out the missing link in the
steps which I am doing in order to boot the kernel image.</font>
<br>
<br><font size=2 face="sans-serif">Your reply & suggestion will be
of great help.</font>
<br>
<br><font size=2 face="sans-serif">Chetan<br>
<br>
*********************** FSS-Unclassified ***********************</font>