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: Update to the OpenEmbedded Thud resp. Yocto Project 2.6 release. - Drop support for the Apalis T30 and Colibri T20/T30/VF.
- Drop support for the legacy update procedure. - Drop Qt4 from the default install - Change the distro from Angstrom to Poky based but keep systemd as the default init manager.

Description: 4.4.220 and 4.9.220 which both have a matching RT-patch available.

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: 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: Include hostapd in demo builds. Note that this is only about the naked daemon without any configuration which depends on resp. requirements. So nothing of the hostapd will be automatically started by default.

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: 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: Hitting the eject button either in the PCManFM file manager (pcmanfm) or the Disks gnome-disk-utility tool (gnome-disks) fails as follows due to the eject command line tool being missing:
Error ejecting media
Error ejecting /dev/sda: Error spawning command-line 'eject "/dev/sda"': Failed to execute child process "eject" (No such file or directory) (g-exec-error-quark, 8) (udisks-error-quark, 0)

Description: Add the driver for RTL8188EU which is e.g. used in LM816 to our standard images.

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

Description: After the RTC has been under-powered, some RTC deliver invalid date/time. The external RTC currently shipped on Toradex evaluation boards has a oscillator fail bit which indicates when RTC does not contain a valid date/time.

Description: Update toradex-bsp-platform.git branch LinuxImageV2.6.1 to the latest of the jethro branches. Note that we do not provide any binary demo images.

Description: Systemd may hang upon first boot due to certain services like run-postinsts and opkg-configure triggering a configuration reload later causing dynamic device services like the dev-ttyS0 one to hang.

Workaround: A fix has been implemented in our -next branch.

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: Bitbake for some time checks what other packages a package depends on by e.g. examining the output of ldd of a binary or examining used interpreters in scripts. So RDEPENDS are only needed for non obvious packages, e.g. such which get dynamically linked in code or packages providing data. Cleanup our layers.

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: The kernel currently does not know a power-off mode which makes the system switch into halt mode. In this mode, the module draws even more power compared to regular power on mode. Implement a power-off mode which switches the SoC into its deepest sleep state.

Workaround: Instead of shutdown (poweroff), use standby or suspend mode.

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: So far U-Boot writes a BCB (Boot Configuration Block) crafted in a way to work around errata e9609. This also requires the U-Boot to be written in a way which only uses 3/4 of a page (implemented by the writeboot command). This mode has a drawback in practice: It cannot detect bad blocks marked with the usual bad block marker. Colibri iMX7 V1.1B and later do not suffer errata e9609. In order to overcome the limitations of the work-around, new U-Boot version will write the BCB in a new format which allows detecting bad block markers and use complete pages. This also allows to write the boot loader using standard nand write commands.

Description: OTG support for Vybrid in das U-Boot is currently missing.

Description: As OE moves to GCC-6 we should provide our U-Boot and 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: 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: UART Mark parity bit mode always generates a space parity bit (a 0 instead of a 1).

Description: When using the unexport functionality through the GPIO sysfs interface, the pin keeps the last configured state. The typical expecation is that the pin is being disabled (set to Hi-Z).

Workaround: Set the GPIO as input before unexport.

Description: UART receiver path can overflow in certain conditions when using DMA mode. This leads to the receive path being stuck and not receiving any character anymore.

Workaround: Disable DMA mode by overwriting the dma-names property in the device tree.

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

Description: Various UBIFS errors reported by Linux kernel especially while booting. Some errors might lead to root file system not being mountable.

Description: The USB ID pin shall be used for automatic USB device/host detection.

Workaround: Use implementation available in resp. -next branch for now.

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

Description: Support standby and suspend-to-RAM for newer (mainline) Kernel versions. True suspend-to-RAM (self-refresh) only works with newest hardware revision 1.2.

Description: Support Framebuffer in U-Boot to provide graphical output at bootloader time.

Description: GPIO support in U-Boot

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

Workaround: None.

Description: Sometimes the kernel freezes right on startup. The last message being shown in the serial console is "Starting kernel ...".

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

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: Colibri VF50 128MB IT V1.2B may not wake-up from software suspend.

Workaround: Please contact support.

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 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: 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: IrDA requires specially modulated UART signals. While at least some of the UART drivers can be compiled or configured to use IrDA we didn't test if this would actually work.

Description: For many utils (e.g. ls) we use busybox in our image. These utils in the used busybox version display chars outside of the 7 bit ASCII range as a '?' even if the locale is set correctly and the system uses e.g. UTF-8.

Workaround: Just enable UNICODE in the BusyBox configuration and re-compile.

Description: In USB device mode using RNDIS on Vybrid with Windows as host might result in a kernel crash during continuous bi-directional data transfer.

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: Xinput-calibrator may fail when axis are swapped. Usually a single axis swapped works however when there are multiple ones swapped the algorithm may fail getting any useful calibration coefficients.

Workaround: Avoid swapped axis e.g. by fixing the hardware wiring or pre-configure them via e.g. /etc/X11/xorg.conf as follows:
Section "InputClass"
    Identifier    "ResistiveTouch"
    MatchProduct  "stmpe-ts"
    Option    "SwapAxes"  "1"
EndSection

Description: Currently a static parent clock is used which might give suboptimal pixel clock frequencies. An improved algorithm is desired which chooses a parent clock leading to the most accurate pixel clock frequency.

Workaround: Select a different clock parent using the device tree assigned-clocks and assigned-clock-parents property.