public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] flashing CHIP with 2016.03 (or master)
Date: Mon, 3 Oct 2016 02:01:03 -0400	[thread overview]
Message-ID: <20161003060103.GA6772@openSUSE-i7.site> (raw)

Hi,

Today I built an image for the CHIP using OE and was able to flash it to the
CHIP board. I was a bit disappointed to find
https://github.com/NextThingCo/CHIP-u-boot is from a year ago and
https://github.com/NextThingCo/CHIP-linux is 4.2 from Aug 2015. Marek
suggested I try u-boot's master branch since it includes support for the CHIP.
So I changed my build to use the current u-boot recipe in OE (which builds
2016.03 or df61a74e6845ec9bdcdd48d2aff5e9c2c6debeaa) and configured it to use
configs/CHIP_defconfig.

The CHIP's flashing procedure creates a u-boot script
(https://github.com/NextThingCo/CHIP-tools/blob/chip/stable/chip-fel-flash.sh#L86)
which calls u-boot's "nand" procedure. The "nand" command is not built/enabled
in u-boot master for CHIP. Tweaking the CHIP_defconfig to enable it causes a
build failure.

My guess is this is something to keep the user from bricking their device?
So I guess I either have to figure out how to merge NextThing's nand code
into master, or I would need to figure out how to flash the CHIP without this
procedure?

Although I'm using 2016.03 specifically, it looks like the same applies to
master as well.

Best regards,
	Trevor

             reply	other threads:[~2016-10-03  6:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-03  6:01 Trevor Woerner [this message]
2016-10-03  8:27 ` [U-Boot] flashing CHIP with 2016.03 (or master) Maxime Ripard

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=20161003060103.GA6772@openSUSE-i7.site \
    --to=twoerner@gmail.com \
    --cc=u-boot@lists.denx.de \
    /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