mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Michael Burkey <mdburkey@gmail.com>
To: barebox@lists.infradead.org
Subject: Porting barebox (devicetree) to Variscite iMX6 SOM
Date: Wed, 11 Dec 2013 12:07:17 -0500	[thread overview]
Message-ID: <CAJyuEeeO5KpoZpmoSFj8AOOPJ+1o-iWjmQVBZS9FCj2Z7d38kA@mail.gmail.com> (raw)

I figured I'd just throw this out to everyone..

Is there any really good source of information or directions on the
correct steps involved in getting a devicetree based barebox image
built and then correctly programmed onto an SD Card? I feel like I am
missing something somewhere.

I have been involved in getting barebox working on a Variscite i.MX6
SOM with the intent to send it to Sascha, et al. for inclusion in the
tree (once I get it actually working....).

Back in August, I managed to get the Variscite board booting with an
earlier version of barebox and my additions using the "old-style"
methodology in the arch/arm/boards file and the older style DCD header
info. Unfortunately, this version was prior to the inclusion of GPMI
NAND support and other features we needed.

So...I have now been attempting to migrate things to the most current
barebox releases and transfer everything I have done into the newer
style formats aimed at devicetree -- and I haven't been able to get it
to work yet.

So far, I started from the imx_v7_defconfig,  created what I think are
appropriate dts/dtsi files that describe my baseboard and SOM, updated
my board.c and lowlevel.c files (hopefully correctly -- there just
isn't much code in these files anymore with devicetree), created a
flash-header-variscite.imxcfg file using the DCD information I had
already verified worked in the old format (based on the u-Boot DCD
info from Variscite), updated the appropriate Makefiles to build the
new modules, added the appropriate entry to images/Makefile.imx, etc.

I then built it and programmed the resulting .img file into an SD Card
but I get nothing apparent in terms of a response (no serial console,
no blinking LED, etc).

I do NOT have an env partition at the moment but have it set to build
a default environment into barebox itself (which tends to be how we
prefer to have it for our current SD card boot mechanism -- which is
aimed primarily at recovery and upgrade anyway).

Are there any steps I'm missing or anything major I'm doing wrong? Do
I need to be manually specifying a dtb file to include?

Any and all help would be greatly appreciated!

Thanks again,
Michael Burkey

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

             reply	other threads:[~2013-12-11 17:07 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-11 17:07 Michael Burkey [this message]
2013-12-11 23:17 ` Alexander Aring
2013-12-12  8:04 ` Sascha Hauer
2013-12-12 18:49   ` Michael Burkey
2013-12-12 18:56     ` Michael Burkey
2013-12-12 19:12       ` Alexander Aring
2013-12-12 19:24         ` Michael Burkey
2013-12-12 19:58     ` Sascha Hauer
2013-12-12 22:44       ` Michael Burkey
2013-12-18 16:39         ` Michael Burkey
2013-12-18 21:34           ` Michael Burkey
2013-12-19  8:09             ` Sascha Hauer
2014-01-09  7:20               ` Michael Burkey
2014-01-09 19:59                 ` Michael Burkey
2014-01-10  8:00                   ` Sascha Hauer
2014-01-10  8:13                 ` Sascha Hauer
2014-01-15 18:35                   ` Michael Burkey
2014-01-16 14:13                     ` Sascha Hauer
2014-01-16 21:18                       ` Michael Burkey
2014-01-20  8:00                         ` Sascha Hauer
2014-01-29 21:10                           ` Michael Burkey
2014-01-29 21:53                             ` Michael Burkey
2014-02-01 18:35                             ` Sascha Hauer
2014-02-04 21:44                               ` Michael D. Burkey

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=CAJyuEeeO5KpoZpmoSFj8AOOPJ+1o-iWjmQVBZS9FCj2Z7d38kA@mail.gmail.com \
    --to=mdburkey@gmail.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