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: Qt 4 was first released in 2005 and has been unsupported since 2015. For our 3.0 (thud based) release we remove meta-qt4 from the installed layers and remove related image recipes.

Workaround: Forward port applications to use Qt 5.

Description: The following pinmuxing error may be seen during boot: [ 20.255028] vf610-pinctrl 40048000.iomuxc: pin VF610_PAD_PTB21 already requested by 40048000.iomuxc; cannot claim for spi1.0 [ 20.281777] vf610-pinctrl 40048000.iomuxc: pin-43 (spi1.0) status -22 [ 20.296277] vf610-pinctrl 40048000.iomuxc: could not request pin 43 (VF610_PAD_PTB21) from group can_int on device 40048000.iomuxc [ 20.324217] mcp251x spi1.0: Error applying setting, reverse things back

Workaround: Luckily, due to the pin already being muxed as a GPIO by means of hogging it still actually functions properly.

Description: Provide 5.4 based Backports for the i.MX 4.14-2.3.x Kernel to improve WiFi driver stability

Workaround: Compile a new 5.4 kernel

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

Description: We switched from CRDA to direct loading of the Wi-Fi regulatory domain database in-kernel.

Description: The touchscreen with 7" Capacitive Touch Display may not work well when used either on an Evaluation Board with the Capacitive Touch Adapter or on Aster or Ixora.

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: Modules with NANYA RAM chips assembled may rarely show timing issues leading to non-booting modules or otherwise unstable behaviour. We adjusted the on-die termination settings and fully validated & verified various modules in our temperature chambers.

Description: In OE we build the device trees listed in conf/machine/xxx.conf (build-time variable KERNEL_DEVICETREE) and put them into the image. In the update.sh script we currently also have a variable KERNEL_DEVICETREE with a list of what to put on the update media. We could patch update.sh in OE during image creation time, so that update.sh contains the list from conf/machine/xxx.conf rather than having to maintain that list in both places.

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

Workaround: It works on Ubuntu 16.04 LTS.

Description: When the UART without DMA (fsl_lpuart.nodma=1) overruns, the FIFO can get out of sync. Once out of sync, characters appear delayed only after new characters have been received.

Workaround: Reopen UART in case overruns have been detected (see /proc/tty/driver/fsl-lpuart). Use UART in DMA mode makes overruns less likely to occur and seems not to suffer issues on overruns.

Description: Currently the Toradex configuration block parser suffers an off by one issue potentially leading to spurious printout during boot e.g.
Model: Toradex V1.2A,
instead of
Model: Toradex UNKNOWN MODULE V1.2A.

Workaround: Fix available on 2016.11-toradex-next branch of git.toradex.com/u-boot-toradex.git.

Description: To get atmel mxt based touchscreens with GPIO connected reset line to work GPIO needs to be configured as an output with appropriate level separately.

Description: In order to allow our customers easy re-flashing of the touch controller configuration, we need to add the mxt-app as well as the proper configuration files to our images.

Workaround: https://www.toradex.com/community/questions/25020/view.html

Description: The update to rocko (BSP 2.8b1) made automount fail for systems which do not trigger mounting through dbus/udisk2, i.e. which rely on udev rules.

Description: In the demo images for BSP 2.8b1 the image viewer gpicview is not installed.

Workaround: Remove adwaita-icon-theme from BAD_RECOMMENDATIONS when building the image with openembedded.

Description: After building an image completely successfully, building the same image the next day without any changes leads to an error "do_image_teziimg: Error executing a python function in exec_python_func()".

Workaround: Make an unrelated change in any recipe to force recreation of the rootfs.

Description: Upstream libusbgx accepted our implementation of OS Descriptor support. However, during review process the configuration schema changed slightly. Update libusbgx to the latest upstream version and use the new configuration format.

Description: Enable "user debug" which enables kernel messages when a user process crashes due to an exception.

Description: We are currently using 4.11 which is not really an LTS release however we opted to do that because we were relying on it for certain later features for certain Wi-Fi solutions we wanted to support. It may make sense to stabilise on an LTS release for the future.

Workaround: You may find our backports based on Linux kernel 4.14 here: http://git.toradex.com/cgit/backports-toradex.git/log/?h=toradex-4.14

Description: Update meta-lxde to build the latest LXDE sources. The latest lxpanel release doesn't work with our GTK+3.

Description: Allow for easier OpenEmbedded machine configuration by our customers.

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: Our 2016.11 U-Boot recipe in meta-toradex-nxp fails to build. - The RPM packaging errors out because the generated spec file contains a dash in the Release variable: Release: 2.7.2-gitr60021a4

Workaround: - Edit recipes-bsp/u-boot/u-boot-toradex_2016.11.bbappend so that the PR variable does not contain a dash ('-').

Description: Include multiple Bluetooth and Wi-Fi kernel modules in our BSP demo image release packages.

Workaround: You may find our backports based on Linux kernel 4.11 here: http://git.toradex.com/cgit/backports-toradex.git/log/?h=toradex-4.11

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: A few Colibri VF50/VF61 (IT) modules flashed with our latest beta BSP release V2.7Beta1_20170112 may hang during DRAM initialization (e.g. right after printing DRAM:). Attempting recovery with that same beta release will likewise fail.

Workaround: This is a software regression in U-Boot. Either compile U-Boot from our -next branch or use our latest stable BSP release V2.5_20151216 which has been fully validated & verified and does not exhibit this issue.

Description: On modules with newer kernels we set up a composite USB gadget with an RNDIS and a ACM USB endpoint providing a virtual Ethernet and serial link on the USB client port. Currently for Colibri VF a getty is spawned on the serial link giving you a login console on that connection. All other modules do not spawn a getty. We no longer spawn a getty on any module since some host platforms do have issues with composite USB gadgets.

Workaround: Please have a look at the following article on our developer website for more information: http://developer.toradex.com/knowledge-base/usb-device-mode-(linux)

Description: On Colibri VF50/VF61 in situations with frequent unexpected power-cuts there is a possibility of filesystem getting corrupted.

Workaround: Use a Read-Only Root Filesystem.

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: With the move to morty all SysV initscripts have been installed which caused interference. This got fixed by finally getting rid of all SysV remnants.

Description: SPI read issue when using multiple SPI_IOC_MESSAGEs.

Workaround: Always use SPI_IOC_MESSAGE(1).

Description: The SD card 1-bit operation mode, enabled by seeting the 'bus-width' property of the device tree 'esdhc' node to <1>, not work while using SD card. It was tested with Colibri VFxx.

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: When connecting the module using USB device connection, the module provides an IP address via it's own DHCP server. The DHCP server uses DHCP Option 3 (Router) to announce itself as router which can lead to internet connection interruption on the host.

Description: OE migrated the sato image to GTK+ 3. This includes pcman-fm with its libfm. As lxpanel is using libfm we have to follow here or provide our own pcman-fm/libfm recipes. If we move to GTK+ 3 I guess we should do it with all GTK+ based software. e.g all of lxde/lxdm (which may have some issues), the GPIOconfig tool and tegrastats-gtk.

Description: Udisks development has stalled in 2014, udisks2 seems to be the successor. According to the OE recipes udisks2 also has less dependencies (notable lvm2, which adds almost 3.2MiB to the image and is not commonly used in embedded systems as well as sg3-utils, another 1.1MiB). Udisks2 also has a command line utility see: https://zeth.net/2014/05/28/modern_mounting_with_udisks2.html.

Description: Suspend/resume on Vybrid is currently broken.

Description: Deploy rpmsg configuration for Vybrid in OpenEmbedded.

Description: There was a bug in the parity control of the Vybrid lpuart driver.

Description: Support DMA enabled receive and send transfers.

Description: Evaluate Linux rpmsg multi-core communication solutions (Remote Processor Messaging).

Workaround: Use MCC version 1.

Description: With the change to the DRM based Display Controller driver display timings are taken from a the Simple Panel driver. The Simple Panel driver does not include timings for the Fusion Capacitive Multi-Touch Displays currently.

Workaround: None.

Description: Vybrid's display controller (DCU) has more capabilities then currently being supported by the frame buffer driver. Implement a Linux DRM driver to support all the features of the DCU and leverage the advanced interfaces provided by the Kernel (KMS/DRI).

Workaround: Use the DCU frame buffer driver to provide display output.

Description: Audio settings do not get restored after suspend-to-RAM (LPSTOP2).

Workaround: Use standby (STOP) mode instead for now.

Description: Use long-term supported Linux kernel release 4.4.

Description: The USB host (USBH) bus disconnects all devices after resuming from LPSTOP (suspend-to-memory) low-power mode.

Workaround: Use unbind before entering suspend and (re)bind the driver after suspend. This method has been implemented as a systemd service (usb-resume.service). Alternatively, use standby mode instead.

Description: This version is identical to the previous beta version V2.5 beta 3.

Description: Driver support for non standard UART baud rates.

Description: Full UBIFS root file system can lead to a system which is not able to mount the root file system anymore.

Workaround: Take measures to avoid the root file system completely running out of space.

Description: Tear-free double buffering using the Linux framebuffer is currently not possible since there is no method to synchronize the buffer swap with the vertical synchronization period.

Description: Support using RS-485 transmitter on UART interfaces using the UART_x_RTS signal as DE (driver enable).

Description: The U-Boot boot loader does not switch on the power on the USB host port. This makes the USB host port not working by default on the Viola and Iris Carrier Boards.

Workaround: Use U-Boot's GPIO functionality to switch on the USB host power (GPIO 83).

Description: Increase ECC level from 6 errors to 8 errors per 512 bytes page to reach typical endurance of 100K cycles.

Description: The current software AC97 driver supports audio playback and touch. It needs to be extended with receive capabilities to support analogue audio capture as well.

Description: Publishing our machine support into the community driven meta-fsl layer.

Description: Using UART on Vybrid without DMA can lead to boot freezes when characters have been received during startup.

Workaround: Enable DMA mode to avoid this problem completely or avoid character transmission to the module during startup.

Description: SPI by using Vybrid's DSPI peripheral does not work as intended.

Description: Currently there are kernel errors after suspend to RAM when using AC97.

Description: UBI needs about 10 seconds to attach on a current Colibri VF61 with 1GB NAND flash. While this will decrease a little with our switch to just 512MB NAND use of fastmap is desired but requires a later kernel.

Description: USB Host/Client capabilities in U-Boot.

Description: Current Timesys kernel is considered obsolete. Migration to a later version is desired.

Description: The Vybrid internal RTC would allow waking up the system from low power modes based on a time (wakealarm).

Description: Vybrid's internal RTC is not as accurate as expected (~2% drift).

Workaround: Update time regularly using NTP or use external RTC (/dev/rtc1).

Description: Base on later U-Boot version in order to support Device Tree for newer Kernel version.

Description: Some pins used for AC97 (VF61) resp. ADC (VF50) resistive touch changed. ADC resistive touch driver requires adapting to work with both previous V1.0A as well as new V1.1A Colibri VF50 modules.

Description: From time to time boot-up hangs just after RTC detection (or nearby). Usually boot-up can be unfrozen by sending a character.

Workaround: This issue is related to UART. If the UART is not connected, the issue doesn't appear.

Description: Send Ethernet PHY to powersave when going into sleep modes.

Description: The current working implementation uses the hacked up rpmsg driver implemented in line with the downstream rpmsg driver for the i.MX 7 as done by NXP. Investigate and possibly implement a remoteproc driver which can also be upstreamed.

Description: Currently native Compilation is not working in the regular Bsp (version > 2.8) due to a mismatch of GCC libraries.

Workaround: Do cross-compilation or create a custom image with GCC being pre-installed.
IMAGE_INSTALL_append = " packagegroup-sdk-target"

Description: On 32-bit systems, Linux uses a 32-bit signed integer type 'time_t' to represent the time at various locations. It gives the time as seconds relative to 1970. The time_t type wraps at "2038-01-19 03:14:07", so all users of time_t likely fail when a type_t instance is set to a timer after that date. This issue is applicable to all 32-bit systems and will be fixed in the mainline eventually.

Description: NXP doesn't provide any support for FreeRTOS and is not writing peripheral drivers for ADC and SPI on Vybrid.

Workaround: FreeRTOS on i.MX 7 provides support for ADC and SPI. It might be taken as a base for a port to Vybrid modules. This has not been verified by Toradex.

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: When using UBIFS image type the resulting image is not bootable. Systemd fails to mount file systems and ultimately drops into an emergency shell. The reason is that the resulting image has wrong user/group ids assigned to directories and files.

Workaround: The utility mkfs.ubifs is compiled as a 32-bit binary for the legacy image format. Make sure to remove the 32-bit flag by removing meta-toradex-(demos|bsp-common)/recipes-devtools/mtd/mtd-utils_%.bbappend.

Description: Using legacy Ubuntu 12.04 is not compatible with our update script due to too old split implementation in coreutils. Coreutils needs to be 8.16 or later.

Workaround: Have a look at the various suggestions given in our community: https://www.toradex.com/community/questions/15912/apalis-module-update-script-fails.html

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: On Colibri VF50/VF61 in situations with frequent unexpected power-cuts, there is a possibility of filesystem getting corrupted. The issue is related to extended filesystem attributes (xattrs). Release V2.6b6 allows to disable the extended attributes through the Kconfig config symbol CONFIG_UBIFS_FS_XATTR.

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: Due to a chip errata the main CPU clock may be unstable. During our extensive testing We have not observed issues with our design so far. We never saw any problem and also don't have any negative customer feedback.

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: With #16470 the Ethernet PHY power down mode has been disabled. This increased the power consumption during suspend. Since Ethernet is often not used on power constrained devices, we prefer lower power consumption over working Ethernet. Therefor we should reenable the PHY power down mode when using suspend.

Workaround: Use U-Boot's MII capability to put the PHY into sleep mode at boot time (use "mii write 0 0 0x3800" to set PHY's PDOWN mode).

Description: eCos freezes or deadlocks after running MCC pingpong for some time.

Description: Modem control signals such as DTR, DSR, DCD and RI are not available in the LPUART peripheral block. Consider using GPIOs to emulate the modem control signals.

Workaround: Use sysfs in userspace to control the GPIOs.

Description: Driver support for 8-bit BT656 YUV aka parallel camera interface as well as analogue video inputs.

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.