From: Graeme Russ <gruss@tss-engineering.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] No console output once kernel starts loading.
Date: Mon, 16 Mar 2015 22:10:27 +1100 [thread overview]
Message-ID: <5506BA23.1030506@tss-engineering.com> (raw)
In-Reply-To: <1425509212145-207674.post@n7.nabble.com>
Hi David,
On 05/03/15 09:46, DaveKucharczyk wrote:
> I'm currently working on the kernel dtb for our MX53 board.
>
> U-boot loads the dtb and kernel and then gets stuck at "starting kernel...".
>
> I've triple checked the uart pad setup in imx53.dtsi
This is probably a long shot, but I had the same issue when I did the
original x86 port. It turned out that I had not routed the UART
interrupt signal correctly in U-Boot - I think the Linux kernel may have
been waiting on some kind of interrupt from the UART (probably buffer
empty) before it sent anything to it.
Regards,
Graeme
prev parent reply other threads:[~2015-03-16 11:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-04 22:46 [U-Boot] No console output once kernel starts loading DaveKucharczyk
2015-03-11 17:29 ` DaveKucharczyk
2015-03-11 17:41 ` Fabio Estevam
2015-03-16 11:10 ` Graeme Russ [this message]
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=5506BA23.1030506@tss-engineering.com \
--to=gruss@tss-engineering.com \
--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