NEW  We're currently migrating our content to a new developer website.
You are visiting the archived website. Click here to go to the new version!
Toradex Developer Center
 
Search by Tags
Software

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.

Get Updates
View All Submitted (open) Released (closed)
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-736FixedDefine Standard Rootfs Mount Behaviour and OptionsColibri iMX7, Apalis iMX6, Colibri iMX6, Colibri VF50, Colibri VF61, Apalis TK1, Colibri T20, Colibri T30, Apalis T30Bootloader, FlashMediumNo

Description: The kernel does not know about rw,noatime. The string rw by itself is valid, and to pass additional arguments rootflags=noatime can be used. The kernel mounts ext3/ext4 file systems by default ro, hence so far the kernel mounted the rootfs read-only. The init manager systemd then remounts the rootfs after file system checking. This makes sense and does not add measurable boot time. Let the kernel explicitly mount ro on block device based rootfs. The root mount flag noatime is only relevant when re-mounting read-write, hence it needs to be present in /etc/fstab. UBIFS used on raw NAND devices has no user space file checking, hence there is no value to mount it in read-only first. Also mount time for UBIFS is larger, and mounting first read-only and then read-write has higher boot time (300ms, likely due to missing block cache). Let the kernel explicitly mount rw on raw NAND based rootfs. UBIFS has no atime support, hence no root mount flags needed.

Workaround: The change to initially read-only mounted root file system on Apalis TK1 requires the U-Boot emmcargs environment variable to be adjusted to run NVIDIA's JetPack resp. L4T as documented here: http://developer.toradex.com/knowledge-base/installing-nvidia-jetpack-with-l4t-on-apalis-tk1#Flashing_Latest_Boot_Loader
 
 
Subscribe to changes on the Developer Center 
 
Toradex AG | Ebenaustrasse 10 | CH-6048 Horw | Switzerland | T: +41 41 500 4800 | info@toradex.com
Copyright © 2024