- In U-Boot, USB functions are limited:
- USB 3.0 is disabled in U-Boot, only USB 2.0 is available
- The OTG ID pin 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.
- In U-Boot, there is no PRU Ethernet support. Only the primary Ethernet port
X5 is usable in the bootloader.
- From U-Boot, most GPIOs can't be read or set, as they are disabled in the
default pinmuxing. This also affects LED and button GPIOs. LEDs and buttons
are working as expected on Linux.
- There is currently no driver support for the Bluetooth module of the MBaX4XxL.
- In rare cases, the USB3 PHY initialization has been observed to fail with the
message "Timeout waiting for CMN ready" during boot, leaving the USB
controller unusable. A power cycle is necessary to recover from this state.
- On variants with only a single R5 core (TQMa6412L, TQMa6411L), booting
R5 programs and communicating with them using the Linux remoteproc/rpmsg
drivers is currently unsupported.
- The AM64x currently doesn't support Suspend-to-RAM
PRU Gigabit Ethernet
There is a regression in scarthgap.TQ.ARM.BSP.0005 which prevents that the PRU firmware can be loaded properly during system start.
As workaround meta-tq and meta-ti have to be updated to the following commit ids
| Layer | Commit ID |
| meta-tq | 7c8a9e582df35a7e7f9bb95288b728da5c4011d2 |
| meta-ti | 8c258e731e62954ff41460febc2c036fb5ca552c |