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

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: http://developer.toradex.com/software/linux/linux-software/release-details?view=all&issue=27678
ELB-720FixedParallel RGB Display and/or SD Card May Not Work Reliably on Latest ModulesColibri iMX7CAN, Device Tree, GPIO, Graphics, RGB, SDIO/SD/MMCLowNo

Description: Note: This is only an issue for Colibri iMX7S 256MB V1.1C and Colibri iMX7D 512MB V1.1D and later modules.
As it turns out not using LDO2 anywhere at all in the regular case is a bad idea leading to the following:
[ 2.317688] LDO2: disabling
Of course display and SD card still worked on the EvalBoard due to back feeding through some pull-ups however on Viola with just one pull-up it failed once both display and SD card were active...
Currently without an SD card inserted the regulator framework actually powers the LDO2 off however e.g. the BL_ON pin is also on that same rail!

Workaround: The following fixes were integrated:
http://git.toradex.com/cgit/linux-toradex.git/commit/?h=toradex_4.1-2.0.x-imx&id=0284f779bba00b930bd9bb12703e2092478531c7
http://git.toradex.com/cgit/linux-toradex.git/commit/?h=toradex_4.1-2.0.x-imx&id=ac8dcd0d7b7d17ad8ac42b42cb1f51d4417f4950
Fix this by specifying LDO2 to be always on and use the regular 3.3V supply from the carrier board as the vmmc-supply.
Specify that carrier board 3.3V supply to be always on as well to avoid the following misleading message during boot:
[ 2.299654] 3.3V: disabling
One remaining issue is that now in suspend LDO2 is still powered and even adding the following did not help:
regulator-state-mem {
    regulator-off-in-suspend;
};
Further investigation pending.