TQMa8MPxS - YOCTO Linux BSP documentation

Known Issues

Known Issues BSPs

Known Issues scarthgap.TQ.ARM.BSP.0011

  • Ethernet
    • Possible communication error to PHY attached to FEC, reboot required to fix
    • ETH1 looses manual assigned IP after suspend/resume. Default systemd network configuration uses DHCP with fallback. Has to be adjusted if needed.
  • USB Host
    • USB Superspeed U3 powersave mode is broken
    • Some USB devices are not detected (overcurrent detection on MB-SMARC-2)
  • USB 2.0 DRD (X4 on MB-SMARC-2):
    • Linux: no detection of USB devices in host mode (hardware limitation on SoM)
    • U-Boot: limited to peripheral (dual role not supported by upstream DWC3 driver)
  • USB 3.0 micro (X3 on MB-SMARC-2)
    • peripheral mode not supported (hardware limitation on SoM, connected to Hub)
  • USB Bluetooth:
    • Some adapters cause the following error during bootup
      Bluetooth: hci0: unexpected event for opcode 0xfc2f
      According to https://lkml.org/lkml/2019/6/6/868 this can be ignored
  • UBI / UBIFS images are enabled by default when using DISTRO=spaetzle[-nxp]. The generated rootfs size must not exceed the size defined by UBI_LEB_SIZE and UBI_MAX_LEB_COUNT on machine level.
  • Hardware Rev. 010x: SER2's RTS and CTS signals are controlled by GPIO only, fixed with Hardware Rev. 030x
  • LVDS
    • Display AUO G185HAN01 not tested on regular base
  • Kernel based on linux-tq / linux-rt-tq
    • Suspend & resume not supported (yet)
  • NFS boot: The order of network devices is swapped during Linux boot. Therefore, the U-Boot environment variable netdev must be swapped to the U-Boot network device used.
    • For U-Boot eth0 (ethernet@30bf0000) set netdev=eth1 (default)
    • For U-Boot eth1 (ethernet@30be0000) set netdev=eth0

The information provided on this wiki page is subject to change due to circumstances beyond our control. While we strive to keep all details as accurate and up-to-date as possible, it is possible that certain updates or changes may go unnoticed for some time. As a result, some sections of this page may contain outdated information. If you notice any mistakes in the documentation, we kindly ask you to inform the TQ Support through our ticket system.