Digi
/
meta-digi
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
3,772 Commits 4 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
Tatiana Leon 8f92f634c3 meta-digi-dey: crank: crank-demos: add variables to set the tarballs SHA256 
As we are going to document how to build Crank images using our own recipes, we
need a way for customers to provide the sha256 of the engine and demos tarballs:

  * Storyboard Engines are not available as a compressed file, it is a directory
    available after the installation of the whole Storyboard software, next to
    Storyboard Designer, samples, and other resources. The installer is only
    available after filling a form and receiving an email with the link and a
    license key valid for 1 month.

    To use our 'crank-sbengine_7.2.bb' recipe, users must create the tarball
    from this directory and provide its path in the 'CRANK_ENGINE_TARBALL_PATH'
    and its sha256 in 'CRANK_ENGINE_TARBALL_SHA256'.

  * Regarding Storyboard applications, the included demo in the prebuilt image
    is not publicly available, but customers can use the same recipe to install
    their own applications.

    To use our 'crank-demos_7.2.bb' recipe, users must create a tarball with
    the exported application from Storyboard Designer and provide its path in
    the 'CRANK_DEMOS_TARBALL_PATH' and its sha256 in
    'CRANK_DEMOS_TARBALL_SHA256'.
    There are also other configurable parameters such as 'CRANK_DEMO_PATH' or
    'CRANK_DEMO_OPTIONS'.

The process of adding support to Crank Storyboard applications will be fully
documented as new topics.

Signed-off-by: Tatiana Leon <Tatiana.Leon@digi.com>
 		2022-11-17 10:09:02 +01:00
meta-digi-arm udev: fix RTC rule filename 2022-11-16 17:43:40 +01:00
meta-digi-dey meta-digi-dey: crank: crank-demos: add variables to set the tarballs SHA256 2022-11-17 10:09:02 +01:00
scripts usb_driver: add a script to install Cypress usb driver 2022-10-26 11:30:46 +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

README.md

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.

Tested OS versions

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

  • Ubuntu 18.04

Supported Platforms

Software for the following hardware platforms is in production support:

ConnectCore 6UL

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

4.0-r1

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