From: Sascha Hauer <s.hauer@pengutronix.de>
To: "Baeuerle, Florian" <Florian.Baeuerle@allegion.com>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: [PATCH] ARM: phytec-phycard-imx27: Add debug UART support
Date: Fri, 24 Aug 2018 09:16:56 +0200 [thread overview]
Message-ID: <20180824071656.iwpyy5txv24gsrzq@pengutronix.de> (raw)
In-Reply-To: <5de1c331378034ec7bdbbe58c7e8b1f65debd568.camel@allegion.com>
On Thu, Aug 23, 2018 at 12:20:32PM +0000, Baeuerle, Florian wrote:
> Some background on that patch:
>
> I've tried to get barebox master compiled with OSELAS 2018 running on a
> phycard-imx27. I had a few problems with that:
>
> It turned out, that I can boot the resulting image as a seconds stage (from an
> older version of barebox), after commenting out pca100_usb_init(). I suppose
> that is not a real problem, but probably related to some clock setup that
> barebox master does somewhere during early boot (which I suppose, is skipped
> when booting it as 2nd stage).
>
> However, when flashing the resulting image to NAND, there seems to be a bigger
> issue somewhere during early boot. This problem does not exist when compiling
> barebox master with OSELAS 2016.
>
> The result is that I do not see anything on the console. The imx27 also does not
> seem to enter bootstrap mode though.
>
> Further I found out that with CONSOLE_PBL, barebox also has issues somewhere
> during early boot. It breaks either after calling pbl_set_putc(), or even
> without calling pbl_set_putc(), when I increase the compile and default
> loglevel.
You probably can't use CONSOLE_PBL on the pca100. The i.MX27 NAND boot
requires the initial image portion to fit into 2KiB. These 2KiB are
already almost full with the required code, no place to add console
support there. You could probably through in some putc_ll() into the
initial code (after you've configured the UART with your patch).
The 2KiB constraint makes the boot process rather tricky. I have a
PCA100 at work, I'll give it a try and reproduce the issue next week
when I'm back in the office.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2018-08-24 7:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-23 9:58 Florian Bäuerle
2018-08-23 12:20 ` Baeuerle, Florian
2018-08-24 7:16 ` Sascha Hauer [this message]
2018-08-27 12:10 ` Sascha Hauer
2018-08-27 12:37 ` Baeuerle, Florian
2018-08-27 14:45 ` s.hauer
2018-08-24 1:57 ` Andrey Smirnov
2018-08-31 9:46 ` Baeuerle, Florian
2018-09-10 8:05 ` [PATCH v2] " Florian Bäuerle
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=20180824071656.iwpyy5txv24gsrzq@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=Florian.Baeuerle@allegion.com \
--cc=barebox@lists.infradead.org \
/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