From: "Enrico Weigelt, metux IT consult" <enrico.weigelt@gr13.net>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: d.schultz@phytec.de, barebox@lists.infradead.org, ptxdist@pengutronix.de
Subject: Re: boot problem w/ barebox
Date: Mon, 11 Sep 2017 20:47:03 +0200 [thread overview]
Message-ID: <207dcf09-6116-29e2-e854-aa3e02cc0c10@gr13.net> (raw)
In-Reply-To: <20170911071614.ubhmelfunysejs4a@pengutronix.de>
On 11.09.2017 09:16, Uwe Kleine-König wrote:
> Try adding a #define DEBUG in linux-4.13/arch/arm/boot/compressed/head.S > and make sure enabled DEBUG_LL and selected the right UART in your>
.config.
After deep digging in the init code, I've meanwhile fixed it (at least
with self-compiled 2015 bbx - didn't try newer versions yet). In the end
was just dt misconfiguration (that wasn't obvious in this dts wood,
which I ported from the old 4.1-phy tree): the debug uart was disabled.
This lead to some funny situations:
* DEBUG_ll worked after fixing the port number (the counting is a bit
confusing: ttymxc1 is #2)
* console works up to the point where the uarts tty drivers are
configured. as the uart was disabled in dt, no tty driver was
associated (while ll driver was still active), so the clock was
disabled on some point, leading to supposedly hangup (actually,
just the console was gone)
* hacking out the clock disable lead further to the point where rootfs
is mounted and init started
* init couldn't do much, as it didn't get a console. first I suspected
rootfs would be mounted too late, but then turned out that
/dev/console indeed was there (in the internal initramfs), but open()
returned ENODEV (hmm, we should have verbose errno printouts - already
got some patches for that in some other trees ...)
* the reason for ENODEV was the lack of an tty driver for the uart
(printk() still went through ll driver) -- may we should add a proper
warning for that ...
--mtx
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2017-09-11 18:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-09 9:01 Enrico Weigelt, metux IT consult
2017-09-11 7:16 ` Uwe Kleine-König
2017-09-11 18:47 ` Enrico Weigelt, metux IT consult [this message]
2017-09-12 8:32 ` [ptxdist] " Uwe Kleine-König
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=207dcf09-6116-29e2-e854-aa3e02cc0c10@gr13.net \
--to=enrico.weigelt@gr13.net \
--cc=barebox@lists.infradead.org \
--cc=d.schultz@phytec.de \
--cc=ptxdist@pengutronix.de \
--cc=u.kleine-koenig@pengutronix.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