<div dir="ltr"><div>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. <br><br>[1] <a href="http://paste.ubuntu.com/16221874/">http://paste.ubuntu.com/16221874/</a><br><br></div>_Swami<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, May 4, 2016 at 2:59 AM, Oliver Grawert <span dir="ltr"><<a href="mailto:ogra@ubuntu.com" target="_blank">ogra@ubuntu.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">hi,<br>
<span class="">Am Dienstag, den 03.05.2016, 17:34 -0700 schrieb Swami:<br>
> Thanks. I synced the uboot code from upstream source tree[1] and<br>
> applied the config changes[2] into include/configs/rpi.h, as I am<br>
> trying to use Raspberry Pi2 as reference board. Now, I wanted to see<br>
> if my custom generated uboot.bin works on the board. So, I downloaded<br>
> the rpi2 snap source from [3], replaced the u-boot.bin<br>
> into /snappy-systems/pi2.moved/boot-assets/ and renamed it uboot.bin.<br>
> Ran snappy build in main pi2.moved directory to generate the .snap<br>
> file. Using this snap file and the device tar ball from [4], created<br>
> the image file using below command.<br>
> sudo ubuntu-device-flash core 15.04 --oem mycustom_2.1_all.snap<br>
> --developer-mode --device-part=device-pi2-0.16.tar.xz -o pi2.img.<br>
> Flashing this image, goes to u-boot, but doesn't boot the kernel.<br>
> Also, don't see the environment variables being loaded due to below<br>
> error:<br>
><br>
> reading uboot.env<br>
> *** Warning - bad CRC, using default environment<br>
<br>
</span>you are missing:<br>
#define CONFIG_ENV_SIZE SZ_128K<br>
<br>
in your uboot config patch ... by default the rpi only sets it to 16k<br>
and since uboot.env is a binary blob, size (info) matters ;)<br>
<br>
ciao<br>
oli<br>
<br>
</blockquote></div><br></div>