I am working with the Banana Pi F3 and have come across documentation that mentions 12 UART ports available on the board. However, I am unsure of how these UARTs are mapped to the physical pins (TX, RX) and what their specific use cases are. Can anyone provide detailed information on which UART ports (e.g., UART0, UART1, UART2, etc.) correspond to which physical pins on the GPIO header, and how these UARTs are typically used or configured on this board? Additionally, if there are any relevant device tree settings or other configuration files that define these mappings, I’d appreciate some guidance on accessing that information. Thanks!
I think you can get all or most of the information from the BPI-F3 schematic you can find under Resouces section on the documentation page. In that PDF you can check UART Map on page 7 and 26 pin GPIO on page 28. Also check out the 16.3 UART and 16.4 GPIO sections of the SpacemiT K1 CPU documentation.
Hello @JLP,
Thanks for your response. I will go through the document. The sole intention of this is to use all the serial ports available on the external headers in my project, but I’m unable to activate all the UARTs and use them as mentioned in the schematic (UART0/5/8/9/RUART0/1 available on the external header of the Banana Pi F3).
If you know any dedicated source to set the GPIOs to activate and use them, it would be very helpful.
-
If anyone knows how to configure gpio pins available on 26 pin header for alternative functions. in my project i want to use multiple UART ports. i have derived from the hardware documentation GPIO pin numbers for UART5/8/9 but unable to change the default pin mode to UART mode (MUXMODE) .
-
R_UART0 pins are available but it is not visible under available ttyS. when we checked k1-x_deb1.dtb (converted to dts file) there is no node initialized for r_uart0
-
How to change the baud rate of any UART ports? the api reference given in the documentation https://bianbu-linux.spacemit.com/en/device/peripheral_driver/UART#api%E4%BB%8B%E7%BB%8D is not much useful. @JLP