Go to file
David Escalona 98d514c1c2 dey-examples-hdp: update sample to python3
- Some Python modules are no longer available in DEY-2.2 since
  the official supported Python version is now 3. This caused the
  HDP application to fail importing some of the old modules. For this
  reason the sample application has been updated to use Python3
  syntax and modules.

https://jira.digi.com/browse/DEL-3996

Signed-off-by: David Escalona <david.escalona@digi.com>
2017-03-29 09:25:52 +02:00
meta-digi-arm meta-digi: revert revisions to AUTOREV 2017-03-28 18:54:25 +02:00
meta-digi-dey dey-examples-hdp: update sample to python3 2017-03-29 09:25:52 +02:00
sdk meta-digi: change Freescale references to NXP 2017-03-22 19:58:32 +01:00
README.md README: Update for dey-2.2-r1 2017-03-27 09:57:27 +02:00

README.md

Digi Embedded Yocto (DEY) 2.2

Release 2.2-r1

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

Digi Embedded Yocto 2.2 is based on the 2.2 (Morty) Yocto release.

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

Supported Platforms

The current release supports the following hardware platforms:

Software for the following hardware platforms is in production support:

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

Documentation

Documentation is available online on the Digi documentation site:

Downloads

  • Demo images: ftp://ftp1.digi.com/support/digiembeddedyocto/2.2/r1/images/
  • Software Development Kit (SDK): ftp://ftp1.digi.com/support/digiembeddedyocto/2.2/r1/sdk/

Release Changelog

2.2-r1

  • Release based on Yocto 2.2 (Morty) including:
    • New toolchain based on GCC-6.2.0 and GLIBC-2.24
    • Updated Qt 5.7
    • Cellular support, including the new Quectel EC21 cellular modem
    • TrustFence enabled
    • Remote manager
    • Local and remote manager firmware update
    • Package upgrades and security fixes

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.

  • If TrustFence (TM) image encryption support is enabled, the uSD image will boot a signed U-Boot only.
  • 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).

Digi ConnectCore 6UL

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

Digi ConnectCore 6

  • 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

Digi 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/.txt.gz.
  2. Attach the .txt.gz file to your support ticket.