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.6.0 (Release date: 2024-03-31)
Upcoming Embedded Linux BSP Q1 2024 Quarterly Release
ELB-5683Known IssueM.2 And mPCIe (USB) Cards Not WorkingVerdin AM62GPIO, PCIe, USBLowNo

Description: Verdin PCIE_1_RESET# (PERST#) line stays asserted on the AM62, which can cause problems with USB LTE modems connected to the mini PCIe connectors of our carrier boards.

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

5.6.0 (Release date: 2022-03-31)
Embedded Linux BSP Q1 2022 Quarterly Release. Learn more on
ELB-4299FixedWrong PCIe PERST# Startup SequenceVerdin iMX8M MiniPCIeLowNo

Description: The PCIe initialization on the Verdin IMX8MM doesn't respect the required PCIe PERST# start-up sequence, PERST# is de-asserted too early.

ELB-1986New FeaturePCIe SupportVerdin iMX8M MiniPCIeLowNo

Description: PCIe tested working and documented

5.5.0 (Release date: 2022-01-03)
Embedded Linux BSP Q4 2021 Quarterly Release. Learn more on
ELB-4224FixedPCIe Not WorkingVerdin iMX8M MiniPCIeLowNo

Description: Bring-up of PCIe fails with a PCIe PLL lock timeout at boot.

Workaround: Use BSP 5.2.0.

ELB-3370New FeatureFeature Set: Linux: PCIeVerdin iMX8M PlusPCIeNo

Description: Add support for PCIe on Verdin iMX8M Plus V1.0B.

5.1.0 (Release date: 2020-12-30)
Dunfell Q4 2020 Quarterly Release. Learn more on
ELB-3428FixedPCIe Not WorkingApalis iMX8XPCIeLowNo

Description: Make sure PCIe works for 5.4.x-2.1.0 kernel.

Deferred release. See more at
ELB-1929Feature RequestPCIe SupportApalis iMX8XPCIeLowNo

Description: PCIe does not work on V1.0 PCBs.

Workaround: none

3.0b3 (Release date: 2019-12-31)
This release supports Verdin iMX8M Mini, Apalis TK1, Apalis iMX6, Apalis iMX8, Colibri iMX6, Colibri iMX6ULL, Colibri iMX7 and Colibri iMX8X. Learn more on
ELB-1685New FeaturePCIe SupportApalis iMX8PCIeLowNo

Description: Add support for PCIe

2.8b4 (Release date: 2018-10-05)
ELB-1005FixedApalis TK1 PCIe Gigabit Bring-up Issue in MainlineApalis TK1Ethernet, PCIeLowNo

Description: Forward ported commit 7ad9771527d2 ("apalis-tk1: fix PCIe reset for reliable gigabit Ethernet operation") was never validated. Turns out it does not work and may lead to PCIe gigabit bring-up issues.

2.8b3 (Release date: 2018-06-27)
ELB-944FixedRegression: PCI Express Failing to Enumerate on Apalis iMX6Apalis iMX6Kernel, PCIeLowNo

Description: While BSP 2.8b1 enumerated PCIe on the Apalis evaluation board just fine BSP 2.8b2 may fail with the following error message:
busn_res: can not insert [bus 02-01] under [bus 01] (conflicts with (null) [bus 01])

Workaround: As a workaround you may just revert the following offending commit for now:

ELB-869FixedPCIe Enumeration in U-Boot FailingApalis TK1Bootloader, I2C, PCIe, Power ManagementLowNo

Description: PCIe enumeration aka "pci enum" U-Boot command may fail in U-Boot due to some I2C/Power management issue.

2.8b2 (Release date: 2018-03-31)
In this release we switched to the generic compressed Kernel image type (zImage) instead of the legacy U-Boot specific uImage format. This could lead to non booting modules if a previously saved U-Boot environment is still set to uImage. Please see the following issue for more details:
ELB-789FixedDisable ASPM on TK1 to Increase PCIe Device CompatibilityApalis TK1PCIeLowNo

Description: Adding pcie_aspm=off to kernel cmdline may fix problems with PCIe cards on Apalis TK1.

2.7b4 (Release date: 2017-10-05)
In this release we changed to use Ext4 file system by default. This could lead to non booting modules if a previously saved U-Boot environment is set to non-ext4. Please see the following issue for more details:
ELB-740FixedPotential Gigabit Ethernet resp. PCIe InstabilityApalis TK1Bootloader, Ethernet, Kernel, PCIeLowNo

Description: So far in U-Boot we violated the PCIe reset timing specification and in Linux we did not do anything about doing the PCIe reset unisono with the separately switchable voltage rail of the gigabit Ethernet chip.

Workaround: A solution to the U-Boot side of things may be found on our -next branch now.

V2.7 Beta 1 (Release date: 2017-01-13)
Known Issue for Colibri VF61: U-Boot 2016.11 Missing m4boot Command.
ELB-511FixedPCIe Clock and Reset May not Conform to SpecificationApalis T30PCIeLowNo

Description: Our current PEX 8605 errata workaround violates the PCIe clock and reset specification should no PCIe switch be present as e.g. the case on Ixora.

V2.6.1 Beta 2 (Release date: 2016-11-22)
This is a release for Apalis TK1 2GB V1.1A only. The January 2017 release supporting all platforms (iMX6, iMX7, VFxx, T20, T30, TK1) will follow later as V2.7 Beta 1.
ELB-570FixedPCIe Clock and Reset May not Conform to SpecificationApalis TK1PCIeLowNo

Description: Our current PEX 8605 errata workaround violates the PCIe clock and reset specification should no PCIe switch be present as e.g. the case on Ixora.


V2.6 Beta 1 (Release date: 2016-03-31)
ELB-337New FeaturePCIe Not WorkingApalis iMX6PCIeLowNo

Description: While on the Apalis Evaluation board the PCIe switch as well as plugged-in (mini-)PCIe cards usually get detected actual operation may fail.
On Ixora PCIe may fail due to a device reset/initialisation timing issue.

V2.3 Beta 2 (Release date: 2014-09-03)
ELB-227FixedPCIe and with it Gigabit Ethernet Rarely Unavailable after BootApalis T30Ethernet, PCIeLowNo

Description: PCIe is rarely unavailable after Boot on the Apalis T30 module indicated by the following kernel message(s) during boot: 'PCIE: port 0: link down, ignoring', 'PCIE: port 1: link down, ignoring' and/or 'PCIE: port 2: link down, ignoring'. Gigabit Ethernet is also affected by this issue as its controller chip is connected through PCIe indicated by the following missing kernel message during boot: 'igb 0000:01:00.0: Intel(R) Gigabit Ethernet Network Connection' resp. 'igb 0000:07:00.0: Intel(R) Gigabit Ethernet Network Connection'. We are working together with NVIDIA to solve this issue as it seems to be a hardware issue of the PCIe controller in the T30 SoC.

Workaround: Currently the only thing known to help is power-cycling or sometimes also doing a reset. As the issue is probably dependant on operating conditions such as temperature varying this might also help. We are working together with NVIDIA to find a good software workaround for this issue.

Not Planned
ELB-4835Known IssuePCIe Not Reliable On Suspend/ResumeApalis iMX6Kernel, PCIe, Power ManagementLowNo

Description: Multiple issues can be experiences on suspend/resume when PCIe is used, PCIe device might no longer work after resume and the kernel might have errors (`Unhandled fault`)

ELB-4083Known IssueStop PCIe Endpoint Results in WarningApalis iMX6, Apalis iMX8, Apalis iMX8X, Verdin iMX8M Mini, Verdin iMX8M PlusPCIeLowNo

Description: After an endpoint is started through configfs, if 0 is written to the configfs entry 'start', the controller stops but the epc_group->start value remains 1. A subsequent unlinking of the function from the controller would trigger a spurious WARN_ON_ONCE() in pci_epc_epf_unlink() despite right behavior.


ELB-2791Known IssueApalis iMX8X Sometimes Does Not Boot When PCIe is EnabledApalis iMX8XLowNo

Description: On Apalis iMX8X with PCIe enabled we see the module does rarely unexpectedly stop booting.

Workaround: Disable PCIe in devicetree.

ELB-2504Feature Request[U-Boot] PCI / PCIe related dts issues/cleanupApalis T30, Apalis TK1BootloaderNo

Description: U-Boot maintainer is adding new checks for the format of PCI/PCIe nodes in DTs, which will bring mainline U-boot slightly closer to being in-line with current Linux kernel mainline. See reference at Toradex will sync with the mainline Linux device tree PCI nodes.

ELB-2106Feature RequestPCIe SupportApalis iMX6PCIeNo

Description: Validate support for PCIe

ELB-1351Known IssuePCIe fails randomlyApalis iMX8PCIeLowNo

Description: Currently, PCIe fails. Often with a kernel OOPS backtrace.

Workaround: On the Apalis Evaluation Board, remove the jumper for GPIO7 keeping the PCIe switch in reset.

ELB-851Known IssueRESET_MOCI is Kept in Reset Until Linux Probes PCIe DriverApalis iMX6, Apalis TK1Bootloader, RGB, USBLowNo

Description: U-Boot does not de-assert the RESET_MOCI signal. RESET_MOCI needs to be pulled during PCIe driver initialization sequence. In order to not reset again during Linux boot we do not de-assert RESET_MOCI in the bootloader. Due to this all components on the carrier board connected to RESET_MOCI are kept in their reset state too. On the Evaluation Board that is notably the USB Hub and a display connected to the Unified Interface Display Connector.

Workaround: One may release RESET_MOCI in the bootloader code if needed. During Kernel boot RESET_MOCI will be asserted again for 100ms during PCIe initialization.

ELB-747Known IssueApalis TK1 Linux Kernel Fails to Boot With pci=nomsi Command-Line OptionApalis TK1PCIeLowNo

Description: Adding pci=nomsi to kernel command line will prevent kernel from booting.

ELB-554Known IssueExar PCIe UART driver does not work on Apalis T30Apalis TK1, Apalis T30PCIe, UARTLowNo

Description: Exar PCIe UART driver backport (or official Exar driver) does not work on Apalis T30

ELB-433Known IssueSuspend/Resume does not Work with PCIeApalis iMX6PCIe, Power ManagementLowNo

Description: Suspend/Resume does not work if a PCIe device has been found. e.g. if 'lspci' returns at least one device. Symptom is that resume blocks after all CPUs have been brought up.

[   76.698740] Enabling non-boot CPUs ...
[   76.703043] CPU1: Booted secondary processor
[   76.703366] CPU1 is up
[   76.710663] CPU2: Booted secondary processor
[   76.711040] CPU2 is up
[   76.718242] CPU3: Booted secondary processor
[   76.718603] CPU3 is up
Refer to:

ELB-290Known IssuePCIe GEN2 not Working on Apalis Evaluation BoardApalis iMX6, Apalis TK1PCIeLowNo

Description: PCIe GEN2 is currently not working with Apalis iMX6 and Apalis TK1 on the Apalis evaluation board.

Workaround: The mini-PCIe slot on Ixora is known to work also at GEN2 speeds.

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`

ELB-1306Known IssueSuspend does not work with PCIeApalis iMX8X, Colibri iMX8X, Apalis iMX8PCIeLowNo

Description: Suspend does not work with PCIe enabled

Workaround: Use "clk_ignore_unused" boot kernel option