Go to file

Hector Palacios eb49d927a5 trustfence: enable auth capabilities on TF-A independently of TRUSTFENCE_SIGN Sometimes, it may be desired that the DEY project does not sign the artifacts, for example, if they are going to be externally signed on a secure server. In this case, the user sets TRUSTFENCE_SIGN="0". On STM platforms, all the variables were being set if TRUSTFENCE_SIGN="1" and authentication support is not enabled on TF_A otherwise. Set TF_A_SIGN_ENABLE (which adds authentication support to TF_A) always for STM platforms (as long as the project inherits the trustfence class) and set FIP_SIGN_ENABLE="0" if its sibling TRUSTFENCE_SIGN="0", so that DEY doesn't sign the FIP image either. Signed-off-by: Hector Palacios <hector.palacios@digi.com>		2023-05-10 17:33:23 +02:00
meta-digi-arm	tf-a-stm32mp: obtain password to use during FIP image signing process	2023-05-10 17:33:23 +02:00
meta-digi-dey	trustfence: enable auth capabilities on TF-A independently of TRUSTFENCE_SIGN	2023-05-10 17:33:23 +02:00
scripts	usb_driver: add a script to install Cypress usb driver	2022-10-26 11:30:46 +02:00
sdk	meta-digi: cosmetic, delete machine variants dead code	2023-05-05 14:39:34 +02:00
README.md	meta-digi-dey: bump distro version to 4.0-r3	2023-03-31 11:15:31 +02:00

Digi Embedded Yocto (DEY) 4.0

Release 4.0-r3

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.