| commit | 41d2d2675d2092d906d185488e77fadd247f1672 | [log] [tgz] |
|---|---|---|
| author | Jan Kundrát <jan.kundrat@cesnet.cz> | Fri Oct 27 18:29:33 2017 +0200 |
| committer | Jan Kundrát <jan.kundrat@cesnet.cz> | Fri Oct 27 18:29:33 2017 +0200 |
| tree | 968f32d30311ff0b7a5c314bbc243e6116db5d37 | |
| parent | 11f729e67aa6c439f9dbbff6497b8e1a36ab8abd [diff] |
Save persistent DSes to /cfg upon each change This is pretty crude -- whenever an "interesting" file in our overlay /etc/sysrepo/data gets changed, ensure that we store it in the non-volatile /cfg partition as well. Change-Id: Ie6165564a03bf49a51e3475d61d77e3a0374632c
This repository contains CzechLight-specific bits for Buildroot. Buildroot is a tool which produces system images for flashing to embedded devices. They have a nice documentation which explains everything that one might need.
Everything is in Gerrit. One should not need to clone anything from anywhere else. The build will download source tarballs of various open source components, though.
TODO: Automate this via the CI system. I want to get the .img files for testing of each change, eventually.
git clone ssh://$YOUR_LOGIN@cesnet.cz@gerrit.cesnet.cz:29418/CzechLight/br2-external czechlight pushd czechlight git submodule update --init --recursive popd mkdir build-clearfog cd build-clearfog ../czechlight/dev-setup-git.sh make czechlight_clearfog_defconfig make
A full rebuild takes between 30 and 45 minutes on a T460s laptop for targets which use a pre-generated Linaro toolchain (clearfog, beaglebone). Other targets take longer because one has to build a toolchain first. When the build finishes, the generated image to be dd-ed to an SD card is at images/sdcard.img.
WARNING: Buildroot is fragile. It is not safe to perform incremental builds after changing an "important" setting. Please check their manual for details. Using ccache might help, but a significant time is wasted in configure steps which are not parallelized :( as of October 2017. This can be hacked by patching Buildroot's top-level Makefile, but note that one cannot easily debug stuff afterwards:
diff --git a/Makefile b/Makefile index 79db7fe..905099a 100644 --- a/Makefile +++ b/Makefile @@ -114,7 +114,7 @@ endif # this top-level Makefile in parallel comment the ".NOTPARALLEL" line and # use the -j<jobs> option when building, e.g: # make -j$((`getconf _NPROCESSORS_ONLN`+1)) -.NOTPARALLEL: # absolute path TOPDIR := $(CURDIR)
Apart from the traditional way of re-flashing the SD card or the eMMC from scratch, it's also possible to use RAUC to update. This method preserves the U-Boot version and the U-Boot's environment. Apart from that, everything starting with the kernel and the DTB file and including the root FS is updated.
FIXME: the system uses separate config partitions (/cfg), so these persistent bits are not preserved yet (see these user stories).
To install an update:
# build node make rsync -avP images/update.raucb somewhere.example.org:path/to/web/root # target, perhaps via an USB console wget http://somewhere.example.org/update.raucb -O /tmp/update.raucb rauc install /tmp/update.raucb reboot