mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Lucas Stach <l.stach@pengutronix.de>
To: gianluca <gianlucarenzi@eurekelettronica.it>
Cc: barebox@lists.infradead.org
Subject: Re: Information regarding iMX6 QuadPlus and iMX6 DualLite
Date: Thu, 23 Mar 2017 17:59:48 +0100	[thread overview]
Message-ID: <1490288388.29056.48.camel@pengutronix.de> (raw)
In-Reply-To: <15ffeb4b-92e9-bf89-57b2-dc73251bb90c@eurekelettronica.it>

Am Donnerstag, den 23.03.2017, 17:56 +0100 schrieb gianluca:
> On 03/23/2017 04:15 PM, Lucas Stach wrote:
> > Hi,
> >
> > Am Donnerstag, den 23.03.2017, 16:04 +0100 schrieb gianluca:
> >> Hello,
> >> I was looking around to have a common Barebox binary to bootup two
> >> boards based on iMX6 SoC.
> >>
> >> The PCB are at 99.8% the same.
> >> PCB#0 has iMX6QP and a VDDCore of 1.38V (LDO enabled)
> >> PCB#1 has iMX6DL and a VDDCore of 1.32V (LDO enabled)
> >>
> >> I was wondering how other boards (like Nitrogen6x) does for booting.
> >>
> >> As soon as my boards have the same DDR Memory routing and types, the oly
> >> thing I can think is the different memory address space for DDR controller.
> >
> > Even if the external memory is the same, you need 2 different DRAM
> > setups. Quad and DualLite differ in IOMUX setup and maximum DRAM
> > frequency, the QuadPlus needs additional setup for the NoC.
> >
> 
> So you need two DRAM setup only? And no problem for NoC. Our boards will 
> have only QuadPlus and DualLite.

Do you mean the regular Quad model? The QuadPlus has the NoC.

> 
> >> In fact, the Nitrogen6x boards, differs from the #include of the ddr
> >> controller (one is for dual-lite, the other for quad).
> >
> > For the Nitrogen boards we just build multiple images for different
> > SoC/DRAM configurations. This is the easiest and most reliable way of
> > dealing with this issue.
> >
> 
> So you will have different device-tree .dts file? One for each SoC even 
> if the pinout are the same?
> 
> In this way, having two DRAM Setups, two IOMUX setup, different DRAM 
> Frequencies and two device-tree blobs, this leads me to a conclusion:
> 
> -- They are TWO DIFFERENT BOARDS (even the PCB and the pinouts are the same)

Well, welcome to the i.MX6 world. :)


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2017-03-23 17:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-23 15:04 gianluca
2017-03-23 15:15 ` Lucas Stach
2017-03-23 16:56   ` gianluca
2017-03-23 16:59     ` Lucas Stach [this message]
2017-03-23 17:03       ` gianluca
2017-03-23 18:47   ` 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=1490288388.29056.48.camel@pengutronix.de \
    --to=l.stach@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=gianlucarenzi@eurekelettronica.it \
    /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