| commit | 1e5dfebc8adfb0085b31d99564c687222f41efad | [log] [tgz] |
|---|---|---|
| author | Jan Kundrát <kundrat@cesnet.cz> | Fri Sep 14 13:40:34 2018 +0200 |
| committer | Jan Kundrát <kundrat@cesnet.cz> | Fri Sep 14 13:44:12 2018 +0200 |
| tree | c51f67b71c2bba4c05217f58959ac4f50d1d4c27 | |
| parent | 2917becf9b6cd729a9b18d473dbd2ced46d683aa [diff] |
Delay SSH key copying after the sshd have finished generating them Previously, we were getting this dependency "for free" because the netopeer2-keystored package was blocking on sshd to start because it was requsing sshd's keys for its own purposes. Now that our keys are different (that change happened in the main buildroot repo in our add-on branch), we no longer depended on sshd to finish its key generation, and in turn this meant that the main sshd's host keys were not being preserved in our /cfg: # ls -al /cfg/etc/ssh/ total 8 drwxr-xr-x 2 root root 4096 Sep 12 18:37 . drwxr-xr-x 4 root root 4096 Sep 13 18:39 .. -rw------- 1 root root 0 Sep 12 18:37 ssh_host_rsa_key.NHsbsiTO7k Fix this by waiting for sshd to finish starting up, and only copy the SSH host keys afterwards. Also split copying of OpenSSH's host keys from copying og Netopeer2-server's host keys because these are conceptually unrelated. Change-Id: Ic927ec2316595d1f0722e2aad097e0ae9ab60690
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:
./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.