Go to file

David Escalona 1ec5cc172c meta-digi-dey: crank-demos: fix crank demo for CCMP15 Crank demo was not working on CCMP15 devices due to several changes on weston service and the user launching it. This commit makes several fixes to make the demo to work again: - Add 'DEMO_USER' parameter to determine which user will launch the demo. Update recipe and start script accordingly. - Add 'DEMO_DISPLAY' parameter to determine the display that will be used to launch the demo. Update recipe and start script accordingly. - Parameterize the name of the Weston service after which the demo must be started. Update recipe and service file accordingly. - Give Crank engine read and execution permissions so the engine can be started by any user. - Add new method to the demo start script to wait until Wayland is fully setup before actually starting the demo. Signed-off-by: David Escalona <david.escalona@digi.com>		2022-10-25 18:09:27 +02:00
meta-digi-arm	ccmp1: remove usage of $singlemtdsys variable	2022-10-25 16:57:02 +02:00
meta-digi-dey	meta-digi-dey: crank-demos: fix crank demo for CCMP15	2022-10-25 18:09:27 +02:00
scripts	scripts: add dey-aws-tool script	2017-07-05 13:43:28 +02:00
sdk	build.sh: add core-image-base for ccimx6ulsbc	2022-10-19 14:00:29 +02:00
README.md	meta-digi: update README.md file for DEY-4.0	2022-07-20 16:55:31 +02:00

Digi Embedded Yocto (DEY) 4.0

Release 4.0-r1

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 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.