03-07-2018, 01:35 PM
Hi,
We are porting some of our company products (amusement games), currently based on Raspberry Pi3, to your awesome Tinker Board.
We expected a 100% compatibility as regards the 40 pins socket, but if we swap the RPi3 with a Tinker Board, the latter does not boot.
We investigated, and we found that the reason is the UART1: if we disconnect the RX (pin10) and TX (pin8) wires, the Tinker boots normally!
The adapter board takes the UART1 TX/RX connections, and converts them to a CCTALK bus (TTL 5V), and I suppose TX and RX are internally connected together.
It seems that the Tinker at boot time checks something at UART1 TX/RX that prevents booting for some reasons...
If we enable UART2 on the Tinker, and connect RX (pin33) and TX (pin32) to our adapter, it boots normally, so the problem is related to UART1 only.
How can we disable this behavior ?
Thank you very much for your support.
David
We are porting some of our company products (amusement games), currently based on Raspberry Pi3, to your awesome Tinker Board.
We expected a 100% compatibility as regards the 40 pins socket, but if we swap the RPi3 with a Tinker Board, the latter does not boot.
We investigated, and we found that the reason is the UART1: if we disconnect the RX (pin10) and TX (pin8) wires, the Tinker boots normally!
The adapter board takes the UART1 TX/RX connections, and converts them to a CCTALK bus (TTL 5V), and I suppose TX and RX are internally connected together.
It seems that the Tinker at boot time checks something at UART1 TX/RX that prevents booting for some reasons...
If we enable UART2 on the Tinker, and connect RX (pin33) and TX (pin32) to our adapter, it boots normally, so the problem is related to UART1 only.
How can we disable this behavior ?
Thank you very much for your support.
David
