[U-Boot] flashing CHIP with 2016.03 (or master)

[U-Boot] flashing CHIP with 2016.03 (or master)

[Trevor Woerner]

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

[U-Boot] flashing CHIP with 2016.03 (or master)

[Maxime Ripard]

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>