Skip to content

Release notes

Releases

Version 1.2.0

Version 1.2.0 - ''Fighting Egg''

New functionality

  • Lifecycle management for host firmware upgrades
  • Support configuration of host via host-config.yaml
  • Support linuxcan as CAN driver
  • Support using Kvaser Edge as standalone USB interface

Breaking changes: v1.1.0 to v1.2.0

  • Removed the mounted /dev/rtc device from the container. See here on how to add it if needed.

  • The host upgrade command has moved to under the new host subcommand in hostctl.

Security

  • Several CVE fixes.

Fixed

  • The LED triggers CAN1, CAN2... (ch1, ch2... in the system) works properly with a Kvaser USB CAN device connected. They can also be enabled from the container.

Known issues

  • If a USB device is connected to the Edge when it is powered on the serial port won't attach properly to a running container and can't be used until the system has been rebooted.

  • CAN hardware timestamp clock/counter is reset to 0 after suspend/resume.

  • If a device is not detected during boot the user will not get notified. Work around is to check, when booted, that the devices that are going to be used are detected and functional, if they are not reboot.

  • EDGE serial port not showing with certain older canlib versions on Windows.

Not supported

  • Bluetooth

Version 1.1.0

Version 1.1.0

New functionality

  • Support for Kvaser Edge WL420s

Breaking changes: v1.0.0 to v1.1.0

Known issues

  • The Edge will not present itself as a USB device if there are USB devices connected to the Edge USB port when it is powered on. This applies to both the serial console to the container and the mass storage device during initial setup. The Edge can be connected to a PC as a device. If it does not show up, try unplugging and replugging the usb cable to the PC or rebooting the device.

  • CAN hardware timestamp clock/counter is reset to 0 after suspend/resume

  • The default configured LED netdev triggers for LEDs CAN1...CAN4 (ch1...ch4in the system) stops working when Kvaser USB CAN devices are inserted. They cannot be reconfigured from the container.

  • If a device is not detected during boot the user will not get notified. Work around is to check, when booted, that the devices that are going to be used are detected and functional, if they are not reboot.

  • EDGE serial port not showing with canlib on Windows

Not supported

  • Bluetooth

Version 1.0.0

Version 1.0.0 -- ''First release''

New functionality

  • Power off USB during suspend

  • Privileged operations

    • Decrease nice value
    • Set system time
    • Set RTC time

  • Access to host journal

Breaking changes: v0.4.0 to v1.0.0

Known issues

  • The Edge will not present itself as a USB device if there are USB devices connected to the Edge USB port when it is powered on. This applies to both the serial console to the container and the mass storage device during initial setup. The Edge can be connected to a PC as a device. If it does not show up, try unplugging and replugging the usb cable to the PC or rebooting the device.

  • Container shutdown is delayed for 15 seconds without a connected console peer

  • CAN hardware timestamp clock/counter is reset to 0 after suspend/resume

  • The default configured LED netdev triggers for LEDs CAN1...CAN4 (ch1...ch4in the system) stops working when Kvaser USB CAN devices are inserted. They cannot be reconfigured from the container.

  • If a device is not detected during boot the user will not get notified. Work around is to check, when booted, that the devices that are going to be used are detected and functional, if they are not reboot.

  • EDGE serial port not showing with canlib on Windows

Not supported

  • Bluetooth

Pre-releases

Release notes for Pre-Releases