This is a list of known issues and limitations for Digi Embedded Yocto 4.0-r7:

  • Firmware update

    • The software update package must be located in the root level of the update media (subfolders are not yet supported).

    • To update from dey-3.2 version or lower to dey-4.0-r7 on a single boot layout, you must flash the recovery partition with the latest Yocto release before performing the firmware update.

  • ConnectCore Cloud Services

    • Remote file system management only supports names and paths up to 255 characters.

  • Recipes with large downloads may fail during fetch operation due to timeout.

    Bitbaking an image recipe implies downloading and building the source code of all the recipes that form part of the root file system, which takes several hours the first time. Some source code repositories, such as the Linux kernel, represent a large download that might time out and make your build process fail. If this happens, run the following command to just fetch the source code of the offending recipe separately (to dedicate all CPU resources to it):

    $ bitbake -k --runall=fetch <image-recipe>

    When this task finishes successfully (you may need several retries), you can proceed to build your image recipe. Do the same with any recipe that fails with a timeout during the fetch operation.

ConnectCore 6UL SOM

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

    • The QCA6564 wireless chip does not support Wake On Wireless LAN.

    • For P2P connections, Digi recommends "Negotiated GO" modes. The ConnectCore 6UL fails to join autonomous groups.

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