| commit | c34a5457909116096d9a17dacb9a46b79dc15d68 | [log] [tgz] |
|---|---|---|
| author | Tomáš Pecka <tomas.pecka@fit.cvut.cz> | Wed Dec 16 21:29:09 2020 +0100 |
| committer | Tomáš Pecka <tomas.pecka@fit.cvut.cz> | Thu Jan 07 16:08:15 2021 +0100 |
| tree | 87999cbdbb4e4564516e63ca3f80fa338d1c6eff | |
| parent | a31ea7c4d1db4a7e9a918167be4830b9ab99ce6c [diff] |
Update cla-sysrepo and velia to use ietf-hardware Update cla-sysrepo and velia. They now implement ietf-hardware YANG model instead of ietf-hardware-state (both defined in RFC 8348 [1]). With latest changes to cla-sysrepo and velia, we should install ietf-hardware model instead of ietf-hardware-state now. Unfortunately, we encountered a bug/feature of Sysrepo. When uninstalling implemented model which has an imported dependency, then the YANG model of the imported dependency is not removed from the repository. See example below. Link to Sysrepo's issue tracker is in the footer. We have two implemented models. iana-hardware and ietf-hardware-state. ietf-hardware model is imported as a dependency of ietf-hardware-state. # pwd is sysrepo repository $ sysrepoctl -l | grep hardware | cut -d"|" -f1-3 iana-hardware | 2018-03-13 | I ietf-hardware | 2018-03-13 | i ietf-hardware-state | 2018-03-13 | I $ ls *hardware* iana-hardware@2018-03-13.yang ietf-hardware-state@2018-03-13.yang ietf-hardware@2018-03-13.yang $ sysrepoctl -u ietf-hardware-state --apply $ sysrepoctl -l | grep hardware | cut -d"|" -f1-3 iana-hardware | 2018-03-13 | I $ ls *hardware* iana-hardware@2018-03-13.yang ietf-hardware@2018-03-13.yang [1] https://tools.ietf.org/html/rfc8348 Bug: https://github.com/sysrepo/sysrepo/issues/2263 Depends-on: https://cesnet-gerrit-czechlight/c/CzechLight/cla-sysrepo/+/3352 Depends-on: https://gerrit.cesnet.cz/c/CzechLight/cla-sysrepo/+/3352 Depends-on: https://cesnet-gerrit-czechlight/c/CzechLight/velia/+/3329 Depends-on: https://cesnet-gerrit-public/c/CzechLight/velia/+/3329 Depends-on: https://gerrit.cesnet.cz/c/CzechLight/velia/+/3329 Change-Id: I580e52ff10c5a17f99db18c080b10c1d40aacd78
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.
The system architecture is described in another document. This is a quick build HOWTO.
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.
By default, each change of this repo uploaded to Gerrit causes the CI system to produce a firmware update. On Gerrit, the change will get a comment from Zuul with a link to the CI log server. Next to the logs, a file named artifacts/update.raucb can be used for updating devices.
Behind the scenes, the system uses Zuul with a configuration tracked in git.
Here's how to reproduce the build on a developer's workstation:
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.
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 or over SSH rauc install http://somewhere.example.org/update.raucb reboot
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 0 1 0 0 1 (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.
Turn off power, remove the USB flash, re-jumper the board (0 0 1 1 1), power-cycle, and configure MAC addresses and system type at the U-Boot prompt. The MAC addresses are found on the label at the front panel.
=> setenv eth1addr 00:11:17:01:XX:XX => setenv eth2addr 00:11:17:01:XX:YY => setenv eth3addr 00:11:17:01:XX:ZZ => setenv czechlight sdn-roadm-line => saveenv Saving Environment to MMC... Writing to redundant MMC(0)... OK => boot
Once the system boots (which currently requires a reboot for some unknown reason -- fsck, perhaps?), configure hostname, plug in the network cable, and update SW:
# hostnamectl set-hostname line-XYZSERIALNO # cp /etc/hostname /cfg/etc/ # rauc install http://somewhere.example.org/update.raucb # reboot
Obtain a reasonable Linux distro image for BBB and flash it to a µSD card. Unlock eMMC boot partitions (echo 0 > /sys/class/block/mmcblk1boot0/force_ro; echo 0 > /sys/class/block/mmcblk1boot1/force_ro). Clean the eMMC data (blkdiscard /dev/mmcblk1). Flash the content of images/emmc.img to device's /dev/mmcblk1. Flash what fits into /dev/mmcblk1boot0 and /dev/mmcblk1boot1. Fetching the image over web (python3 -m http.server and wget http://...:8000/emmc.img -O - | dd of=/dev/mmcblk1 conv=sparse) works well.