Skip to content

Latest commit

 

History

History
225 lines (181 loc) · 10.1 KB

README.md

File metadata and controls

225 lines (181 loc) · 10.1 KB
Raw

Digi Embedded Yocto (DEY) 3.0

Release 3.0-r2

This document provides information about Digi Embedded Yocto, Digi International's professional embedded Yocto development environment.

Digi Embedded Yocto 3.0 is based on the Yocto Project(TM) 3.0 (Zeus) release.

For a full list of supported features and interfaces please refer to the online documentation.

Tested OS versions

The current release has been verified and tested with the following OS versions:

  • Ubuntu 18.04

Supported Platforms

Software for the following hardware platforms is in production support:

ConnectCore 8M Nano

ConnectCore 8X

ConnectCore 6UL

ConnectCore 6 Plus

ConnectCore 6

Installation

Digi Embedded Yocto is composed of a set of different Yocto layers that work in parallel. The layers are specified on a manifest file.

To install, please follow the instructions at the dey-manifest README

Documentation

Documentation is available online at https://www.digi.com/resources/documentation/digidocs/embedded/

Downloads

Release Changelog

3.0-r2

  • Updated BSP to NXP release rel_imx_5.4.24_2.1.0.
  • Added support to ConnectCore 6 and ConnectCore 6 Plus (kernel v5.4).
  • Updated U-Boot to version 2020.04-r1 for ConnectCore 8X.
  • TrustFence: added secure console and U-Boot environment encryption support. to ConnectCore 8X and 8M Nano.
  • Added MCA keypad support for ConnectCore 8X and 8M Nano.
  • Fix SoftAP on 5GHz on ConnectCore 6UL.
  • Other minor fixes.

3.0-r1

  • Release based on Yocto 3.0 (Zeus) including:
    • New toolchain based on GLIBC-2.30
    • Updated Qt 5.13.2
    • Updated NetworkManager to v1.18.4
    • Updated Wpa-supplicant to v2.9
    • Updated gstreamer1.0 to v1.16.0
    • Updated busybox to v1.31.0
    • Removed support to bluez4
    • Updated OpenSSL to v1.1.1d
    • Package upgrades and security fixes
  • Updated kernel version to v5.4 for ConnectCore 8X, ConnecCore 8M Nano and ConnectCore 6UL
  • Updated U-Boot to version 2017.03-r6 for ConnectCore 6UL
  • Updated U-Boot to version 2018.03-r4 for ConnectCore 8 MNano platform
  • Updated U-Boot to version 2019.04-r2 for ConnectCore 8X platform
  • Added support for ConnectCore 8M Nano v2 SOM
  • Added initial TrustFence support for ConnectCore 8M Nano

Known Issues and Limitations

This is a list of known issues and limitations at the time of release. An updated list can be found on the online documentation.

  • Firmware update
    • The software update package must be located in the root level of the update media (subfolders are not yet supported).
  • Cloud Connector
    • Remote file system management fails with long file names and paths (over 255 characters).
  • Wireless
    • Performance of the wireless interface is reduced when using concurrent mode, as the wireless interface is shared between several different functionalities.
    • When using wireless concurrent mode, Digi recommends you keep the different modes on the same frequency channels. For example, when configuring access point mode on channel 36 in the 5GHz band, connect to the same channel both in station mode and Wi-Fi direct so that the radio performance is optimized.
    • When working as an access point, DFS-capable channels in the 5GHz band are not supported.
    • For P2P connections Digi recommends "Negotiated GO" modes. The QCA6564 devices (ConnectCore 6UL, ConnectCore 6 Plus, and ConnectCore 8M Nano) fail to join autonomous groups.

ConnectCore 8M Nano

  • ConnectCore 8M Nano System-on-Module (SOM)
    • CPU wake-up sources are not yet supported

ConnectCore 8X

  • i.MX8QXP Processor
    • GPU maximum performance reduced. The maximum frequency targets are 850 MHz for the shaders and 700 MHz for the core. However, in this hardware release the maximum frequency is limited to 650 MHz for the shaders and 600 MHz for the core, with the corresponding performance reduction. These targets will be met in future releases of the hardware.
    • BSDL operation is not supported. It will be available in future releases of the hardware.

ConnectCore 6UL

  • ConnectCore 6UL System-on-Module (SOM)
    • The UART connected to the Bluetooth chip on early versions of the ConnectCore 6UL system-on-module (hardware version < 4) cannot properly execute flow control. To work around this issue, UART1 of these SOM versions has been configured to operate at 115200 bps and without hardware flow control, reducing the maximum throughput of this interface.
    • The QCA6564 wireless chip does not support Wake On Wireless LAN.

ConnectCore 6 Plus

  • ConnectCore 6 Plus System-on-Module (SOM)
    • NXP i.MX6QP processor has a documented errata (ERR004512) whereby the maximum performance of the Gigabit FEC is limited to 400Mbps (total for Tx and Rx).
  • ConnectCore 6 Plus SBC
    • The Micrel PHY KSZ9031 may take between five and six seconds to auto-negotiate with Gigabit switches.

ConnectCore 6

  • ConnectCore 6 System-on-Module (SOM)
    • NXP i.MX6 processor has a documented errata (ERR004512) whereby the maximum performance of the Gigabit FEC is limited to 400Mbps (total for Tx and Rx).
    • When using softAP mode on Band A on the Qualcomm AR6233, channels used for Dynamic Frequency Selection (DFS) are not supported.
    • The Qualcomm AR6233 firmware does not support the following configuration modes:
      • Concurrent modes involving P2P mode, such as P2P + softAP or P2P + STA.
      • Bluetooth + softAP + STA concurrent mode.
    • A maximum of five clients are supported when using Qualcomm's AR6233 in softAP mode.
    • A maximum of ten connected devices are supported when using Qualcomm's AR6233 Bluetooth Low Energy mode.
  • ConnectCore 6 SBC
    • The Micrel PHY KSZ9031 may take between five and six seconds to auto-negotiate with Gigabit switches.

Support Contact Information

For support questions please contact Digi Technical Support:

When you contact Digi Technical Support, include important system details and device information to help Digi resolve the issue more quickly.

  1. In the device, run the command 'sysinfo'. This generates the following file: /tmp/<current timestamp>.txt.gz.
  2. Attach the <current timestamp>.txt.gz file to your support ticket.