BSP Layers and Reference Images for Yocto Project Issue Tracker

Description: Restarting hostapd makes it impossible for clients to connect to the AP.

Workaround: Reboot the system after a hostapd configuration change. It's also possible to rmmod / modprobe mwifiex before restarting hostapd to apply the configuration change without a reboot.

Description: In some specific condition modules using Micron MTFC4GACAJCN eMMC might get stuck during boot with the following error `mmc0: Card stuck in programming state! mmcblk0 card_busy_detect`.

Workaround: Apply patch `ed9009ad300c ("mmc: Add quirk MMC_QUIRK_BROKEN_CACHE_FLUSH for Micron eMMC Q2J54A")` to your kernel (https://lore.kernel.org/all/20231030224809.59245-1-beanhuo@iokpp.de/).

Description: USB Host interface is not working in U-Boot.

Workaround: apalis-imx8: execute `gpio set 132` before `usb start`

Description: Ethernet bridge mode on ETH_1 is not working. See also https://github.com/torvalds/linux/commit/a7602e7332b97cfbec7bacb0f1ade99a575fe104 and https://community.nxp.com/t5/i-MX-Processors-Knowledge-Base/Workaround-for-issue-Bridge-mode-on-EQoS-module-will-not-work/ta-p/1559302

Description: /dev/colibri-watchdog-soc and /dev/colibri-watchdog-som symlinks are erroneously pointing to the SoM watchdog

Workaround: Patch /dev/udev/rules.d/99-toradex.rules -ACTION=="add|change", KERNEL=="watchdog", DRIVERS=="rn5t618-wdt", SYMLINK+="colibri-watchdog", SYMLINK+="colibri-watchdog-som" -ACTION=="add|change", SUBSYSTEM=="watchdog", KERNELS=="soc*", SYMLINK+="colibri-watchdog-soc" +ACTION=="add|change", SUBSYSTEM=="watchdog", DRIVERS=="rn5t618-wdt", SYMLINK+="colibri-watchdog", SYMLINK+="colibri-watchdog-som" +ACTION=="add|change", SUBSYSTEM=="watchdog", DRIVERS=="imx2-wdt", SYMLINK+="colibri-watchdog-soc"

Description: Using the DPU DPI Display Interface, around 10% of the times the display is initialized (e.g. at every boot), ghosting artifact are present on the display.

Description: It's not possible to use Wi-Fi AP mode and client mode simultaneously.

Workaround: Update sdiouart8997_combo_v4.bin Wi-Fi firmware to the latest version from https://github.com/nxp-imx/imx-firmware/tree/lf-6.1.36_2.1.0/nxp/FwImage_8997_SD

Description: U-Boot is not properly driving the CTRL_SLEEP_MOCI# signal, because on that some carrier board peripheral might not be powered while in U-Boot. For this reason the Carrier Board EEPROM on I2C_1 bus is not working properly on the Yavia Carrier Board. This prevents the board to boot on Verdin AM62 + Yavia. On Verdin iMX8MM and iMX8MP the following errors are printed every boot: ``` wait_for_sr_state: Arbitration lost sr=93 cr=80 state=2020 i2c_init_transfer: failed for chip 0x57 retry=0 i2c_idle_bus: failed to clear bus, sda=0 scl=0 i2c_init_transfer: give up i2c_regs=0x30a50000 get_tdx_eeprom: cannot find EEPROM by node ```

Workaround: Verdin iMX8MP and iMX8MM boot fine despite this bug. If needed CTRL_SLEEP_MOCI# can be driven from U-Boot command line using the `gpio` command.

Description: OpenEmbedded build fails while fetching `isp-imx-4.2.2.19.0` with a checksum error. This is happening because the file was replaced by NXP without updating the filename. ``` WARNING: isp-imx-4.2.2.19.0-r0 do_fetch: Checksum failure encountered with download of https://www.nxp.com/lgfiles/NMG/MAD/YOCTO//isp-imx-4.2.2.19.0.bin;fsl-eula=true - will attempt other sources if available ERROR: isp-imx-4.2.2.19.0-r0 do_fetch: Fetcher failure for URL: 'https://www.nxp.com/lgfiles/NMG/MAD/YOCTO//isp-imx-4.2.2.19.0.bin;fsl-eula=true'. Checksum mismatch! ```

Workaround: Apply this patch https://github.com/Freescale/meta-freescale/commit/832250bdf2eb99d1727413b791b18f326d39446a

Description: Because of a misconfiguration of RALAT/WALAT DDR parameters memory errors (e.g. bit-flips) and crashes are possible, this was experienced with Colibri iMX6 Solo IT starting from 60 Celsius Degrees temperature.

Description: Booting a FIT image that includes a RAM disk is not working. Boot fails with the following errors: `Error: ramdisk overwritten`, `Ramdisk image is corrupt or invalid`.

Workaround: Update `UBOOT_RD_LOADADDRESS` in OE machine conf file.

Description: Using Iris / Iris v2 carrier board device tree and during the initial boot the kernel print some errors: ``` imx8qxp-pinctrl scu:pinctrl: pin IMX8QXP_QSPI0A_DATA1 already requested by scu:pinctrl; cannot claim for gpio-keys imx8qxp-pinctrl scu:pinctrl: pin-157 (gpio-keys) status -22 imx8qxp-pinctrl scu:pinctrl: could not request pin 157 (IMX8QXP_QSPI0A_DATA1) from group gpiokeysgrp on device scu:pinctrl gpio-keys gpio-keys: Error applying setting, reverse things back ```

Workaround: No know issues because of that. The pin is configured correctly and the error is showing that there is a duplicated configuration. The affected pin is still correctly configured and it is fully working as expected (SoM wake up source).

Description: Suspend/resume functionality is not working correctly, the kernel crashes during the resume.

Description: SATA device is not always detected at boot

Description: When using the “fsl,imx6sx-lcdif” (ADMA LCDIF DPI Interface) driver and rendering graphics using the GPU some display artifacts can happen.

Workaround: Set `use-g2d=0` in /etc/xdg/weston/weston.ini or Use DPU ( "fsl,imx-lcdif-mux-display" driver, display_lcdif) as a display controller.

Description: Booting a kernel with an external initrd fails in U-Boot. ``` ERROR: Failed to allocate 0x4d000 bytes below 0x100000000. device tree - allocation error FDT creation failed! resetting ... ```

Workaround: Remove `initrd_high` variable from U-Boot environment, `setenv initrd_high` or set `CONFIG_LMB_MAX_REGIONS=16` in U-Boot configuration

Description: Playtime on analog audio is faster (2x), this happen around 15% of the time after a reboot.

Workaround: Set `assigned-clock-rates = <786432000>, <49152000>, <12288000>;` in DTS `spdif0` node.

Description: The wakealarm feature of RTC1 does not work when using the `sysfs` interface. Thus one can do a timebased wakeup from suspend from any source provided by the SoM.

Workaround: Use `rtcwake` tool.

Description: Bluetooth interface might not be properly initialized at boot, the following errors might happen: `Bluetooth: hci0: command 0x1003 tx timeout`, `Failed to start discovery: org.bluez.Error.NotReady`

Description: There is a performance and boot time regression on initial BSP 6 releases compared to BSP 5, e.g. boot time on Apalis iMX6 increased from ~18seconds to ~30seconds, the reason is that some unwanted debug kernel configuration was enabled.

Workaround: Set `CONFIG_DEBUG_WW_MUTEX_SLOWPATH=n` or `CONFIG_PROVE_LOCKING=n` in the Linux kernel configuration

Description: The NAU8822 audio codec available on the Verdin development board cannot be configured in bridge-tied load

Description: Colibri iMX6ULL doesn't wake up from suspend if the ethernet interface is disabled when the system is put to sleep. With the ethernet interface enabled, suspend / resume works.

Workaround: Don't disable the ethernet interface if you need to sleep/resume. Otherwise, use BSP 6.1 or later, this issue is already fixed there.

Description: The bootaux command is not enabled on the Verdin iMX8MM u-boot default configuration.

Workaround: If the bootaux command is needed, build a custom u-boot with CONFIG_IMX_BOOTAUX set.

Description: When no display is connected the graphical demo application is crashing

Description: Some OE overrides in our layers are using a no longer supported syntax, because of that Bluetooth does not work out-of-the-box on Verdin iMX8M Plus >= V1.1A.

Workaround: Manually execute hciattach: ``` /usr/bin/hciattach /dev/ttymxc3 any 115200 flow /usr/sbin/rfkill unblock bluetooth /usr/bin/hciconfig hci0 up # Change BT UART baudrate to a higher speed, for example 921600 /usr/bin/hcitool -i hci0 cmd 0x3F 0x09 0x00 0x10 0x0e 0x00 /bin/stty -F /dev/ttymxc3 921600 ```

Description: The default audio interface is not the analogue one

Workaround: Explicitly specify the required audio interface

Description: Bluealsa is not starting/working

Description: The Wi-Fi regulatory DB is not automatically loaded, because of that a limited number of Wi-Fi channels is available and the sample Wi-Fi AP configuration is not working out of the box.

Workaround: Manually reload the regulatory db: `iw reg reload` and `iw reg set `. Verify with `iw reg get`

Description: Wi-Fi connection is not stable, it stops working after less than a minute of stress testing.

Description: CAAM driver has some failure warning during boot (`caam_jr 30901000.jr: failed to flush job ring 0`, `caam_jr: probe of 30901000.jr failed with error -5`). JR0 is reserved for secure world usage and Linux kernel cannot use it.

Workaround: The error message is just cosmetic, no known issues.

Description: DSI-to-HDMI does not implement hot plug detect on event, a 10 seconds polling is used instead. Because of that timing could be incorrect when a different monitor is plugged in.

Description: USB Port works only in host mode.

Description: USB host port is not working, it resets every 2 seconds (`usb 1-1: reset high-speed USB device number 2 using ci_hdrc`)

Description: Playing audio on a Dahlia Carrier Board using a Verdin iMX8MM causes distortion on the audio output.

Workaround: Use 48kHz sample rate or set `simple-audio-card,mclk-fs = <256>;` in sound_card dts node.

Description: Under very rare timing circumstances, a data corruption might occur on a dirty cache line that is evicted from the L1 Data Cache due to another cache line being fully written, see ARM Cortex-A9 Errata 845369 for details. This could happen because `CONFIG_ARM_ERRATA_845369` is not enabled in U-Boot configuration. Enabling this errata has some effect on memory benchmark results, but it is not expected to have a significant impact on real applications.

Workaround: Enable `CONFIG_ARM_ERRATA_845369` in U-Boot configuration.

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: Sometime (around 20% of the time) it is not possible to resume from suspend.

Description: Restarting hostapd makes it impossible for clients to connect to the AP.

Workaround: Reboot the system after a hostapd configuration change. It's also possible to rmmod / modprobe mwifiex before restarting hostapd to apply the configuration change without a reboot.

Description: USB Host interface is not working in U-Boot.

Workaround: apalis-imx8: execute `gpio set 132` before `usb start`

Description: As per NXP errata ERR050805 (https://www.nxp.com/docs/en/errata/IMX8MM_0N87W.pdf), DRAM Controller automatic de-rating logic may not work when the LPDDR4 memory temperature is above 85ºC at initialization. The DDR Controller will therefore not automatically adjust the memory refresh rate or de-rate memory timings based on the LPDDR4 memory temperature. This may cause the controller incorrectly setting the refresh period, potentially cause the LPDDR4 memory losing data contents and lead to possible data integrity issues above 85ºC.

Description: USB Host doesn't work on Colibri i.MX8X with Aster device tree

Workaround: Use evaluation board device tree file

Description: Under very rare timing circumstances, a data corruption might occur on a dirty cache line that is evicted from the L1 Data Cache due to another cache line being fully written, see ARM Cortex-A9 Errata 845369 for details. This could happen because `CONFIG_ARM_ERRATA_845369` is not enabled in U-Boot configuration. Enabling this errata has some effect on memory benchmark results, but it is not expected to have a significant impact on real applications.

Workaround: Enable `CONFIG_ARM_ERRATA_845369` in U-Boot configuration.

Description: The SLEEP_MOCI# is not properly configured on the Verdin iMX8M Plus, because of that any carrier board relying on this signal could have malfunctions. CAN/PCIe and USB are not working correctly on Dahlia because of that.

Description: Playing audio on a Dahlia Carrier Board using a Verdin iMX8MM causes distortion on the audio output.

Workaround: Use 48kHz sample rate or set `simple-audio-card,mclk-fs = <256>;` in sound_card dts node.

Description: Hot-plugging USB devices on the USB host port USB_2 does not work on a custom carrier board without a USB hub in-between. Note that current Toradex carrier boards (Dahlia and the Verdin Development Board) do have such a USB hub and therefore do NOT exhibit this issue as the USB hub itself is handling the hot-plugging. This issue is related to USB runtime power-management.

Workaround: Add `power-domains = <&usb_otg2_pd>;` property to `&usbphynop2` node in the device tree.

Description: It is not possible to control the built-int Ixora V1.2 LEDs using the Apalis IMX8.

Description: Print systemd boot messages to the uart, the default console output

Description: MDIO read timeout is randomly popping up during link-up and causing ethernet to stop working

Workaround: Setting the interface down and up again fixes the problem

Description: MDIO read timeout can prevent proper ethernet initialization at boot

Workaround: Bring the interface down and up again

Description: Spi CAN Controller is receiving wrong data when frames of different length are sent

Description: The Verdin iMX8M Mini may crash during boot with the default configuration if the DSI to HDMI display adapter is NOT plugged in.

Workaround: Remove DSI to HDMI adapter overlay in case you do not have the adapter present (see also `skip_fdt_overlays`)

Description: Bring-up of PCIe fails with a PCIe PLL lock timeout at boot.

Workaround: Use BSP 5.2.0.

Description: In U-Boot the NAND storage is much slower compared to Linux (1MiB/s vs 30MiB/s)

Description: Suspend/Resume sometimes freezes when going to suspend. This happens about every 5 to 10 times when going to suspend.

Workaround: None

Description: The 0028 Apalis iMX6 Quad 2GB IT SoM may sporadically fail to boot in case the ambient temperature exceeds 70 degrees Celsius. The issue is likely caused by sub-optimum RAM timings. The issue is going to be resolved by a future software update (delivering updated RAM timings).

Workaround: Updating to BSP 5.4.0 or any newer release fixes the issue.

Description: The interactive U-Boot cfgblock create command wrongly always creates a ConfigBlock for the NAND rather than the eMMC version of the module.

Description: The following messages are shown upon resume:
[ 1912.202108] fec 30be0000.ethernet eth0: MDIO write timeout
[ 1912.202119] Micrel KSZ8041 30be0000.ethernet-1:00: failed to set led mode

Workaround: Cosmetic problem. Nothing needs to be done.

Description: SATA is not working stable.

Workaround: None

Description: When trying to resume an apalis-imx8 with WAKE1_MICO# signal it does not wake up and the module freezes. It seems to crash on resume.

Description: We may violate the on-module PHY reset timing and attempt communication with the PHY after resume while the PHY is still held in reset.

Workaround: In device tree delay the voltage regulator coupled to the fec/phy

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: cfgblock create <16-digit-serial> modifies the 7th digit to be always 0. This creates a wrong version information for modules with an assembly version 'K' or higher (e.g. Apalis iMX6 V1.1K)

Workaround: Start 'cfgblock create' without parameters to enter the data in the interactive mode.

Description: As version X1 of the camera adapter board uses different GPIOs as compared to the initial E1 version, the apalis-imx8_ar0521_overlay for the e-con Systems e-CAM55_CUMI0521_MOD camera does not work on BSP 5.1.0 Quarterly.

Workaround: You may find the following patch fixing the pin muxing for the Rev. X1 camera adapters:
https://git.toradex.com/cgit/device-tree-overlays.git/commit/?h=toradex_5.4-2.3.x-imx&id=08808b502c224e6143ae19518cf4f844ca2ee03c

Description: The following crash can be observed during system reboot:To reproduce please type, reboot command and check for trace from weston ........ [ 54.358713] weston: unhandled page fault (11) at 0x636f6c33, code 0x005 [ 54.365339] pgd = d33edf7e [ 54.368125] [636f6c33] *pgd=00000000 [ 54.371718] CPU: 0 PID: 495 Comm: weston Not tainted 5.4.91-5.1.0-devel+git.6ad99da2c675 #1 [ 54.380101] Hardware name: Freescale i.MX6 Ultralite (Device Tree) [ 54.386291] PC is at 0x76d5cc88 [ 54.389459] LR is at 0x76d5cc79 [ 54.392604] pc : [<76d5cc88>] lr : [<76d5cc79>] psr: 600b0030 [ 54.398895] sp : 7e84c698 ip : 76eb1bfc fp : 7e84c810 [ 54.404121] r10: 01cf4cd8 r9 : 7e84c9fc r8 : 01cf9988 [ 54.409371] r7 : 01cf5308 r6 : 01cf9988 r5 : 01d51d78 r4 : 636f6c2f [ 54.415901] r3 : 01d22b40 r2 : 01cf305c r1 : 02000000 r0 : 636f6c2f [ 54.422467] Flags: nZCv IRQs on FIQs on Mode USER_32 ISA Thumb Segment user [ 54.429907] Control: 10c5387d Table: 9530406a DAC: 00000055 [ 54.435659] CPU: 0 PID: 495 Comm: weston Not tainted 5.4.91-5.1.0-devel+git.6ad99da2c675 #1 [ 54.444013] Hardware name: Freescale i.MX6 Ultralite (Device Tree) [ 54.450222] [<8010db6c>] (unwind_backtrace) from [<8010ae84>] (show_stack+0x10/0x14) [ 54.457980] [<8010ae84>] (show_stack) from [<808c9514>] (dump_stack+0x90/0xa4) [ 54.465218] [<808c9514>] (dump_stack) from [<8011194c>] (__do_user_fault+0xfc/0x100) [ 54.472972] [<8011194c>] (__do_user_fault) from [<80111d2c>] (do_page_fault+0x354/0x394) [ 54.481074] [<80111d2c>] (do_page_fault) from [<80111ed4>] (do_DataAbort+0x3c/0xc0) [ 54.488741] [<80111ed4>] (do_DataAbort) from [<80101ddc>] (__dabt_usr+0x3c/0x40) [ 54.496138] Exception stack(0x952fdfb0 to 0x952fdff8) [ 54.501199] dfa0: 636f6c2f 02000000 01cf305c 01d22b40 [ 54.509385] dfc0: 636f6c2f 01d51d78 01cf9988 01cf5308 01cf9988 7e84c9fc 01cf4cd8 7e84c810 [ 54.517567] dfe0: 76eb1bfc 7e84c698 76d5cc79 76d5cc88 600b0030 ffffffff\ ........

Description: There is no output on the parallel RGB port which affects the operation of 7 inch capacitive and resistive touch panels.

Description: The XDG_RUNTIME_DIR variable required for graphical Wayland/Weston output is not set in an SSH shell.

Workaround: Use the local serial console instead.

Description: USB switches its role-state from client to host, client works but host does not enumerate plugged in devices.

Workaround: None

Description: HDMI driver is sometimes crashing when booted.

Workaround: Do not use CONFIG_DRM_CDNS_HDMI_CEC

Description: On certain modules USB Host does not work correctly and outputs an endless error "usb 3-1: device descriptor read/all, error -71"

Workaround: Use the adjusted pinmuxing for USB-HSIC &usbh1 node in devicetree from most recent images. http://git.toradex.com/cgit/linux-toradex.git/tree/arch/arm64/boot/dts/freescale/imx8-apalis-v1.1.dtsi?h=toradex_5.4-2.3.x-imx#n1192

Description: Add support for USB Host in U-Boot.

Description: Add STMPE ADC driver back that is missing.

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

Description: The Apalis iMX8 HDMI has problems with some display resolutions. This ticket solves the issues.

Description: NXP i.MX 8QXP/8QM-based modules the buildinfo shows some garbage instead of IMX-MKIMAGE version used.

Description: WEIM pins missing in device tree.

Workaround: Copy the device tree setting from kernel branch 4.14-2.3.x-imx.

Description: Enabling fec2 in device tree will lead to eth0 and eth1 interfaces stop working.

Description: USB not working properly with multiple errors looking like
[ 12.054106] usb 1-1.1: new high-speed USB device number 7 using cdns-usb3
[ 12.199669] usb 1-1.1: unable to read config index 0 descriptor/all
[ 12.206008] usb 1-1.1: can't read configurations, error -71
[ 12.298077] usb 1-1.1: new high-speed USB device number 8 using cdns-usb3
[ 12.455115] usb 1-1.1: unable to read config index 0 descriptor/all
[ 12.461442] usb 1-1.1: can't read configurations, error -71

Description: Add usbgadget and libcomposite to upstream images.

Description: When using the on-module Wi-Fi "Invalid Sched_scan" message appears. This error message has no meaning in our use-case so we removed it.

Description: The GPIO list as visible at /sys/kernel/debug/gpios is shifted by one (e.g. it starts with gpio5-01 while it really should start with gpio5-00).

Description: UMS command doesn't work on Verdin iMX8M Mini.

Description: The OV5640 camera currently only works when requesting a 640x480 resolution. All higher resolutions have the gstreamer pipeline start but then no video data get displayed.

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

Description: This issue occurs for transferring 2 to 31 bytes count.

Workaround: Apply fix https://github.com/torvalds/linux/commit/2801b2f5fad3d1e9ea0ac8484584051071065645#diff-4cb745fc6dcd5915b18eb9baa5beee00.

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: RpMsg char Device does not work correctly

Description: Audio codec sgtl5000 doesn't successfully resume after suspending the system.

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: Apalis TK1 dual camera use case crashes when one camera application is stopped and subsequently restarted.

Description: Commit 41ec065f fixed the eCSPI SDMA script type for SPI1-4 only.
Commit df07101e did set the wrong SDMA script type for SPI5. The workaroud SDMA script does NOT work on the SPBA bus, so revert to the correct SDMAa script type for SPI5.

Description: Using GStreamer 1.12 from the OpenEmbedded/Yocto BSP with the MIPI-CSI OV5640 camera driver CONFIG_MXC_CAMERA_OV5640_MIPI_NV stutters (frames seem to be shown not in the correct order).

Description: cfgblock create <16-digit-serial> modifies the 7th digit to be always 0. This creates a wrong version information for modules with an assembly version 'K' or higher (e.g. Apalis iMX6 V1.1K)

Workaround: Start 'cfgblock create' without parameters to enter the data in the interactive mode.

Description: hostapd systemd does not work on the startup

Workaround: In /lib/systemd/system/hostapd.service, change the line "After=network.target" to "After=multi-user.target"

Description: The analogue camera adapter/module connected to the parallel camera interface of the Colibri T20 is not working.

Workaround: Manually enabling the BL_ON GPIO which is used as NRESET on the ACA may help.

Description: In order to use USB 3.0 with BSP 2.8b6 modify the U-Boot defargs environmental variable from "usb_port_owner_info=2" to "usb_port_owner_info=3". This will disable USB OTG functionality on USBO1 port and enable USB 3.0 host mode.

Description: We still had some recipes labelled with 21.5. Going through all our TK1 recipes we identified libgstnvegl and libgstomx-0.10 never actually got updated to building off from R21.7 sources.

Workaround: Fix available on meta-toradex-tegra.git branch rocko-next.

Description: If an Android phone is connected to the Colibri iMX6ULL, then an unexpected Linux kernel bug is shown and Bluetooth stops connecting. The only solution is to restart the module.

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: Kernel crashes after M4 firmware started. The only log message is "Starting Kernel ...".

Workaround: Enter the following commands in U-Boot: setenv fdt_high=0xffffffff saveenv

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: Wake from suspend is not working on Colibri iMX6ULL 512MB Wi-Fi / Bluetooth IT.

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

Description: We have unused pinmuxings for flexcan1 and flexcan2. Unify the pad settings for the two.

Description: The Colibri iMX7 dts files define a flexcan1 node, but the developer webpage https://developer.toradex.com/knowledge-base/can-(linux) only describe how to enable a (non existing) flexcan2 node. Clean that up. Probably one should add in both places the missing node.

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: In dual CAN operation, Apalis TK1 CAN may stop working, when error or collision happens on one of the busses.

Description: In a period between driver initialisation and interface bring-up, packets send on the bus with baud rate different then 1Mbps will be treated as invalid.

Description: Currently, the device tree specifies 2.5V as SGTL5000 VDDA. This is wrong, in practice, the board uses 3.3V Audio voltage as VDDA.

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: 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: 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: In a SDK the symlink sysroots/armv7at2hf-neon-angstrom-linux-gnueabi/usr/lib/arm-linux-gnueabihf/tegra/libGL.so currently points to ./arm-linux-gnueabihf/tegra/libGL.so.1 which does not exist.

Workaround: Fix the symlink in the unpacked SDK: ln -fs libGL.so.1 .../sysroots/armv7at2hf-neon-angstrom-linux-gnueabi/usr/lib/arm-linux-gnueabihf/tegra/libGL.so

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: Unfortunately, starting with BSP 2.8b2 the regular LXDE based demo image root file system reached a size which does no longer easily fit into 256MB of RAM, therefore, failing the legacy update procedure (it may just hang or even crash but definitely fails updating the root file system).

Workaround: Doing the following before 'run setupdate; run update' helps:
setenv fdt_addr_r 0x01000000

Description: Colibri iMX6ULL Crashing After Resuming from Suspend on Iris

Workaround: A patch is available in toradex_4.9-1.0.x-imx-next "arm: imx: gpc: do not poweroff M/F mix in suspend"

Description: Apalis TK1 legacy update is not deploying the v1.2 devicetree.

Workaround: Use Toradex Easy installer or u-boot ums mode.

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: 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: Integrate solutions proposed by Nvidia (L4T R21.7) and NXP to mitigate Meltdown and Spectre security vulnerabilities.

Description: The built-in/on-module Wi-Fi of the Colibri iMX6ULL 512MB Wi-Fi / Bluetooth IT module currently does not support the access point aka ap mode.

Workaround: You may force the mwifiex driver to create two interfaces during initialization
echo "options mwifiex driver_mode=0x3" > /etc/modprobe.d/mwifiex.conf
The interface mlan0 is a regular station interface while the uap0 interface can be used as an access point.

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: The USBC port does only work in device mode. Switching to host does not work. This is a regression introduced with the move to the 4.9 kernel version.

Workaround: Cherry-pick the following commit: 'ARM: dts: imx6ull-colibri: Specify cable detect as ID and VBUS pin' and recompile and deploy the device tree.

Description: The internal aka on-module RTC is not available since we migrated to the Linux 4.9 kernel (2.8b1).

Description: The system freezes during boot shortly after initializing the MCP2515 CAN controller. The CAN controller triggers a (re)probe of the thermal driver which fails to probe during boot. This late probe causes the driver to access OTOCP registers which are not clocked anymore.

Workaround: Add clk_ignore_unused to defargs in the U-Boot command line (e.g. by using "setenv defargs ${defargs} clk_ignore_unused").

Description: Adding pcie_aspm=off to kernel cmdline may fix problems with PCIe cards on Apalis TK1.

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: We moved a while ago to a SPL/u-boot.img approach. The SPL runs in SRAM and configures the DDR-RAM, then it loads U-Boot proper into DDR and passes control. In the legacy update procedure, the recovery mechanism however stayed with a monolithic u-boot.imx binary which had to be built separately. Change also the recovery procedure to a download chain of first loading SPL and then u-boot.img. Note that the Toradex Easy Installer works that way successfully for some time.

Description: The early sample hardware Apalis iMX6 V1.0A/B have a different UART pin-out which require a specific device tree. Starting with 2.8 Beta 1 we no longer provide these device trees.

Workaround: Use an older BSP or forward port the relevant changes between the device tree targeting the later HW vs. V1.0 HW.

Description: The kernel prints "Timeout waiting for hardware interrupt" errors when accessing eMMC, particularly at boot-up.

Description: Apalis/Colibri T30 PWM was capped at 12.45kHz. We've increased it to 99.6kHz that can be further divided by integer divider.

Workaround: PWM peripheral input clock value can be increased to a maximum of 48MHz. Valid clock values can be calculated pwm_clk = 408MHz/N, where N=<1 , 128.5> in 0.5 increments

Description: We fixed CAN after NVIDIA's recent L4T R21.6 SPI improvements.

Description: As we juggled around some of the pins the GPIO Tool also needs updating.

Description: As PWM support is currently not available the PWM pin (SODIMM 59) is statically set to output with the value '0' in the regular U-Boot and to an input with pullup in the case of the Toradex Easy Installer. If a connected display has its backlight off in that case one ends up with a dark display. The VGA (RGB DAC) output is not affected.

Workaround: - On the Evaluation Board remove the PWM jumper and hard-wire the desired level. - For a regular image one can change the value from the U-Boot command line: 'gpio set 107'. E.g. add that as the first command to the bootcmd environment variable. - For the Toradex Easy Installer one can configure the pin to gpio and set a value from the U-Boot command line: 'mw.l 020e01a4 5 1; gpio clear 107'.

Description: The config block check aka check_configblock may fail during update depending on the size of the hardware area boot partition which may lead to the config block not getting properly migrated or updated if still using parts of the legacy update procedure.

Workaround: Use U-Boot's built-in 'cfgblock create' functionality or use the Toradex Easy Installer where applicable. Alternatively find fixed legacy U-Boot update scripts in the -next branch of our meta-toradex-demo repository.

Description: So far in U-Boot we violated the PCIe reset timing specification and in Linux we did not do anything about doing the PCIe reset unisono with the separately switchable voltage rail of the gigabit Ethernet chip.

Workaround: A solution to the U-Boot side of things may be found on our -next branch now.

Description: The Colibri iMX7D has 512MiB of memory. However, when running the Cortex-M4 core only half of the memory is available in Linux.

Description: We forgot to actually deploy the new device tree: imx6q-apalis-ixora-v1.1.dtb.

Workaround: Just checkout the Linux kernel sources, build the device trees and copy imx6q-apalis-ixora-v1.1.dtb to the update SD card into the apalis_imx6 folder. Then in U-Boot first 'setenv fdt_file imx6q-apalis-ixora-v1.1.dtb; saveenv' and do a 'run setudpate; run update_fdt'.

Description: Power I2C bus communication speed should be reduced to 100 KHz as our temperature sensor chip LM95245 is not rated for higher speeds.

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: 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: 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: When booting after flashing the root file system from within Linux (e.g. Toradex Easy Installer) booting fails with UBI init error 22.

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: Trying to sdboot from an ext4 rootfs fails due to us defaulting to ext3. While the downstream T20/T30 L4T kernel has issues with ext4 later TK1 L4T should work just fine with it.

Workaround: Just change the sdargs to ext4 as follows: setenv sdargs 'ip=off root=/dev/mmcblk1p2 rw rootfstype=ext4 rootwait'

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: Since the move to the toradex_4.1-2.0.x-imx kernel poweroff fails powering off the PMIC once Linux reached halt.

Workaround: One could poweroff the carrier board by using a GPIO. http://developer.toradex.com/knowledge-base/gpio-(linux)#GPIO_PowerOff

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: The udev rule /etc/udev/rules.d/hdmi.rules which should take care of this now fails with exit code 1. It looks like the RUN part of that rule should be reworked into its separate unit file to be spawned using SYSTEMD_WANTS.

Workaround: Manually call xrandr to get the desired effect.

Description: CPU and GPU thermal throttling is not working which can be seen from /sys/kernel/debug/tegra_throttle/ being empty.

Workaround: Find the fix on 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: Using PREEMPT_RT patch with Linux 4.4.21 on Colibri VF61 results in a freeze at boot time.

Workaround: Disable serial console either via kernel boot arguments or kernel configuration (CONFIG_SERIAL_FSL_LPUART_CONSOLE).

Description: Colibri T20 modules may hang during boot if HDMI is not connected.

Workaround: The fix for this issue may be found here: http://git.toradex.com/cgit/linux-toradex.git/commit/?h=tegra&id=943dd8a82f13c2e31a7f243bb15ae64edf45b7fa

Description: The frame buffer boot configuration integration via kernel command line is still missing.

Workaround: The LVDS configuration is currently hard-coded here: http://git.toradex.com/cgit/linux-toradex.git/tree/arch/arm/mach-tegra/panel-c-lvds-1366-14.c?h=toradex_tk1_l4t_r21.5#n322

Description: When using UART with DMA it can lock up the UART sending path. The serial console might lock up completely.

Workaround: Disable DMA for UART.

Description: No more driver limitation requiring to have a valid Link on the external Ethernet port (FEC0) in order to send and receive frames from Linux.

Description: SPI read issue when using multiple SPI_IOC_MESSAGEs.

Workaround: Always use SPI_IOC_MESSAGE(1).

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: Currently our update.sh script limits the partition size to around 4GB by default so even after our automatic resizing only 4GB of the 8GB of available eMMC space on the Apalis T30 2GB can be used.

Workaround: Manually modify the EMMC_SIZE calculation for apalis-t30 in our update.sh script. Our upcoming Toradex Easy Installer will no longer suffer from this limitation.

Description: Our current update procedure requires the rootfs payload to fit in one file on a FAT filesystem. This limits its usable size to 4GB.

Workaround: - use the ums command in U-Boot to export the module's eMMC as a mass storage device - deploy a minimum rootfs and install the 'big' payload after booting into Linux - update over tftp, but see http://developer.toradex.com/software/linux/linux-software/release-details?view=release-roadmap&&issue=21229

Description: Currently our update.sh script limits the partition size to around 8GB by default so even after our automatic resizing only 8GB of the 16GB of available eMMC space can be used.

Workaround: Manually modify the EMMC_SIZE calculation for apalis-tk1 in our update.sh script. Our upcoming Toradex Easy Installer will no longer suffer from this limitation.

Description: Closing the touch device while the touchscreen locks the closing task and leads to a task blocked kernel message.

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: Our current PEX 8605 errata workaround violates the PCIe clock and reset specification should no PCIe switch be present as e.g. the case on Ixora.

Workaround: http://git.toradex.com/cgit/linux-toradex.git/commit/?h=toradex_tk1_l4t_r21.5&id=3e2259b04c2e2c029f742e9dda06a3a2739977d4

Description: The GPIO used on MXM Pin 190 on Apalis TK1 V1.0 modules cannot be used correctly. We therefore changed to another GPIO in our V1.1 of the Apalis TK1 module.

Workaround: http://git.toradex.com/cgit/linux-toradex.git/commit/?h=toradex_tk1_l4t_r21.5&id=b205234f92db5980ca374de65408f81f6dcf37d8

Description: Flashing module using an U-Boot loaded via USB fails.

Workaround: Set "soc" environment variable to imx7d or imx7s (depending on your module) before executing the update commands.

Description: Currently NVIDIA's proprietary hardware accelerated Gstreamer plug-in nvvidconv is missing from our Embedded Linux BSP release.

Workaround: You may use either NVIDIA's L4T directly or at least specific Gstreamer plug-ins therof: http://developer.toradex.com/knowledge-base/installing-nvidia-jetpack-with-l4t-on-apalis-tk1

Description: Suspend/resume on Vybrid is currently broken.

Description: BL_ON GPIO control is currently missing.

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

Description: If no HDMI screen is connected pcmanfm will consume 100% CPU.

Workaround: Removing the '/usr/bin/xrandr --output LVDS-0 --off' line from /etc/xdg/lxsession/LXDE/autostart works around this issue.

Description: u-boot reads the chip temperature and doesn't continue to boot if it's above 80°C. That doesn't make sense for industrial temperature range modules.

Description: On the BSB V2.6 Beta1 an OV5640 MIPI Camera does no longer work out of the box. This is caused by a driver having its compatible string changed.

Workaround: Correct the compatible string in the device tree.

Description: On the Colibri iMX6DL the RAM configuration is not patched correctly causing only 256MB aka half of the RAM being available.

Workaround: A fix is already available on the 2015.04-toradex-next U-Boot branch.

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: 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: We are currently chasing a strange race condition/sequencing issue concerning eMMC seen on certain Colibri iMX6 modules. An affected module will continue to boot off the regular eMMC user area while our update scripts will update the one located in the boot area which may lead to quite some confusion/inconsistencies.

Workaround: Just manually enter the following from within U-Boot for now and you should be fine again:
Colibri iMX6 # mmc partconf 0 1 1 0
More information about this is available here: http://developer.toradex.com/software-resources/arm-family/linux/linux-booting#eMMC_Hardware_Boot_Area_Partitions_ApalisColibri_iMX6_and_ApalisColibri_T30

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

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: Libc based memory copy recently slowed down by almost a factor of two.

Workaround: Use one of our V2.1 based BSPs which did not exhibit this issue.

Description: On Ixora with set jumper JP2 the lower X8 USB host port (shared with the X9 micro USB port) is not reliably working. There seems to be a race condition in NVIDIA's USB OTG driver concerning the loading and binding of the USB device gadget driver which prevents Apalis USBO1 being operational in host mode.

Workaround: Disconnecting the USB device, removing the jumper JP2, connecting a USB micro cable to a PC, disconnecting the same again, jumpering JP2 again and connecting the USB device again should remedy the issue. Alternatively booting with JP2 removed and only connecting JP2 after boot also works.

Description: One might get the following floating point exception when using nv_omx_h264enc either trying to transcode MPEG transport streams or encode video stream coming from a Gstreamer appsrc: +NvxVideoEncoderSetNvMMAttributes-NvxVideoEncoderSetNvMMAttributesFloating point exception

Workaround: If you experience this exact issue please downgrade to our V2.3 Beta 3 (October 31, 2014) release for now. We opened a ticket with NVIDIA and are working with them to get this resolved as soon as possible.

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: Currently there are kernel errors after suspend to RAM when using AC97.

Description: The USB client implementation is unreliable and freezes communication from time to time (e.g. when using the USB client driver RNDIS/g_ether).

Description: Certain low-speed USB devices are not detected correctly when plugged into a running system.

Workaround: Use a hub or ensure device is connected before power up. A driver fix will be made to correct this behaviour.

Description: PCIe is rarely unavailable after Boot on the Apalis T30 module indicated by the following kernel message(s) during boot: 'PCIE: port 0: link down, ignoring', 'PCIE: port 1: link down, ignoring' and/or 'PCIE: port 2: link down, ignoring'. Gigabit Ethernet is also affected by this issue as its controller chip is connected through PCIe indicated by the following missing kernel message during boot: 'igb 0000:01:00.0: Intel(R) Gigabit Ethernet Network Connection' resp. 'igb 0000:07:00.0: Intel(R) Gigabit Ethernet Network Connection'. We are working together with NVIDIA to solve this issue as it seems to be a hardware issue of the PCIe controller in the T30 SoC.

Workaround: Currently the only thing known to help is power-cycling or sometimes also doing a reset. As the issue is probably dependant on operating conditions such as temperature varying this might also help. We are working together with NVIDIA to find a good software workaround for this issue.

Description: Rare I/O error observed on eMMC which might prevent successful boot.

Workaround: Power-cycle usually helps. Alternatively use a later custom kernel or await our official release thereof.

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: Currently NFS booting mostly fails due to some timeouts in the Ethernet resp. USB stack.

Workaround: Build latest U-Boot sources from git.toradex.com.

Description: HDMI audio has an incorrect sampling frequency so the recorded audio stream is distorted.

Workaround: None. Await updated driver.

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.