If you try to use libmbim (the API is used at least by mbim-network, mbimcli and ModemManager applications) you get the following error: ModemManager: Error converting string: Conversion from character set 'utf-8' to 'utf-16le' is not supported In order to solve this we need to integrate glibc gconv UTF16le library in the build (and its dependencies). Signed-off-by: Mike Engel Mike.Engel@digi.com https://jira.digi.com/browse/DEL-3830 |
||
|---|---|---|
| meta-digi-arm | ||
| meta-digi-dey | ||
| sdk | ||
| README.md | ||
README.md
Digi Embedded Yocto (DEY) 2.0
Release 2.0-r6
This document provides information about Digi Embedded Yocto, Digi International's professional embedded Yocto development environment.
Digi Embedded Yocto 2.0 is based on the 2.0 (Jethro) 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 beta support:
- Digi ConnectCore 6UL
- Digi ConnectCore 6UL Starter Kit
- Digi ConnectCore 6UL Development Kit
Software for the following hardware platforms is in production support:
-
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
Documentation is available online on the Digi documentation site:
- Digi ConnectCore 6UL Starter Kit
- Digi ConnectCore 6UL Development Kit
- Digi ConnectCore 6 Jumpstart Development Kit
Downloads
- Demo images: ftp://ftp1.digi.com/support/digiembeddedyocto/2.0/r5/images/
- Software Development Kit (SDK): ftp://ftp1.digi.com/support/digiembeddedyocto/2.0/r5/sdk/
Release Changelog
2.0-r6
- TBC
2.0-r5
- Digi Embedded Yocto
- Support firmware update through the new recovery mode
- Initial support to connect to Remote Manager with the CloudConnector
- Updated U-Boot to version 'dub-2015.04-r7' for Digi ConnectCore 6 and 6UL
- Digi ConnectCore 6UL
- Added support to audio codec MAX98089
- Added support to camera Omnivision OV5642
- Optimized kernel configuration (smaller kernel)
- Added support for EDO mode on NAND Flash
- Added PMIC NVRAM support through sysfs
- Added suspend support for PMIC regulators
- Added support for i.MX6UL ADC channels
- Added voltage scaling support for MCA ADC
- Added full-system reset support to MCA watchdog
- Added MCA 32KHz output control through sysfs
- Added VRef output control through sysfs
- Added support to PWM1 on Starter Board expansion header
- Kernel v4.1.38
2.0-r4
- Digi ConnectCore 6UL
- Support for Digi ConnectCore 6UL SBC
- Linux kernel v4.1.35
- Support for Fusion touch displays
- Authenticated and encrypted initramfs, bootscripts and DTBs
- Encrypted root filesystem
- MCA firmware update
- MCA tampering
- Power management optimizations
- Support for Digi ConnectCore 6UL SBC
- Digi ConnectCore 6
- Support for Quectel EC-20 LTE modem
- Authenticated and encrypted initramfs, bootscripts and DTBs
- Linux kernel v3.14.79
- Minor bug fixes
2.0-r3
- Support for the new Digi ConnectCore 6UL System-On-Module and Starter Kit
- U-Boot 2015.04
- Linux kernel v4.1.28
- Support for TrustFence security enhancements
- Secure console
- Secure boot
- Secure JTAG
- Encrypted root filesystem
- True Random Number Generator
2.0-r2
- Release based on Yocto 2.0 (Jethro) for ConnectCore 6 SBC including:
- Update support for new PMIC hardware revision
- Minor bug fixes
2.0-r1
- U-Boot 2015.04 for the Digi ConnectCore 6 System-On-Module and SBC
- Linux kernel v3.14.57 for the Digi ConnectCore 6 System-On-Module and SBC
- Release based on Yocto 2.0 (Jethro) for Digi ConnectCore 6 SBC including:
- Bluez5
- QT5 (over X11 and Framebuffer graphical systems)
- New toolchain based on GCC-5.2 and GLIBC-2.22
- Cellular support
- 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
- Updating from a microSD card is not supported, only from local partitions (e.g. the 'update' partition) or from external USB memory devices.
- 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.
- In the device, run the command 'sysinfo'. This generates the following file: /tmp/.txt.gz.
- Attach the .txt.gz file to your support ticket.