Skip to content

Release Notes

Releases

Version 0.4.0

Version 0.4.0 -- ''Pre-Release 4''

New functionality

Breaking changes: v0.3.0 to v0.4.0

  • hostctl container subcommand has been renamed to hostctl system

  • hostctl system upgrade has been renamed to hostctl upgrade

  • hostctl now requires meta data to be passed as a flag argument and not just an argument. See host service documentation

  • The file path used when upgrading the host system is now /host/upgrade instead of /host/update

  • config.yaml for container config has been renamed to container-config.yaml for the initial setup

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

  • High Power Usage in suspend

    • Attached USB devices are powered on

  • 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.

    When using canlib drivers versions 5.49 and 5.50 they can mistakingly assign the canlib device driver to the Kvaser EDGE instead of the serial driver, which results in the serial port, inside the container, on Edge devices to be missing. At the moment there is a workaround to change the device driver used by the edge device manually.

    • To change the driver go to Device manager.
    • Once there look for CAN Hardware (Kvaser).
    • If the problem exists there should be a Kvaser Edge device with a warning symbol, right click on it and choose Update driver.
    • Pick Browse my computer for drivers and then Let me pick from a list of available drivers on my computer.
    • Select USB Serial Device. If there are multiple USB Serial Device options select either one.
    • Then reboot the Edge, it should now be correctly configured as a serial port.

Not supported

  • Bluetooth

Version 0.3.0

Version 0.3.0 -- ''Pre-Release 3''

New functionality

  • Improved WiFi stability.

  • Introduction of host service that enables host function control from inside user container.

  • Activation signal event. The activation signal is available as an input event, and can be monitored similar to the push buttons.

  • Support for USB Mass Storage Devices.

  • Container hostname can now be based on template strings.

  • Updated factory reset procedure.

  • LEDs CAN1...CAN4 (ch1...ch4in the system) are default configured to be controlled by netdev trigger for the corresponding SocketCAN device (can0...can3).

  • Kvaser USB CAN device plug and play.

  • WiFi module is powered off in suspend.

Breaking changes and migration: v0.2.0 to v0.3.0

  • Updated factory reset procedure.

  • The system will no longer suspend automatically when activation signal is low. System suspension can only be initiated by the container. The activation signal is always configured as wakeup source.

  • Remove SocketCAN network interfaces from the container configuration. Now all SocketCAN network interfaces are always added to the container.

  • Host system updates are now provided as .multi-mender-files.

  • Renamed LEDs:

    • {red,green,blue,multi}:LED1..LED4 -> {red,green,blue,multi}:led1..led4

    • {red,green}:CAN1..CAN4 -> {red,green}:ch1..ch4

Note

When updating from v0.2.0 to v0.3.0, the system needs to be updated twice:

  1. Factory reset the device according to instructions for v0.2.0.

  2. Copy kvaser-image-edge-imx8mp-wl400s.mender to /host/update.

  3. Power cycle the device to perform the update.

  4. Factory reset the device again, according to step 1 above.

  5. Copy kvaser-image-edge-imx8mp-wl400s.multi-mender to /host/update.

    Note: This time we use the .multi-mender and not .mender.

  6. Power cycle the device to perform the update.

  7. Now the device is properly upgraded to v0.3, and the factory reset procedure is as described in the Getting Started section.

Known Issues

  • Can't create USB serial port used for /dev/console if booted as host

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

  • High Power Usage in suspend

    • Attached USB devices are powered on

  • 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.

Not yet supported

  • Trigger I/O

  • GPS/GNSS

  • Bluetooth

  • 6-axis IMU

Version 0.2.0

Version 0.2.0 -- ''Pre-Release 2''

New functionality

  • Onboarding in USB mass storage mode

  • USB audio/video device plug and play

  • LED control

  • Button events

    • 2x push buttons

  • Factory reset

Known Issues

  • Can't create USB serial port used for /dev/console if booted as host

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

  • The WiFi module crashes intermittently, requiring a system restart to restore functionality

  • High Power Usage in suspend

    • WiFi powered on

    • Attached USB devices are powered on

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

Not yet supported

  • Trigger I/O

  • GPS/GNSS

  • Bluetooth

  • 6-axis IMU

  • User controlled activation signal, currently a de-asserted activation signal will set the device in suspend automatically