mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sean Cross <xobs@kosagi.com>
To: barebox@lists.infradead.org
Subject: Porting Barebox to i.MX6QDL "Novena"
Date: Mon, 06 Jan 2014 17:20:37 +0800	[thread overview]
Message-ID: <52CA7565.7060808@kosagi.com> (raw)

Hi,

After talking with people at 30C3, I've decided to try moving from
U-Boot to Barebox.  I've got things building to the point where I have a
single ">" character being printed (after reading an earlier SOM porting
message), but I'm starting to grasp at straws now when it comes to
bringing DDR up.

Novena has an SO-DIMM slot.  In U-Boot, we wrote a hook for setup_ddr()
that got the SO-DIMM's SPD via I2C, performed calibration, and returned
with DDR all configured.

In Barebox, I'm running into some trouble:

    1) How do I access I2C routines from lowlevel.c?  I need to be able
to query the EEPROM on the DDR module itself to get its timing parameters.

    2) How much character printing can I get in lowlevel.c?  I notice
putc_ll() works, but puts_ll() doesn't, presumably because I have the
text offset incorrectly set.

    3) How much functionality can I have in ~96 KiB?  I believe that's
roughly the amount of space allowed in the OCRAM on an i.MX6DL once you
allow for code in ROM that's actually doing the loading.

    4) Failing that, is it possible to load some preboot code to set up
DDR?  I realize the traditional method is a hardcoded pokefile, but
since we support DDR3 modules, we can't rely on that.


Sean

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

             reply	other threads:[~2014-01-06  9:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-06  9:20 Sean Cross [this message]
2014-01-06 10:20 ` Sascha Hauer
2014-01-06 12:58   ` Sean Cross
2014-01-06 14:41     ` 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=52CA7565.7060808@kosagi.com \
    --to=xobs@kosagi.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