Go to file

Gabriel Valcazar 44ad42551a cryptoauthlib: use digi-embedded github mirror The commit we use to build the cryotpauthlib package is currently not part of any branches or tags in the original MicrochipTech repo. To make sure the package can always be built, use our mirror of the repo, which includes an additional branch for the specific commit. While at it, move the "nobranch=1" parameter to the GIT_URI variable, since we're putting all other git parameters there, anyway. Also, remove the "branch" parameter because it isn't needed in this case. https://onedigi.atlassian.net/browse/DEL-8015 Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>		2023-04-17 17:55:36 +02:00
meta-digi-arm	cryptoauthlib: use digi-embedded github mirror	2023-04-17 17:55:36 +02:00
meta-digi-dey	update URL of NXP recipes from codeaurora to Github	2023-04-03 11:53:49 +02:00
scripts	usb_driver: add a script to install Cypress usb driver	2022-10-26 11:30:46 +02:00
sdk	build.sh: add dey-image-qt for ccmp15-dvk	2023-03-17 12:26:56 +01:00
README.md	README: fix cc6ul supported platforms	2023-03-22 17:11:02 +01:00

Digi Embedded Yocto (DEY) 4.0

Release 4.0-r2

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

Digi Embedded Yocto 4.0 is based on the Yocto Project(TM) 4.0 (Kirkstone) release.

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

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

Software for the following hardware platforms is in production support:

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

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 MP1 System-on-Module (SOM)
- Wireless
  - P2P on the ConnectCore MP1 doesn't currently work in concurrency with other modes (station or SoftAP).
- The following features are not yet supported:
  - TrustFence

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.

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.