<div class="gmail_quote">Hi ALL,<div><br></div><div>I have been woking on upgrading an embedded system based on MPC8241 from 2.4.17 linux to 2.6.30 kernel.</div><div>I am currently struck one point.</div><div><br></div><div>
Here is the console output where I am struck: </div>
<div>=================================</div><div>cpboot> bootm</div><div>## Booting image at 08000000 ...</div><div> Image Name: Linux-2.6.30</div><div> Image Type: PowerPC Linux Kernel Image (gzip compressed)</div>
<div> Data Size: 21729342 Bytes = 21220 kB = 20 MB</div><div> Load Address: 01900000</div><div> Entry Point: 01900570</div><div> Verifying Checksum ... OK</div><div> Uncompressing Kernel Image ... OK</div><div>
Memory <- <0x0 0x10000000> (256MB)</div><div>CPU clock-frequency <- 0xbebc1fe (200MHz)</div><div>CPU timebase-frequency <- 0x17d783f (25MHz)</div><div>CPU bus-frequency <- 0x5f5e0ff (100MHz)</div><div><br>
</div><div>zImage starting: loaded at 0x01900000 (sp: 0x0fdc3a08)</div><div>Allocating 0x165ca04 bytes for kernel ...</div><div>gunzipping (0x00000000 <- 0x0190c000:0x02f58efc)...done 0x1637b54 bytes</div><div><br></div>
<div>Linux/PowerPC load:</div><div>Finalizing device tree... flat tree at 0x2f65300 <== Beyond this point no output is available.</div><div>(The size of image is 20MB because ramfs embedded inside the image)</div><div>
<br></div><div>==================================</div><div><br></div><div>Here are the steps I have taken till now.</div><div>1) Defined platform.dts file for my platform. Since I am using MPC8241, I have taken cuboot-824x.c. Is this file correct. </div>
<div>Do I need to define my own cuboot-*.c file ?</div><div><br></div><div>2)Built cuImage and loaded it into memory. I am not seeing any output once control passes from wrapper to kernel. As you can see from logs mentioned above.</div>
<div><br></div><div>While going through mail achieves I found two possible reasons for this </div><div>1) Wrong entries inside dts file</div><div>I am sure serial attributes are correctly defined inside the file. Also it works for wrapper. It should work for linux also.</div>
<div><br></div><div>2) PPCboot not providing information.</div><div>I have built cuImage . Shouldn't kernel be getting its attributes from dtb file rather then depending on bd_info structure.</div><div>I cannot upgrade to uboot. Is there some way I can make my board come up?</div>
<div><br></div><div>Thanks in advance,</div><div>Vijay</div><font color="#888888"><div><br></div>
</font></div><br>