The tisdk-default-image built for am64xx-evm invokes agetty on ttyS1,
which fails because the corresponding UART mcu_uart1 is disabled in the
device tree.  systemd respawns agetty every 10 seconds, thereby filling
the log files with error messages and wearing out the SD card:

  systemd[1]: [email protected]: Scheduled restart job, restart 
counter is at 9.
  systemd[1]: Stopped Serial Getty on ttyS1.
  systemd[1]: Started Serial Getty on ttyS1.
  systemd[1]: [email protected]: Succeeded.
  agetty[1282]: /dev/ttyS1: not a tty
  systemd[1]: [email protected]: Scheduled restart job, restart 
counter is at 10.

systemd can't tell whether agetty failed transiently or permanently
because its exit code is 1 in either case and diagnostics are only
reported via syslog.

However since mcu_uart1 is disabled by default in both existing am64xx
device trees (k3-am642-evm.dts and k3-am642-sk.dts), configuring it as
console is pointless, so disable it (but retain the one on ttyS2).
If a future device tree enables mcu_uart1 by default, the corresponding
machine config may add ttyS1 to SERIAL_CONSOLES.

Signed-off-by: Lukas Wunner <[email protected]>
---
 conf/machine/include/am64xx.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/conf/machine/include/am64xx.inc b/conf/machine/include/am64xx.inc
index 641bddd..3d40c4c 100644
--- a/conf/machine/include/am64xx.inc
+++ b/conf/machine/include/am64xx.inc
@@ -3,7 +3,7 @@ SOC_FAMILY_append = ":am64xx"
 
 MACHINE_FEATURES += "screen touchscreen"
 
-SERIAL_CONSOLES = "115200;ttyS2 115200;ttyS1"
+SERIAL_CONSOLES = "115200;ttyS2"
 SERIAL_CONSOLES_CHECK = "${SERIAL_CONSOLES}"
 
 KERNEL_DEVICETREE = " \
-- 
2.31.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13782): 
https://lists.yoctoproject.org/g/meta-ti/message/13782
Mute This Topic: https://lists.yoctoproject.org/mt/82870554/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to