In message [off-list ref] you wrote:
Does anybody have any idea about the problem? Also,
Yes.
is it possible to print some debug messages at this
point of booting? {Note that, in the early stage of
Use a BDI2000.
Can somebody help me with the above problem?
Maybe you start reading the FAQ... See
http://www.denx.de/twiki/bin/view/DULG/LinuxHangsAfterUncompressingKernel
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
A wise person makes his own decisions, a weak one obeys public
opinion. -- Chinese proverb
Hi, Vinay
Please reply to the list also!
I can guess your problem, but you should give more
information about your system i.e.
Processor / Board / Kernel version, ...
vinay hegde wrote:
I do not have the board in my possesion. Actually, I
am using the board through virtual network. Hence, I
am unable to use any of the debugging techniques
(JTAG, logic analyzer etc) except going through the
source code and printing some messages.
Then you depend on the console output at least.
-> early printk.
Also, how do I enable early printk option? I did not
find any such option under kernel configuration.
i.e. if you use one of the latest 2.6 kernels,
turn on "Support for early boot texts over serial port"
(That's in in "Kernel hacking")
Verify your console settings twice.
You can even start to poke out some characters manually
to the serial port to see if (where) it really hangs if
you cannot use or don't want to spend lots of money to
get a hw debugger just for this.
And, thanks for referring me to the mailing
addresses. I will immediately subscribe to Ozlabs!
Read the list archives and the FAQ's mentioned
in here and ask google. You will get good answers there,
too!
Best greets,
Clemens Koller
_______________________________
R&D Imaging Devices
Anagramm GmbH
Rupert-Mayer-Str. 45/1
81379 Muenchen
Germany
http://www.anagramm.de
Phone: +49-89-741518-50
Fax: +49-89-741518-19
On Tue, 6 Sep 2005, Clemens Koller wrote:
Hi, Vinay
Please reply to the list also!
I can guess your problem, but you should give more
information about your system i.e.
Processor / Board / Kernel version, ...
i missed the first part of this. i've booted a 2.6 kernel on an 8xx
board and got to the command prompt. is that of any use here?
rday
p.s. i'm not using u-boot as the bootloader but that shouldn't be an
unmanageable difference.