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.
The current release supports the following hardware platforms:
Software for the following hardware platforms is in production support:
-
Digi ConnectCore 6UL
- Digi P/N CC-WMX-JN58-NE
- Digi P/N CC-MX-JN58-Z1
- Digi P/N CC-WMX-JN7A-NE
-
Digi ConnectCore 6UL SBC Express
-
Digi ConnectCore 6UL SBC Pro
-
Digi ConnectCore 6
- Digi P/N CC-WMX-J97C-TN
- Digi P/N CC-WMX-L96C-TE
- Digi P/N CC-WMX-L87C-TE
- Digi P/N CC-MX-L76C-Z1
- Digi P/N CC-MX-L86C-Z1
- Digi P/N CC-MX-L96C-Z1
- Digi P/N CC-WMX-L76C-TE
- Digi P/N CC-WMX-K87C-FJA
- Digi P/N CC-WMX-K77C-TE
- Digi P/N CC-WMX-L97D-TN
- Digi P/N CC-WMX-J98C-FJA
- Digi P/N CC-WMX-J98C-FJA-1
-
Digi ConnectCore 6 Development Kit
-
Digi ConnectCore 6 SBC
Previous versions of Digi Embedded Yocto include support for additional Digi hardware.
Documentation is available online on the Digi documentation site:
- Digi ConnectCore 6UL SBC Express
- Digi ConnectCore 6UL SBC Pro
- Digi ConnectCore 6 Jumpstart Development Kit
- Demo images: ftp://ftp1.digi.com/support/digiembeddedyocto/2.2/r2/images/
- Software Development Kit (SDK): ftp://ftp1.digi.com/support/digiembeddedyocto/2.2/r2/sdk/
- Use NetworkManager for ethernet, wireless (station) and cellular network interfaces
- Updated kernel version to v4.1.41 for CC6 platform
- Added support for SPI Slave mode on CC6UL platform
- Added support for Atmel Cryptochip ATEC508A using Cryptoauthlib
- Network failover mechanism
- Powered by AWS certified on all supported hardware platforms including:
- AWS GreenGrass core software
- AWS IoT Device SDK for embedded C
- Updated AR6233 firmware for Radio Equipment Directive module certification
- QCA6564 WorldWide board data file available on request
- Includes MCA firmware v1.0:
- MCA analog tamper detection
- MCA ADC-based analog comparators
- Updated U-Boot to version 2015.04-r9
- Added support for CC6UL variant 0x4
- Added dynamic environment location and bad block handling for the environment
- TrustFence:
- Move RootFS encryption key to 'safe' partition
- Added support for four tamper interfaces
- Disable external memory boot in OTP for secure boot
- Skip initial scanning of bad blocks for faster boot on NAND
- Updated documentation
- Release based on Yocto 2.2 (Morty) including:
- New toolchain based on GCC-6.2.0 and GLIBC-2.24
- Updated Qt 5.7
- Updated ModemManager with validated support for:
- Digi's XBee Cellular LTE Cat 1 (USA/Verizon), with P/N XBC-V1-UT-001
- Digi's XBee Cellular 3G Global, with P/N XBC-M5-UT-001
- U-Blox's TOBY L-200/L-210
- Telit's LE910 and HE910
- Huawei's ME909u
- Quectel's EC21 and EC25
- Modified default networking settings:
- Defalt to dynamic IP addresses assignments
- Default station and softAP concurrent wireless mode
- TrustFence enabled
- Remote manager
- Local and remote manager firmware update
- Package upgrades and security fixes
- U-boot support for 1GB DDR3 RAM on CC6UL
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).
- 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.
- When using wireless concurrent mode as the wireless interface is shared between several different functionalities performance is reduced.
- When using wireless concurrent mode Digi recommends to keep the different modes on the same frequency channels. For example, when configuring access point mode on channel 36 on band A, the recommendation would be to connect to the same channel both in station mode and WiFi direct so that the radio performance is optimized
- When working as an access point, DFS capable channels in band A are not currently supported.
- The QCA6564 wireless chip does not support Wake On Wireless LAN
- 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
- The Micrel PHY KSZ9031 may take between five and six seconds to auto-negotiate with Gigabit switches
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.
- In the device, run the command 'sysinfo'. This generates the following file: /tmp/<current timestamp>.txt.gz.
- Attach the <current timestamp>.txt.gz file to your support ticket.