From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] request for some debugging hints
Date: Wed, 29 Jun 2011 15:42:44 +0200 [thread overview]
Message-ID: <20110629134244.C552015AEB85@gemini.denx.de> (raw)
In-Reply-To: <4E0B20D0.4070000@matrox.com>
Dear Christopher Harvey,
In message <4E0B20D0.4070000@matrox.com> you wrote:
>
> I was under the impression that the second a working kernel got passed
> the "Uncompressing Linux... done, booting the kernel." point there was
> very little that could go wrong since it means the kernel was completely
> loaded into memory and the entry point was picked properly.
You are perfectly right and totally wrong.
Yes, you are right: when reaching this point there is not much left
that can go wrong - in U-Boot, that is.
But of course there is a million things that can go wrong in Linux,
and it appears you are running onto one of these.
> The kernel is a very standard kernel, and uboot is a very minimal uboot
> build with no extra soc or board initializations besides memory size.
> eg:
> lowlevel_init is blank
> reset_cpu is an infinite loop
> timers aren't used
May I suggest to run a standard U-Boot version instead, which includes
all the necessary initialization?
You don't mention a board name, so I guess all your code is not
available in mainline?
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
The most difficult thing in the world is to know how to do a thing
and to watch someone else doing it wrong, without commenting.
-- T.H. White
next prev parent reply other threads:[~2011-06-29 13:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-29 12:55 [U-Boot] request for some debugging hints Christopher Harvey
2011-06-29 13:42 ` Wolfgang Denk [this message]
2011-06-29 14:08 ` Chander Kashyap
2011-06-29 14:17 ` Christopher Harvey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110629134244.C552015AEB85@gemini.denx.de \
--to=wd@denx.de \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox