NixOS on ARM/PINE64 ROCKPro64 - Revision history

SigmaSquadron: /* Serial console */ Dark mode support

2025-04-17T17:27:34Z

Serial console: Dark mode support

← Older revision		Revision as of 17:27, 17 April 2025
Line 63:		Line 63:
	{\| class="table"		{\| class="table"
	\|-		\|-
	!colspan="2" style="background: ~~#fafafa~~"\| Pi-2 Bus		!colspan="2" style="background: var(--color-inverted)"\| Pi-2 Bus
	\|-		\|-
	! Pin		! Pin

Mic92: fix links

2024-04-01T14:02:32Z

fix links

← Older revision		Revision as of 14:02, 1 April 2024
Line 30:		Line 30:
	U-Boot for this board is packaged in nixpkgs, and Hydra builds can be found here: https://hydra.nixos.org/job/nixpkgs/trunk/ubootRockPro64.aarch64-linux		U-Boot for this board is packaged in nixpkgs, and Hydra builds can be found here: https://hydra.nixos.org/job/nixpkgs/trunk/ubootRockPro64.aarch64-linux

	It can also be [~~https://nixos.wiki/wiki/NixOS_on_ARM~~#~~Compiling_through_QEMU~~ cross compiled] with		It can also be [[NixOS on ARM#Compiling through binfmt QEMU \| cross compiled]] with
	<syntaxhighlight lang="bash">		<syntaxhighlight lang="bash">
	nix-build '<nixpkgs>' --argstr system aarch64-linux -A ubootRockPro64 --out-link ubootRockPro64		nix-build '<nixpkgs>' --argstr system aarch64-linux -A ubootRockPro64 --out-link ubootRockPro64

imported>Tom: Remove superfluous info about downstream kernels. Mainline works fine, as of many versions ago.

2023-03-06T12:19:01Z

Remove superfluous info about downstream kernels. Mainline works fine, as of many versions ago.

@@ Line 101: / Line 101: @@
 See https://wiki.pine64.org/wiki/ROCKPro64#Setup_a_Serial_Console_.28UART.29 for more information on setting up the serial console
 == Resources ==
 * [https://www.pine64.org/rockpro64/ Official product page]

imported>Cyber-murmel: add nix-build for uboot

2022-01-14T00:16:41Z

add nix-build for uboot

← Older revision		Revision as of 00:16, 14 January 2022
Line 29:		Line 29:

	U-Boot for this board is packaged in nixpkgs, and Hydra builds can be found here: https://hydra.nixos.org/job/nixpkgs/trunk/ubootRockPro64.aarch64-linux		U-Boot for this board is packaged in nixpkgs, and Hydra builds can be found here: https://hydra.nixos.org/job/nixpkgs/trunk/ubootRockPro64.aarch64-linux

			It can also be [https://nixos.wiki/wiki/NixOS_on_ARM#Compiling_through_QEMU cross compiled] with
			<syntaxhighlight lang="bash">
			nix-build '<nixpkgs>' --argstr system aarch64-linux -A ubootRockPro64 --out-link ubootRockPro64
			</syntaxhighlight>

	== Board-specific installation notes ==		== Board-specific installation notes ==

imported>Kreyren: Nixified the picocom command

2021-07-29T20:05:18Z

Nixified the picocom command

← Older revision		Revision as of 20:05, 29 July 2021
Line 92:		Line 92:
	<syntaxHighlight lang=console>		<syntaxHighlight lang=console>
	# Connect to /dev/ttyUSB0 at baud 1500000		# Connect to /dev/ttyUSB0 at baud 1500000
	$ picocom -~~b 1500000~~ /dev/ttyUSB0		$ nix-shell -p picocom --run "picocom /dev/ttyUSB0 -b 1500000"
	</syntaxHighlight>		</syntaxHighlight>

imported>Kreyren: Moved the note up as i was stuck for 4 days figuring out why is it not booting

2021-07-29T20:03:05Z

Moved the note up as i was stuck for 4 days figuring out why is it not booting

← Older revision		Revision as of 20:03, 29 July 2021
Line 51:		Line 51:

	== Serial console==		== Serial console==

			{{note\|Do not connect RxD (pin 10) until the U-Boot SPL is running (see [RK3399 boot sequence\|https://wiki.pine64.org/wiki/RK3399_boot_sequence]) or the SPL will not start}}

	The ROCKPro64 uses a GPIO pinout compatible with the Raspberry Pi 2 and newer. This means that the following pins can be used to connect a serial adapter:		The ROCKPro64 uses a GPIO pinout compatible with the Raspberry Pi 2 and newer. This means that the following pins can be used to connect a serial adapter:
Line 94:		Line 96:

	See https://wiki.pine64.org/wiki/ROCKPro64#Setup_a_Serial_Console_.28UART.29 for more information on setting up the serial console		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.}}

	== Downstream kernel ==		== Downstream kernel ==

imported>Mic92: fix markup

2021-07-27T05:40:23Z

fix markup

← Older revision		Revision as of 05:40, 27 July 2021
Line 75:		Line 75:
	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:		To connect check your <code>dmesg</code> for an identifier of the serial console:

	~~```~~		<syntaxHighlight>
	[78635.965459] usb 2-1: new full-speed USB device number 8 using xhci_hcd		[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.119008] usb 2-1: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.63
Line 84:		Line 84:
	[78636.127103] ch341 2-1:1.0: ch341-uart converter detected		[78636.127103] ch341 2-1:1.0: ch341-uart converter detected
	[78636.142043] usb 2-1: ch341-uart converter now attached to ttyUSB0		[78636.142043] usb 2-1: ch341-uart converter now attached to ttyUSB0
	~~```~~		</syntaxHighlight>

	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`:		In our example that coresponds to the <code>ttyUSB0</code> which makes a new device available at <code>/dev/ttyUSB0</code> to which you can connect using for (example) <code>picocom</code>:

	~~```~~		<syntaxHighlight lang=console>
	# Connect to /dev/ttyUSB0 at baud 1500000		# Connect to /dev/ttyUSB0 at baud 1500000
	picocom -b 1500000 /dev/ttyUSB0		$ picocom -b 1500000 /dev/ttyUSB0
	~~```~~		</syntaxHighlight>

	See https://wiki.pine64.org/wiki/ROCKPro64#Setup_a_Serial_Console_.28UART.29 for more information on setting up the serial console		See https://wiki.pine64.org/wiki/ROCKPro64#Setup_a_Serial_Console_.28UART.29 for more information on setting up the serial console

imported>Kreyren: Added more info on the connection using serial console

2021-07-26T17:55:17Z

Added more info on the connection using serial console

@@ Line 70: / Line 70: @@
 | UART0_RX
 |}
 The serial console runs at 1500000 baud in the bootloader.
 {{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.}}

imported>Mic92: Mention nixos-aarch64-images

2020-12-02T20:28:23Z

Mention nixos-aarch64-images

← Older revision		Revision as of 20:28, 2 December 2020
Line 31:		Line 31:

	== Board-specific installation notes ==		== Board-specific installation notes ==

			You can use [https://github.com/Mic92/nixos-aarch64-images nixos-aarch64-images] to get an rockpro64 compatible disk image or running the commands manually as described below:

	U-Boot needs to be copied to specific sectors on the microSD card, eMMC or image with <code>dd</code>. Download/build U-Boot for the board, and write <code>idbloader.img</code> and <code>u-boot.itb</code> to the correct locations with (replace <code>/dev/mmcblkX</code> with the correct path to the card or image):		U-Boot needs to be copied to specific sectors on the microSD card, eMMC or image with <code>dd</code>. Download/build U-Boot for the board, and write <code>idbloader.img</code> and <code>u-boot.itb</code> to the correct locations with (replace <code>/dev/mmcblkX</code> with the correct path to the card or image):

imported>Lopsided98: I thought mainline didn't need the ethernet checksumming fix anymore, but it still does.

2019-12-15T20:20:34Z

I thought mainline didn't need the ethernet checksumming fix anymore, but it still does.

← Older revision		Revision as of 20:20, 15 December 2019
Line 40:		Line 40:

	{{note\|Prior to NixOS 20.03, a downstream version of U-Boot 2017.09 was packaged, which placed U-Boot in a single <code>idbloader.img</code> file. If that version is used, simply disregard the second command above.}}		{{note\|Prior to NixOS 20.03, a downstream version of U-Boot 2017.09 was packaged, which placed U-Boot in a single <code>idbloader.img</code> file. If that version is used, simply disregard the second command above.}}

			On many kernels, the ethernet driver cannot handle hardware check-summing of large packets, therefore this feature must be disabled for the ethernet to be stable. This can be done with the following NixOS configuration:
			<syntaxhighlight lang="nix">
			networking.localCommands = ''
			${pkgs.ethtool}/bin/ethtool -K eth0 rx off tx off
			'';
			</syntaxhighlight>

	== Serial console==		== Serial console==