commit | 6b05a1d09bea3cc869b4f49867c2a6b13db6d2aa | [log] [tgz] |
---|---|---|
author | Jan Kundrát <kundrat@cesnet.cz> | Wed Mar 06 17:01:28 2019 +0100 |
committer | Jan Kundrát <kundrat@cesnet.cz> | Wed Mar 06 17:01:28 2019 +0100 |
tree | 150d5c02956398f949c725e55c949b6105f76da8 | |
parent | ea098db319e200f1a9570ecec3a9beb90453151d [diff] |
Preserve random seed across reboots At first I tried to just use systemd's systemd-random-seed, but that one does not actually use an appropriate ioctl for persuading kernel that entropy is there. There's a patch [1] for this, but its fate is far from certain, and even with it, I am not completely sure that I got everything working correctly (some boots were quick, others waited for systemd-resolved in the same manner as before this patch). In the end, just seeding stuff from the initrd [2] is much easier. A downside is that the systemd unit systemd-random-seed.service will add the contents of that file once again -- but that doesn't matter much because we do not patch it, and therefore it does not increase kernel's idea about available entropy. Changes from that upstream rndaddentropy: - larger buffer - more conservative entropy contribution [1] https://github.com/systemd/systemd/pull/10621 . [2] https://github.com/rfinnie/twuewand/blob/master/rndaddentropy/rndaddentropy.c Change-Id: Ibe3c926c241d75fb7d7c40f3df2a96813931971b
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.
WARNING: Buildroot is fragile. It is not safe to perform incremental builds after changing an "important" setting. Please check their manual for details.
A significant amount of time is wasted in configure
steps which are not parallelized :( as of November 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. Configuration stored in /cfg
is brought along and preserved as well.
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
On development boards with a µSD card slot, simply dd
the images/sdcard.img
to the SD card and boot from there.
On a regular Clearfog Base with an eMMC, one has to bootstrap the device first. If recovering a totally bricked board, one can use the kwboot
command to upload the initial U-Boot via the console. Ensure that the jumpers are set to 1 1 1 1 0
(default for eMMC boot is 0 0 1 1 1
), and then use U-Boot's kwboot
tool:
./tools/kwboot -b ./u-boot-spl.kwb -t -p /dev/ttyUSB0
Once in U-Boot (a stock factory image is OK as well), plug a USB flash disk which contains images/usb-flash.img
and execute:
usb start; fatload usb 0:1 00800000 boot.scr; source 00800000
The system will boot and flash the eMMC from the USB drive. Once the status LED starts blinking in yellow, data are being transferred to the eMMC. The light changes to solid yellow in later phases of the flashing process. Once everything is done, the status LED shows a solid white light and the system reboots automatically.