|Known Issue for Colibri VF61: U-Boot 2016.11 Missing m4boot Command.|
| 22974||Fixed||SysV Initscript Interference at Times Causing Networking Subsystem not to Start||Apalis T30, Apalis TK1, Apalis iMX6, Colibri T20, Colibri T30, Colibri VF50, Colibri VF61, Colibri iMX6, Colibri iMX7|
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.
| 22319||Fixed||Ethernet Switch Requires the External Ethernet Port to be Connected||Colibri VF50, Colibri VF61||Ethernet, Kernel|
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.
| 21704||Fixed||Using keypad driver causes kernel freeze on iMX7||Colibri iMX7||Kernel, Miscellaneous Peripherals|
Description: Using keypad driver causes kernel freeze on iMX7
Workaround: Use the generic GPIO driven matrix keyboard driver
| 21618||Fixed||SPI read issue when using multiple SPI_IOC_MESSAGE||Colibri VF50, Colibri VF61||SPI|
Description: SPI read issue when using multiple SPI_IOC_MESSAGEs.
Workaround: Always use SPI_IOC_MESSAGE(1).
| 21604||New Feature||Linux-ptp in BSP||Apalis T30, Apalis TK1, Apalis iMX6, Colibri VF50, Colibri VF61, Colibri iMX6, Colibri iMX7||Buildsystem, Ethernet|
Description: Include linuxptp in BSP image
| 21499||Fixed||SD-card: 1-bit bus width operation not working||Colibri VF50, Colibri VF61||Kernel, SDIO/SD/MMC|
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.
| 21351||Fixed||Adjust X22 EvalLoc in GPIO Tool (formerly GPIOConfig) to Latest Colibri Evaluation Board V3.2 Pinout||Colibri T20, Colibri T30, Colibri iMX6||GPIO|
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.
| 21277||New Feature||Port GPIO Tool to Apalis TK1||Apalis TK1||GPIO|
Description: The gpio-tool will allow to override pin muxing functionality and test GPIO input/output functionality.
| 21274||New Feature||Configure IPv6-in-IPv4 Tunnel (SIT Driver) as Module||Apalis T30, Apalis iMX6, Colibri T20, Colibri T30, Colibri VF50, Colibri VF61, Colibri iMX6, Colibri iMX7||Ethernet|
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.
| 21273||New Feature||Port GPIO Tool to Colibri iMX7||Colibri iMX7||GPIO|
Description: The gpio-tool will allow to override pin muxing functionality and test GPIO input/output functionality at runtime.
| 21272||New Feature||Support I2C RTC||Apalis TK1||I2C, RTC|
Description: Support I2C RTC.
Workaround: Use PMIC integrated RTC for now.
Alternatively the mainline Linux kernel already supports the board-level I2C RTC.
| 21238||Fixed||PCIe Clock and Reset May not Conform to Specification||Apalis T30||PCIe|
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.
| 21234||Fixed||eMMC Partition Limited to 4GB||Apalis T30||Flash|
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.
| 21229||Fixed||Update Scripts Limits rootfs Size to around 5GB when using TFTP||Apalis T30, Apalis TK1, Apalis iMX6, Colibri T30||Flash|
Description: Our current update procedure reads the rootfs payload in pre split files of 64 MB size. The number of chunks is limited to 89 resulting in a maximum size of 5.5 GB.
Workaround: - use the ums command in U-Boot to export the modules eMMC as a mass storage device.
- deploy a minimum rootfs and install the 'big' payload after booting into Linux
| 21228||Fixed||Update Scripts Limits rootfs Size to 4GB||Apalis T30, Apalis TK1, Apalis iMX6, Colibri T30, Colibri iMX6||Flash|
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
| 21227||New Feature||Update U-Boot for all Modules to be Based on Latest Mainline Release||Apalis T30, Apalis TK1, Apalis iMX6, Colibri T20, Colibri T30, Colibri VF50, Colibri VF61, Colibri iMX6, Colibri iMX7||Bootloader|
Description: Updates our downstream U-Boot to latest mainline, likely 2016.11.
| 21226||New Feature||OpenEmbedded: Update to the Morty Release||Apalis T30, Apalis TK1, Apalis iMX6, Colibri T20, Colibri T30, Colibri VF50, Colibri VF61, Colibri iMX6, Colibri iMX7||Buildsystem|
Description: Update our layers and the OE setup to support and use the morty release aka. Yocto Project 2.2.
| 21141||New Feature||SODIMM 45 Wake-up uses Pull-up while carrier boards and other modules use Pull-down||Colibri iMX7||GPIO|
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.
| 21136||Fixed||Using Rpmsg Leads to Kernel Crashes||Colibri iMX7||Miscellaneous Peripherals|
Description: Using rpmsg and exercising the memory subsystem leads to unrecoverable kernel crashes.
Workaround: Use "linux,usable-memory = <0x80000000 0xff00000>;" for iMX 7Solo or "linux,usable-memory = <0x80000000 0x1ff00000>;" for i.MX 7Dual in the device tree memory node.
| 20869||Fixed||eMMC Partition Limited to 8GB||Apalis TK1||Flash|
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.
| 20820||Fixed||SSH X11 Forwarding is Disabled by Default||Apalis T30, Apalis TK1, Apalis iMX6, Colibri T20, Colibri T30, Colibri VF50, Colibri VF61, Colibri iMX6, Colibri iMX7||Ethernet|
Description: In later OE versions the default SSH config changed so that X11 forwarding is not allowed.
$ ssh -X firstname.lastname@example.org
X11 forwarding request failed on channel 0
Workaround: Edit /etc/ssh/sshd_config to include
| 20753||Fixed||Resistiv Touch Driver Crashing with Stuck Touch Screen||Colibri VF50||Resistive Touch|
Description: Closing the touch device while the touchscreen locks the closing task and leads to a task blocked kernel message.
| 20642||New Feature||Support Touchscreen and ADC on K20 MCU||Apalis TK1||Resistive Touch|
Description: Integrate K20 MCU based touchscreen support connected to TK1 via SPI.
| 20407||New Feature||Support Basic GPIO Feature on K20 MCU||Apalis TK1||GPIO|
Description: Add support to use signals from the K20 companion MCU connected to the MXM connector as GPIOs. Basic support will be non-interrupt safe (may sleep) and the latency will be similar to regular SPI GPIO expanders.
| 20370||New Feature||Regression: Poweroff when Poweroff||Colibri VF50, Colibri VF61||Kernel, Power Management|
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.
| 20173||Fixed||DMA Error with UART on Stress Testing SPI/CAN||Colibri VF50, Colibri VF61||DMA, SPI, UART|
Description: SPI transfers using DMA can be affected if another peripheral like UART relying on DMA is also being simultaneously stressed during the SPI transfers.
Workaround: Disable DMA for UART while using SPI
| 20116||New Feature||Migrate i.MX 6 Products to FSL Community Kernel||Apalis iMX6, Colibri iMX6||Kernel|
Description: Migrate the kernel used on our i.MX 6 based products to be based on the 4.1-2.0.x-imx branch of the FSL community kernel aka linux-fslc-imx which does already include NXP's latest 4.1.15 2.0.0 GA release changes.
| 19580||New Feature||Add option to completely erase K20 flash||Apalis TK1||Flash|
Description: Documented here: http://developer.toradex.com/knowledge-base/using-k20-companion-mcu-on-apalis-tk1#Erase_Chip_Without_Reprogramming
| 18770||Fixed||DHCP Server on USB RNDIS Announces Module as Router||Apalis T30, Apalis TK1, Apalis iMX6, Colibri T20, Colibri T30, Colibri VF50, Colibri VF61, Colibri iMX6, Colibri iMX7||USB|
Description: When connecting the module using USB device connection, the module provides an IP address via it's own DHCP server. The DHCP server uses DHCP Option 3 (Router) to announce itself as router which can lead to internet connection interruption on the host.
| 18672||Fixed||OE Build on Distro with GCC 6 Host Toolchain||Apalis T30, Apalis TK1, Apalis iMX6, Colibri T20, Colibri T30, Colibri VF50, Colibri VF61, Colibri iMX6, Colibri iMX7||Buildsystem|
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.
| 18015||Fixed||Move to GTK+ 3 in Demo Image||Apalis T30, Apalis TK1, Apalis iMX6, Colibri T20, Colibri T30, Colibri VF50, Colibri VF61, Colibri iMX6, Colibri iMX7||Buildsystem, Graphics|
Description: OE migrated the sato image to GTK+ 3. This includes pcman-fm with its libfm.
As lxpanel is using libfm we have to follow here or provide our own pcman-fm/libfm recipes.
If we move to GTK+ 3 I guess we should do it with all GTK+ based software. e.g all of lxde/lxdm (which may have some issues), the GPIOconfig tool and tegrastats-gtk.
| 17981||New Feature||Distro Boot Integration||Apalis T30, Apalis TK1, Colibri T20, Colibri T30, Colibri VF50, Colibri VF61, Colibri iMX7||Bootloader, SDIO/SD/MMC, USB|
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.
| 16936||New Feature||Implement U-Boot SPL for Memory Bring-up||Apalis iMX6, Colibri iMX6||Bootloader, RAM|
Description: U-Boot SPL will greatly improve overall system boot flexibility.
| 16420||New Feature||Consider Using Udisks2||Apalis T30, Apalis TK1, Apalis iMX6, Colibri T20, Colibri T30, Colibri VF50, Colibri VF61, Colibri iMX6, Colibri iMX7||Buildsystem|
Description: Udisks development has stalled in 2014, udisks2 seems to be the successor.
According to the OE recipes udisks2 also has less dependencies (notable lvm2, which adds almost 3.2MiB to the image and is not commonly used in embedded systems as well as sg3-utils, another 1.1MiB).
Udisks2 also has a command line utility (see: https://zeth.net/2014/05/28/modern_mounting_with_udisks2.html).
| 16131||New Feature||Add FlexCAN Support||Colibri iMX7||CAN|
Description: Add FlexCAN support.
| 16024||New Feature||Update BCB to Support Bad Block Markers and Complete Pages||Colibri VF50, Colibri VF61, Colibri iMX7||Bootloader, ConfigBlock|
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.
|This is a release for Apalis TK1 2GB V1.1A only. The January 2017 release supporting all platforms (iMX6, iMX7, VFxx, T20, T30, TK1) will follow later as V2.7 Beta 1.|
| 21967||Fixed||PCIe Clock and Reset May not Conform to Specification||Apalis TK1||PCIe|
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.
| 21966||Fixed||Update Source Mirror||Apalis TK1||Buildsystem|
Description: As that whole source mirror stuff has been introduced rather haphazardly whoever did that also failed maintaining/updating it since V2.5 (e.g. http://sources.toradex.com/V2.5/). The wohle process around this is currently unclear.
| 21965||New Feature||Configure IPv6-in-IPv4 Tunnel (SIT Driver) as Module||Apalis TK1||Ethernet|
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.
| 21270||New Feature||Support Apalis UART4||Apalis TK1||UART|
Description: Support Apalis UART4.
Workaround: Use UART1, UART2 or UART3 for now.
Alternatively the mainline Linux kernel already supports all 4 UARTs.
| 20736||Fixed||Use Different GPIO for SD1_CD# (MXM Pin 190) on Apalis TK1 V1.1||Apalis TK1||Bootloader, Kernel, SDIO/SD/MMC|
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.
| 19109||Fixed||Resolve Apalis vs. Jetson TK1 Performance Discrepancy||Apalis TK1||CPU, Kernel, Power Management, Temperature Sensor|
Description: VisionWorks demo achieves 10FPS on Apalis TK1 & 30FPS on Jetson TK1. Please identify the cause and resolve it.
Workaround: Fixed by a combination of Norrin soctherm and Laguna cl-dvfs just like used on Jetson TK1: http://git.toradex.com/cgit/linux-toradex.git/commit/?h=toradex_tk1_l4t_r21.5-next&id=3c204d1590b9fcead7169c7f066f6918bcbde55f
| 16986||New Feature||Bring-up eDP||Apalis TK1||Bootloader, Graphics, Kernel, eDP|
Description: Bring-up optional eDP.
| 16984||New Feature||Bring-up CSI-2 Camera Interfaces||Apalis TK1||CSI|
Description: Bring-up type specific CSI-2 camera interfaces.
| 20568||Fixed||Flashing Module Using a U-Boot Loaded via USB Fails||Colibri iMX7||Bootloader|
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.
| 20402||Fixed||100mW Power Saving by Changing Default Settings of Multiplexed Pins of Camera Input||Apalis T30, Colibri T30||Bootloader|
Description: Changing the default settings of multiplexed pins of the camera input allows saving up to 100mW of power.
| 20394||Fixed||Gstreamer Hardware Accelerated Video Format Conversion, Interpolation, Rotation and Scaling Plugin Missing (nvvidconv)||Apalis TK1||DSI, HDMI, LVDS, Video Codecs|
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
| 20365||Fixed||Using Colibri iMX7S Freezes when Using Viola||Colibri iMX7||RTC|
Description: Using Colibri iMX7S freezes when using Viola. Could be a boot rom issue.
Workaround: Disable SNVS RTC in the device tree.
| 20280||Fixed||Fix Broken Suspend/Resume on Vybrid||Colibri VF50, Colibri VF61||Power Management|
Description: Suspend/resume on Vybrid is currently broken.
| 20274||Fixed||Rpmsg does not Work when Using U-Boot to Start FreeRTOS||Colibri VF61||Kernel|
Description: When booting the M4 core using U-Boot (m4boot) rpmsg seems not to work (the kernel module loads but the initial test message does not seem to arrive/be recognized at the FreeRTOS side).
Workaround: Use the remoteproc method to boot the M4 core.
| 20160||New Feature||Deploy Rpmsg Configuration for Vybrid in OpenEmbedded||Colibri VF61||Miscellaneous Peripherals|
Description: Deploy rpmsg configuration for Vybrid in OpenEmbedded.
| 20059||Fixed||Support missing BL_ON GPIO control||Colibri iMX7||GPIO|
Description: BL_ON GPIO control is currently missing.
| 19487||New Feature||Implement OTG Support for Vybrid in das U-Boot||Colibri VF50, Colibri VF61||Bootloader|
Description: OTG support for Vybrid in das U-Boot is currently missing.
| 19484||Fixed||Loading Default USB Gadget Schema Fails||Colibri iMX7||USB|
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.
| 19452||Fixed||Bug in the Parity Control of the Vybrid lpuart Driver||Colibri VF50, Colibri VF61||UART|
Description: There was a bug in the parity control of the Vybrid lpuart driver.
| 19323||Fixed||Missing RS485 Handling||Apalis iMX6, Colibri iMX6||UART|
Description: Our latest kernel is missing RS485 handling e.g. to use the RTS (CTS) output to control a RS485 transmitter.
Workaround: You may find the following commit from our older Linux kernel 3.10.17 as deployed in our embedded Linux BSP V2.4 Beta 1 (May 18, 2015) useful:
| 19086||New Feature||GCC-6 Usable as the Crosstoolchain||Apalis T30, Apalis TK1, Colibri T20, Colibri T30||Kernel|
Description: As OE moves to GCC-6 we should provide our NVIDIA Kernel sources in a way that they can be built with gcc 6.
This would allow customers taking our BSP and using it with a later Yocto project release.
| 19050||New Feature||Enable USB OTG Device/Host Detection on USBC||Colibri iMX7||USB|
Description: Automatic USB Device/Host Detection will allow to use the USB port as either Device or Host (OTG).
Note: The current default on the USB client port (USBC, OTG) is to be USB host. The reason for this default is that the Colibri iMX7S modules only provide this USB port, and USB host is typically used more often than client.
Workaround: If USB device is preferred as default set the device tree "dr_mode" property of the "usbotg1" node to "peripheral".
| 18768||New Feature||EDID Causing Kernel Panic on T30||Apalis T30, Colibri T30||HDMI, Kernel|
Description: Certain EDID from HDMI screens are causing a kernel panic upon boot on T30.
| 18673||New Feature||GCC-6 Usable as the Crosstoolchain||Apalis iMX6, Colibri VF50, Colibri VF61, Colibri iMX6, Colibri iMX7||Bootloader, Buildsystem, Kernel|
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.
| 18669||Fixed||High CPU Usage if no HDMI Screen Connected||Apalis TK1||Graphics, HDMI, LVDS|
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.
| 18404||New Feature||Apalis iMX6Q MXM Pin 130 not Accessible in GPIO Config Tool||Apalis iMX6||GPIO|
Description: A bug in our GPIO Config Tool prevents the Apalis iMX6Q MXM Pin 130 to be accessible.
| 18164||New Feature||Support PWM Polarity Selection||Colibri iMX7||PWM|
Description: Support configuring the polarity of PWM signals via device tree and sysfs.
Workaround: Inverse polarity by calculate duty time as a difference to the current period.
| 18161||New Feature||Unify and Document the Use of fdt_fixup||Apalis T30, Apalis TK1, Apalis iMX6, Colibri T20, Colibri T30, Colibri iMX6, Colibri iMX7||Bootloader|
Description: The use of fdt_fixup should be unified across all our modules and document.
| 16122||New Feature||Fix i.MX 7 Display Timings native-mode Property not Working||Colibri iMX7||Graphics|
Description: The native-mode property for i.MX 7 display timings is not working.
| 16121||New Feature||Add i.MX 7 GPIO Support for all Pins w/o Specific Function||Colibri iMX7||GPIO|
Description: All pins without a specific function should be configured for regular GPIO support.
| 15694||New Feature||Support DMA Mode for SPI||Colibri VF50, Colibri VF61||SPI|
Description: Support DMA enabled receive and send transfers.
| 15351||New Feature||Separate meta-toradex Layer||Apalis T30, Apalis TK1, Apalis iMX6, Colibri T20, Colibri T30, Colibri VF50, Colibri VF61, Colibri iMX6, Colibri iMX7||Buildsystem|
Description: Separate the 'one size fits all' meta-toradex layer into BSP layers by SoC vendor and a software layer for the demo images.
| 10772||New Feature||Switch to Rpmsg as Multi-Core Communication Framework||Colibri VF61||Miscellaneous Peripherals|
Description: Evaluate Linux rpmsg multi-core communication solutions (Remote Processor Messaging).
Workaround: Use MCC version 1.
| 20288||New Feature||Apalis/Colibri T30/iMX6 Stable Release||Apalis T30, Apalis iMX6, Colibri T30, Colibri iMX6||Buildsystem|
Description: This release is identical to the previous V2.6 Beta 2 release and has passed full validation and verification for Apalis T30, Apalis iMX6, Colibri T30 and Colibri iMX6.
| 18016||Fixed||iMX6 Modules don't Boot at Chip Temperatures of 80°C or Higher||Apalis iMX6, Colibri iMX6||Bootloader|
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.
| 17885||New Feature||Upgrade to Linux Kernel 4.1.15||Colibri iMX7||Bootloader, Kernel|
Description: Upgrade the Linux kernel and U-Boot to NXP's latest official i.MX 7 L4.1.0_1.1.0_GA BSP.
| 17884||Fixed||Linux Freezes when using FreeRTOS on Cortex-M4||Colibri iMX7||Kernel|
Description: Despite removing the conflicting UART2 Linux freezes on startup.
| 17736||Fixed||Apalis iMX6 and OV5640 MIPI Camera||Apalis iMX6||Camera Parallel Interface|
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.
| 17564||Fixed||Florence On-Screen Keyboard not Showing Labels on Special Keys||Apalis T30, Apalis iMX6, Colibri T20, Colibri T30, Colibri VF50, Colibri VF61, Colibri iMX6, Colibri iMX7||Miscellaneous Peripherals|
Description: The labels on special keys such as caps lock, enter or tab are missing.
Workaround: A fix is already available on the V2.6-next Meta-Toradex branch.
| 17560||Fixed||Colibri iMX6DL RAM Size Missconfiguration||Colibri iMX6||RAM|
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.
| 17559||Fixed||Potential Gstreamer Freeze on Generating Initial Database||Apalis iMX6, Colibri iMX6||Multimedia|
Description: Gstreamer may freeze when generating its initial database on some modules resulting in the following error message:
(gst-plugin-scanner:683): GLib-GObject-WARNING **: cannot register existing type 'GstImxCompositorPad'
Workaround: The following gets you around this:
mv /usr/lib/libgstimxcompositor.so.0.12.0 /usr/lib/libgstimxcompositor.so.0.12.0.orig
mv /usr/lib/libgstimxcompositor.so.0.12.0.orig /usr/lib/libgstimxcompositor.so.0.12.0
Alternatively one may uninstall libgstimxcompositor0 as follows:
opkg remove --force-depends libgstimxcompositor0
| 16943||Fixed||U-Boot on Colibri iMX7S Freezes when Executing 'usb start'||Colibri iMX7||Bootloader, USB|
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.
| 16466||New Feature||Add Fusion Displays to Simple Panel Driver||Colibri VF50, Colibri VF61||RGB|
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.
| 16129||New Feature||Add i.MX7 Fusion Capacitive Touch Support||Colibri iMX7||Capacitive Touch|
Description: Support the Multi-Touch Controller used on the Toradex Capacitve Multi-Touch Displays.
| 14787||New Feature||LVDS Display Timing Configuration||Apalis iMX6||LVDS|
Description: The move to the 3.14 kernel dropped the possibility to configure the LVDS timings and resolution from the kernel command line and forced the use of the device tree. This provides that feature again.
| 8532||New Feature||Support Ethernet L2 Switch in Vybrid SoC||Colibri VF50, Colibri VF61||Ethernet|
Description: Support Vybrid's internal 10/100MBit hardware L2 Ethernet switch.
Workaround: Use Linux Ethernet bridging support.
| 16470||New Feature||Ethernet Communication not Possible Sometimes||Colibri VF50, Colibri VF61||Ethernet|
Description: On some modules in certain temperature ranges Ethernet might not work after suspend or after bringing down the network interface. The LED constantly blinks and receive/transmit errors might be reported. No frames can be received or sent in this state.
| 16108||New Feature||Audio Codec does not Restore Settings after LPSTOP2||Colibri VF61||Analog Audio, Power Management|
Description: Audio settings do not get restored after suspend-to-RAM (LPSTOP2).
Workaround: Use standby (STOP) mode instead for now.
| 15990||Fixed||Some Modules don't Boot Reliably Because of eMMC Configuration||Apalis iMX6, Colibri iMX6||Bootloader|
Description: A low percentage of modules don't boot reliably because of the bootrom not handling the eMMC correctly. This leads to non booting modules. Using reset solves the problem, a power-cycle mostly works too.
Workaround: Using different i.MX6 fusing options and eMMC configurations seems to solve the problem. For the time being you may evaluate this as described in the following article on our developer website: http://developer.toradex.com/software-resources/arm-family/linux/linux-booting#eMMC_Fast_Boot_Mode_ApalisColibri_iMX6
| 15893||New Feature||Fix 8m/s1 Support in LPUART Driver||Colibri VF50, Colibri VF61||UART|
Description: UART Mark parity bit mode always generates a space parity bit (a 0 instead of a 1).
| 15800||New Feature||Upgrade to Linux Kernel 4.4 LTS||Colibri VF50, Colibri VF61||Kernel|
Description: Use long-term supported Linux kernel release 4.4.
| 15754||New Feature||UART_A DCD Signal can Lead to System Freeze||Apalis iMX6, Colibri iMX6||UART|
Description: When triggering the DCD signal an interrupt is generated which is not handled by the UART driver.
| 15446||New Feature||Unexporting a GPIO does not Disable the Pin||Colibri VF50, Colibri VF61||GPIO|
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.
| 15250||New Feature||PCIe Not Working||Apalis iMX6||PCIe|
Description: While on the Apalis Evaluation board the PCIe switch as well as plugged-in (mini-)PCIe cards usually get detected actual operation may fail.
On Ixora PCIe may fail due to a device reset/initialisation timing issue.
| 12685||Fixed||USB Host does not Work after using LPSTOP Suspend Mode||Colibri VF50, Colibri VF61||Power Management, USB|
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.
| 11844||New Feature||Fix Overrun on UART RX DMA||Colibri VF50, Colibri VF61||UART|
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.
| 10082||New Feature||Use DRM Driver for Vybrid's DCU||Colibri VF50, Colibri VF61||Graphics, RGB, VGA|
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.
| 16903||New Feature||Colibri iMX7 Alpha Release||Colibri iMX7||Buildsystem|
Description: Alpha release for FCS.
| 15322||New Feature||Colibri VF50/VF61 Stable Release||Colibri VF50, Colibri VF61||Buildsystem|
Description: This version is identical to the previous beta version V2.5 beta 3.
| 14901||Fixed||Ethernet PHY State is not Reset on Soft-Reboot||Colibri iMX6||Ethernet|
Description: When rebooting the system using software reboot Linux can leave the PHY in an undefined state (e.g. down) in which case Ethernet may not work in U-Boot unless a hardware reset is performed.
| 14774||Fixed||U-Boot mmc partconf Command Issue||Colibri iMX6||Bootloader, Flash, SDIO/SD/MMC|
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:
| 14194||New Feature||Add Driver for LM006 USB Wi-Fi Dongle to Standard Image||Apalis T30, Apalis iMX6, Colibri T20, Colibri T30, Colibri VF50, Colibri VF61, Colibri iMX6||USB, Wi-Fi|
Description: Add support for the LM Technologies LM006 Wi-Fi USB dongle to our standard images.
| 10723||New Feature||Yocto Integration||Apalis iMX6, Colibri iMX6||Buildsystem|
Description: Move the machine support of the i.MX 6 based modules into the community driven meta-fsl layer.
<machine>.conf, U-Boot and Linux recipes are now available in meta-fsl-arm-extra starting with the OE 'jethro' release.
Note: The V2.5 BSPs which are based on the OE 'fido' release have the Toradex i.MX 6 machine support still in meta-toradex.
| 7798||New Feature||Non Standard UART Baud Rates||Colibri VF50, Colibri VF61||UART|
Description: Driver support for non standard UART baud rates.
| 13770||Fixed||Various UBIFS Related Errors||Colibri VF50, Colibri VF61||Flash|
Description: Various UBIFS errors reported by Linux kernel especially while booting. Some errors might lead to root file system not being mountable.
| 13130||Fixed||USB Detection Issue & Low Transfer Speed||Apalis T30, Colibri T30||USB|
Description: USB detection may fail especially on the OTG port plus the transfer speed may be rather low.
Workaround: Reverting http://git.toradex.com/cgit/linux-toradex.git/commit/?h=tegra&id=629b91fa046df5213ed3312d2e2b8683e6bdd70c helps but reintroduces issue #6422.
| 12661||Fixed||Stuck in U-Boot SPL upon Watchdog Reset||Colibri T20||Bootloader, Power Management, Watchdog|
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.
| 11827||Fixed||Rare I/O Error on eMMC||Apalis T30, Colibri T30||SATA, SDIO/SD/MMC|
Description: Very rare occurrence of eMMC issues as shown below in combination with extensively heavy SATA and/or SD card stress testing: I/O error, dev mmcblk0
Workaround: Avoid extensively heavy SATA and/or SD card stress testing. Usually power-cycling brings the system back to life.
| 11822||New Feature||UBIFS Errors when File-System is Full||Colibri VF50, Colibri VF61||Bootloader, Flash|
Description: Full UBIFS root file system can lead to a system which is not able to mount the root file system anymore.
Workaround: Take measures to avoid the root file system completely running out of space.
| 11602||Fixed||Slow Memory Copy||Apalis T30, Colibri T30||RAM|
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.
| 11601||Fixed||Software Reboot Lock-up||Colibri T20||Kernel|
Description: Rarely after about 500 software reboot cycles the module locks up during boot.
Workaround: Just power-cycle again.
| 11520||Fixed||PMIC RTC Accuracy||Colibri T20||RTC|
Description: The PMIC RTC does not meet the expected accuracy.
Workaround: If possible use the external RTC provided by the carrier board.
| 8342||Fixed||Race Condition in USB OTG Device/Host Detection on Ixora||Apalis T30||USB|
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.
| 8185||New Feature||Add CSI Camera Support||Apalis iMX6||CSI|
| 7674||New Feature||Automatic USB Device/Host Detection||Colibri VF50, Colibri VF61, Colibri iMX6||USB|
Description: The USB ID pin shall be used for automatic USB device/host detection.
Workaround: Use implementation available in resp. -next branch for now.
| 7194||New Feature||T30 U-Boot Framebuffer||Apalis T30, Colibri T30||Bootloader, RGB|
Description: No framebuffer support in U-Boot for Colibri/Apalis T30, therefore splashscreen in U-Boot is not possible.
Workaround: Use splashscreen support in Linux.
| 6527||New Feature||BCT Memory Optimisation||Apalis T30||Bootloader, RAM|
Description: Currently DDR3L RAM is running at 533MHz. Further optimisations to achieve 800MHz speeds are required.
| 11881||New Feature||Provide WAITFORVSYNC Ioctrl for Vybrid DCU Framebuffer Driver||Colibri VF50, Colibri VF61||LVDS|
Description: Tear-free double buffering using the Linux framebuffer is currently not possible since there is no method to synchronize the buffer swap with the vertical synchronization period.
| 11519||New Feature||Switch to Linux Kernel 4.1 LTS||Colibri VF50, Colibri VF61||Kernel|
Description: Use long-term supported Linux kernel release 4.1.
| 10578||New Feature||Support RS485 Transceiver on UART Interfaces||Colibri VF50, Colibri VF61||UART|
Description: Support using RS-485 transmitter on UART interfaces using the UART_x_RTS signal as DE (driver enable).
| 9720||New Feature||LPSTOP2/3 Suspend/Resume Support for Newer Kernel Version||Colibri VF50, Colibri VF61||Power Management|
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.
| 10588||Fixed||USB Host in U-Boot does not Work on Iris Carrier Board||Colibri VF50, Colibri VF61||Bootloader, USB|
Description: The U-Boot boot loader does not switch on the power on the USB host port. This makes the USB host port not working by default on the Viola and Iris Carrier Boards.
Workaround: Use U-Boot's GPIO functionality to switch on the USB host power (GPIO 83).
| 10550||New Feature||Vybrid U-Boot Framebuffer Support||Colibri VF50, Colibri VF61||Bootloader, Graphics|
Description: Support Framebuffer in U-Boot to provide graphical output at bootloader time.
| 10532||New Feature||Increase ECC Level for Colibri VF61||Colibri VF61||Flash|
Description: Increase ECC level from 6 errors to 8 errors per 512 bytes page to reach typical endurance of 100K cycles.
| 10441||New Feature||Support System-on-Chip Bus||Colibri VF50, Colibri VF61||Kernel|
Description: Support the Kernels SoC bus which makes sure SoC peripherals are exported within a sub-directory in sysfs. That also allows to export SoC information such as Type and unique ID through sysfs.
| 10291||Fixed||Floating Point Exception using nv_omx_h264enc||Apalis T30, Colibri T30||Video Codecs|
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.
| 10172||New Feature||AC97 Audio Capture||Colibri VF61||Analog Audio, Resistive Touch|
Description: The current software AC97 driver supports audio playback and touch. It needs to be extended with receive capabilities to support analogue audio capture as well.
| 10051||Fixed||Rare I/O Error on eMMC||Apalis T30, Colibri T30||Flash, Kernel, SDIO/SD/MMC|
Description: Rare occurrence of eMMC issues as shown below can lead to read-only root file system or even non-booting systems:
I/O error, dev mmcblk0
Workaround: Usually power-cycling brings the system back to life. The tegra-next branch of our Linux kernel source repository contains a fix for this.
| 9813||New Feature||GPIO Support for U-Boot||Colibri VF50, Colibri VF61||Bootloader, GPIO|
Description: GPIO support in U-Boot
| 9097||New Feature||Yocto Integration||Colibri VF50, Colibri VF61||Buildsystem|
Description: Publishing our machine support into the community driven meta-fsl layer.
| 8184||New Feature||Add Parallel Camera Interface Support||Apalis iMX6, Colibri iMX6||Camera Parallel Interface|
Description: Use Analog Camera Adapter (ACA, formerly ACM) as Video Source.
| 7211||Fixed||Different Mountpoint Names when Mounted at Boot vs. Mounted at Runtime / with Diskutility||Apalis T30, Apalis iMX6, Colibri T20, Colibri T30, Colibri VF50, Colibri VF61, Colibri iMX6||SATA, SDIO/SD/MMC, USB|
Description: Mountpoint names are different when mounted at boot vs. mounted at runtime / with diskutility.
| 10139||Fixed||UART Without DMA Leads to Freeze/Lockup During Boot-up||Colibri VF50, Colibri VF61||UART|
Description: Using UART on Vybrid without DMA can lead to boot freezes when characters have been received during startup.
Workaround: Enable DMA mode to avoid this problem completely or avoid character transmission to the module during startup.
| 10083||Fixed||Kernel Freeze on Startup (in V2.3 Beta 5)||Colibri VF50||Kernel|
Description: Sometimes the kernel freezes right on startup. The last message being shown in the serial console is "Starting kernel ...".
| 10057||New Feature||Create Pinmux Entries for all GPIOs||Colibri VF50, Colibri VF61||GPIO|
Description: Exporting of GPIOs using the sysfs interface fails with "Invalid argument". This is due to lack of GPIO pinmux configurations in the device tree. Currently, only few pins have pinmux information for GPIO use.
Workaround: The device tree needs to be extended to provide the pinmux for the required GPIOs.
| 9980||Fixed||Default SPI Peripheral Driver DSPI not Working||Colibri VF50, Colibri VF61||SPI|
Description: SPI by using Vybrid's DSPI peripheral does not work as intended.
| 8152||New Feature||Support USB Firmware Upgrade (Fastboot/DFU Device Class)||Colibri VF50, Colibri VF61||Bootloader, USB|
Description: Support upgrade through USB device capabilities using the DFU device class.
| 7628||Fixed||AC97 Suspend Support||Colibri VF61||Analog Audio, Resistive Touch|
Description: Currently there are kernel errors after suspend to RAM when using AC97.
| 7190||New Feature||AC97 Implementation||Colibri VF61||Analog Audio, Resistive Touch|
Description: Current software AC97 driver only supporting touch requires extension for analogue audio to work as well.
| 10174||New Feature||Apalis iMX6Q 2GB IT BSP||Apalis iMX6||Buildsystem|
Description: Support Apalis iMX6Q 2GB IT in our BSP.
| 10123||New Feature||Implement Optional MMC UHS Support||Apalis T30||SDIO/SD/MMC|
Description: Implement optional MMC UHS support (enable using mmc_uhs=1 kernel command line parameter, requires V1.1A or later HW).
| 9562||Fixed||X-Server Rotation Broken||Apalis T30, Colibri T20, Colibri T30||Graphics, HDMI, LVDS, RGB, VGA|
Description: XRandR based rotation as described on the following article on our developer website is broken since our V2.1 releases:
Workaround: Please revert to one of our older V2.0 based releases for now.
| 8810||Fixed||Unreliable RNDIS/g_ether over USB Client||Colibri VF50, Colibri VF61||USB|
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).
| 8709||Fixed||Memory Leak during Gstreamer Video Playback||Apalis T30, Colibri T30||Multimedia|
Description: Several hours of gstreamer streaming aborts due to memory leak in nvvidconv gstreamer plugin.
Workaround: Under certain circumstances using an older NVIDIA L4T R16.3 based BSP might be feasible until NVIDIA releases a fix.
| 8260||New Feature||USB Host/Client in U-Boot||Colibri VF50, Colibri VF61||Bootloader, USB|
Description: USB Host/Client capabilities in U-Boot.
| 8192||New Feature||Implement Suspend Modes (and Wakeup)||Apalis iMX6, Colibri iMX6||Power Management|
| 7848||New Feature||USB Host Functionality on USBC||Colibri VF50, Colibri VF61||USB|
Description: The Colibri USB client aka USBC port shall be usable as a regular USB host port as well.
| 7529||New Feature||Use Fastmap for UBI to Decrease Boot Time||Colibri VF50, Colibri VF61||Flash|
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.
| 7198||New Feature||Base on Later Stable kernel.org Mainline Linux Kernel||Colibri VF50, Colibri VF61||Kernel|
Description: Current Timesys kernel is considered obsolete. Migration to a later version is desired.
| 6422||Fixed||USB Low-Speed Issue||Apalis T30, Colibri T30||USB|
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.
| 9083||New Feature||Colibri iMX6 BSP||Colibri iMX6|
| 8924||New Feature||Analog Inputs||Apalis iMX6, Colibri iMX6||Analog Inputs|
Description: Support analog inputs from STMPE811 via IIO framework.
Workaround: Use V2.2 beta 1 based on older Linux kernel 3.0.35 for now.
| 8890||New Feature||I2C SMBus Block Read Support||Colibri VF50, Colibri VF61||I2C|
Description: The imx I2C driver does not support block read support. However, in order to use some I2C devices, the I2C bus adaptor driver needs to support SMBus block reads.
| 8622||Fixed||Analogue Audio Codec Disappearing during Reboot||Apalis T30, Colibri T30||Analog Audio|
Description: Analogue audio codec disappearing during reboot particularly if previously used for audio recording.
Workaround: Power-cycling should help. Alternatively wait for us to backport respective Linux kernel driver fixes.
| 8188||New Feature||RS485||Apalis iMX6||UART|
Description: Test and document the HW options to control an RS485 transceiver.
| 7724||New Feature||RTC Wakeup Support||Colibri VF50, Colibri VF61||RTC|
Description: The Vybrid internal RTC would allow waking up the system from low power modes based on a time (wakealarm).
| 7193||New Feature||U-Boot Gigabit Ethernet||Apalis T30||Bootloader, Ethernet|
Description: No support for Ethernet on Apalis T30 in U-Boot.
Workaround: Use an Asix based USB to Ethernet dongle if you need Ethernet support in U-Boot.
| 8348||Fixed||PCIe and with it Gigabit Ethernet Rarely Unavailable after Boot||Apalis T30||Ethernet, PCIe|
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.
| 8754||Fixed||PWM Output do not Work||Colibri VF50, Colibri VF61||PWM|
Description: The PWM other than PWM do not work.
| 8748||Fixed||Rare I/O Error on eMMC||Apalis T30||Flash, Kernel, SDIO/SD/MMC|
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.
| 8703||Fixed||Internal RTC not Accurate||Colibri VF50, Colibri VF61||RTC|
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).
| 8621||New Feature||Multi-Touch Integration||Apalis iMX6, Colibri iMX6||Capacitive Touch|
Description: Multi-touch integration pending.
Workaround: Port multi-touch integration from Tegra resp. Vybrid BSPs.
| 8190||New Feature||PWM from Userspace||Apalis iMX6||Graphics, PWM|
Description: Assign the PWM to the LED-PWM class to have a consistent interface across modules.
| 8177||New Feature||Update to Latest Freescale Kernel||Apalis iMX6||Kernel|
| 8145||Fixed||Disabling HDMI Display Controller via modedb Kernel Arguments||Apalis T30, Colibri T20, Colibri T30||Graphics, HDMI|
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.
| 8074||Fixed||U-Boot SD Boot Environment||Colibri T20||Bootloader, SDIO/SD/MMC|
Description: Currently if doing SD boot the U-Boot environment is not preserved on the SD card.
Workaround: Build latest U-Boot sources from git.toradex.com.
| 8073||Fixed||U-Boot TFTP/NFS Booting via USB-to-Ethernet||Apalis T30, Colibri T30||Bootloader, Ethernet|
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.
| 7634||New Feature||Internal CAN Controller||Colibri VF50, Colibri VF61||CAN|
Description: Support Vybrid SoC internal CAN controllers.
| 7214||New Feature||RNDIS Setup||Apalis iMX6||USB|
Description: Implement RNDIS DHCP server for seamless Ethernet over USB device operation.
| 7196||New Feature||Add Apalis MXM Pin Descriptions to the GPIO Config Tool||Apalis T30||GPIO|
Description: Add Apalis MXM pin descriptions to the GPIO config tool.
| 7189||Fixed||Audio Capture Issue||Colibri T20||Analog Audio|
Description: Audio capture can stall causing stutter in captured stream.
Workaround: None. Await for update to driver.
| 7182||New Feature||Camera Serial Interface (CSI-2)||Apalis T30||CSI|
Description: Implement initial CSI-2 support for the Aptina AS0260 YUV sensor.
| 7177||Fixed||HDMI Audio Issue||Colibri T30||HDMI|
Description: HDMI audio has an incorrect sampling frequency so the recorded audio stream is distorted.
Workaround: None. Await updated driver.
| 8153||New Feature||Base on Later Mainline U-Boot||Colibri VF50, Colibri VF61||Bootloader|
Description: Base on later U-Boot version in order to support Device Tree for newer Kernel version.
| 7847||New Feature||Second Ethernet MAC||Colibri VF50, Colibri VF61||Ethernet|
Description: Implement support for Vybrid SoC internal second Ethernet MAC.
| 7841||New Feature||Adapt Pinmux for Hardware Revision V1.1A||Colibri VF50, Colibri VF61||Resistive Touch|
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.
| 7820||Fixed||Non-monotonic Increasing sched_clock||Colibri VF50, Colibri VF61||RTC|
Description: The main scheduling clock is non-monotonic increasing, which leads to time gaps in kernel log output.
Workaround: So far we haven't noticed any issues because of that. The real-time clock works as expected.
| 7620||Fixed||Boot Freeze after RTC Detection||Colibri VF50, Colibri VF61||UART|
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.
| 7215||New Feature||Recovery, Fusing, Serial Downloader||Colibri VF50, Colibri VF61||Bootloader, UART|
Description: Implement serial downloader for recovery.
Workaround: For initial (non-fused) samples, recovery from a SD-Card using resistors for SD bootstrap is possible.
| 7619||New Feature||Ethernet PHY Power Save||Colibri VF50, Colibri VF61||Ethernet|
Description: Send Ethernet PHY to powersave when going into sleep modes.
| 25147||Feature Request||New Versioning Scheme||Apalis T30, Apalis TK1, Apalis iMX6, Colibri T20, Colibri T30, Colibri VF50, Colibri VF61, Colibri iMX6, Colibri iMX7||Buildsystem|
Description: We changed our versioning scheme. Our BSP demo image packages are now e.g. called Apalis-iMX6_LinuxImage_2.7b2_20170331.tar.bz2. The Linux kernel will report e.g. the version number 3.10.40-v2.7.2+g1928374 and U-Boot will report e.g. 2016.11-2.7.2+g8462861.
| 24475||Known Issue||Potential Systemd Hang on First Boot||Apalis T30, Apalis TK1, Apalis iMX6, Apalis iMX8, Colibri T20, Colibri T30, Colibri VF50, Colibri VF61, Colibri iMX6, Colibri iMX6ULL, Colibri iMX7||Buildsystem|
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.
| 24327||Known Issue||Modules May Hang During RAM Initialisation||Colibri VF50, Colibri VF61||Bootloader, RAM|
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: The latest stable BSP release V2.5_20151216 has been fully validated and does not exhibit this issue.
| 24296||Known Issue||Module May Draw More Power||Colibri T20||Graphics, Kernel|
Description: Colibri T20 modules may draw more power be it during regular operation or in suspend.
Workaround: This issue is related to the 'Module May Hang During Boot if HDMI is not Connected' one whose fix can be found on the tegra-next branch of our linux-toradex Linux kernel repository: http://git.toradex.com/cgit/linux-toradex.git/log/?h=tegra-next
| 23872||Feature Request||Deploy mmc-utils||Apalis T30, Apalis TK1, Apalis iMX6, Colibri T30, Colibri iMX6||Buildsystem, Flash, SDIO/SD/MMC|
Description: The mmc-utils allow e.g. inspecting the current health and life time estimation of the on-module eMMC.
| 23740||Known Issue||Adapt wrapup script for Colibri iMX6||Colibri iMX6|
Description: The wrapup script in the Toradex Easy Installer Colibri iMX6 V2.7 Beta 1 image does not allow to flash Colibri iMX6 modules.
| 23690||Known Issue||CPU & GPU Thermal Throttling Not Working||Apalis TK1||CPU, Device Tree, Graphics, Kernel, Power Management, Temperature Sensor|
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.
| 23492||Known Issue||U-Boot: USB Host Mode Not Working||Colibri iMX7||Bootloader|
Description: In the U-Boot version 2016.11 as shipped with our BSP V2.7 beta 1 the USB host mode initialisation (usb start) returns "Port not available." on both ports. This issue has been fixed and is available on our -next branch.
| 23271||Known Issue||Update Meta-Angstrom to Latest Resulting in Using Linaro GCC 6 Compiler||Apalis T30, Apalis TK1, Apalis iMX6, Colibri T20, Colibri T30, Colibri VF50, Colibri VF61, Colibri iMX6, Colibri iMX7|
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.
| 22972||Feature Request||U-Boot SPL Version Handling||Apalis iMX6||Bootloader|
Description: With our unified (Linux/WEC) SPL in place we need a way to tell what version of SPL thereof is installed.
| 22937||Feature Request||Remove Unneeded RDEPENDS From Our Recipes||Apalis T30, Apalis TK1, Apalis iMX6, Colibri T20, Colibri T30, Colibri VF50, Colibri VF61, Colibri iMX6, Colibri iMX7||Buildsystem|
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.
| 22228||Known Issue||UBI/UBIFS issues on Colibri VF50/VF61: Crash during filesystem recovery after an unexpected power cut||Colibri VF50, Colibri VF61||Flash|
Description: On Colibri VF50/VF61 in situations with frequent unexpected power-cuts there is a possibility of filesystem getting corrupted.
Workaround: Use a Read-Only Root Filesystem.
| 21661||Feature Request||U-Boot SPL, Do Not Output Anything on the Debug UART||Apalis iMX6, Colibri iMX6||Bootloader|
Description: Don't output anything on the DEBUG console unless there is a fatal error.
| 21280||Feature Request||SoC Unique Number||Apalis T30, Apalis TK1, Apalis iMX6, Colibri T20, Colibri T30, Colibri VF50, Colibri VF61, Colibri iMX6, Colibri iMX7||Miscellaneous Peripherals|
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
| 21275||Known Issue||U-Boot: Support Elf File Format for Cortex-M4 Firmwares||Colibri VF50, Colibri VF61, Colibri iMX7||Bootloader|
Description: The elf file format is supported by most commercial and free development environments and provides a standardized header for crucial information such as load address and entry point.
| 20968||Known Issue||Module May Hang During Boot if HDMI is not Connected||Colibri T20||Graphics, Kernel|
Description: Colibri T20 modules may hang during boot if HDMI is not connected.
Workaround: The fix for this issue can be found on the tegra-next branch of our linux-toradex Linux kernel repository: http://git.toradex.com/cgit/linux-toradex.git/log/?h=tegra-next
| 20847||Known Issue||Temperature Test on Colibri T20 Uncovered UBI Error when using bonnie++ with latest Image||Colibri T20||Flash|
Description: Temperature test on Colibri T20 uncovered UBI error when using bonnie++ with latest image.
Workaround: Use stable BSP V2.3 based on YAFFS2.
| 20395||Known Issue||SDIO Lock-up||Apalis TK1||Kernel, SDIO/SD/MMC, Wi-Fi|
Description: Testing various SDIO based Wi-Fi solutions we observed it to completely lock-up the system.
Workaround: Find the following commit fixing this:
| 19436||Known Issue||Framebuffer Boot Configuration Integration Missing||Apalis TK1||LVDS|
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
| 18187||Feature Request||Implement CAN Functionality||Apalis TK1||CAN|
Description: Add support for the CAN feature of the Apalis TK1 module.
| 16996||Feature Request||Test Low-Power/Suspend Modes||Apalis TK1||Power Management|
Description: Test low-power/suspend modes.
| 16995||Feature Request||Test JTAG||Apalis TK1||Miscellaneous Peripherals|
Description: Test JTAG. Description see: http://developer.toradex.com/knowledge-base/jtag
| 16469||Feature Request||Implement and Validate Suspend/Low-Power Modes||Colibri iMX7||Power Management|
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.
| 7208||Feature Request||Configure Optimised MMC Read-Ahead||Apalis TK1, Apalis iMX6, Colibri T20, Colibri VF50, Colibri VF61, Colibri iMX6, Colibri iMX7||Flash, SDIO/SD/MMC|
Description: Configure optimised MMC read-ahead.
Workaround: Manually set /sys/block/mmcblk0/queue/read_ahead_kb.
| 24542||Feature Request||Implement and Validate LPSR Suspend/Low-Power Mode||Colibri iMX7||Power Management|
Description: Implement and validate LPSR suspend/low-power mode.
| 24541||Feature Request||Test LP0 Low-Power/Suspend Mode||Apalis TK1||Power Management|
Description: Test LP0 low-power/suspend mode.
Workaround: Use LP1
| 23870||Known Issue||HDMI Hot-Plugging Fails Configuring Desktop Output||Apalis T30, Apalis TK1, Colibri T20, Colibri T30||HDMI|
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.
| 16945||Known Issue||Timeout Waiting for dev-ttys0.device on First Boot||Apalis T30|
Description: Rarely a timeout waiting for dev-ttys0.device on first boot has been observed.
Workaround: Just power-cycle again.
| 9858||Feature Request||Deploy Device Tree(s)||Apalis T30, Apalis TK1, Apalis iMX6, Colibri T20, Colibri T30, Colibri VF50, Colibri VF61, Colibri iMX6||Buildsystem, Device Tree|
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.
|Issues in this section are not scheduled yet. Please get in touch with our support if you need to have any of these issues scheduled.
| 25067||Known Issue||Regression: Poweroff when Poweroff||Apalis iMX6, Colibri iMX6||Kernel, Power Management|
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.
| 24305||Feature Request||Allow for Easier OpenEmbedded Machine Configuration||Apalis T30, Apalis TK1, Apalis iMX6, Apalis iMX8, Colibri T20, Colibri T30, Colibri VF50, Colibri VF61, Colibri iMX6, Colibri iMX6ULL, Colibri iMX7||Buildsystem|
Description: Allow for easier OpenEmbedded machine configuration by our customers.
| 24293||Feature Request||Develop a bmode CLI Equivalent for Linux||Apalis iMX6, Colibri iMX6||Miscellaneous Peripherals|
Description: Add a Linux accessible way to set the boot mode for the next warm start to be 'serial download mode' aka. 'recovery mode' to ease updating the module.
| 23995||Known Issue||Module May Hang During Boot Upon Hardware Reset||Apalis T30, Colibri T30||Bootloader, Kernel, Power Management|
Description: Depending on its DVFS state right before hardware reset the Apalis/Colibri T30 module may hang during a subsequent boot. Software reset seems not affected.
Workaround: Either power-cycle or make sure you are running at a higher DVFS state upon hardware reset.
| 23833||Known Issue||HDMI Hot-Plugging May Fail||Apalis TK1||Graphics, HDMI, I2C, Kernel|
Description: While HDMI hot-plugging works just fine on the Apalis Evaluation board it currently fails with EDID errors on Ixora.
| 23272||Known Issue||Colibri T30 May Freeze on Concurrent SD Card and Multiple USB Devices Stress Testing||Apalis T30, Colibri T30||SDIO/SD/MMC, USB|
Description: In use cases involving all 3 USB host controllers with USB hubs connected to the OTG as well as the regular host port with USB keyboard/mouse resp. USB-to-serial-adapter connected plus an SD card the Colibri T30 may freeze upon stress testing.
Workaround: Only use two USB host controllers. Ethernet already uses one of them. Use an external USB hub for further USB ports.
| 22975||Known Issue||Sometimes the RTC driver recovers invalid date/time from the external RTC||Apalis T30, Apalis TK1, Apalis iMX6, Colibri T20, Colibri T30, Colibri VF50, Colibri VF61, Colibri iMX6, Colibri iMX7||RTC|
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.
| 22947||Known Issue||Spawn getty on USB Serial Gadget||Apalis iMX6, Colibri VF50, Colibri VF61, Colibri iMX6, Colibri iMX7||UART|
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.
Unify that behaviour across modules.
Workaround: If you want a getty, either:
- enable the relevant systemd service and reboot,
systemctl enable serial-getty@ttyGS0.service
- before building the image with openembedded adapt the following for your module in build/local.conf
| 21416||Known Issue||Kernel bootup issue using PREEMPT_RT with Linux 4.4.21 on VF61 ||Colibri VF61||Kernel|
Description: Using PREEMPT_RT patch with Linux 4.4.21 on VF61 results in a freeze at boot time.
| 21279||Known Issue||Graphical Desktop not Starting||Apalis iMX6||Graphics|
Description: At times the graphical desktop is not starting and screen stays black albeit mouse cursor is showing.
| 21271||Feature Request||Support USB 3.0 SuperSpeed on USBO1||Apalis TK1||USB|
Description: Support USB 3.0 SuperSpeed on USBO1.
Workaround: Use USB 3.0 SuperSpeed on USBH4 for now.
Alternatively the mainline Linux kernel already supports USB 3.0 SuperSpeed on USBO1 as well as USBH4. You may also use the following mainline Linux based demo image http://developer.toradex.com/files/toradex-dev/uploads/media/Colibri/Linux/Images/Apalis_TK1_Mainline_LinuxImageV2.7Beta1_20170112.tar.bz2
| 21236||Known Issue||Gstreamer Video Playback Segmentation Fault||Apalis TK1||Video Codecs|
Description: While gstreamer video playback works fine it segmentation faults at the very end as follows:
exec gdb failed: No such file or directory
Spinning. Please run 'gdb gst-launch-1.0 889' to continue debugging, Ctrl-C to quit, or Ctrl-\ to dump core.
Workaround: Just Ctrl-C the gstreamer process as indicated.
| 20821||Feature Request||Support MXM/SODIMM Pin Numbers to Get/Set GPIOs||Apalis T30, Apalis TK1, Apalis iMX6, Colibri T20, Colibri T30, Colibri VF50, Colibri VF61, Colibri iMX6, Colibri iMX7||GPIO|
Description: Allow using MXM or SODIMM pin numbers to get or set GPIOs. This also allows for easier code porting from one to another Toradex module.
| 20397||Feature Request||Over Temperature Notice Message||Apalis T30, Colibri T30||Temperature Sensor|
Description: As on our T30 designs there is a hardware over-temperature shut-off directly via PMIC we should check whether we could at least have an over temperature message shortly before that (e.g. 5 deg C).
| 19952||Known Issue||SPDIF not Working||Apalis T30, Colibri T20, Colibri T30||Digital Audio|
Description: SPDIF is not working in the V2.6 beta 2 release. This is a regression against older releases.
| 19951||Known Issue||SPDIF not Working||Apalis iMX6, Colibri iMX6||Digital Audio|
Description: SPDIF is not working in the V2.6 beta 2 release. This is a regression against older releases.
| 19441||Feature Request||Implement Upstream Remoteproc Driver for Rpmsg Communication||Colibri VF61||Miscellaneous Peripherals|
Description: The current working implementation uses the hacked up rpmsg driver implemented in line with the downstream rpmsg driver for the i.MX 7 as done by NXP. Investigate and possibly implement a remoteproc driver which can also be upstreamed.
| 17733||Known Issue||UART Overruns when using DMA||Apalis iMX6, Colibri iMX6||UART|
Description: The UART may overrun when using DMA.
| 16994||Feature Request||Bring-up Digital Audio Interface DAP1||Apalis TK1||Digital Audio|
Description: Bring-up digital audio interface DAP1.
| 16988||Feature Request||Bring-up SPDIF||Apalis TK1||Digital Audio|
Description: Bring-up SPDIF.
| 16300||Feature Request||BCT Memory Optimisation Phase 2||Apalis T30||Bootloader, RAM|
Description: Currently DDR3L RAM is running at a fixed 800MHz frequency. Further optimisations to allow for automatic frequency switching in order to save power and decrease dissipated heat are required.
Workaround: You may use the previous fixed 533MHz BCT still shipping in our latest BSP demo image packages as well (see apalis-t30_bin/apalis_t30_12MHz_MT41K512M8RH-125_533MHz.bct).
| 16130||Feature Request||Add 16-Bit Muxed Parallel Bus Support||Colibri iMX7||External Memory Bus|
Description: Add 16-bit muxed parallel bus support.
| 16128||Feature Request||Add Camera Support||Colibri iMX7||Camera Parallel Interface|
Description: Add camera support
| 16125||Feature Request||SoC Internal RTC Broken on i.MX 7Solo||Colibri iMX7||RTC|
Description: The SoC internal RTC seems broken on the i.MX 7Solo.
Workaround: Use a board-level I2C RTC.
| 16123||Feature Request||Allow Setting the Display Timings from the Kernel Cmdline||Colibri iMX7||Graphics|
Description: Fix the Colibri iMX7 display timings and allow setting them from the kernel cmdline.
Workaround: Use native mode node in device-tree
| 15910||Known Issue||Kernel Panic while using RNDIS USB Gadget||Colibri VF50, Colibri VF61||USB|
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.
| 10744||Known Issue||PCIe GEN2 not Working on Apalis Evaluation Board||Apalis TK1, Apalis iMX6||PCIe|
Description: PCIe GEN2 is currently not working with Apalis iMX6 and Apalis TK1 on the Apalis evaluation board.
Workaround: The mini-PCIe slot on Ixora is known to work also at GEN2 speeds.
| 7181||Feature Request||Freescale SGTL5000 using External LDO||Apalis T30, Apalis iMX6, Colibri T30, Colibri iMX6||Analog Audio|
Description: Current module hardware revisions use an external rail rather than the embedded LDO having certain boot issues as mentioned in the errata. The drivers should be adjusted in that respect.
|Issues in this section are not planned to be addressed. Please get in touch with our support if you need to have any of these issues addressed.
| 24823||Known Issue||Ethernet Switch Not Monitoring External Ethernet Ports||Colibri VF50, Colibri VF61||Ethernet, Kernel|
Description: The current Ethernet switch implementation does not allow monitoring the external Ethernet ports. Further Linux switchdev subsystem integration would be needed.
| 23446||Known Issue||Distro Boot Integration||Apalis iMX6, Colibri iMX6||Bootloader, SDIO/SD/MMC, USB|
Description: At least Fedora 25 for ARM currently just hangs upon booting the kernel without any further messages being printed.
| 22347||Known Issue||LX Panel, CPU Usage Monitor & Confusing Display Due to Dynamic Full Scale||Apalis T30, Apalis TK1, Colibri T30||CPU|
Description: The LX Panel gives an overview of the current CPU Usage by providing a rolling chart of the last minute.
Full Scale of the chart is what all the CPU cores which are currently on could compute at the current CPU speed.
Since the CPU speed adapts to the current workload full scale is not a constant.
On top of that on some modules CPU cores are dynamically switched on or off depending on the current computing load. This can lead to the confusing effect that increasing the load by a little can lead to a decreased load displayed in the 'CPU Usage Monitor' because on additional core is switched on.
| 22153||Known Issue||Memory Corruption with ext4 Filesystem||Apalis T30, Colibri T20, Colibri T30||Flash, Kernel, SATA, SDIO/SD/MMC, USB|
Description: NVIDIA's downstream L4T kernel our BSPs are based on has issues with the ext4 file system.
Workaround: Use the ext3 file system instead.
| 21874||Known Issue||GPIO interrupts do not work on Cortex-M4 after Linux boot||Colibri iMX7||GPIO|
Description: If a GPIO bank is assigned to Linux (defined in the device tree), the driver masks and clears all GPIO interrupts on startup. If a GPIO of the same bank is used as a interrupt source on the Cortex-M4 core, the interrupts will not work after Linux started. If the M4 enables an interrupt after Linux started, Linux will receive that interrupt too and mask the interrupt again (since from a Linux perspective, the interrupt is not enabled).
Workaround: Disable a GPIO bank in the device tree to assign it exclusively to the Cortex-M4 core.
| 21605||Known Issue||Implement workaround for unstable 500MHz clock errata (e6235)||Colibri VF61||CPU|
Description: Due to a chip errata the main CPU clock may be unstable. During our extensive testing We have not observed issues with our design so far.
We never saw any problem and also don't have any negative customer feedback.
| 21501||Known Issue||I2C6 on Apalis TK1||Apalis TK1||I2C|
Description: I2C6 as available on Apalis TK1 MXM3 pins 71/73 aka DP_AUX_CH0_N/P is currently not supported.
| 21353||Feature Request||ARM DS MDK Linux Kernel Debugging||Colibri iMX7||Buildsystem, Miscellaneous Peripherals|
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
| 21344||Known Issue||Some USB Thumb Drives don't Work Well in U-Boot||Apalis iMX6, Colibri iMX6||Bootloader, USB|
Description: Use these results in load errors when copying large files, e.g. once used for image update.
Workaround: Find one that works for you. All USB SD card readers we tried so far worked.
| 21343||Known Issue||First Boot, Rootfs Expansion Affects System Performance||Apalis T30, Apalis TK1, Apalis iMX6, Colibri T30, Colibri iMX6||Flash|
Description: On first boot the rootfs partition gets expanded to the full size of the partition it lives in. This resizing process adversely affects system performance for the first few minutes until completed.
| 21342||Known Issue||USB Hub on Evaluation Board not Enabled in U-Boot||Apalis iMX6||Bootloader, USB|
Description: USB hub on Evaluation Board not enabled in U-Boot.
Workaround: Use USBH3 or USBH4 if you need a USB host in U-Boot.
| 21340||Known Issue||No Backlight PWM on V1.0 HW||Apalis iMX6||PWM|
Description: There is no backlight PWM on V1.0 HW. The pin can be used as a backlight GPIO to switch between off and on.
| 21339||Known Issue||X11 can only use one Screen||Apalis iMX6, Colibri iMX6||DSI, Graphics, HDMI, LVDS, RGB, VGA|
Description: The Vivante X driver can only make use of the first framebuffer /dev/fb0 while the others can be used through the fbdev framebuffer interface.
| 21338||Known Issue||On some Monitors HDMI EDID is Problematic||Apalis iMX6, Colibri iMX6||Graphics, HDMI|
Description: On some monitors HDMI EDID does not negotiate correct timings.
Workaround: Adding/removing mxc_hdmi.only_cea=1 to the kernel command line may help.
| 21337||Known Issue||Mic Input not Hot-Pluggable||Apalis iMX6, Colibri iMX6||Analog Audio|
Description: Hot-plugging a microphone can reset the audio codec.
The driver is not able to bring up the codec again after such an event.
This is fixed in Apalis iMX6 V1.1 and will be fixed in Colibri iMX6 V1.2.
Workaround: Not hot-plug the microphone or rebooting fixes the issue.
Having a 100 Ohm resistor in series to the microphone on a carrier board makes the module mic hot-pluggable.
| 21335||Known Issue||HDA Audio not Available||Apalis iMX6||Digital Audio|
Description: The i.MX 6 SoC does not feature HDA audio functionality. Thus the HDA codec on the Apalis Evaluation Board can not be used.
Workaround: If a audio codec needs to be connected you could use I2S and AC97.
Refer also to: http://developer.toradex.com/software/linux/linux-software/release-details?view=release-roadmap&&issue=21313
| 21334||Known Issue||UART Control Signals DCD/DSR/DTR/RI not working||Apalis iMX6, Colibri iMX6||UART|
Description: The UART DCD/DSR/DTR/RI signals are not integrated into the driver.
Workaround: Configure them to be GPIO and read/set them from userspace.
| 21328||Known Issue||IrDA not Implemented||Apalis T30, Apalis TK1, Apalis iMX6, Colibri T20, Colibri T30, Colibri VF50, Colibri VF61, Colibri iMX6, Colibri iMX7||IrDA|
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.
| 21327||Known Issue||U-Boot: USB OTG Port is Always Client||Apalis iMX6, Colibri iMX6||Bootloader, USB|
Description: In U-Boot the USBO1 and USBC ports for Colibri and Apalis respectively are configured to be client only.
| 21313||Feature Request||SGTL5000 Audio Multi Instance Codec Driver||Apalis T30, Apalis TK1, Apalis iMX6, Colibri T30, Colibri iMX6, Colibri iMX7||Analog Audio|
Description: The SGTL5000 driver in the Linux Kernel currently only supports one codec.
The driver would need amending so that multiple codecs can be used. The issue is the statically created VDDD_LDO regulator.
| 21312||Feature Request||Add support for DSI Display||Apalis iMX6||DSI, Graphics|
Description: The i.MX 6 MIPI DSI interface is available on type specific pins.
Setup HW on those pins and bring up the DSI interface.
Workaround: The DSI interface is expected to work, however it has not yet been tested.
| 21137||Known Issue||Colibri Evaluation Board: USB 3.0 Devices Plugged in at Boot Time is not Accessible||Colibri iMX7||USB|
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).
| 20643||Feature Request||Implementing Linux Serial Driver using K20 UARTs||Apalis TK1||UART|
Description: K20 MCU has multiple UART peripherals. Special driver integration would allow to use them as serial ports from Linux running on TK1.
| 19547||Known Issue||Connected SDCard Prevents U-Boot from entering Recovery Mode||Colibri iMX6, Colibri iMX7||Bootloader, SDIO/SD/MMC|
Description: When one wants to enter recovery mode, aka serial download mode, that mode is not correctly working when a SD/MMC card is connected on the SD1 interface, e.g. the SD slot on the Evaluation Board.
If the SD card is flashed with an U-Boot the module does not enter recovery mode at all but tries to load said U-Boot.
On i.MX6, even if the SD card is not flashed with U-Boot the module does fail when downloading DCD data over USB.
Workaround: Remove any SD card from your system during power cycle / reset when you intend to enter recovery mode.
| 19468||Known Issue||USB OTG on Aster, Orchid, Viola Need USB_P_EN# for Host Role||Colibri T20, Colibri T30, Colibri VF50, Colibri VF61, Colibri iMX6, Colibri iMX7||USB|
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.
| 18671||Known Issue||Suspend/Resume does not Work with PCIe||Apalis iMX6||PCIe, Power Management|
Description: Suspend/Resume does not work if a PCIe device has been found. e.g. if 'lspci' returns at least one device.
Symptom is that resume blocks after all CPUs have been brought up.
[ 76.698740] Enabling non-boot CPUs ...
[ 76.703043] CPU1: Booted secondary processor
[ 76.703366] CPU1 is up
[ 76.710663] CPU2: Booted secondary processor
[ 76.711040] CPU2 is up
[ 76.718242] CPU3: Booted secondary processor
[ 76.718603] CPU3 is up
Refer to: https://community.nxp.com/docs/DOC-94856
| 18014||Feature Request||LVDS Channel Configuration||Apalis iMX6||LVDS|
Description: Starting with Apalis_iMX6_LinuxImageV2.6Beta2 the display timings and resolution can be set from the kernel command line or from the device tree. However the LVDS channel configuration can only be set from the device tree.
Implement a command line parameter to bring back this functionality similar to the ldb=xxx parameter from the 3.10.17 kernel.
Colour Depth and mapping.
Workaround: Change the device tree according to the needed LVDS configuration.
| 17925||Feature Request||Switch to zImage instead of uImage||Apalis iMX6, Colibri iMX6||Kernel|
Description: Switch to the generic compressed Kernel image type (zImage) instead of the U-Boot specific uImage format.
| 17732||Known Issue||Busybox and UTF-8 Chars in Filenames||Apalis T30, Apalis TK1, Apalis iMX6, Colibri PXA270, Colibri PXA300, Colibri PXA300 XT, Colibri PXA310, Colibri PXA320, Colibri T20, Colibri T30, Colibri VF50, Colibri VF61, Colibri iMX6, Colibri iMX7||Buildsystem|
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.
| 17143||Known Issue||Gstreamer/Nvgstplayer Memory Leak||Apalis T30, Colibri T30||Multimedia, Video Codecs|
Description: Each iteration of a movie H264 playback using gstreamer/nvgstplayer allocates a queue via NvMMQueueCreate(phQueue=0x4225f318, max_entries=32, entry-size=224, thread_safe=1) inside NVIDIA's binary only libnvmm_utils.so library which is never freed (such a function creates three pointers of total size 7392 + 28 + 32). Most probably there is a missing NvMMQueueDestroy() somewhere in the decoder handling.
Workaround: The easiest workaround would be to spawn a new gstreamer process for every movie being played as destroying that process after the playback will explicitly free any memory even if not previously implicitly having been freed.
Alternatively our partner Antmicro hacked up a custom libnvmm_utils.so wrapper library to be loaded by LD_PRELOAD which may intercept NvMMQueueCreate() calls and adaptively revert to a static queue in order to prevent any memory leaks. While such a solution will of course be highly use-case dependant it should fully fix any leaking.
Further investigation on NVIDIA's side is pending.
| 16834||Feature Request||i.MX 6 Thermal Throttling||Apalis iMX6, Colibri iMX6||CPU, Temperature Sensor|
Description: When the measured SOC temperature reaches /sys/devices/virtual/thermal/thermal_zone0/trip_point_0_temp (currently set to 85°C) the GPU frequency is reduced to 1/64 of its normal value. Once the SOC cooled down to 75°C the clock is set back to 64/64.
Should the temperature reach trip_point_1_temp (105°C) the OS is shut down.
- Implement a gradual reduction of GPU performance when trip_point_0_temp is reached.
- Increase trip_point_0_temp for Industrial Graded products.
Workaround: Set the GPU clock for higher temperatures to something higher than 1/64 in /sys/bus/platform/drivers/galcore/gpu3DMinClock for a trade off of higher performance vs. lower power dissipation.
| 16537||Feature Request||Use Ethernet PHY Power Down Mode for Suspend Mode||Colibri VF50, Colibri VF61||Ethernet|
Description: With #16470 the Ethernet PHY power down mode has been disabled. This increased the power consumption during suspend. Since Ethernet is often not used on power constrained devices, we prefer lower power consumption over working Ethernet. Therefor we should reenable the PHY power down mode when using suspend.
Workaround: Use U-Boot's MII capability to put the PHY into sleep mode at boot time (use "mii write 0 0 0x3800" to set PHY's PDOWN mode).
| 16168||Feature Request||Board Temperature Measurement Not Usable as it's Not Calibrated||Colibri iMX7||Temperature Sensor|
Description: The board temperature read from the touch controller isn't accurate. We would have to add a calibration feature.
| 15251||Feature Request||Linux Kernel Splash Screen doesn't Work on HDMI Output||Apalis T30, Apalis TK1, Apalis iMX6, Colibri T20, Colibri T30, Colibri iMX6||HDMI|
Description: Using a Linux logo be it the penguins or a custom one as e.g. explained at http://developer.toradex.com/knowledge-base/splash-screen-linux does not work on the HDMI output.
When the kernel sets up the display driver it first sets up VGA resolution subsequently doing DDC/EDID and then sets the final resolution. While the Logo is drawn during the VGA resolution setting it is lost later on.
Workaround: On Apalis/Colibri iMX6 one may use the U-Boot splash screen on HDMI output as well.
| 14771||Known Issue||HDMI Violation on 720x480p 16:9||Apalis iMX6, Colibri iMX6||HDMI|
Description: At 720x480p resolution the 'AVI Information Frame' might inadvertently report an aspect ratio of 4:3 even though 16:9 is in effect.
| 13614||Feature Request||eCos Freeze/MCC Lockup||Colibri VF61||CPU, Kernel|
Description: eCos freezes or deadlocks after running MCC pingpong for some time.
| 13134||Known Issue||Incompatibility between L4T Linux Kernel and iproute2-ss140804||Apalis T30, Colibri T20, Colibri T30||CAN|
Description: There exists an incompatibility of sorts between the older L4T Linux kernel version our Tegra BSPs are based on and the newer iproute2-ss140804 from our V2.4 BSPs leading to errors as follows:
root@apalis-t30:~# ip -details link show can0
RTNETLINK answers: Invalid argument
Cannot send link get request: Invalid argument
Workaround: Either downgrade to iproute2-ss131122 from our V2.3 BSPs or simply drop specifying a particular interface (e.g. use 'ip -details link show' instead).
| 13128||Feature Request||Support Cryptographic Acceleration and Assurance Module (CAAM)||Colibri VF50, Colibri VF61||Miscellaneous Peripherals|
Description: The CAAM module offers features such as cryptographic authentication (hashing/MACs), symmetric key block ciphers such as AES, DES and 3DES, and random number generation.
Workaround: Use cryptography libraries which implement the algorithms in pure software (such as OpenSSL).
| 11604||Known Issue||Audio Capture Stereo Issue||Colibri T20||Analog Audio|
Description: Capturing stereo audio inhibits audio fragments being swapped left/right at times.
Workaround: Use mono capture for now.
| 10626||Feature Request||Use DAC as Cheap Analog Audio Output||Colibri VF50||Analog Audio|
Description: Analog audio output support on DAC output pins (HEADPHONE_L/R).
| 7770||Feature Request||Analog/Digital Video Input||Colibri VF50, Colibri VF61||Camera Parallel Interface|
Description: Driver support for 8-bit BT656 YUV aka parallel camera interface as well as analogue video inputs.
| 7630||Feature Request||Choose Better Clock Parent for Display Clock||Colibri VF50, Colibri VF61||RGB|
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.
| 7176||Feature Request||H264 Enabled Browser||Apalis T30, Apalis TK1, Apalis iMX6, Colibri T20, Colibri T30, Colibri iMX6||Browser, Video Codecs|
Description: Implement support for H.264 acceleration in web browser.
| 6420||Feature Request||Support Suspend LP0||Apalis T30, Colibri T20, Colibri T30||Power Management|
Description: We do not support LP0 during suspend.
Workaround: Use LP1 during suspend.