What are you trying to achieve with fragment 2? If fragment 1 is ever enabled (I see that it is currently dormant) then it will clash with fragment 2 for GPIO 7. If the two are meant to be alternatives then it would be cleaner to write fragment 2 in the same style as fragment 1: (The uart3_pins node already has the equivalent of "brcm,function = <3>;")
Code:
fragment@1 {target = <&uart3_pins>;__dormant__ {brcm,pins = <4 5 7>;brcm,pull = <0 2 0>;};};Statistics: Posted by PhilE — Thu Aug 01, 2024 4:23 pm