User:Fxc/Draft:PineTab2 SPI - Revision history

Fxc: typo

2023-06-22T20:25:25Z

typo

← Older revision		Revision as of 20:25, 22 June 2023
Line 75:		Line 75:

	* To reflash the SPI with a working bootloader: See section [[#Flashing]]		* To reflash the SPI with a working bootloader: See section [[#Flashing]]
	* To remove the SPI contents: If the path ''/dev/mtd0'' is available in the devfs, overwrite the SPI contents with zeroes. If the path is not available, check if the bypass switch on the UART adapter was still set to ''ON'' after booting the microSD card. If it was not set to ''ON'' then you need to overwrite the SPI from the U-Boot command line		* To remove the SPI contents: If the path ''/dev/mtd0'' is available in the devfs, overwrite the SPI contents with zeroes. If the path is not available, check if the bypass switch on the UART adapter was still set to ''ON'' after booting the microSD card. If it was not set to ''ON'' then you need to overwrite the SPI from the U-Boot command line.

Fxc: /* Recovery */ Added alternative

2023-06-22T17:41:08Z

Recovery: Added alternative

← Older revision		Revision as of 17:41, 22 June 2023
Line 72:		Line 72:
	Then power on the tablet with a flashed microSD card (which includes a bootloader) and '''unplug the debug board or set the switch to the position ''OFF'' again''' when the factory image is started, otherwise the factory image won't find the SPI.		Then power on the tablet with a flashed microSD card (which includes a bootloader) and '''unplug the debug board or set the switch to the position ''OFF'' again''' when the factory image is started, otherwise the factory image won't find the SPI.

	Then remove the SPI contents:		Then reflash a working bootloader or remove the SPI contents:

	* If the path ''/dev/mtd0'' is available in the devfs, overwrite the SPI contents with zeroes		* To reflash the SPI with a working bootloader: See section [[#Flashing]]
	* If the path is not available, check if the bypass switch on the UART adapter was still set to ''ON'' after booting the microSD card. If it was not set to ''ON'' then you need to overwrite the SPI from the U-Boot command line		* To remove the SPI contents: If the path ''/dev/mtd0'' is available in the devfs, overwrite the SPI contents with zeroes. If the path is not available, check if the bypass switch on the UART adapter was still set to ''ON'' after booting the microSD card. If it was not set to ''ON'' then you need to overwrite the SPI from the U-Boot command line

Fxc: /* Recovery */ Clarified instructions

2023-06-22T17:32:09Z

Recovery: Clarified instructions

← Older revision		Revision as of 17:32, 22 June 2023
Line 72:		Line 72:
	Then power on the tablet with a flashed microSD card (which includes a bootloader) and '''unplug the debug board or set the switch to the position ''OFF'' again''' when the factory image is started, otherwise the factory image won't find the SPI.		Then power on the tablet with a flashed microSD card (which includes a bootloader) and '''unplug the debug board or set the switch to the position ''OFF'' again''' when the factory image is started, otherwise the factory image won't find the SPI.

	Then ~~zeroize~~ the SPI ~~likely located under~~ ''/dev/mtd0''~~. If~~ the ~~path of~~ the SPI ~~memory can't be found in~~ the ~~devfs~~, the bypass switch was still set to ''ON'' after booting the microSD card.		Then remove the SPI contents:

			* If the path ''/dev/mtd0'' is available in the devfs, overwrite the SPI contents with zeroes
			* If the path is not available, check if the bypass switch on the UART adapter was still set to ''ON'' after booting the microSD card. If it was not set to ''ON'' then you need to overwrite the SPI from the U-Boot command line

Fxc: /* Recovery */ Typo

2023-06-22T17:28:33Z

Recovery: Typo

← Older revision		Revision as of 17:28, 22 June 2023
Line 72:		Line 72:
	Then power on the tablet with a flashed microSD card (which includes a bootloader) and '''unplug the debug board or set the switch to the position ''OFF'' again''' when the factory image is started, otherwise the factory image won't find the SPI.		Then power on the tablet with a flashed microSD card (which includes a bootloader) and '''unplug the debug board or set the switch to the position ''OFF'' again''' when the factory image is started, otherwise the factory image won't find the SPI.

	~~The zeorize~~ the SPI likely located under ''/dev/mtd0''. If the path of the SPI memory can't be found in the devfs, the bypass switch was still set to ''ON'' after booting the microSD card.		Then zeroize the SPI likely located under ''/dev/mtd0''. If the path of the SPI memory can't be found in the devfs, the bypass switch was still set to ''ON'' after booting the microSD card.

Fxc: /* Flashing */ Fix

2023-06-22T17:27:57Z

Flashing: Fix

← Older revision		Revision as of 17:27, 22 June 2023
Line 57:		Line 57:
	# Verify that the download was complete and successful using the provided checksum of the corresponding release		# Verify that the download was complete and successful using the provided checksum of the corresponding release
	# Flash the SPI using one of the methods:		# Flash the SPI using one of the methods:
	:# NOTE: These commands do not verify if the SPI was flashed successful. The step is done '''AT OWN RISK'''!		## NOTE: These commands do not verify if the SPI was flashed successful. The step is done '''AT OWN RISK'''!
	:# Using the U-Boot command line: for Kwiboo's U-Boot release the instruction for the U-Boot command line can be found under https://github.com/Kwiboo/u-boot-build#spi-flash		## Using the U-Boot command line: for Kwiboo's U-Boot release the instruction for the U-Boot command line can be found under https://github.com/Kwiboo/u-boot-build#spi-flash
	:# Using flashcp: run the command <code>flashcp -v -p u-boot-rockchip-spi.bin /dev/mtd0</code>, with ''u-boot-rockchip-spi.bin'' being an example for a U-Boot release. It has to be stored in the directory you're running the command in. If the path in the devfs is not found, the SPI bypass switch on the UART adapter is either enabled or the SPI is protected from being overwritten in the operating system.		## Using flashcp: run the command <code>flashcp -v -p u-boot-rockchip-spi.bin /dev/mtd0</code>, with ''u-boot-rockchip-spi.bin'' being an example for a U-Boot release. It has to be stored in the directory you're running the command in. If the path in the devfs is not found, the SPI bypass switch on the UART adapter is either enabled or the SPI is protected from being overwritten in the operating system.
	# Wait for the command to successfully flash your SPI		# Wait for the command to successfully flash your SPI

Fxc: /* Flashing */ Fix

2023-06-22T17:27:16Z

Flashing: Fix

← Older revision		Revision as of 17:27, 22 June 2023
Line 57:		Line 57:
	# Verify that the download was complete and successful using the provided checksum of the corresponding release		# Verify that the download was complete and successful using the provided checksum of the corresponding release
	# Flash the SPI using one of the methods:		# Flash the SPI using one of the methods:
	#: NOTE: These commands do not verify if the SPI was flashed successful. The step is done '''AT OWN RISK'''!		:# NOTE: These commands do not verify if the SPI was flashed successful. The step is done '''AT OWN RISK'''!
	#: Using the U-Boot command line: for Kwiboo's U-Boot release the instruction for the U-Boot command line can be found under https://github.com/Kwiboo/u-boot-build#spi-flash		:# Using the U-Boot command line: for Kwiboo's U-Boot release the instruction for the U-Boot command line can be found under https://github.com/Kwiboo/u-boot-build#spi-flash
	#: Using flashcp: run the command <code>flashcp -v -p u-boot-rockchip-spi.bin /dev/mtd0</code>, with ''u-boot-rockchip-spi.bin'' being an example for a U-Boot release. It has to be stored in the directory you're running the command in. If the path in the devfs is not found, the SPI bypass switch on the UART adapter is either enabled or the SPI is protected from being overwritten in the operating system.		:# Using flashcp: run the command <code>flashcp -v -p u-boot-rockchip-spi.bin /dev/mtd0</code>, with ''u-boot-rockchip-spi.bin'' being an example for a U-Boot release. It has to be stored in the directory you're running the command in. If the path in the devfs is not found, the SPI bypass switch on the UART adapter is either enabled or the SPI is protected from being overwritten in the operating system.
	# Wait for the command to successfully flash your SPI		# Wait for the command to successfully flash your SPI

Fxc: /* Flashing */ Explanation added

2023-06-22T17:26:51Z

Flashing: Explanation added

← Older revision		Revision as of 17:26, 22 June 2023
Line 56:		Line 56:
	# Download a listed release. Verify multiple times that the correct file is downloaded and that it is compatible with your device. Other devices might have a similar name or the filename might be similar to incompatible files.		# Download a listed release. Verify multiple times that the correct file is downloaded and that it is compatible with your device. Other devices might have a similar name or the filename might be similar to incompatible files.
	# Verify that the download was complete and successful using the provided checksum of the corresponding release		# Verify that the download was complete and successful using the provided checksum of the corresponding release
	# ~~Understand and then~~ run the command <code>flashcp -v -p u-boot-rockchip-spi.bin /dev/mtd0</code>, with ''u-boot-rockchip-spi.bin'' being an example for a U-Boot release. It has to be stored in the directory you're running the command in. ~~NOTE: This command does~~ not ~~verify if~~ the SPI ~~was flashed successful~~. ~~The step is done '''AT OWN RISK'''!~~		# Flash the SPI using one of the methods:
			#: NOTE: These commands do not verify if the SPI was flashed successful. The step is done '''AT OWN RISK'''!
			#: Using the U-Boot command line: for Kwiboo's U-Boot release the instruction for the U-Boot command line can be found under https://github.com/Kwiboo/u-boot-build#spi-flash
			#: Using flashcp: run the command <code>flashcp -v -p u-boot-rockchip-spi.bin /dev/mtd0</code>, with ''u-boot-rockchip-spi.bin'' being an example for a U-Boot release. It has to be stored in the directory you're running the command in. If the path in the devfs is not found, the SPI bypass switch on the UART adapter is either enabled or the SPI is protected from being overwritten in the operating system.
	# Wait for the command to successfully flash your SPI		# Wait for the command to successfully flash your SPI

Fxc: /* Flashing */ Typo

2023-06-22T16:56:28Z

Flashing: Typo

← Older revision		Revision as of 16:56, 22 June 2023
Line 56:		Line 56:
	# Download a listed release. Verify multiple times that the correct file is downloaded and that it is compatible with your device. Other devices might have a similar name or the filename might be similar to incompatible files.		# Download a listed release. Verify multiple times that the correct file is downloaded and that it is compatible with your device. Other devices might have a similar name or the filename might be similar to incompatible files.
	# Verify that the download was complete and successful using the provided checksum of the corresponding release		# Verify that the download was complete and successful using the provided checksum of the corresponding release
	# Understand and then run the command <code>flashcp -v -p u-boot-rockchip-spi.bin /dev/mtd0</code>, with ''u-boot-rockchip-spi.bin'' being an example for a U-Boot release. It has to be stored in the directory you're running the command in. NOTE: This command does not verify if the SPI was flashed successful. The step is ~~down~~ '''AT OWN RISK'''!		# Understand and then run the command <code>flashcp -v -p u-boot-rockchip-spi.bin /dev/mtd0</code>, with ''u-boot-rockchip-spi.bin'' being an example for a U-Boot release. It has to be stored in the directory you're running the command in. NOTE: This command does not verify if the SPI was flashed successful. The step is done '''AT OWN RISK'''!
	# Wait for the command to successfully flash your SPI		# Wait for the command to successfully flash your SPI

Fxc: /* Getting started */ Correction

2023-06-22T16:47:42Z

Getting started: Correction

← Older revision		Revision as of 16:47, 22 June 2023
Line 10:		Line 10:
	The PineTab2 includes an SPI flash memory. An SPI flash memory is a non-volatile memory that uses Serial Peripheral Interface (SPI) protocol for communication. The memory can be used to store a bootloader on it. This is an important hardware functionality, because it can be used to modify the boot order (see the section [[#Boot order]]) and to store the bootloader away and independent from any operating system (on the SPI flash memory as dedicated memory, instead on the same disk like the operating system).		The PineTab2 includes an SPI flash memory. An SPI flash memory is a non-volatile memory that uses Serial Peripheral Interface (SPI) protocol for communication. The memory can be used to store a bootloader on it. This is an important hardware functionality, because it can be used to modify the boot order (see the section [[#Boot order]]) and to store the bootloader away and independent from any operating system (on the SPI flash memory as dedicated memory, instead on the same disk like the operating system).

	The SPI on the ~~currently shipped~~ PineTab2 batch is ~~shipped~~ and will ~~likely~~ contain a bootloader in future batches to simplify the booting procedure for users ~~in the future~~.		The SPI on the current PineTab2 batch is empty and will probably contain a bootloader in future batches to simplify the booting procedure for new users.

	== Boot order ==		== Boot order ==

Fxc: /* Boot order */ Fixed list style

2023-06-22T16:45:51Z

Boot order: Fixed list style

← Older revision		Revision as of 16:45, 22 June 2023
Line 16:		Line 16:
	The RK3566 SoC searches for the U-Boot SPL in a fixed order:		The RK3566 SoC searches for the U-Boot SPL in a fixed order:

	* SPI flash memory		# SPI flash memory
	* eMMC		# eMMC
	* MicroSD card		# MicroSD card

	The subsequent boot order in the U-Boot SPL can then be changed in software. Example: There is the U-Boot bootloader installed on the eMMC (the internal memory of the PineTab2), which tries to boot from a microSD card if it finds a bootable medium and it will otherwise load the installation from the eMMC. Another example: There is the U-Boot bootloader installed to the eMMC, which tries to first boot from microSD card and then from the eMMC.		The subsequent boot order in the U-Boot SPL can then be changed in software. Example: There is the U-Boot bootloader installed on the eMMC (the internal memory of the PineTab2), which tries to boot from a microSD card if it finds a bootable medium and it will otherwise load the installation from the eMMC. Another example: There is the U-Boot bootloader installed to the eMMC, which tries to first boot from microSD card and then from the eMMC.