BSP Layers and Reference Images for Yocto Project Issue Tracker

Description: Update RT Linux Kernel to v6.1

Description: Update to Linux Kernel v6.1

Description: Update Linux Kernel to 6.0.17

Description: 0041 Colibri iMX7D 512MB EPDC is no longer supported.

Description: The instruction set used to compile userspace components is currently forced to be Thumb2 even for recipes which explicitly ask to be compiled for the ARM instruction set (the default for the armv7a machines was and stays Thumb2).

Workaround: No known issues because of this error

Description: In case a driver requests a firmware (even if it is optional) and this firmware is not present in the fs, the driver loading time will be delayed for 60 seconds, Atmel MXT capacitive touchscreen is affected by this bug

Workaround: Disable legacy `CONFIG_FW_LOADER_USER_HELPER` in kernel configuration

Description: Revise CMA memory allocation: 96MiB CMA memory for 256MiB SOM, 192MiB CMA memory for 512MiB SOM, 256MiB CMA memory for >= 1GiB SOM

Description: The U-Boot mmc info command may truncate the eMMC name by one character at the end.

Workaround: Use BSP6 or backport patch from upstream U-Boot where this got already fixed. https://source.denx.de/u-boot/u-boot/-/commit/84191f73847c351019bb50728d28220d91b0aee4

Description: When using a large kernel, more than 32MB, and using a ramdisk (e.g. initrd) image, the ramdisk image would get overwritten by the uncompressed kernel.

Description: Remove `toradex-fitimage.bbclass`, use standard OE kernel-fitimage.bbclass instead

Description: Spidev is no longer enabled on base dts file, add a device tree overlay to enable the functionality.

Description: Mount "boot" partition to the standard location and `mount --bind` from `/boot` to that location instead of mounting the "boot" partition in `/boot`

Description: Update U-Boot to v2022.07 version for imx6 and imx7 modules.

Description: Update on the U-Boot config block code: - use official SoM names on prints - interactive config block code creation ask for the PID4 number instead of y/n interactive questions

Description: U-Boot environment config moved from U-Boot to libubootenv recipe.

Description: Update system critical shutdown threshold to match the SoC maximum junction temperature.

Description: Add WAKE#_MICO signal as default wake-up source for every module and carrier board.

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: The custom fstab that's installed on our builds doesn't include the "defaults" option that gets substituted by "to" as part of the openembedded "read-only-rootfs" IMAGE_FEATURE. Because of this, setting the image feature doesn't achieve the desired result of having the rootfs mounted as read-only.

Workaround: Patch the file meta-toradex-demos/recipes-core/base-files/base-files/fstab and include the "defaults" option: - /dev/root / auto noatime 1 1 + /dev/root / auto defaults,noatime 1 1

Description: Update Linux Kernel patch version to 5.4.193

Description: The sound card name may be different preventing the regular ALSA configuration/state from being properly applied. Therefore, the initial ALSA mixer configuration may not be very user-friendly.

Workaround: Manually adjust the ALSA configuration to your liking. It should automatically get preserved over subsequent re-boots.

Description: Sometimes audio playback time on SGTL5000 does not match the input file duration.

Description: Update to NXP released L5.4.70_2.3.7 (SECO, user-space, imx-boot)

Description: Enable CONFIG_DYNAMIC_DEBUG Kernel Config

Description: Do not override other meta-freescale recipe from our Open Embedded layers

Description: Do not store u-boot environment during boot unasked

Description: Increase kernel partition size to 12MB for NAND based SOM

Description: on colibri-imx6ull and colibri-imx7 (nand variant) u-boot is configured to use just 1 block for environment, while in linux userspace (fw_env.conf) 4 blocks are configured for the environment. In case the currently used environment block become bad u-boot will not longer be able to access it, while the linux utilities will just use the next available block, leading to inconsistency in the u-boot environment content between linux and u-boot.

Description: Update to latest kernel.org patch release and pull in latest patches from linux-imx 5.4.70_2.3.3 patch release.

Description: CMA memory allocation is a fixed value and takes up too much space on certain SKUs. Drop the configuration of the CMA in the device tree in favour of specifying it in the kernel config with a size of 256MB or 12% of total memory which ever is less.

Description: Software reboot may stall 1.5 minutes stopping Weston Wayland compositor.
Stopping Weston Wayland Compositor...
[* ] (1 of 2) A stop job is running for …ayland Compositor (13s / 1min 31s)
This does not always happen. Not sure whether it depends on how long the session was already active.

Workaround: Just be patient (;-p).

Description: A kernel configured with THUMB2_KERNEL compiled with GCC 10 doesn't boot.

Workaround: Compile without THUMB2

Description: An image for Apalis iMX8 contains in addition to the ones specific to Apalis iMX8 the specific ones for Apalis iM8X. While this does not hurt it might be confusing.

Workaround: -

Description: Change OpenEmbedded recipes from Toradex to fetch from https instead of git where possible.
In an approach to make it more user-friendly, especially for big company customers that do not allow git-protocol in their networks we decided to use https as a fetching source.
We are aware that we cannot do this for each and every layer but at least for ours we decided to switch from git to https.

Description: Due to the class "classes/image_type_tezi.bbclass" in "meta-toradex-bsp-common" setting the label to all upper-case "BOOT", and WIC images using all lower-case "boot", the /boot mounting may actually not work at all (given that an image got actually installed to eMMC using the Toradex Easy Installer prior to distrobooting from SD card and/or USB memory stick). However, rather than having the eMMC's boot partition mounted to /boot it would make much more sense to mount the resp. boot media's boot partition there.

Description: Update Linux kernel to new NXP L5.4.70-2.3.0 release.

Description: WIC images do not contain the device tree overlays. This affects users that boot from the SD card or USB sticks. See Boot From an SD Card / USB Stick / SATA drive for reference.

Workaround: Manually deploy them. See how-to on Deploying a Device Tree Overlay.

Description: Adjust developer website to new paths used on BSP 5.

Description: When doing soft reboot Colibri iMX7 hangs during poweroff sequence.

Description: Make sure to document on our developer website which display interfaces are used by default.

Description: Make sure the boot partition on eMMC-based modules is mounted consistently across all modules to /boot.

Description: Support Iris 2.0 SD card (without external pull-ups).

Description: On NXP i.MX 6ULL and i.MX 7 based modules the qt-demo is not working due to the missing qt-wayland backend. Fix this.

Description: Use KBUILD_DEFCONFIG in OpenEmbedded to define the defconfig to build the kernel from. Toradex is now using the defconfigs from the kernel-repo instead of providing separate defconfigs in OpenEmbedded. However if you wish to provide your own defconfig in OpenEmbedded you can still do so.

Description: Add support for DHCP/TFTP boot via distroboot.

Description: Enable Linux kernel support for the CAN SAE J1939 protocol for the vehicle bus recommended practice used for communication and diagnostics among vehicle components.

Workaround: You may manually enable CONFIG_CAN_J1939, re-build and re-deploy the Linux kernel and/or Linux kernel modules.

Description: Enable systemd-analyze.

Description: The Linux kernel configurations CONFIG_PPS_CLIENT_GPIO and CONFIG_PPS_CLIENT_LDISC may be usefull.

Description: Update graphics to the latest version from NXP.

Description: Create a new unified manifest repository called toradex-manifest for Embedded Linux BSP and TorizonCore.

Description: Synchronize our local.conf sample (in meta-toradex-distro) with the one provided by OE as OE has made some changes.

Description: Change udev rule symlink naming to uart instead of tty.

Description: VGA Output not working in U-Boot but in Linux

Description: The fw_setenv config file uses a hardcoded device file for where the U-Boot environment can be found. (mostly /dev/mmcblk0boot0. Depending on the kernel version the device number might change. Generalize this so that fw_printenv/fw_setenv finds the U-Boot environment independent on how mmc gets enumerated.

Description: [userspace] systemd/connman withdraws IP when NFS is used

Description: Update downstream kernel to the latest NXP BSP L4.14.98_2.3.0.

Description: The relevant patches to use bootaux with ELF files exist only in our downstream 2016.11 based U-Boot. [krm@max-pc u-boot-toradex]$ git log --oneline arch/arm/imx-common/imx_bootaux.c 08972759fd imx: imx-common: do not zero out outside of regions f0d5faf6f5 imx: imx-common: add elf firmware support 0c62005b96 imx: imx-common: move aux core image parsing to common code I assume that the 'while (mmap)' loop might loop forever if the address cannot be found. Probably 'while (mmap->size)' would leave the loop when reaching the sentinel entry.

Description: meta-toradex-demos currently provides /etc/profile. Rework that to take /etc/profile from OE core and put our extension as scripts into /etc/profile.d.

Description: NXP released BSP L4.14.98_2.0.0_ga. Update the kernel to that release.

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: Dropped support for the Lightweight X11 Desktop Environment (LXDE) in favour of single application use-case.

Workaround: Use the latest stable BSP 2.8.

Description: Update OpenSSL to version 1.1.1d

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

Description: Resuming after suspend may not work.

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: Doing ifdown/ifup may leave Ethernet PHY in an unknown state just permanently blinking preventing any communication. This is caused by an Ethernet PHY power-down without physically powering down resp. rail leaving the PHY in an unknown state which later upon powering it back up fails locking PLL. We may just disable PHY power-down bit (already implemented on Colibri VF50/61) or where possible properly implement powering down resp. rail.

Description: Back feeding on Ethernet rail when Ethernet is powered down.

Description: NXP released BSP 4.9.123_2.3.0_ga. Patches for the user space components are on the meta-freescale mailing list.

Description: The CAN muxing ALT2 (can1.RX, can1.TX) for these pins are labelled ftm1.RX, ftm1.TX. Fix this.

Description: Update Wi-Fi Backports to 4.18

Description: When running with HS400 at 200 MHz the Kernel may report eMMC errors such as "mmcblk0: error -84 transferring data". Some systems also show "warning! HS400 strobe DLL status REF not lock!". We have not seen issues which lead the system to be completely stuck. However, when using HS200 at 200MHz it affects performance very little (~5%) but seems to run without any errors.

Description: Enforcing to build 32-bit binaries for native and portions thereof using -m32 in EXTRA_OEMAKE_class-native may lead to the following error when building e.g. u-boot-toradex:
cbootimage: Accessing a corrupted shared library

Workaround: The -m32 as specified in EXTRA_OEMAKE_class-native in recipes-bsp/cbootimage/cbootimage.bb of meta-toradex-tegra may be overridden to your liking. The same applies to the following as well:
meta-toradex-demos: recipes-devtools/mtd/mtd-utils_%.bbappend
meta-toradex-nxp: recipes-devtools/imx-loader/imx-loader_git.bb
meta-toradex-tegra: recipes-bsp/tegrarcm/tegrarcm.bb
meta-toradex-tegra: recipes-support/libcryptopp/libcryptopp_5.6.4.bb

Description: U-Boot typically tears down the display controller before handing control over to Linux. On LCD displays disabling pixel clock leads to a fading out effect with vertical/horizontal lines. Make sure to disable back light before booting Linux.

Description: With the toradex_4.9-1.0.x-imx kernel the sgtl5000 audio codec is bound to the I2S interface with the simple card driver but the driver is not part of the kernel config.

Workaround: Add CONFIG_SND_SIMPLE_CARD to the kernel config.

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: RS485 with using RTS to control the transceiver is not working. The RTS signal is not asserted during transmission. This is a regression in 2.8 BSPs (Linux kernel 4.9).

Workaround: Use ioctl to configure RS-485 and set the flag SER_RS485_RX_DURING_TX and SER_RS485_RTS_AFTER_SEND.

Description: When migrating to the Linux kernel only the evaluation board device trees got updated, others may have diverged. This is especially the case with the Colibri camera device tree concerning e.g. RTC and new capacitive touch aka mxt.

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 scrot recipe source is 404.

Description: Forward-port the change to allow configuring the display timings via kernel command line to the Linux kernel 4.9.

Workaround: -

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: The thermal sensor driver on i.MX 7Solo does not probe successfully. There is no thermal sensor data available.

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: 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: 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: The kernel prints "Timeout waiting for hardware interrupt" errors when accessing eMMC, particularly at boot-up.

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

Description: Update our i.MX kernel to the 4.9-1.0.x-imx branch of the FSL community kernel aka linux-fslc-imx which includes NXP's latest 4.9.11 1.0.0 GA release changes.

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: Use optimized RAM timings as we found some issues on some modules and in our temperature testing.

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: 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.

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: Fix the Colibri iMX7 display timings and allow setting them from the kernel cmdline.

Workaround: Use native mode node in device-tree

Description: The i.MX 7Solo is only rated up to 800MHz, hence operating it at 1GHz is outside of the official specification. There have been no negative effects observed.

Description: In the 3.14 based kernels the device tree property "linux,rs485-enabled-at-boot-time" allowed to enable RS485 at boot time. This device tree property so far had no effect on 4.1 based releases.

Workaround: This is now implemented in our toradex_4.1-2.0.x-imx-next branch.

Description: Wakeup on CAN does not work in suspend mode with FlexCAN with 4.1.39 kernel.

Description: Using UBIFS rootfs with extended attributes (xattr, by default used in the Toradex BSP) might cause file system corruptions and lead to an unbootable system. Affected versions:
Colibri_iMX7_LinuxImageV2.6.1Beta1_20160929
Colibri_iMX7_LinuxImageV2.6Alpha1_20160315
Colibri_iMX7_LinuxImageV2.6Beta2_20160701
Colibri_iMX7_LinuxImageV2.7Beta1_20170112

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: 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: 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: At this point the Linux suspend to memory and standby power states are supported ("mem"/"standby"). The standby mode uses a low power run state, whereas suspend to memory makes use uses the SoCs deep sleep mode (DSM). Wakeup from external GPIO as well as internal RTC have been verified working.

Description: Add FlexCAN support.

Description: Using keypad driver causes kernel freeze on iMX7

Workaround: Use the generic GPIO driven matrix keyboard driver

Description: The IPv6-in-IPv4 tunnel driver creates an additional network interface (sit0). To avoid confusion around that interface and since the sit interface is only used seldom the driver should be made available as a module.

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: The Colibri iMX7 SODIMM 45 wake-up configures an internal pull-up while other modules use pull-down. Also some carrier boards use a external pull-down resistor. Configure an internal pull-down resistor on the pin do be consistent with carrier boards and other modules.

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: 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: All pins without a specific function should be configured for regular GPIO support.

Description: Using Colibri iMX7S freezes when using Viola. Could be a boot rom issue.

Workaround: Disable SNVS RTC in the device tree.

Description: Even if a USB controller is in peripheral mode, loading the USB Gadget schema fails with "Failed to start Load default USB gadget schema g1.schema.".

Workaround: Remove the command (ExecStartPost) copying the serial-number to the USB Gadget configuration in /etc/systemd/system/multi-user.target.wants/usbg.service.

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: The use of fdt_fixup should be unified across all our modules and document.

Description: Support the Multi-Touch Controller used on the Toradex Capacitve Multi-Touch Displays.

Description: Despite removing the conflicting UART2 Linux freezes on startup.

Workaround: None.

Description: The Colibri iMX7 Solo does only have one USB port. However the bootloader code of the Alpha1 release touches registers of the not available second USB port which leads to a freeze of U-Boot.

Workaround: None.

Description: `fdtfile` variable always takes precedence over `fdt_board`

Workaround: From U-Boot, use the following commands to properly use the `fdt_board` variable: ``` setenv fdtfile setenv fdt_board ${carrier_board} # e.g. setenv fdt_board dahlia saveenv reset ``` replacing `${carrier_board}` with the actual carrier board name according to the dtb filename.

Description: The pixel clock frequency on the parallel RGB interface is not perfect, because of that some display might not work as expected. For example if the requested clock is 25175000 Hz the resulting pixel clock is 23450000 Hz

Description: Linux kernel might print NAND I/O errors related to block 0 at boot, `I/O error, dev mtdblock0, sector 0 op 0x0:(READ)`. Reading the first MTD block device is not possible from Linux since it is used to store the BCB (boot control block) that is used by the bootrom and has a different ECC protection scheme.

Workaround: Ignore the warnings, no known malfunction.

Description: Later distros like Fedora 36 will fail to connect as follows unless the configuration is explicitly weakened: Unable to negotiate with 192.168.10.2 port 22: no matching host key type found. Their offer: ssh-rsa scp: Connection closed

Workaround: Put the following in your ~/.ssh/config below resp. host you are trying to connect to: PubkeyAcceptedAlgorithms +ssh-rsa HostkeyAlgorithms +ssh-rsa

Description: Sometime reading /sys/devices/virtual/thermal/thermal_zone0/temp returns "Resource temporarily unavailable" (`EAGAIN`)

Workaround: Trying a second time solves the issue

Description: CMA memory allocation is a fixed value and takes up too much space on certain SKUs. Drop the configuration of the CMA in the device tree in favour of specifying it in the kernel config with a size of 256MB or 12% of total memory which ever is less.

Description: Loading of M4 Firmware does not work.

Description: On Colibri iMX6ULL and Colibri iMX7 X11 does not work out of the box if using a mainline kernel.

Workaround: Add the xf86-video-modesetting package to your Yocto build and delete the installed /etc/X11/xorg.conf file on the module.

Description: Provide proper vidargs for mainline 5.4 in BSP 4.0.0

Description: Add support for resistive touch screens available in the Toradex webshop

Description: Support the USB WiFi products available in the Toradex webshop

Description: Add support for VGA (Analog RGB)

Description: Add support for S/PDIF Audio

Description: Add support for the Analogue Camera Adapter (ACA)

Description: Add support for suspend/resume including wake-up sources (e.g. RTC, GPIO)

Description: Add support for watchdog

Description: Add support for SPI

Description: Add support for PWM

Description: Add support for Analog Inputs

Description: Add support for Analog Audio Mic in

Description: Add support for Analog Audio Line In

Description: Add support for USB Client

Description: Add camera support

Description: The NXP i.MX 7 SoC has an issue which prevents doing this.

Description: Setting the RTS pin low in idle state for RS485 communication is not possible.

Workaround: Put a hardware inverter on the carrier board resp. use the exact RS485 hardware design of our Evaluation Boards.

Description: While the CAN transceiver regulator is properly powered-down on non-use such functionality during suspend is currently missing in flexcan.c.

Workaround: A custom power-down GPIO may be implemented.

Description: Switching multiple times back and forth between USB device/host mode sometimes may freeze the module.

Description: At the moment for iMX7 it is not possible to identify the Reset Reason. For future at least the Reset POR should be differentiated from Watchdog Reset.

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: Using default suspend to memory (i.MX 7 DSM, deep sleep mode) seems to crash on wake-up.

Workaround: Use latest stable.

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: The gatttool is deprecated, GATT functionality is available through bluetoothctl.
https://docs.ubuntu.com/core/en/stacks/bluetooth/bluez/docs/reference/gatt-services

Description: Add CDC ECM Configuration.

Workaround: Use RNDIS instead.

Description: Currently access point aka ap mode is not supported on the LM816 Wi-Fi USB dongle.

Description: LM816 Wi-Fi speed is limited to 1 Mbit/s rx/tx.

Workaround: Updating to a later Wi-Fi backports may help but only marginally.

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: In the testing of Colibri iMX7S the U-Boot environment variable 'ethaddr' was set to the value '00:14:2d:12:34:56' and thus cloaking the value set in the configblock. Our test procedure has been updated in order for a regular MAC address being used.

Workaround: Deleting the U-Boot environment variable ethaddr fixes the issue. This can be done by any of the following: 1) flashing an image 2) setenv ethaddr; saveenv 3) env default -a; saveenv

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: GPIO poweroff is currently gated by CONFIG_POWER_RESET_GPIO which is not documented on our developer website. Rather use the device tree property (e.g. /soc/fsl,use-lpm-poweroff) like implemented on Vybrid.

Workaround: Re-compile the kernel with CONFIG_POWER_RESET and CONFIG_POWER_RESET_GPIO enabled.

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: ARM DS MDK requires a special set of Linux kernel configuration options in order to allow for debugging the Linux kernel (incl. modules) and FreeRTOS side by side. Unfortunately some of those required configurations are unsuitable for our regular BSP plus one anyway needs the full debug symbol for any real debugging.

Workaround: Please enable the following Linux kernel configuration options: CONFIG_DEVKMEM, CONFIG_DEBUG_INFO, CONFIG_PROFILING, CONFIG_FTRACE and CONFIG_ENABLE_DEFAULT_TRACERS. Then disable this option: CONFIG_CPU_IDLE. Now re-compile as explained in the following article on our developer website: http://developer.toradex.com/knowledge-base/build-u-boot-and-linux-kernel-from-source-code

Description: On the Colibri Evaluation Board V3, a USB 3.0 device plugged in at boot time is not accessible after boot. Furthermore, the device seems to influence the on-board USB hub in a way that any USB port 1-4 won't work anymore.

Workaround: Using a regulator in the device tree to toggle the reset of the external USB hub might help avoiding the issue, see https://community.nxp.com/thread/335298.

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: 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: Passing Mac address from U-Boot to Linux kernel not working Properly for second PHY

Workaround: Add the aliases of both Ethernet Interfaces to the devicetree files as "ethernet0 = &fec1; ethernet1 = &fec2;"

Description: Splash screen isn't shown during boot time

Description: Add support for Iris 2.0

Description: Kernel warnings can be seen right before the system reboots. This is due to I2C transfers calling the scheduler which is not allowed at this point.

Workaround: So far the warnings have not shown negative effects.