Other Parts Discussed in Thread: SYSCONFIG
Hi,
we are struggling to enable the MCU_UART1 as two-pin uart on pads C9 and D9 from Linux.
A similar thread for I2C conceptionally is here
The question is:
Can you explain the usage of &wkup_pmx0 (sysconfig tool, other platforms like J7 and AM65) vs &cbass_mcu (in the above e2e thread)? Is there a fundamental difference between the AM64xx and other platforms?
The sysconfig outputs the following for the MCU_UART1 for the pinmux:
&wkup_pmx0 { mymcu_uart1_pins_default: mymcu_uart1_pins_default { pinctrl-single,pins = < AM64X_WKUP_IOPAD(0x0038, PIN_INPUT, 0) /* (C9) MCU_UART1_RXD */ AM64X_WKUP_IOPAD(0x003c, PIN_OUTPUT, 0) /* (D9) MCU_UART1_TXD */ >; }; };
However the e2e thread shows something like this (here for an MCU_UART1)
&cbass_mcu { mcu_uart1_pins_default: mcu-uart1-pins-default { pinctrl-single,pins = < AM64X_MCU_IOPAD(0x0038, PIN_INPUT, 0) /* (C9) MCU_UART1_RXD */ AM64X_MCU_IOPAD(0x003c, PIN_INPUT, 0) /* (D9) MCU_UART1_TXD */ >; }; };
However we are not able to make the UART1 work with either &cbass_mcu or &wkup_pmx0.
When we check the particular PADCONFIG for the two pins we also see that the pads are still in MUXMODE=7, and not 0.
Is there anything we are missing?
Thanks!
--Gunter