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.2.0 (Release date: 2023-03-31)
Embedded Linux BSP Q1 2023 Quarterly Release. Learn more on https://www.toradex.com/news/bsp-layers-reference-images-yocto-project-6-2-0-quarterly
ELB-4989FixedNAND Bad Block Table Is Corrupted At Every BootColibri iMX7, Colibri T20, Colibri VF50, Colibri VF61Flash, KernelLowNo

Description: The NAND bad block table is getting corrupted at every boot because of a configuration mismatch between U-Boot (using OOB data for bad blocks) and Linux (using an in-band table at the end in the last 2 NAND blocks). This could potentially cause data loss in case a bad block is reused and the error is not recoverable with ECC.

Workaround: Set `CONFIG_SYS_NAND_USE_FLASH_BBT=y` in U-Boot configuration.

5.7.2
Upcoming Embedded Linux BSP 5.7 First Maintenance Release
ELB-4989Known IssueNAND Bad Block Table Is Corrupted At Every BootColibri iMX7, Colibri T20, Colibri VF50, Colibri VF61Flash, KernelLowNo

Description: The NAND bad block table is getting corrupted at every boot because of a configuration mismatch between U-Boot (using OOB data for bad blocks) and Linux (using an in-band table at the end in the last 2 NAND blocks). This could potentially cause data loss in case a bad block is reused and the error is not recoverable with ECC.

Workaround: Set `CONFIG_SYS_NAND_USE_FLASH_BBT=y` in U-Boot configuration.