Digi
/
meta-digi
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
4,844 Commits 3 Branches 0 Tags 196 MiB
C 32.9%
Shell 29%
BitBake 16.1%
TL-Verilog 9.9%
C++ 4.8%
Other 7.3%
Go to file
Gabriel Valcazar d595a2e3b5 connectcore-demo-example: restructure multimedia dependencies 
At the moment, we provide four versions of the connectcore demo package:

    * webkit + multimedia: we include this one in webkit images
    * webkit (no multimedia): used in cases where the platform supports webkit,
      but video/webgl performance isn't optimal
    * regular: only contains the demo server and basic assets, we include it in
      non-webkit images
    * regular + multimedia: contains the regular package plus video/webgl web
      content

This last version doesn't make a lot of sense because video/webgl content is
meant to showcase the target's VPU/GPU capabilities, and that can only be done
when running the demo on the target via webkit. Besides, even though we don't
include this version of the package in our default non-webkit images, the
runtime dependencies in the .inc file make bitbake generate the video-examples
and webglsamples packages during the image builds, even if they don't end up
in the final image. This is true even for platforms that don't support webkit,
such as the ccimx6ul, ccimx91 and ccimx93.

Initially, I tried making the -multimedia package exclusive to the webkit
recipe, but this causes its contents to be bundled with the base (regular)
package. To avoid this, define the -multimedia package in the .inc file, and
move its dependency with video-examples and webglsamples to the webkit recipe.
This way, the regular + multimedia version of the package still exists, but
it no longer causes bitbake to generate video/webgl packages when not needed.

Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
 		2025-01-07 16:10:33 +01:00
meta-digi-arm imx-digi-base.inc: Set generic tuning for i.MX8/i.MX9 2025-01-07 13:09:28 +01:00
meta-digi-dey connectcore-demo-example: restructure multimedia dependencies 2025-01-07 16:10:33 +01:00
scripts Update Digi Copyright header 2024-07-15 09:28:58 +02:00
sdk sdk: build.sh: only build dey-toolchain when building SDKs 2024-11-26 18:36:34 +01:00
README.md README.md: update to Yocto 5.0 (Scarthgap) 2024-10-17 13:03:17 +02:00

README.md

Digi Embedded Yocto (DEY) 5.0

Release 5.0-r1

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.

Tested OS versions

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

  • Ubuntu 20.04
  • Ubuntu 22.04

Supported Platforms

Software for the following hardware platforms is in production support:

ConnectCore MP25

ConnectCore 91

ConnectCore 93

ConnectCore MP13

ConnectCore MP15

ConnectCore 8M Mini

ConnectCore 8M Nano

ConnectCore 8X

ConnectCore 6UL

ConnectCore 6 Plus

ConnectCore 6

Installation

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

Documentation

Documentation is available online at https://www.digi.com/resources/documentation/digidocs/embedded/

Downloads

Release Changelog

5.0-r1

  • Release based on Yocto 5.0 (Scarthgap) including:
    • New toolchain based on GLIBC-2.39
    • Updated bluez5 to v5.72
    • Updated busybox to v1.36.1
    • Updated NetworkManager to v1.46.0
    • Updated gstreamer1.0 to v1.22.12
    • Updated OpenSSL to v3.2.3
    • 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.

  • 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 MP25

  • ConnectCore MP2 System-on-Module (SOM)
    • Power management
      • Power management support is not yet implemented.
    • Firmware update
      • Update single file and update with rdiff don't currently work.

ConnectCore MP15/MP13

  • ConnectCore MP1 System-on-Module (SOM)
    • Wireless
      • P2P on the ConnectCore MP1 doesn't currently work in concurrency with other modes (station or SoftAP).

ConnectCore 6UL

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

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.

  1. In the device, run the command 'sysinfo'. This generates the following file: /tmp/<current timestamp>.txt.gz.
  2. Attach the <current timestamp>.txt.gz file to your support ticket.