Release Notes

Introduction

Edgehog OS, based on the Yocto framework is the Linux Operating System optimized for SECO design. It is intended to provide the highest standards in terms of security and stability thanks to features like delta updates, double partitions, and fallback procedures. Edgehog OS integrates a device manager to communicate with the Cloud and allows a family of products to be managed as a fleet.

Added Features

This is the first official version of Edgehog OS released to the public. The main features presents are listed below.

Edgehog Things

  • Support to Edgehog Device Runtime version 0.6.
  • Support to RAUC version 1.6.
  • Slot management at U-Boot level based on sysdata for ARM-based CPU boards.
  • Slot management at grub level for x86-based CPU boards.
  • Binding of the devices to the Astarte and Edgehog Cloud portals.
  • OTA (Over The Air) updates of RAUC bundles via the Edgehog portal.
  • Failover management after a failed update.

Edgehog Embedded

  • Support to Edgehog Embedded Full and Edgehog Embedded Base images: the first one contains a complete set of packages for testing purpose, while the second one contains a minimal set of packages to let user specific layers to be added.
  • Support to Chromium and HTML5.
  • Support to GPU/VPU hardware accelerations for ARM-based CPU boards.
  • Support to Qt5.

Hardware support

This version of Edgehog OS is compatible with the following SECO hardware:

Board CPU Architecture Soc Board Documentation
SBC-MX6 (formerly codenamed A62) ARM i.MX6QDL SBC-MX6 (A62)
SBC-3.5-MX8M (formerly codenamed C20) ARM i.MX8MQ SBC-3.5-MX8M (C20)
SOM-SMARC-MX8M (formerly codenamed C12) ARM i.MX8MQ SOM-SMARC-MX8M (C12)
SOM-Q7-MX8 (formerly codenamed C26) ARM i.MX8QM SOM-Q7-MX8 (C26)
SBC-3.5-MX8 (formerly codenamed C43) ARM i.MX8QM SBC-3.5-MX8 (C43)
SBC-3.5-RK3399 (formerly codenamed C31) ARM RK3399 SBC-3.5-RK3399 (C31)
SBC-TANARO-MX8M-Mini (formerly codenamed Tanaro) ARM i.MX8MM SBC-TANARO-MX8M-Mini (TANARO)
Intel Apollo Lake boards x86 Apollo Lake APOLLO LAKE

Link References

Here below the user can find the link to the Software artifacts associated to this release.

Board Distro U-Boot Kernel Filesystem RAUC Bundle Image Bmap File
SBC-MX6 (formerly codenamed A62) Edgehog Things U-Boot Kernel Filesystem RAUC Bundle Image Bmap file
Edgehog Embedded Base U-Boot Kernel Filesystem / Image Bmap file
Edgehog Embedded Full U-Boot Kernel Filesystem / Image Bmap file
SBC-3.5-MX8M (formerly codenamed C20) Edgehog Things U-Boot (HDMI) Kernel Filesystem RAUC Bundle Image Bmap file
Edgehog Embedded Base U-Boot (HDMI) Kernel Filesystem / Image Bmap file
Edgehog Embedded Full U-Boot (HDMI) Kernel Filesystem / Image Bmap file
SOM-SMARC-MX8M (formerly codenamed C12) Edgehog Things U-Boot Kernel Filesystem RAUC Bundle Image Bmap file
Edgehog Embedded Base U-Boot Kernel Filesystem / Image Bmap file
Edgehog Embedded Full U-Boot Kernel Filesystem / Image Bmap file
SOM-Q7-MX8 (formerly codenamed C26) Edgehog Things U-Boot Kernel Filesystem RAUC Bundle Image Bmap file
Edgehog Embedded Base U-Boot Kernel Filesystem / Image Bmap file
Edgehog Embedded Full U-Boot Kernel Filesystem / Image Bmap file
SBC-3.5-MX8 (formerly codenamed C43) Edgehog Things U-Boot Kernel Filesystem RAUC Bundle Image Bmap file
Edgehog Embedded Base U-Boot Kernel Filesystem / Image Bmap file
Edgehog Embedded Full U-Boot Kernel Filesystem / Image Bmap file
SBC-3.5-RK3399 (formerly codenamed C31) Edgehog Things U-Boot Kernel Filesystem RAUC Bundle Image Bmap file
Edgehog Embedded Base U-Boot Kernel Filesystem / Image Bmap file
Edgehog Embedded Full U-Boot Kernel Filesystem / Image Bmap file
SBC-TANARO-MX8M-Mini (formerly codenamed Tanaro) Edgehog Things U-Boot Kernel Filesystem RAUC Bundle Image Bmap file
Edgehog Embedded Base U-Boot Kernel Filesystem / Image Bmap file
Edgehog Embedded Full U-Boot Kernel Filesystem / Image Bmap file
Intel Apollo Lake Boards Edgehog Things / / Filesystem RAUC Bundle Image Bmap file

Changelog

The changelog related to this release can be found at the following link.

Known Issues

Edgehog Filesystem

  1. FPS drop in Weston terminal. If the user starts a video in Weston terminal, the frame rate drops visually in comparison of a video started via serial debug terminal. Furthermore, when the video is started in Weston terminal, the “Weston” process occupy more than 60% of the CPU usage, while if started from debug UART terminal the same process occupy 2-3% of CPU usage.
  2. Intel Apollo Lake - Error in booting with USB pen drive connected or directly from eMMC. The following error occurs when booting the board with Edgehog installed on a USB pen drive and another USB connected to the device. Although the grub loaded is that of the correct pen drive (the one containing Edgehog OS), it seems to be trying to load the kernel on the other connected USB pen drive, thus causing a failure. The same error is seen when the Edgehog OS is installed in the eMMC, since the system seems to try to start what’s inside the “/dev/sda“ device in any case.
  3. A62 - OTA update fail. OTA update from Edgehog portal fails frequently because of main issue in the 1Gb Ethernet port connection (see a62 issue below). A possible workaround is to connect the board to a 10/100 Mb switch.
  4. Rauc - slot health status. When a slot is set on “bad” health status, there are two anomalous behaviour:
    • It’s not possible to mark it’s health status on “good” manually, preventing the user to change the status when the slot could be effectively damaged.
    • If A is the primary slot and B is marked as “bad”, selecting B as primary slot automatically changes B health status to “good”. This behaviour should be prevented if the health of the B partition is "bad".
  5. C43 - Wrong U-Boot/Firmware files in Edgehog distros. The U-Boot and Image binaries are not working for C43 board because of an error in the machine config file (see https://git.seco.com/edgehog/layers/seco/meta-seco-imx/-/blob/kirkstone/conf/machine/seco-imx8qm-c43.conf).

Board Support Package (BSP)

  1. TFTP/NFS via DHCP on seco_config. Trying to start TFTP/NFS via seco_config with dynamic IP address assignment to the board, what happens is that the ability to enter the IP address of the TFTP server does not appear. The user is forced to give it by hand by editing the environment at U-Boot. The same is true for the selection of the NFS server.
  2. A62 - Ethernet Issue. With the kernel 5.10.x, the 1Gb network interface sometimes struggles to receive an IP address when connected to a DHCP server. Once the network is hooked up there are visible packet loss problems by performing few pings. A possible workaround is to connect the board to a 10/100 Mb switch.
  3. C20 - Boot via USB. Booting via USB (using seco_config tool to configure boot options) is successful in the case of loading only Kernel and FDT from USB, while the filesystem loading via USB fails.
  4. C20 - HDMI Audio level control. The audio file seems to be played smoothly, however, no output is heard. Using alsamixer to try to turn up the volume actually fails to change any parameters related to the HDMI sound card.
  5. C26 - U-Boot for Edgehog Things image not working. The error appears on U-Boot for C26 board on Edgehog Things distro only and should be related to some bugs in the U-Boot timings (not related to the distro).
  6. C26/C43 - Errors at boot time. Running on/off cycles resulted in the following sporadic errors after a few dozen cycles: error loading the filesystem, error loading HDMI firmware for the board with HDMI output selected.
  7. C26/C43 - RTC failure.
  8. C43 - USB boot not working. The loading of kernel, FDT and filesystem from an USB pen drive fails from both USB connectors.
  9. C43 - qSPI flash. The onboard qSPI flash is not detected.
  10. C43 - audio reproduction. No output in the headphones can be heard coming out of the card even when increasing the alsamixer levels.
  11. C43 - HDMI Audio level control. The audio file seems to be played smoothly, however, no output is heard. Using alsamixer to try to turn up the volume actually fails to change any parameters related to the HDMI sound card.
  12. C31 - boot takes up to few minutes. The boot phase of the filesystem may take up to a few minutes to complete.