Pinebook Pro SPI - Revision history

Reukiodo: add TowBoot for beginners

2024-11-18T14:34:32Z

add TowBoot for beginners

← Older revision		Revision as of 14:34, 18 November 2024
Line 4:		Line 4:

	== Writing to SPI from within PBP ==		== Writing to SPI from within PBP ==

			The easiest way to start with SPI is to flash [https://tow-boot.org/devices/pine64-pinebookPro.html TowBoot] using its dedicated installer SD image from https://github.com/Tow-Boot/Tow-Boot/releases . TowBoot is a much simplified U-Boot with a UI menu for selecting a boot device.

	Forum user [https://forum.pine64.org/member.php?action=profile&uid=15527 pcm720] provided an example of writing to the SPI from within Linux in [https://github.com/pcm720/u-boot-build-scripts/releases their self-published version of U-Boot] that offers boot functionality for NVMe drives. It involves use of <code>flash_erase</code> command (available in the mtd-utils package on Arch Linux and Manjaro) and the <code>dd</code> command.		Forum user [https://forum.pine64.org/member.php?action=profile&uid=15527 pcm720] provided an example of writing to the SPI from within Linux in [https://github.com/pcm720/u-boot-build-scripts/releases their self-published version of U-Boot] that offers boot functionality for NVMe drives. It involves use of <code>flash_erase</code> command (available in the mtd-utils package on Arch Linux and Manjaro) and the <code>dd</code> command.

Dsimic: /* Maskrom mode (unreliable method) */ Wording improvements

2023-11-07T05:47:38Z

Maskrom mode (unreliable method): Wording improvements

← Older revision		Revision as of 05:47, 7 November 2023
Line 18:		Line 18:

	=== Maskrom mode (unreliable method) ===		=== Maskrom mode (unreliable method) ===
	{{Hint\|The recovery button relies on software support in the boot loader, which makes it unreliable.}}		{{Hint\|The recovery button relies entirely on the software support in the boot loader, which makes it unreliable.}}

	According to Rockchip documentation, these steps should work; unfortunately, many users have reported them to be unsuccessful. You may need to repeat these steps several times for them to work.		According to Rockchip documentation, these steps should work; unfortunately, many users have reported them to be unsuccessful. You may need to repeat these steps several times for them to work.
Line 26:		Line 26:
	# Release recovery button after about three seconds.		# Release recovery button after about three seconds.

	In case this approach fails, please see the section below.		In case this approach fails, please see the section below for a more reliable method.

	=== Maskrom mode (reliable method) ===		=== Maskrom mode (reliable method) ===

Dsimic: /* Writing to SPI from a second machine */ Proper hierarchy

2023-11-06T19:53:33Z

Writing to SPI from a second machine: Proper hierarchy

← Older revision		Revision as of 19:53, 6 November 2023
Line 46:		Line 46:
	# Check is the Pinebook Pro connected by running <code>rkdeveloptool ld</code>. If successful, the output should be like: <code>DevNo=1 Vid=0x2207,Pid=0x330c,LocationID=1401 Maskrom</code>		# Check is the Pinebook Pro connected by running <code>rkdeveloptool ld</code>. If successful, the output should be like: <code>DevNo=1 Vid=0x2207,Pid=0x330c,LocationID=1401 Maskrom</code>

	=== After entering maskrom mode ===		==== After entering maskrom mode ====

	Now that when the RK3399 SoC is in <code>maskrom mode</code>, you can use <code>rkdeveloptool</code> to write data to the SPI. To do so you'll need the binary file you'll be writing to SPI, which will be referred to as <code>SPI_new.bin</code>, and a helper file named [https://dl.radxa.com/rockpi4/images/loader/spi/rk3399_loader_spinor_v1.15.114.bin rk3399_loader_spinor_v1.15.114.bin].		Now that when the RK3399 SoC is in <code>maskrom mode</code>, you can use <code>rkdeveloptool</code> to write data to the SPI. To do so you'll need the binary file you'll be writing to SPI, which will be referred to as <code>SPI_new.bin</code>, and a helper file named [https://dl.radxa.com/rockpi4/images/loader/spi/rk3399_loader_spinor_v1.15.114.bin rk3399_loader_spinor_v1.15.114.bin].
Line 55:		Line 55:
	# Run <code>rkdeveloptool rd</code> to reboot your Pinebook Pro.		# Run <code>rkdeveloptool rd</code> to reboot your Pinebook Pro.

	=== Zeroing out the SPI ===		==== Zeroing out the SPI ====

	In case, you wrote something bad to your SPI, it's helpful to wipe away that data with zeros. To do that, you follow the same steps above to enter <code>maskrom mode</code> and then write a binary file that consists of all zeros.		In case, you wrote something bad to your SPI, it's helpful to wipe away that data with zeros. To do that, you follow the same steps above to enter <code>maskrom mode</code> and then write a binary file that consists of all zeros.

Dsimic: /* Maskrom mode (reliable method) */ Ditto

2023-11-06T19:52:11Z

Maskrom mode (reliable method): Ditto

← Older revision		Revision as of 19:52, 6 November 2023
Line 36:		Line 36:
	# Power off the Pinebook Pro.		# Power off the Pinebook Pro.
	# Unscrew the bottom cover.		# Unscrew the bottom cover.
	# Remove the metal shield surrounding the main CPU. The shield is held in place by ~~a tape and micro~~ clamps on the board. The clamps can be released with a pry tool and some force. [https://forum.pine64.org/showthread.php?tid=11073&pid=75096#pid75096 This forum post with photos] shows how it can be done.		# Remove the metal RF shield surrounding the main CPU. The shield is held in place by small clamps on the board. The clamps can be released with a pry tool and some force. [https://forum.pine64.org/showthread.php?tid=11073&pid=75096#pid75096 This forum post with photos] shows how it can be done.
	# Disconnect all ~~(!!!)~~ boot devices ~~(emmc~~, ~~sdcard~~, ~~usb)~~.		# Disconnect all boot devices, i.e. eMMC, microSD card and USB.
	# Locate SPI flash (component number 29 on [https://wiki.pine64.org/images/4/45/PBPL_S.jpg this photo of the Pinebook Pro internals]).		# Locate SPI flash (component number 29 on [https://wiki.pine64.org/images/4/45/PBPL_S.jpg this photo of the Pinebook Pro internals]).
	# Connect your Pinebook Pro with USB-C to USB-A cable to second machine (Pinebook Pro on the USB-C side)		# Connect your Pinebook Pro with USB-C to USB-A cable to second machine (Pinebook Pro on the USB-C side)

Dsimic: /* Writing to SPI from a second machine */ Wording improvements

2023-11-06T19:48:28Z

Writing to SPI from a second machine: Wording improvements

Dsimic: /* Writing to SPI from within PBP */ More misleading information corrected

2023-11-06T19:46:19Z

Writing to SPI from within PBP: More misleading information corrected

← Older revision		Revision as of 19:46, 6 November 2023
Line 5:		Line 5:
	== Writing to SPI from within PBP ==		== Writing to SPI from within PBP ==

	[https://forum.pine64.org/member.php?action=profile&uid=15527 ~~Forum user~~ pcm720] ~~showed~~ an example of writing to the SPI from within ~~PBP~~ in [https://github.com/pcm720/u-boot-build-scripts/releases their self-published version of U-Boot] that offers boot functionality for NVMe drives. It involves use of <code>flash_erase</code> command (available in the mtd-utils package on Arch/Manjaro) and the <code>dd</code> command.		Forum user [https://forum.pine64.org/member.php?action=profile&uid=15527 pcm720] provided an example of writing to the SPI from within Linux in [https://github.com/pcm720/u-boot-build-scripts/releases their self-published version of U-Boot] that offers boot functionality for NVMe drives. It involves use of <code>flash_erase</code> command (available in the mtd-utils package on Arch Linux and Manjaro) and the <code>dd</code> command.

			However, <code>flashcp</code> command should be used instead of <code>dd</code>, to make sure all specifics of the underlying flash memory are covered.

	== Writing to SPI from a second machine ==		== Writing to SPI from a second machine ==

Dsimic: /* Maskrom mode (unreliable method) */ Another cleanup

2023-11-06T10:16:01Z

Maskrom mode (unreliable method): Another cleanup

← Older revision		Revision as of 10:16, 6 November 2023
Line 24:		Line 24:
	# Release recovery button after about three seconds.		# Release recovery button after about three seconds.

	In case this approach fails, ~~the two pins on the SPI chip can shorted by hand, as described in~~ the section below.		In case this approach fails, please see the section below.

	=== Maskrom mode (reliable method) ===		=== Maskrom mode (reliable method) ===

Dsimic: /* Maskrom mode (unreliable method) */ Spelled out

2023-11-06T10:10:53Z

Maskrom mode (unreliable method): Spelled out

← Older revision		Revision as of 10:10, 6 November 2023
Line 22:		Line 22:
	# Press and hold recovery button.		# Press and hold recovery button.
	# Short press reset.		# Short press reset.
	# Release recovery button after about 3 seconds.		# Release recovery button after about three seconds.

	In case this approach fails, the two pins on the SPI chip can shorted by hand, as described in the section below.		In case this approach fails, the two pins on the SPI chip can shorted by hand, as described in the section below.

Dsimic: /* Maskrom mode (unreliable method) */ Removed the misleading descriptions, check out the PBP schematic to verify it yourself

2023-11-06T10:10:32Z

Maskrom mode (unreliable method): Removed the misleading descriptions, check out the PBP schematic to verify it yourself

← Older revision		Revision as of 10:10, 6 November 2023
Line 24:		Line 24:
	# Release recovery button after about 3 seconds.		# Release recovery button after about 3 seconds.

	~~Why~~ this ~~procedure is unreliable is not clear~~, ~~but there are two suspicions:~~		In case this approach fails, the two pins on the SPI chip can shorted by hand, as described in the section below.

	* The button is not working correctly or is just prone to failures.
	* The problem occurs only when the ~~SPI was previously flashed.~~

	~~The button works by shorting~~ two pins in the SPI ~~device. But in some cases it just does nothing. Fortunately, the two pins~~ can shorted by hand, as described in the ~~next method~~.

	=== Maskrom mode (reliable method) ===		=== Maskrom mode (reliable method) ===

Dsimic: /* Maskrom mode (unreliable method) */ Added a hint

2023-11-06T10:02:39Z

Maskrom mode (unreliable method): Added a hint

← Older revision		Revision as of 10:02, 6 November 2023
Line 16:		Line 16:

	=== Maskrom mode (unreliable method) ===		=== Maskrom mode (unreliable method) ===
			{{Hint\|The recovery button relies on software support in the boot loader, which makes it unreliable.}}

	According to Rockchip documentation, these steps should work; unfortunately, many users have reported them to be unsuccessful. You may need to repeat these steps several times for them to work.		According to Rockchip documentation, these steps should work; unfortunately, many users have reported them to be unsuccessful. You may need to repeat these steps several times for them to work.

← Older revision		Revision as of 19:48, 6 November 2023
Line 11:		Line 11:
	== Writing to SPI from a second machine ==		== Writing to SPI from a second machine ==

	Writing to the SPI from a second machine is more complicated than the other method, but it is the only option when troubleshooting an SPI flash gone wrong. This method works by bringing the ~~PBP~~ into <code>maskrom mode</code> and issuing commands on the second machine that download the flash image onto the ~~PBP~~.		Writing to the SPI from a second machine is more complicated than the other method, but it is the only option when troubleshooting an SPI flash gone wrong. This method works by bringing the RK3399 SoC into <code>maskrom mode</code> and issuing commands on the second machine that download the flash image onto the Pinebook Pro.

	Upon entering <code>maskrom mode</code>, the power LED on your ~~PBP~~ won't light up and neither will the display. Instead, your second machine, the one connected to your ~~PBP~~ via USB, will indicate <code>maskrom mode</code> by logging to <code>journalctl</code>.		Upon entering <code>maskrom mode</code>, the power LED on your Pinebook Pro won't light up and neither will the display. Instead, your second machine, the one connected to your Pinebook Pro via USB, will indicate <code>maskrom mode</code> by logging to <code>journalctl</code>.

	There are two ways to reach <code>maskrom mode</code>, but the first tends to be less reliable.		There are two ways to reach <code>maskrom mode</code>, but the first tends to be less reliable.
Line 39:		Line 39:
	# Disconnect all (!!!) boot devices (emmc, sdcard, usb).		# Disconnect all (!!!) boot devices (emmc, sdcard, usb).
	# Locate SPI flash (component number 29 on [https://wiki.pine64.org/images/4/45/PBPL_S.jpg this photo of the Pinebook Pro internals]).		# Locate SPI flash (component number 29 on [https://wiki.pine64.org/images/4/45/PBPL_S.jpg this photo of the Pinebook Pro internals]).
	# Connect your ~~PBP~~ with USB-C - USB-A cable to second machine (~~PBP~~ on USB-C side)		# Connect your Pinebook Pro with USB-C to USB-A cable to second machine (Pinebook Pro on the USB-C side)
	# Short pins CLK and VSS (see chip diagram to the right for the names of pins). This can be done with a pair of tweezers when short on tools. [[File:Spi.png\|right]]		# Short pins CLK and VSS (see chip diagram to the right for the names of pins). This can be done with a pair of tweezers when short on tools. [[File:Spi.png\|right]]
	# Power on the Pinebook Pro.		# Power on the Pinebook Pro.
	# Press the reset button (component number 28).		# Press the reset button (component number 28).
	# Check if there is new output from <code>journalctl</code> program.		# Check is there new output from <code>journalctl</code> program.
	# Check if the ~~PBP~~ connected by running <code>rkdeveloptool ld</code>. If successful, the output should be like: <code>DevNo=1 Vid=0x2207,Pid=0x330c,LocationID=1401 Maskrom</code>		# Check is the Pinebook Pro connected by running <code>rkdeveloptool ld</code>. If successful, the output should be like: <code>DevNo=1 Vid=0x2207,Pid=0x330c,LocationID=1401 Maskrom</code>

	=== After entering maskrom mode ===		=== After entering maskrom mode ===

	Now that the ~~PBP~~ is in <code>maskrom mode</code>, you can use <code>rkdeveloptool</code> to write data to the SPI. To do so you'll need the binary file you'll be writing to SPI, which will be referred to as <code>SPI_new.bin</code>, and a helper file named [https://dl.radxa.com/rockpi4/images/loader/spi/rk3399_loader_spinor_v1.15.114.bin rk3399_loader_spinor_v1.15.114.bin].		Now that when the RK3399 SoC is in <code>maskrom mode</code>, you can use <code>rkdeveloptool</code> to write data to the SPI. To do so you'll need the binary file you'll be writing to SPI, which will be referred to as <code>SPI_new.bin</code>, and a helper file named [https://dl.radxa.com/rockpi4/images/loader/spi/rk3399_loader_spinor_v1.15.114.bin rk3399_loader_spinor_v1.15.114.bin].

	# Flash the flash helper db file: <code>rkdeveloptool db rk3399_loader_spinor_v1.15.114.bin</code>. If successful, the output should read <code>Downloading bootloader succeeded</code>.		# Flash the flash helper db file: <code>rkdeveloptool db rk3399_loader_spinor_v1.15.114.bin</code>. If successful, the output should read <code>Downloading bootloader succeeded</code>.