Release Notes
Added Features
The main features added by this release of Edgehog OS are listed below. Please check the Changelog section for further details.
Edgehog Things
- Support to Edgehog Device Runtime version 0.7.
Edgehog Embedded
- Support for FrameBuffer (FB) as backend.
- Enhanced Qt support.
- Increase package support for GStreamer tool.
- Add packages on Embedded Full distro for a more complete image.
- Add support to Edgehog Embedded image for Intel CPU-based boards.
Bug Fixes
The main bug fixes added by this release of Edgehog OS with respect to the previous one are listed below. Please check the Changelog section for further details.
- BIOS Control: Add support to missing packages necessary to perform BIOS operations like check of BIOS version and BIOS update.
- NXP URL references: Change reference to NXP source repositories from codeaurora.org to GitHub. The reference to codeaurora.org does not allow to build older versions of Edgehog OS.
- i.MX6 Splash Screen: Fix on video configuration at U-Boot level.
- SBC-MX6 (A62): Fix on watchdog not working on board reboot.
- SBC-MX6 (A62): Fix on video output for LVDS and HDMI+LVDS configurations at U-Boot level.
- SBC-MX6 (A62): Fix on 1Gb/s Ethernet RGMII configuration not allowing the board to properly work at full bandwidth.
- WiLink: Include WiLink firmware in i.MX recipes allowing some of the boards (e.g. SOM-SMARC-MX8M) to correctly initialize the Wi-Fi.
- SOM-SMARC-MX8M (C12): Fix 'failed to reparent uart2'.
- SOM-SMARC-MX8M (C12): Add TLV320AIC32X4 audio support.
- SOM-SMARC-MX8M (C12): Add vpu, gpu3d support.
- SOM-SMARC-MX8M (C12): Fix on uSD boot issue, upgrade straps management.
- i.MX8QM: Fix on broken U-Boot binary for Edgehog Things and Embedded distros on some builds not allowing the board to boot.
- BSP NXP Typos: Generic fix on typos on U-Boot and Kernel source code.
- X11 on Rockchip: Add DPMS and display-off timings in X11 configuration file, in order to disable both power management and screensaver and keep the display always on.
Hardware support
This version of Edgehog OS is compatible with the following SECO hardware:
| Board | CPU Architecture | SOC | Board Documentation |
|---|---|---|---|
| SOM-Q7-MX6 (formerly codenamed 928) | ARM | i.MX6QDL | SOM-Q7-MX6 (928) |
| SOM-uQ7-MX6 (formerly codenamed 962) | ARM | i.MX6QDL | SOM-uQ7-MX6 (962) |
| 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) |
| SOM-SMARC-MX8M-Plus (formerly codenamed D18) | ARM | i.MX8MP | SOM-SMARC-MX8M-Plus (D18) |
| SOM-uQ7-MX8M-Nano (formerly codenamed C72n) | ARM | i.MX8MN | SOM-uQ7-MX8M-Nano (C72n) |
| SBC-TANARO-MX8M-Mini (formerly codenamed Tanaro) | ARM | i.MX8MM | SBC-TANARO-MX8M-Mini (TANARO) |
| SBC-3.5-RK3399 (formerly codenamed C31) | ARM | RK3399 | SBC-3.5-RK3399 (C31) |
| SBC-3.5-PX30 (formerly codenamed D23) | ARM | PX30 | SBC-3.5-PX30 (D23) |
| Intel Apollo Lake boards | x86 | Apollo Lake | APOLLO LAKE |
| Intel Elkhart Lake boards | x86 | Elkhart Lake | ELKHART LAKE |
| Intel Tiger Lake boards | x86 | Tiger Lake | TIGER LAKE |
Link References
Here below the user can find the link to the Software artifacts associated to this release.
| Board | RAM | Distro | U-Boot | Kernel | Filesystem | RAUC Bundle | Image | Bmap File |
|---|---|---|---|---|---|---|---|---|
| SOM-Q7-MX6 (formerly codenamed 928) | 1G - 4x256M | 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 | ||
| 2G - 4x512M | 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 | ||
| 4G - 8x512M | 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-uQ7-MX6 (formerly codenamed 962) | 512M - 2x256M | 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 | ||
| 1G - 4x256M | 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 | ||
| 2G - 4x512M | 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-MX6 (formerly codenamed A62) | 1G - 4x256M | 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) | All | Edgehog Things | U-Boot (HDMI) | Kernel | Filesystem | RAUC Bundle | Image | Bmap file |
| Edgehog Embedded Full | U-Boot (HDMI) | Kernel | Filesystem | / | Image | Bmap file | ||
| Edgehog Embedded Base | U-Boot (HDMI) | Kernel | Filesystem | / | Image | Bmap file | ||
| SOM-SMARC-MX8M (formerly codenamed C12) | All | 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) | All | 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) | All | 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-SMARC-MX8M-Plus (formerly codenamed D18) | All | 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-uQ7-MX8M-Nano (formerly codenamed C72n) | All | 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) | All | 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-PX30 (formerly codenamed D23) | All | 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) | All | 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 | All | Edgehog Things | / | / | Filesystem | RAUC Bundle | Image | Bmap file |
| Edgehog Embedded Base | / | / | Filesystem | / | Image | Bmap file | ||
| Edgehog Embedded Full | / | / | Filesystem | / | Image | Bmap file | ||
| Intel Elkhart Lake Boards | All | Edgehog Things | / | / | Filesystem | RAUC Bundle | Image | Bmap file |
| Edgehog Embedded Base | / | / | Filesystem | / | Image | Bmap file | ||
| Edgehog Embedded Full | / | / | Filesystem | / | Image | Bmap file | ||
| Intel Tiger Lake Boards | All | Edgehog Things | / | / | Filesystem | RAUC Bundle | Image | Bmap file |
| Edgehog Embedded Base | / | / | Filesystem | / | Image | Bmap file | ||
| Edgehog Embedded Full | / | / | Filesystem | / | Image | Bmap file |
Changelog
The changelog related to this release can be found at the following link.
Known Issues
Edgehog Filesystem
- 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.
- 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 OS 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.
-
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".
-
D18 - Edgehog Device Runtime loading. After poweron or reboot the service
edgehog-device-runtime.servicestarts with a delay of at least two minutes, in this time the service is loaded but inactive and doesn’t seems to attempt a restart as expected behaviour. -
D18 - Edgehog things services load chain bug. At FileSystem loading, the services load chain is incorrect, in particular, the string
[ OK ] Started Boot OK Succesful Notifier.relative to the boot-notifier is printed before the string[ OK ] Finished RAUC Good-marking Service.relative to RAUC service. - Edgehog things - error count ambigous behaviour. The error counter on secondary partition seems to be enabled only in the first boot after a rauc update, if the boot is a success, it will be deactivated. This behaviour cuts away some critical cases, such as updates that fails only a certain percentage of times giving the possibility of a first successfull update that’ll deactive the counter, and validate a bugged BSP.
- Modem utils (e.g. mmcli, qmcli). There is the necessity to add utils to manage LTE modem modules.
- Desktop environment always ON. In the Edgehog Embedded Full image, the Desktop environment on Wayland goes Off about 30 seconds after power-up if no activity is performed. It would be crucial to have screen always on enabled by default or at least the necessary tools to set this option.
Board Support Package (BSP)
- 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.
- 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.
- 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.
- 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.
- C26/C43 - RTC failure.
- C43 - qSPI flash. The onboard qSPI flash is not detected.
- C43 - audio reproduction. No output in the headphones can be heard coming out of the card even when increasing the alsamixer levels.
- 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.
- i.MX8QM - HDMI-IN not working. For these platforms (i.e. C26 and C43), the HDMI-IN signal is still not working correctly.
- C31 - boot takes up to few minutes. The boot phase of the filesystem may take up to a few minutes to complete.
- C12 - Edgehog things image not booting. There is an error in the sysdata management at U-Boot that prevents the board from booting.
- TANARO - Internal Bluetooth isn't working. In the current BSP version the bluetooth interface is not working.
- TANARO - RTC isn't configured. The Tanaro normally detects the equipped RTC during installation and then generates the full DT from an overlay. This isn’t working for WiC images.
- TANARO - Internal Wifi isn't working. In the current BSP version the Wi-Fi interface is not working.
- i.MX6 - Ethernet low bandwidth. It has been verified on 928/962/A62 boards that the performance of the 1Gb/s ethernet interface is well below the nominal value. In particular, the values recorded for 962 by means of iperf3 tests are ~500 Mb/s (client) and ~700 Mb/s (server), which are well below the expected value.
- 928 - SGTL5000 not found. Even if the right configuration is selected at U-boot with seco-config, the audio card can’t be found with “aplay -l”. Furthermore, no trace of the audiocard load can be found in dmesg.
- 928 - SATA kernel and fdt load fail. Trying to load zImage and fdt from the first SATA partition results in the attached error, instead, the FileSystem is correctly loaded from SATA.
- 962 - SGTL5000 Audio sometimes not working. Audio was tested on carrier A42 with connector A74 for audio via I2S. Although the audio card is recognised correctly by selecting the option at seco_config, sometimes (to be investigated the incidence) no output is heard and errors are thrown when using alsamixer.
- i.MX6 - Sdma firmware deferred loading. sdma firmware takes approximately 1 minute to load and trying to use a dma application (uart, aplay…) before the loading leads to a kernel panic.
- C72n - Bridge DSI to LVDS not working.
- C72n - USB interfaces not working. No USB port is initialized when checking at filesystem level.
- c72n - Boot from NFS/TFTP not working. The boot from TFTP/NFS option via seco_config pointed out some errors. Once the configuration is set via seco_config command the new U-Boot environment seems not to be saved correctly (the IP addresses of the server/client remain the same). Sometimes the board does not even boot the kernel from TFTP in a point-to-point connection to the PC even though the environment is correct.
- C72n - Audio reproduction error. An error is displayed when trying to reproduce a sample track with an A74 I2S audio module connected to A42 carrier board.
- C72n - eMMC detected as 'mmcblk2'. The eMMC device is detected as ‘mmcblk2' at kernel level. This bug introduces issues at U-Boot level, in particular when performing seco_config command, because the 'root_device_id’ variable is set to 0 when selecting the boot option from eMMC.
- C72n - Edgehog Things distro not mounting filesystem. The C72n board is not able to boot filesystem components (datafs partition) with Edgehog Things distro neither from eMMC nor uSD. This is a consequence of the previous error.
- 962 - PCIe not working. The test was performed connecting a Quectel EG25-G LTE module to the CN8 connector on A42 carrier board. No output is displayed when executing the lspci command.
- 962 - TFTP/NFS U-Boot option. Once the board is configured at U-Boot (via the seco_config tool) to load the kernel from TFTP and the filesystem from NFS, it happens that if static IPs are configured for the server and the client, the board does not boot because it continues to use the default IP address for the server (i.e. 13.0.0.1). A power on/off cycle of the board is always required to correctly load the kernel/FileSystem.
- D23 - Wireless devices soft-blocked at power on. Wireless devices (Bluetooth and Wi-Fi if connected) are not used immediately at start-up as they are set as 'soft blocked'. This can be seen for instance by using the “rfkill list” command.
- D23 - CAN peripherals support. Currently, although D23 exposes CAN peripherals, these are not initialised in the BSP (and cannot be displayed via 'ifconfig -a' commands).