rjhdakota

Disregard this thread, got it working.

Since I am using Armbian kernel V5, it is using Device Trees for GPIO config rather than .FEX files. The build for this board appears to be setting up uart2 with the following overlay file. This is not working and I suspect this overly needs to change. Anyone know what changes are needed? Maybe the address is incorrect? /dts-v1/; / { compatible = "allwinner,sun8i-r40"; fragment@0 { target-path = "/aliases"; __overlay__ { serial2 = "/soc/serial@1c28800"; }; }; fragment@1 { target = < 0xffffffff >; __overlay__ { pinctrl-names = "default"; pinctrl-0 = < 0xffffffff >; status = "okay"; }; }; __fixups__ { uart2 = "/fragment@1:target:0"; uart2_pi_pins = "/fragment@1/__overlay__:pinctrl-0:0"; }; };

Thanks for responding. Not sure which logs I can give? This is a not a running issue its a configuration issue. It appears that the default OS build does include support for the UART on the GPIO. I do have an OrangePI board running Armbian that does support this and works fine. For our project we would like to use the Bananapi board since it fits in our existing enclosure. I believe I need to modify one of the .fex files in the BSP to assign pins to the TX/RX but docs on this is scarce, I found one reference where someone got it working with a different OS but the change does not seem to apply to Armbian. -Rich

I am able to rebuild the kernel for this board and the image runs fine, but it appears that is does not support the UART on the GPIO. Does anyone know which kernel files need to be modified for this? It looks like its one of the .fex files in the pack-uboot folder. But there are multiple folders in that folder with multiple .fex files that all reference the uart. (sun50iw6/sun50iw9). How can I tell which .fex file the build is using? Thanks for any help, -Rich