Name | Last modified | Size | Description | |
---|---|---|---|---|
Parent Directory | - | |||
README.html | 2015-04-15 22:30 | 2.3K | ||
README.md | 2015-04-15 22:30 | 2.1K | ||
device-pi2-0.9.tar.xz | 2015-04-09 15:48 | 25M | ||
device-pi2-0.10.tar.xz | 2015-04-15 17:01 | 29M | ||
device-pi2-0.11.tar.xz | 2015-04-15 19:01 | 29M | ||
pi2.img.gz | 2015-04-15 21:45 | 245M | ||
pi2.lool_0.9_all.snap | 2015-04-09 15:50 | 1.7M | ||
pi2.lool_0.10_all.snap | 2015-04-09 16:08 | 1.7M | ||
pi2.lool_0.11_all.snap | 2015-04-15 14:46 | 2.1M | ||
These contain pre-built bits to bootstrap your Raspberry Pi 2 with a Snappy image.
pi2.img
: pre-built dd-able image; 3,9 GB; SSH is enabled, login with
ubuntu / ubuntudevice-pi2-*.tar.xz
: device tarball (kernel, initrd, dtbs); from
Paolo Pisati's binary buildpi2.lool_*_all.snap
: unsigned OEM snaps (bootloaders, boot configs and
scripts); from
U-Boot and Broadcom bits described here
Source is kept at
lp:~lool/+junk/pi2.lool].To create a new image with the store's signed OEM snap and system-image's rootfs (e.g. because you want a different size, newer rootfs, pointing at a different channel, turning developer mode on etc.) run:
sudo ubuntu-device-flash core \
--oem pi2.lool \
--enable-ssh \
--device-part=device-pi2-0.11.tar.xz \
-o pi2.img
If you want to build against a local OEM snap, you need developer mode as to disable signature verification:
sudo ubuntu-device-flash core \
--oem pi2.lool_0.11_all.snap \
--developer-mode \
--device-part=device-pi2-0.11.tar.xz \
-o pi2.img
Unpack the device tarball, update files and repack from within the unpacked directory with:
tar cvJf ../device-x.y.tar.xz *
To update the initrd, unpack it with:
mkdir initrd
cd initrd
xzcat ../initrd.img|cpio -d -i -m
Repack it with:
cd initrd
find . | cpio -o -H newc | xz --check=crc32 --arm --lzma2=dict=512KiB > ../new-initrd.img
Unpack the snap with:
dpkg-deb -x pi2.lool_0.11_all.snap extracted
Repack with:
cd unpacked
snappy build .