Please discard this message. I found what was causing the kernel to hang. It has nothing to do with u-boot. Thank you all for your help so far!
Mitsy
---------- Forwarded message ---------- From: mitsy mitsy12@gmail.com Date: Jul 25, 2006 3:47 PM Subject: Debug kernel init code? (was: Load address and entry point for mips?) To: u-boot-users@lists.sourceforge.net
Again, thank you Andrew. I believe I got those parameters correctly now!
However, I tried everything I can think of, but it's still not working. I took a look at log_buf mem location and it sure it is hanging inside the kernel. What is the best way to debug kernel init code (rather than putting bunch of printk)? I know there's a how-to on how to debug kernel module but I can't find one for init code.
Mitsy
On 7/25/06, mitsy mitsy12@gmail.com wrote:
Hi Andrew,
Thank you so much for your help on this. I tried my best but I couldn't figure them out. I'll try these numbers and let you know how it goes.
I really appreciate your help. Thank you so much!
Have a great day!
Mitsy
On 7/24/06, Andrew Dyer amdyer@gmail.com wrote:
On 7/24/06, mitsy mitsy12@gmail.com wrote:
When I do the mkimage with linux bin, I'm not sure what values to use for load address and entry point. In README file, it says for powerpc use 0 for both, but I think for mips, it won't be the case. (SDRAM base is 0x80000000.)
this is a snippet from the script we use:
START=`${CROSS_COMPILE}objdump -h vmlinux |awk '$2 == ".text" {print $4;}'` ENTRY=`${CROSS_COMPILE}objdump -f vmlinux |awk '/start/ {print $3;}'`
-- Hardware, n.: The parts of a computer system that can be kicked.