TQMa62xx - YOCTO Linux BSP documentation
Known Issues
Known Issues BSPs
Known Issues scarthgap.TQ.ARM.BSP.0004
- Waking up from Suspend-to-RAM currently does not work on the MBa62xx.
- Under high system load, the AM62x may become unstable during audio playback or recording.
- During audio playback or recording, the kernel prints various error messages regarding DMA controller configuration timeouts.
- Very rarely, under high system load, the I2C controller of the AM62x has been seen to get stuck in a state in which it permanently pulls down the SCL pin until the controller is reset.
- The OTG ID pin of the Micro-USB port (X10) is ignored in U-Boot. The mode of
the port is determined by the boot mode:
- When booting in USB host mode (from mass storage), the port uses host mode. Access to the connected USB storage device is possible from the U-Boot command line.
- For all other boot modes, the port will be in device mode. The "dfu" command can be used to flash the boot media from a connected host.
- On TQMa62xx variants with AM62x GP SoC, SD card boot is slow after power-on, taking several seconds before the first messages of the bootloader
- On TQMa62xx variants without user EEPROM, the EEPROM device is not disabled in the Linux Device Tree, resulting in a non-critical error message in the kernel log during boot
- After an unclean reboot without power cycle while the IMX327 camera is running, the camera can be in an inconsistent state where the next attempt to use it will result in a hang (of gst-launch, when using the example commands). Terminating and re-running gst-launch will usually fix this issue; it is unknown if a power cycle may be necessary in some cases.
Known Issues scarthgap.TQ.ARM.BSP.0003
- Waking up from Suspend-to-RAM currently does not work on the MBa62xx.
- Under high system load, the AM62x may become unstable during audio playback or recording.
- During audio playback or recording, the kernel prints various error messages regarding DMA controller configuration timeouts.
- Very rarely, under high system load, the I2C controller of the AM62x has been seen to get stuck in a state in which it permanently pulls down the SCL pin until the controller is reset.
- The OTG ID pin of the Micro-USB port (X10) is ignored in U-Boot. The mode of
the port is determined by the boot mode:
- When booting in USB host mode (from mass storage), the port uses host mode. Access to the connected USB storage device is possible from the U-Boot command line.
- For all other boot modes, the port will be in device mode. The "dfu" command can be used to flash the boot media from a connected host.
- On TQMa62xx variants with AM62x GP SoC, SD card boot is slow after power-on, taking several seconds before the first messages of the bootloader
- On TQMa62xx variants without user EEPROM, the EEPROM device is not disabled in the Linux Device Tree, resulting in a non-critical error message in the kernel log during boot
- After an unclean reboot without power cycle while the IMX327 camera is running, the camera can be in an inconsistent state where the next attempt to use it will result in a hang (of gst-launch, when using the example commands). Terminating and re-running gst-launch will usually fix this issue; it is unknown if a power cycle may be necessary in some cases.
Known Issues scarthgap.TQ.ARM.BSP.0002
- Waking up from Suspend-to-RAM currently does not work on the MBa62xx.
- Under high system load, the AM62x may become unstable during audio playback or recording.
- During audio playback or recording, the kernel prints various error messages regarding DMA controller configuration timeouts.
- Very rarely, under high system load, the I2C controller of the AM62x has been seen to get stuck in a state in which it permanently pulls down the SCL pin until the controller is reset.
- The OTG ID pin of the Micro-USB port (X10) is ignored in U-Boot. The mode of
the port is determined by the boot mode:
- When booting in USB host mode (from mass storage), the port uses host mode. Access to the connected USB storage device is possible from the U-Boot command line.
- For all other boot modes, the port will be in device mode. The "dfu" command can be used to flash the boot media from a connected host.
- On TQMa62xx variants with AM62x GP SoC, SD card boot is slow after power-on, taking several seconds before the first messages of the bootloader
- On TQMa62xx variants without user EEPROM, the EEPROM device is not disabled in the Linux Device Tree, resulting in a non-critical error message in the kernel log during boot
- After an unclean reboot without power cycle while the IMX327 camera is running, the camera can be in an inconsistent state where the next attempt to use it will result in a hang (of gst-launch, when using the example commands). Terminating and re-running gst-launch will usually fix this issue; it is unknown if a power cycle may be necessary in some cases.
Known Issues scarthgap.TQ.ARM.BSP.0001
- Waking up from Suspend-to-RAM currently does not work on the MBa62xx.
- Under high system load, the AM62x may become unstable during audio playback or recording.
- During audio playback or recording, the kernel prints various error messages regarding DMA controller configuration timeouts.
- Very rarely, under high system load, the I2C controller of the AM62x has been seen to get stuck in a state in which it permanently pulls down the SCL pin until the controller is reset.
- The OTG ID pin of the Micro-USB port (X10) is ignored in U-Boot. The mode of
the port is determined by the boot mode:
- When booting in USB host mode (from mass storage), the port uses host mode. Access to the connected USB storage device is possible from the U-Boot command line.
- For all other boot modes, the port will be in device mode. The "dfu" command can be used to flash the boot media from a connected host.
- On TQMa62xx variants with AM62x GP SoC, SD card boot is slow after power-on, taking several seconds before the first messages of the bootloader
- On TQMa62xx variants without user EEPROM, the EEPROM device is not disabled in the Linux Device Tree, resulting in a non-critical error message in the kernel log during boot