Go to file
Hector Palacios 5403b831df u-boot-fw-utils: update patch to support encrypted env
The encryption of the U-Boot environment uses the HWID as key
modifier. The HWID was being read using the fsl_otp driver sysfs
entries and over two words. The driver is now deprecated and also
the cc8x and cc8m platforms have different number of HWID words.

This patch modifies the function that reads the HWID words by
using new entries on the device tree 'digi,hwid_X' where X is the
index of the HWID word.

It also removes the need to select CONFIG_MD5 which is already
auto-selected on sandbox_defconfig by other config switches.

Signed-off-by: Hector Palacios <hector.palacios@digi.com>

https://jira.digi.com/browse/DEL-7185
(cherry picked from commit 8ced362766)
2020-07-24 13:13:40 +02:00
meta-digi-arm u-boot-fw-utils: update patch to support encrypted env 2020-07-24 13:13:40 +02:00
meta-digi-dey sysinfo: adapt script after removal of deprecated fsl_otp driver 2020-07-24 13:13:37 +02:00
scripts scripts: add dey-aws-tool script 2017-07-05 13:43:28 +02:00
sdk build.sh: add support to use an external downloads dir 2020-06-04 08:53:15 +02:00
README.md meta-digi-dey: bump distro version to 3.0-r2 2020-07-17 20:10:26 +02:00

README.md

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

Previous versions of Digi Embedded Yocto include support for additional Digi hardware.

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-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 i.MX8X, i.MX8MN and i.MX6UL platforms
  • Updated U-Boot to version 2017.03-r6 for i.MX6UL platform
  • Updated U-Boot to version 2018.03-r4 for i.MX8MN platform
  • Updated U-Boot to version 2019.04-r2 for i.MX8X 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 and ConnectCore 8M Nano) fail to join autonomous groups.
  • Trustfence is not yet supported on the ConnectCore 8M Nano.

ConnectCore 8M Nano

  • ConnectCore 8M Nano System-on-Module (SOM)
    • CPU wake-up sources are not yet supported
  • ConnectCore 8M Nano DVK
    • The maximum bitrate for CAN interface is 125 Kbits/s. This is a software limitation from the CAN controller.

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.

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.