NixOS on ARM/PINE64 ROCKPro64: Difference between revisions

imported>Mic92
Mention nixos-aarch64-images
imported>Kreyren
Added more info on the connection using serial console
Line 70: Line 70:
| UART0_RX
| UART0_RX
|}
|}
See https://wiki.pine64.org/wiki/ROCKPro64#GPIO_Pins for list of all pins


The serial console runs at 1500000 baud in the bootloader.
The serial console runs at 1500000 baud in the bootloader.
To connect check your `dmesg` for an identifier of the serial console:
```
[78635.965459] usb 2-1: new full-speed USB device number 8 using xhci_hcd
[78636.119008] usb 2-1: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.63
[78636.119017] usb 2-1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[78636.119022] usb 2-1: Product: USB2.0-Serial
[78636.127103] ch341 2-1:1.0: ch341-uart converter detected
[78636.142043] usb 2-1: ch341-uart converter now attached to ttyUSB0
```
In our example that coresponds to the `ttyUSB0` which makes a new device available at `/dev/ttyUSB0` to which you can connect using for (example) `picocom`:
```
# Connect to /dev/ttyUSB0 at baud 1500000
picocom -b 1500000 /dev/ttyUSB0
```
See https://wiki.pine64.org/wiki/ROCKPro64#Setup_a_Serial_Console_.28UART.29 for more information on setting up the serial console


{{note| It is not recommended to connect the serial adapter to pin 10 (RX) while booting, as this often causes the board to hang early in the bootloader. Disconnecting pin 10 still allows the serial console to be viewed, and it can be reconnected after the board boots, allowing interaction with the console.}}
{{note| It is not recommended to connect the serial adapter to pin 10 (RX) while booting, as this often causes the board to hang early in the bootloader. Disconnecting pin 10 still allows the serial console to be viewed, and it can be reconnected after the board boots, allowing interaction with the console.}}