snappy source files

Swami s.swamyn at gmail.com
Wed May 4 17:15:58 UTC 2016


Thanks!. Nope, doesn't help. Still stuck at the same place. Copied the
u-boot.cfg from my source at [1]. The size of uboot.env as present in
pi2.moved is 131072 which is 128K and now I have modified the size to
SZ_128K.

[1] http://paste.ubuntu.com/16221874/

_Swami

On Wed, May 4, 2016 at 2:59 AM, Oliver Grawert <ogra at ubuntu.com> wrote:

> hi,
> Am Dienstag, den 03.05.2016, 17:34 -0700 schrieb Swami:
> > Thanks. I synced the uboot code from upstream source tree[1] and
> > applied the config changes[2] into include/configs/rpi.h, as I am
> > trying to use Raspberry Pi2 as reference board. Now, I wanted to see
> > if my custom generated uboot.bin works on the board. So, I downloaded
> > the rpi2 snap source from [3], replaced the u-boot.bin
> > into /snappy-systems/pi2.moved/boot-assets/ and renamed it uboot.bin.
> > Ran snappy build in main pi2.moved directory to generate the .snap
> > file. Using this snap file and the device tar ball from [4], created
> > the image file using below command.
> > sudo ubuntu-device-flash core 15.04 --oem mycustom_2.1_all.snap
> > --developer-mode --device-part=device-pi2-0.16.tar.xz -o pi2.img.
> > Flashing this image, goes to u-boot, but doesn't boot the kernel.
> > Also, don't see the environment variables being loaded due to below
> > error:
> >
> > reading uboot.env
> > *** Warning - bad CRC, using default environment
>
> you are missing:
> #define CONFIG_ENV_SIZE                        SZ_128K
>
> in your uboot config patch ... by default the rpi only sets it to 16k
> and since uboot.env is a binary blob, size (info) matters ;)
>
> ciao
>         oli
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/snappy-devel/attachments/20160504/18a87298/attachment.html>


More information about the snappy-devel mailing list