Go to file

Gabriel Valcazar 8ec2635654 wpewebkit: add workaround to improve memory usage in ConnectCore Demo app Even though we launch said demo with WebKit's page cache disabled, WebKit still caches most of the demo's contents for two reasons: * The demo is browsed using a non-HTTP(S) protocol (file://) * The demo is contained within the same domain (same-site browsing) This can lead to unexpected behavior on platforms with small RAM size. Add a workaround to force WebKit to create a new web process everytime we open a page on the demo, deleting the previous process and freeing its memory. An alternative solution would be to alter our demo to make sure a page's resources are correctly freed when exiting said page, but this provides a general solution that ensures memory cleanup in all cases, albeit with slightly longer loading times. https://onedigi.atlassian.net/browse/DEL-9498 Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>		2025-04-08 12:13:32 +02:00
meta-digi-arm	linux-dey-6.6: add RT functionality to NXP platforms	2025-04-07 11:03:50 +02:00
meta-digi-dey	wpewebkit: add workaround to improve memory usage in ConnectCore Demo app	2025-04-08 12:13:32 +02:00
scripts	Update Digi Copyright header	2024-07-15 09:28:58 +02:00
sdk	mkproject: add build support for ccimx8m platforms	2025-03-19 10:26:06 +01:00
README.md	README: add missing CC93 P/Ns to supported platforms	2025-03-14 09:39:19 +01:00

Digi Embedded Yocto (DEY) 5.0

Release 5.0-r2

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

Digi Embedded Yocto 5.0 is based on the Yocto Project(TM) 5.0 (Scarthgap) 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

TODO

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 fail to join autonomous groups.

ConnectCore 93 System-on-Module (SOM)
- Trustfence
  - It is not possible to close a device using U-Boot v2024.04 for Secure boot on a device with CPU revision A0. However, it is possible to boot v2024.04 signed images on an already closed device.

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.