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: Mon, 27 Aug 2018 14:10:04 +0200 [thread overview]
Message-ID: <20180827121004.hfeb3bahhyvkoiw4@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.
I gave it a test and can confirm that the board boots when compiled with
OSELAS 2016 and no longer boots with OSELAS 2018.
It's strange and I'm out of ideas for now. In
imx27_barebox_boot_nand_external() we have a place that copies the
initial image poprtion into SDRAM. It seems the SDRAM is never written
to - at least according to the information my BDI2000 gives me.
I assume it must be something to do with the SDRAM setup, but the code
and also the resulting assembly really looks harmless, though a little
different between both toolchains.
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-27 12:10 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
2018-08-27 12:10 ` Sascha Hauer [this message]
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=20180827121004.hfeb3bahhyvkoiw4@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