ubuntu-device-flash errors for building armhf image
ogra at ubuntu.com
Fri Jun 3 09:38:08 UTC 2016
> On Fri, Jun 3, 2016 at 2:59 PM, Woodrow Shen
> <woodrow.shen at canonical.com> wrote:
> Hi all,
> I made roseapple-pi gadget snap
there are multiple issues with your gadget snap ...
in your snap.yaml you define two files that do not exist:
- path: boot-assets/bootloader.bin
- path: boot-assets/u-boot.bin
we also do not support any text files for configuring the bootloader any
more, you need to create a uboot.env (and adjust your uboot build time
configuration to use and find it):
#define CONFIG_ENV_SIZE SZ_128K
#define FAT_ENV_INTERFACE "mmc"
#define FAT_ENV_DEVICE_AND_PART "0:1"
(in include/configs/$your-board.h, note that FAT_ENV_DEVICE_AND_PART
needs to point to your vfat partition that holds the uboot.env file)
the uboot.env needs to be created using the mkenvimage command either
from your uboot tree (it gets built in the tools directory) or from the
u-boot-tools package in the archive:
mkenvimage -r -s 131072 -o uboot.env uEnv.txt
(note the options are not optional ;) -r and -s 131072 are mandatory)
and change "- path: boot-assets/uEnv.txt" to "- path:
boot-assets/uboot.env" in your snap.yaml
first see if it works better with the adjusted gadget snap and the very
latest ubuntu-device-flash from
if there are still issues then we can go through your kernel snap ...
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 181 bytes
Desc: This is a digitally signed message part
More information about the Snapcraft