PineNote Development/Flashing - Revision history

Ahelwer: Expanded page overview

2023-10-24T15:21:38Z

Expanded page overview

← Older revision		Revision as of 15:21, 24 October 2023
Line 4:		Line 4:

	This page contains information on flashing software to the [[PineNote]].		This page contains information on flashing software to the [[PineNote]].
			The general process is as follows:
			# Take a backup of all important data on the PineNote
			# Modify the partition layout to make space for your desired Linux distribution
			# Instantiate a root filesystem (rootfs) in the new partition space
			# Install your Linux distribution to the boot partition
			# Modify the boot process to boot the Linux distribution by default

	~~Currently~~, ~~software~~ can ~~be flashed using~~ rkdeveloptool ~~or from the factory Android installation (~~UART shell~~, adb, or fastboot)~~.		There are multiple possible methods of executing these steps, and this page attempts to document all of them.
			You can use:
			# <code>rkdeveloptool</code>, a command line utility for modifying [https://en.wikipedia.org/wiki/Rockchip Rockchip] devices over USB
			# The [[PineNote_Development/UART\|UART]] shell
			# [https://en.wikipedia.org/wiki/Android_Debug_Bridge Android Debug Bridge]
			# [https://en.wikipedia.org/wiki/Fastboot Fastboot]

	== Getting <code>rkdeveloptool</code> ==		== Getting <code>rkdeveloptool</code> ==

Ahelwer: /* Taking the backup */ can backup all partitions except for super and userdata

2023-10-23T17:42:05Z

Taking the backup: can backup all partitions except for super and userdata

← Older revision		Revision as of 17:42, 23 October 2023
Line 143:		Line 143:
	=== Taking the backup ===		=== Taking the backup ===

	With U-Boot patched, run:		With U-Boot patched, you can back up every partition except for super and userdata; run:

	<code>rkdeveloptool read-partition partition_name partition_name_backup.img</code>		<code>rkdeveloptool read-partition partition_name partition_name_backup.img</code>

			Unfortunately the super and userdata partitions run into a second limitation preventing dumping partitions larger than 2 GB, this time originating in <code>rkdeveloptool</code> itself.

	~~There is~~ a second ~~backup limit~~ preventing dumping partitions larger than 2 GB, this time ~~from~~ <code>rkdeveloptool</code>.
	This means if you have a large number of documents in the Android userdata partition they might not all make it into the backup.		This means if you have a large number of documents in the Android userdata partition they might not all make it into the backup.
	If you don't have many documents (or don't care about losing them) this should not be a problem.		If you don't have many documents (or don't care about losing them) this should not be a problem.

Ahelwer: /* List partitions */ Added partition descriptions

2023-10-23T17:27:07Z

List partitions: Added partition descriptions

← Older revision		Revision as of 17:27, 23 October 2023
Line 119:		Line 119:
	\| 10 \|\| cache \|\| 1 GB \|\| Stores temporary data; can be used to install a minimal Linux distribution!		\| 10 \|\| cache \|\| 1 GB \|\| Stores temporary data; can be used to install a minimal Linux distribution!
	\|-		\|-
	\| 11 \|\| metadata \|\| 17 MB \|\|		\| 11 \|\| metadata \|\| 17 MB \|\| Used for disk encryption
	\|-		\|-
	\| 12 \|\| super \|\| 3.25 GB \|\|		\| 12 \|\| super \|\| 3.25 GB \|\| Android itself is installed here
	\|-		\|-
	\| 13 \|\| logo \|\| 17 MB \|\|		\| 13 \|\| logo \|\| 17 MB \|\| Splash image displayed during boot
	\|-		\|-
	\| 14 \|\| device \|\| 67 MB \|\|		\| 14 \|\| device \|\| 67 MB \|\|
	\|-		\|-
	\| 15 \|\| userdata \|\| 119 GB \|\|		\| 15 \|\| userdata \|\| 119 GB \|\| The big one; user-installed Android apps and files live here
	\|}		\|}

Ahelwer: /* Backup */ Added partition table

2023-10-23T16:52:16Z

Backup: Added partition table

@@ Line 91: / Line 91: @@
 First, run <code>rkdeveloptool list-partitions</code> to print out your PineNote's partitions to get an idea of what you're dealing with.
-The stock PineNote has a fairly standard Android partition setup, including:
+The stock PineNote has a fairly standard [https://source.android.com/docs/core/architecture/partitions Android partition setup]:
-* uboot: the [https://en.wikipedia.org/wiki/Das_U-Boot U-Boot] embedded systems bootloader
-* trust: secrets that can be encrypted with a key stored in the [https://en.wikipedia.org/wiki/Trusted_Platform_Module TPM]
+{| class="wikitable"
-* waveform: important files controlling the e-ink screen's state changes
+|-
-* misc: miscellaneous files needed by the firmware
+! Number !! Name !! Size !! Purpose
-* dtbo: [https://en.wikipedia.org/wiki/Devicetree Device Tree Blob for Overlay], files describing the PineNote's hardware configuration
+|-
-* vbmeta: data required for verified boot
+| 0 || uboot || 4 MB || The [https://en.wikipedia.org/wiki/Das_U-Boot U-Boot] embedded systems bootloader
-* boot, security, recovery, backup, cache, metadata, super, logo, device
+|-
-* userdata: the big one; this is where all your files are stored in the stock Android install
+| 1 || trust || 4 MB || Secrets that can be encrypted with a key stored in the [https://en.wikipedia.org/wiki/Trusted_Platform_Module TPM]
 === Patch U-Boot ===
@@ Line 113: / Line 142: @@
 === Taking the backup ===
 There is a second backup limit preventing dumping partitions larger than 2 GB, this time from <code>rkdeveloptool</code>.

Ahelwer: /* Taking the backup */

2023-10-23T15:57:45Z

Taking the backup

← Older revision		Revision as of 15:57, 23 October 2023
Line 119:		Line 119:
	If you do have a lot of documents, workarounds include:		If you do have a lot of documents, workarounds include:
	* A possible patch written by Thomas exists [https://github.com/tpwrules/nixos-pinenote/blob/96d2c9158edb9da59afcb952cc864fada18382f9/nix/rkdeveloptool/0001-fix-large-dumps.patch here] but has not yet been upstreamed; consider investigating how to get the patch tested & upstreamed, or just apply it to your own local copy of <code>rkdeveloptool</code>		* A possible patch written by Thomas exists [https://github.com/tpwrules/nixos-pinenote/blob/96d2c9158edb9da59afcb952cc864fada18382f9/nix/rkdeveloptool/0001-fix-large-dumps.patch here] but has not yet been upstreamed; consider investigating how to get the patch tested & upstreamed, or just apply it to your own local copy of <code>rkdeveloptool</code>
	* Use [https://github.com/talpadk/pinenote-backup this] Python script written by Visti Andresen to automatically backup your entire partition by splitting reads into 2 GB chunks		* Use [https://github.com/talpadk/pinenote-backup this] Python script written by Visti Andresen (talpadk) to automatically backup your entire partition by splitting reads into 2 GB chunks

	See [https://github.com/m-weigand/pinenote-debian-recipes/releases/tag/v0.1 instructions on this artifact]. It will instruct you on extracting the rootfs into an empty ext4 partition. This can be done from Linux or Android. Further instructions on building your own rootfs [https://github.com/m-weigand/pinenote-debian-recipes can be found here].		See [https://github.com/m-weigand/pinenote-debian-recipes/releases/tag/v0.1 instructions on this artifact]. It will instruct you on extracting the rootfs into an empty ext4 partition. This can be done from Linux or Android. Further instructions on building your own rootfs [https://github.com/m-weigand/pinenote-debian-recipes can be found here].

Ahelwer at 00:19, 23 October 2023

2023-10-23T00:19:38Z

← Older revision		Revision as of 00:19, 23 October 2023
Line 3:		Line 3:
	{{Info\|These instructions are directed towards experienced developers only!}}		{{Info\|These instructions are directed towards experienced developers only!}}

	This page contains information on flashing software to the [~~https://wiki.pine64.org/wiki/PineNote~~ PineNote].		This page contains information on flashing software to the [[PineNote]].

	Currently, software can be flashed using rkdeveloptool or from the factory Android installation (UART shell, adb, or fastboot).		Currently, software can be flashed using rkdeveloptool or from the factory Android installation (UART shell, adb, or fastboot).

Ahelwer: /* Exit */

2023-10-14T02:14:19Z

Exit

← Older revision		Revision as of 02:14, 14 October 2023
Line 69:		Line 69:
	* If this prints out <code>DevNo=1 Vid=0x2207,Pid=0x350a,LocationID=303 Loader</code> then the process succeeded		* If this prints out <code>DevNo=1 Vid=0x2207,Pid=0x350a,LocationID=303 Loader</code> then the process succeeded

	=== ~~Exit~~ ===		=== Exiting ===

	You can boot the PineNote back into its normal mode of operation by powercycling the PineNote with its hardware power switch, or running the <code>rkdeveloptool reboot</code> command.		You can boot the PineNote back into its normal mode of operation by powercycling the PineNote with its hardware power switch, or running the <code>rkdeveloptool reboot</code> command.

Ahelwer: /* Entering Maskrom/Rockusb mode */

2023-10-14T02:13:59Z

Entering Maskrom/Rockusb mode

← Older revision		Revision as of 02:13, 14 October 2023
Line 23:		Line 23:
	Interfacing with the PineNote over USB using <code>rkdeveloptool</code> requires first booting the PineNote into [http://opensource.rock-chips.com/wiki_Rockusb an alternative operating mode] called Maskrom or Rockusb mode.		Interfacing with the PineNote over USB using <code>rkdeveloptool</code> requires first booting the PineNote into [http://opensource.rock-chips.com/wiki_Rockusb an alternative operating mode] called Maskrom or Rockusb mode.

	=== Possible ~~Methods~~ ===		=== Possible methods ===

	There are three possible methods of entering Maskrom/Rockusb mode:		There are three possible methods of entering Maskrom/Rockusb mode:

	==== Hardware ~~Magnet Switch~~ ====		==== Hardware magnet switch ====

	# Connect the PineNote to your computer via USB and boot the PineNote into Android		# Connect the PineNote to your computer via USB and boot the PineNote into Android
Line 38:		Line 38:
	</gallery>		</gallery>

	==== U-Boot ====		==== U-Boot terminal ====
	This method requires a [[PineNote_Development/UART#USB_passthrough\|UART dongle with passthrough]] allowing simultaneous UART & USB connections.		This method requires a [[PineNote_Development/UART#USB_passthrough\|UART dongle with passthrough]] allowing simultaneous UART & USB connections.
	It is nice because you can easily switch back & forth between U-Boot and Rockusb without having to physically manipulate the PineNote or its connectors; this is especially helpful when trying to develop U-Boot.		It is nice because you can easily switch back & forth between U-Boot and Rockusb without having to physically manipulate the PineNote or its connectors; this is especially helpful when trying to develop U-Boot.
Line 49:		Line 49:
	You can exit back to the U-Boot terminal by sending <code>ctrl+c</code> again.		You can exit back to the U-Boot terminal by sending <code>ctrl+c</code> again.

	==== Shorting ~~Test Points~~ ====		==== Shorting test points ====

	If the bootloader is broken/corrupted, you cannot get to Maskrom without opening up the device (it can be opened using spudger and a bit of patience).		If the bootloader is broken/corrupted, you cannot get to Maskrom without opening up the device (it can be opened using spudger and a bit of patience).
Line 69:		Line 69:
	* If this prints out <code>DevNo=1 Vid=0x2207,Pid=0x350a,LocationID=303 Loader</code> then the process succeeded		* If this prints out <code>DevNo=1 Vid=0x2207,Pid=0x350a,LocationID=303 Loader</code> then the process succeeded

	=== ~~Exiting mode~~ ===		=== Exit ===

	You can boot the PineNote back into its normal mode of operation by powercycling the PineNote with its hardware power switch, or running the <code>rkdeveloptool reboot</code> command.		You can boot the PineNote back into its normal mode of operation by powercycling the PineNote with its hardware power switch, or running the <code>rkdeveloptool reboot</code> command.

Ahelwer: /* U-Boot */

2023-10-14T02:12:42Z

U-Boot

← Older revision		Revision as of 02:12, 14 October 2023
Line 43:		Line 43:

	# Connect to the PineNote via UART and USB simultaneously		# Connect to the PineNote via UART and USB simultaneously
	# Interrupt the U-Boot startup using <code>ctrl-c</code> sent over UART		# Interrupt the U-Boot startup using <code>ctrl+c</code> sent over UART
	# In the U-Boot terminal over UART, run <code>rockusb 0 mmc 0</code>		# In the U-Boot terminal over UART, run <code>rockusb 0 mmc 0</code>

			The UART terminal should print <code>RKUSB</code> then a spinner will appear.
			You can exit back to the U-Boot terminal by sending <code>ctrl+c</code> again.

	==== Shorting Test Points ====		==== Shorting Test Points ====

Ahelwer: /* U-Boot */

2023-10-14T02:10:11Z

U-Boot

← Older revision		Revision as of 02:10, 14 October 2023
Line 39:		Line 39:

	==== U-Boot ====		==== U-Boot ====
	This method requires a [[~~PineNote Development~~/UART\|UART dongle ~~for the PineNote~~]] ~~with passthrough~~ allowing simultaneous UART & USB connections.		This method requires a [[PineNote_Development/UART#USB_passthrough\|UART dongle with passthrough]] allowing simultaneous UART & USB connections.
	It is nice because you can easily switch back & forth between U-Boot and Rockusb without having to physically manipulate the PineNote or its connectors; this is especially helpful when trying to develop U-Boot.		It is nice because you can easily switch back & forth between U-Boot and Rockusb without having to physically manipulate the PineNote or its connectors; this is especially helpful when trying to develop U-Boot.

	# Interrupt the U-Boot startup using ''ctrl-c~~'' (while attached using an~~ UART ~~dongle)~~		# Connect to the PineNote via UART and USB simultaneously
	# ~~While in~~ U-Boot ~~use the command~~ <code>rockusb 0 mmc 0</code> ~~to start Rockusb mode.~~		# Interrupt the U-Boot startup using <code>ctrl-c</code> sent over UART
			# In the U-Boot terminal over UART, run <code>rockusb 0 mmc 0</code>

	==== Shorting Test Points ====		==== Shorting Test Points ====