From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] flashing CHIP with 2016.03 (or master)
Date: Mon, 3 Oct 2016 10:27:19 +0200 [thread overview]
Message-ID: <20161003082719.GB5228@lukather> (raw)
In-Reply-To: <20161003060103.GA6772@openSUSE-i7.site>
Hi Trevor,
On Mon, Oct 03, 2016 at 02:01:03AM -0400, Trevor Woerner wrote:
> 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.
You should look closer, we have 2016.01 and 4.4 based branches, which
are the production images.
> 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?
I guess you just found out why we don't have a newer U-Boot?
We still have a bunch of changes that are not upstreamed. The biggest
one being the NAND support, which has a dependency on Linux, which is
also being worked on.
http://lists.infradead.org/pipermail/linux-mtd/2016-April/067322.html
And you're in the same situation with Linux, the NAND support is
missing.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20161003/2414b761/attachment.sig>
prev parent reply other threads:[~2016-10-03 8:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-03 6:01 [U-Boot] flashing CHIP with 2016.03 (or master) Trevor Woerner
2016-10-03 8:27 ` Maxime Ripard [this message]
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=20161003082719.GB5228@lukather \
--to=maxime.ripard@free-electrons.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