From: "Albert, Elmar" <EAlbert@data-modul.com>
To: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Dynamic RAM configuration on iMX6 board
Date: Fri, 4 May 2018 07:57:03 +0000 [thread overview]
Message-ID: <24f0c042-64a4-eaeb-36eb-6fffe8cdb65d@data-modul.com> (raw)
Hello everybody,
I'm working on a board using iMX6. There are variants of the board
differing in iMX6S/DL/D/Q and the size of the memory on CS0. The
iMX6S/DL/D variants are using 32bit interface to two DDR3 devices (e.g.
1GByte), the iMX6Q variant is using 64bit interface to four DDR3 devices
(e.g. 2GByte). This is leading in at least two different .imxcfg files
for DRAM-controller initialization.
The DRAM Density and the number of mounted DDR3 devices can be read from
the board via GPIO-pins.
To prevent multiple barebox-images and so multiple pre-programmed
SPI-Flashes on stock in the factory, I'm looking for a solution to
configure the DRAM-Controller dynamically during barebox boot.
Is it possible to have more than one .imxcfg files in one image and if
so, how can it be selected to configure the DRAM controller depending on
board-info read from GPIO-pins?
--
Mit freundlichen Grüßen / Best Regards
Elmar Albert
Embedded R&D
DATA MODUL AG
Landsberger Str. 322
80687 Munich
Germany
Tel: +49 89 56017 197
Fax: +49 89 56017 345
Mail to: ealbert@data-modul.com
Internet: http://www.data-modul.com
Vertrauliche E-Mail von / Confidential e-mail from: DATA MODUL AG
Vorstand / CEO: Dr. Florian Pesahl
Vorsitzende des Aufsichtsrates / Chairwoman of the Supervisory Board: Kristin D. Russell
Sitz der Gesellschaft / Registered Office: München
Registergericht / Registration Court: München Handelsregister B 85 591
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2018-05-04 7:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-04 7:57 Albert, Elmar [this message]
2018-05-04 8:17 ` Sascha Hauer
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=24f0c042-64a4-eaeb-36eb-6fffe8cdb65d@data-modul.com \
--to=ealbert@data-modul.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