From: Sascha Hauer <s.hauer@pengutronix.de>
To: "Michael D. Burkey" <mdburkey@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: Boot iMX6 from IRAM on new Variscite SOM
Date: Thu, 16 Jun 2016 15:54:49 +0200 [thread overview]
Message-ID: <20160616135449.GI9677@pengutronix.de> (raw)
In-Reply-To: <CAO6XYUuv_VTv6trEFhjzZ=ey+2addAGBRsdqKQwFgbobaHLi-w@mail.gmail.com>
Hi Michael,
On Mon, Jun 13, 2016 at 06:38:31PM -0400, Michael D. Burkey wrote:
> I have already spoken with Sascha about this a bit, but figured I'd
> throw it out here in case anyone had any suggestions.
>
> Specifically, I'm updating the support for the Variscite SOM to handle
> the newest version of their SOM -- which now includes an EEPROM that
> contains a "DCD-like" script for configuring the DDR3 timing
> parameters.
>
> Essentially this means that I have to follow a boot procedure similar
> to that used by the current Wandboard setup, which loads part of
> barebox into IRAM/OCRAM on the iMX6, read/configures the DDR3 timings,
> then reloads barebox into DDR3 and starts it.
>
> I think I have gotten things more or less setup at this point and have
> copied the setup from the Wandboard, but am having trouble getting
> things to actually start from the internal RAM on the board.
>
> For now, I have a correct DCD already built-in that preconfigures DDR3
> "just in case" and if I set the load address to be DDR3, then
> everything starts up as normal -- which in and of itself points to a
> problem.
>
> My suspicion is that the boot ROM is still trying to load the full
> image rather than just part of it -- which means that, when I point it
> to the IRAM/OCRAM, it is writing to the aliased memory regions of the
> built in RAM and overwriting itself in the process.
>
> What/where actually controls the length of the code that gets
> automatically loaded by the iMX6 internal boot ROM and what needs to
> be updated?
Your image name should end with .imx-sram-img, see images/Makefile.imx:
FILE_barebox-imx6-wandboard.img = start_imx6_wandboard.imx-sram-img
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
prev parent reply other threads:[~2016-06-16 13:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-13 22:38 Michael D. Burkey
2016-06-16 13:54 ` Sascha Hauer [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=20160616135449.GI9677@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=mdburkey@gmail.com \
/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