BSP Layers and Reference Images for Yocto Project Issue Tracker

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.

Description: Support Iris 2.0 LVDS converter.

Description: On the Colibri VF50, VF61, T20, T30 and Apalis T30 we will continue maintaining our long-term supported (LTS) BSP 2.8. We are providing updates when there are any HW changes on those platforms, and we will regularly provide critical bug fixes.

Workaround: BSP 2.8 Long Term Support

Description: Update OpenSSL to version 1.1.1d

Description: The 2.8 stable release contains all changes up to 2.8b6.

Description: iptables -L is not supported by our default Linux kernel configuration.

Workaround: A custom Linux Kernel compilation with correct configuration can solve the issue. The correct Linux kernel configuration is e.g. described here:
https://wiki.gentoo.org/wiki/Iptables

Description: Touchscreen with 7" Capacitive Touch Display does not work when used on an Aster carrier board with a Colibri T20/T30 module.

Description: Generating a legacy update media using Debian Stretch and subsequently updating an Apalis TK1 failed during mounting the root file system.

Workaround: We recommend using the Toradex easy installer on platforms where it is supported. For the legacy update procedure, the easiest is to use one of the supported distributions:
https://developer.toradex.com/knowledge-base/board-support-package/openembedded-(core)#Prerequisites
Other distributions may have the option metadata_csum enabled per default for mkfs.ext4 (Debian Stretch, Arch, ...). This option is not supported on Linux kernels below 3.18 and generates a kernel panic during boot after the legacy update. As a workaround, one can disable this option in /etc/mke2fs.conf before executing the update.sh script. The ext4 man page also has a list of options with their corresponding supported kernels, which may be helpful to refer to in case of legacy update attempts on more exotic systems.

Description: Image features (e.g. tools-debug or others documented at https://www.yoctoproject.org/docs/2.2/ref-manual/ref-manual.html#ref-features-image) do currently not work with the console-tdx-image. The reason is that the image is inheriting from image as opposed to core-image.

Workaround: You may use core-image instead but it might have additional effects.

Description: Allow using MXM or SODIMM pin numbers to get or set GPIOs. This also allows for easier code porting from one to another Toradex module.

Description: Our Yocto Project layer readmes may not be up-to-date.

Workaround: Make sure to use valid combinations e.g. as available as tagged repo meta data:
http://git.toradex.com/cgit/toradex-bsp-platform.git

Description: Building 2.8b2 and earlier fails on Ubuntu 18.04 LTS.

Workaround: It works on Ubuntu 16.04 LTS.

Description: Installing a single backport kernel module to an image at build time fails (e.g. by using IMAGE_INSTALL_append in local.conf).

Workaround: Install all backport kernel modules by using the "backports" package.

Description: OE-Core layer did backport more package splits in the linux-firmware recipe. Due to this the HEAD of the morty branch clashes now with a similar split we did in meta-toradex-bsp-common resulting in a fatal QA error. (Compare with commit 0eaef98) ERROR: linux-firmware-1_0.0+gitAUTOINC+bf04291309-r0 do_package: QA Issue: linux-firmware-sd8887 is listed in PACKAGES multiple times, this leads to packaging errors. [packages-list]

Workaround: Delete the lines PACKAGES_prepend = "\ ${PN}-sd8887 \ " from meta-toradex-bsp-common/recipes-kernel/linux-firmware/linux-firmware_%.bbappend

Description: The scrot recipe source is 404.

Description: When building 2.8b1 building stress fails with "ERROR: stress-1.0.4-r0 do_fetch: Fetcher failure for URL: 'http://people.seas.harvard.edu/~apw/stress/stress-1.0.4.tar.gz'. Checksum mismatch!".

Workaround: Use 2.8b2 or remove the stress recipe under "meta-toradex-demos/recipes-support/stress/stress_1.0.4.bb" (this will use a fixed version of stress in openembedded-core/meta/recipes-extended/).

Description: Currently we use an LXDE/GTK+ based desktop for our demo images targetting modules which provide enough storage. Moving this to a LXQt/Qt5 based desktop. This aids customers who want to start developing a Qt5 based application.

Description: Currently, we use an init script which starts X directly and then a Qt demo application. This has some drawbacks, e.g. when one wants to start a touch calibration or the likes. Use some readily available X startup system, e.g. xinit as a better base customers can build upon.

Workaround: Please find a suitable systemd service in the following recipe:
http://git.toradex.com/cgit/meta-toradex-demos.git/tree/recipes-images/images/angstrom-qt5-x11-image.bb?h=rocko#n4

Description: On Apalis/Colibri T20/T30 both fchdir() and fstat() fail with EBADF when the file was previously opened with the O_PATH flag.

Workaround: Required patches have been backported to our downstream Linux kernel: http://git.toradex.com/cgit/linux-toradex.git/log/?h=tegra-next

Description: As per amendment to http://developer.toradex.com/knowledge-base/toradex-software-versioning-convention

Description: Update to the OpenEmbedded Rocko resp. Yocto Project 2.4 release.

Description: Add a -v parameter to fw_printenv/fw_setenv which outputs the U-Boot source version information.

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

Description: Support forcing U-Boot's 'cfgblock create' command to overwrite an existing config block e.g. using a -y parameter and therefore not prompting the user for easier scripting.

Description: Currently various things may fail or behave strangely on certain modules if the config block is missing. Unify that behaviour by e.g. rather not allowing use of any features (e.g. Ethernet, RNDIS) at all in this case.

Workaround: Use the 'cfgblock create' U-Boot command to restore the config block. Alternatively we implemented similar functionality into our Toradex Easy Installer.

Description: Add support for Capacitive Touch Display 7" Parallel V1.0A.

Description: Using ACL with ubifs seems to increase the likelihood of filesystem corruption. Since ACL is an optional features and unlikely necessary on an embedded system switch ACL off.

Description: We changed our versioning scheme. Our BSP demo image packages are now e.g. called Apalis-iMX6_LXDE-Image_2.7b2-20170410.tar.bz2. The Linux kernel will report e.g. the version number 4.1.39-2.7.2+gba2f75f and U-Boot will report e.g. 2016.11-2.7.2+g60021a4. Details about the versioning can be found here: https://developer.toradex.com/knowledge-base/toradex-software-versioning-convention

Description: Colibri T20 modules may draw more power be it during regular operation or in suspend.

Workaround: This issue is related to the 'Module May Hang During Boot if HDMI is not Connected' one whose fix can be found on the tegra-next branch of our linux-toradex Linux kernel repository: http://git.toradex.com/cgit/linux-toradex.git/log/?h=tegra-next

Description: Recently Ångström switched to using the gcc 6 compiler in their 2016.12 aka morty branch. Update meta-angstrom to latest in order for us to also make use of the Linaro gcc 6 compiler.

Description: Most of our SoC have a manufacturer defined unique and not alterable number. It's documented here: http://developer.toradex.com/knowledge-base/soc-unique-id-linux

Description: Configure optimised MMC read-ahead.

Workaround: Manually set /sys/block/mmcblk0/queue/read_ahead_kb.

Description: The X22 pinout changed on the latest Colibri Evaluation Board V3.2. Showing the latest information is desirable as that is what a customer gets shipped if ordered now.

Description: Updates our downstream U-Boot to 2016.11. This also includes a newer UBI/UBIFS stack which fixes issues such as "Error reading superblock on volume 'ubi0:rootfs' errno=-22" when using UBI fastmap in U-Boot.

Description: In later OE versions the default SSH config changed so that X11 forwarding is not allowed. $ ssh -X root@192.168.10.185 X11 forwarding request failed on channel 0

Workaround: Edit /etc/ssh/sshd_config to include X11Forwarding yes

Description: Newer distros like e.g. Fedora 24 use GCC version 6 as the host (native) toolchain. Our jethro based Yocto project build is not able to build the needed native tools, among them the cross compiler on such distros.

Workaround: Use a lightweight container with an older distro as documented on our developer website.

Description: Further U-Boot distro boot integration would allow booting off regular ARM distro's SD cards or USB mass storage devices aka memory sticks.

Description: As OE moves to GCC-6 we should provide our NVIDIA Kernel sources in a way that they can be built with gcc 6. This would allow customers taking our BSP and using it with a later Yocto project release.

Description: Separate the 'one size fits all' meta-toradex layer into BSP layers by SoC vendor and a software layer for the demo images.

Description: Add support for the LM Technologies LM006 Wi-Fi USB dongle to our standard images.

Description: Upon boot after a watchdog reset the U-Boot boot loader gets stuck in SPL. Only a full power-cycle will recover the system.

Workaround: Our stable Embedded Linux BSP V2.3 from 20150320 does not exhibit this issue.

Description: Mountpoint names are different when mounted at boot vs. mounted at runtime / with diskutility.

Workaround: None.

Description: Currently when disabling the HDMI display controller by specifying the modedb option 'video=tegrafb1:off' from within U-Boot as Linux kernel boot argument the Tegra X driver complains with 'failed to initialize the display controller library' and refuses to start X at all.

Workaround: As a workaround one can remove the HDMI display controller's device node 'rm /dev/tegra_dc_1' and restart LXDM 'systemctl restart lxdm' from within Linux.

Description: Audio capture can stall causing stutter in captured stream.

Workaround: None. Await for update to driver.

Description: Provide proper vidargs for mainline 5.4 in BSP 4.0.0

Description: There may be a boot error reported concerning "commit machine-id". This is caused by an incompatibility between later systemd version and the downstream NVIDIA L4T R16.5 based Linux kernel 3.1.10. However, no further adverse effect has been discovered.

Workaround: Running a mainline based Linux kernel does not exhibit this issue.

Description: For single antenna set single_rf=0x01

Description: Certain use-cases may cause UART input overruns.

Workaround: Disabling DMA may help but ultimately this got fixed in the Linux kernel 4.19.

Description: HDMI HDA resp. I2S audio may not work with certain screens depending on available display modes and pixel clock frequencies. HDMI HDA resp. I2S audio may also not work after hot-plugging.

Workaround: Make sure to use vidargs selecting a HDMI audio capable pixel clock frequency. Do not hot-plug resp. power-cycle after plugging in HDMI. If you keep having issues try another brand/model screen.

Description: On NAND flash based modules like the Colibri T20, the legacy update procedure depends on first loading the entire root file system image into RAM. If your custom image is significantly larger than our regular demo images it may no longer easily fit into 256MB of RAM, therefore, failing the legacy update procedure (it may just hang or even crash but definitely fails to update the root file system).

Workaround: Doing the following before 'run setupdate; run update' may help to a certain extend:
setenv fdt_addr_r 0x01000000
However, even bigger images may still fail requiring a different flashing strategy altogether (e.g. initially booting from an initrd or via NFS subsequently updating the root file system from within Linux on-the-fly.

Description: If one moves desktop icons in LXDE they are not redrawn automatically.

Workaround: Click anywhere on the desktop and the icons reappear at the position they have been moved to.

Description: Currently there is no suitable browser which fits in the LXQt recipe. Find a suitable browser and integrate it into the layers.

Description: The ath10k firmware for Qualcom Atheros QCA988x Wi-Fi devices is broken in BSP 2.8b1.

Workaround: Update resp. firmware in /lib/firmware/ath10k from latest linux-firmware git.

Description: An existing OE setup updated to 2.7b4 might show the following error: ERROR: devmem2-1.0-r7 do_populate_lic: QA Issue: devmem2: The LIC_FILES_CHKSUM does not match for file://devmem2.c;endline=38;md5=a9eb9f3890384519f435aedf986297cf This is caused by a file allready in your download directory.

Workaround: Execute the following: bitbake -c cleanall devmem2

Description: For unknown reason /etc/profile does not get properly sourced upon graphical login. Not only does the shell prompt look strange in a desktop terminal but fw_setenv also does not work as it is missing some configuration: When using fw_setenv from a modules desktop environment one gets an error indicating that the boot partition is not writable. sh-4.3# fw_setenv x z Write error on /dev/mmcblk0boot0: Operation not permitted Error: can't write fw_env to flash

Workaround: Revert to a serial terminal or just manually source /etc/profile which will also properly configure fw_setenv: sh-4.3# . /etc/profile root@apalis-t30:~#

Description: Unfortunately U-Boot's USB functionality may be rather limited.

Workaround: Usually using a different brand/model USB stick may prove working just fine. Alternatively USB SD card readers seem to work rather better.

Description: Certain USB memory sticks may not work reliably behind a USB hub. Please note that some (Apalis) if not all (Colibri) USB sockets on our evaluation boards are always behind an on-carrier USB hub.

Workaround: Switch to a different carrier board without an on-carrier USB hub like Iris or Ixora, try a different brand USB memory stick or revert to a completely different update media like an SD card.

Description: NVIDIA's downstream L4T kernel our BSPs are based on has issues with the ext4 file system.

Workaround: Use the ext3 file system instead.

Description: Temperature test on Colibri T20 uncovered UBI error when using bonnie++ with latest image.

Workaround: Use stable BSP V2.3 based on YAFFS2.

Description: On Aster, Orchid and Viola the USB power enable pin (SODIMM 129) is used for both USB ports USBC and USBH. For all modules but the Colibri iMX7S the Linux kernel controls the USB Power Enable only from the USBH port driver. Thus USBC will be non functional if used as a USB Host when the USBH port is disabled in the kernel (i.e. in the device tree for newer or in the platform data for older kernels). Note that on the Evaluation Board and on Iris the USB Power gets enabled when a USB OTG kabel gets connected.

Workaround: Do not disable the USBH port or change the kernel in a way that the USB Power Enable is controlled by the USBC port as well.

Description: Using a Linux logo be it the penguins or a custom one as e.g. explained at http://developer.toradex.com/knowledge-base/splash-screen-linux does not work on the HDMI output. When the kernel sets up the display driver it first sets up VGA resolution subsequently doing DDC/EDID and then sets the final resolution. While the Logo is drawn during the VGA resolution setting it is lost later on.

Workaround: On Apalis/Colibri iMX6 one may use the U-Boot splash screen on HDMI output as well.

Description: Capturing stereo audio inhibits audio fragments being swapped left/right at times.

Workaround: Use mono capture for now.

Description: Implement support for H.264 acceleration in web browser.

Description: The new Iris V2.0A carrier board allows to switch the power of the SD card interface. Add support for this to the BSP.