Search by Tags

BSP Layers and Reference Images for Yocto Project Issue Tracker

 

The following table contains known issues, scheduled bug fixes, and feature improvements for the Toradex BSP Layers and Reference Images for Yocto Project.

The tickets are split into two major states:

  • Submitted (open): new features and bug fixes for BSP versions that have not yet been released. They may be scheduled for a specific release version; not planned; or in our backlog. All of them have one of the following states:
    • Known Issue: a bug or unexpected behavior that has been reported and is pending a fix. Once fixed, the status will transition to Fixed.
    • Feature Request: a new feature that may be added to a future release. Once released, the status will transition to New Feature.
  • Released (closed): new features and bug fixes for BSP versions that have already been released. All of them have one of the following states:
    • Fixed: a bug that has been fixed and released.
    • New Feature: something that didn't exist before and was added to a new release.


Any schedules are not guaranteed but reflect the current planning. The planning could be shifted due to priority changes.

Issues that are scheduled for a specific version will be integrated into the mentioned version of the BSP.

We will update this table continuously in order to always provide the latest state of our development plan. Please see also the Linux Support Strategy to learn more about the different releases.

Clear Filter
Issue #StatusSubjectModuleSubsystemWinCE OSSeveritySubmitted for Mainline

6.3.0 (Release date: 2023-07-10)
Embedded Linux BSP Q2 2023 Quarterly Release.
ELB-5034FixedPCIe/Wi-Fi/BT Interface Is Not Working ReliablyApalis iMX8Bluetooth, PCIe, Wi-FiLowNo

Description: PCIe devices, including Wi-FI, are not always detected at boot, failure rate is about 5%.

6.0.0 (Release date: 2022-10-01)
Embedded Linux BSP Q3 2022 Quarterly Release. Learn more on https://www.toradex.com/news/bsp-layers-reference-images-yocto-project-6-0-0-quarterly
ELB-4505New FeatureUpdate Bluez-Alsa to Version 4.0Apalis iMX8, Colibri iMX6ULL, Colibri iMX8X, Verdin iMX8M Mini, Verdin iMX8M PlusBluetoothNo

Description: Updated bluez-alsa package to version 4.0.

5.3.0 (Release date: 2021-07-08)
Embedded Linux BSP Q2 2021 Quarterly Release. Learn more on https://www.toradex.com/news/bsp-layers-reference-images-yocto-project-5-3-0-quarterly
ELB-3965FixedBluetooth Connection not workingApalis iMX8, Apalis iMX8X, Colibri iMX8X, Verdin iMX8M Mini, Verdin iMX8M PlusBluetoothLowNo

Description: Bluetooth pairing works but connection is not working

Workaround: CONFIG_BT_RFCOMM=m CONFIG_BT_RFCOMM_TTY=y

5.0.0 (Release date: 2020-10-06)
Initial Dunfell Q3 2020 Quarterly Release. Learn more on https://www.toradex.com/news/bsp-layers-reference-images-yocto-project-5-0-0-quarterly
ELB-2732New FeatureOn-module Bluetooth SupportApalis iMX8BluetoothNo

Description: Support on-module Bluetooth

Not Planned
ELB-5016Known IssueFailed to start discovery: org.bluez.Error.NotReadyApalis iMX8BluetoothLowNo

Description: It's possible that starting BT scans fails with error "Failed to start discovery: org.bluez.Error.NotReady"

Workaround: Just retry the command.

ELB-4966Known IssueKernel Error: `Bluetooth: hci0: unexpected event for opcode 0x0000`Apalis iMX8, Colibri iMX8XBluetooth, KernelLowNo

Description: During the initial boot the kernel might print some error on hci interface, `Bluetooth: hci0: unexpected event for opcode 0x0000`.

Workaround: No known issues because of that, bluetooth is just working fine afterward, just ignore the message.

ELB-2306Feature RequestBluetooth audio supportApalis iMX8, Colibri iMX6ULL, Colibri iMX8X, Verdin iMX8M Mini, Verdin iMX8M PlusBluetooth, Digital AudioNo

Description: Add support for Bluetooth audio

Backlog
ELB-5035Known IssuePCIe Wi-Fi/BT Not Properly Initialized at Boot (<0.5% time)Apalis iMX8, Colibri iMX8XBluetooth, Wi-FiLowNo

Description: It is possible that the Wi-Fi/BT interface is not properly detected at boot time with the following error message: `FW failed to be active in time`