Quartz64 Model A Using a battery - Revision history

Rotdrop at 08:48, 23 October 2024

2024-10-23T08:48:01Z

← Older revision		Revision as of 08:48, 23 October 2024
Line 33:		Line 33:

	'''TODO:''' Get one of these and document how to use them		'''TODO:''' Get one of these and document how to use them

			'''TODO''' Could please one of the Pine64 staff clarify the following points:
			* has that case a battery protection circuit (probably)`?
			* what are the paremeters of the NTC resistor in the battery pack? Without those parameters it is impossible to translate the sensor readings into an actual temperature.
			* What is its nominal resistance at the pivot temperature point (e.g. 10kOhm at 20 degrees Celsius or whatever)?
			* What is its B-constant?


	== Using the battery ==		== Using the battery ==

Rotdrop: /* Device Tree Additions */

2024-10-10T14:11:54Z

Device Tree Additions

← Older revision		Revision as of 14:11, 10 October 2024
Line 211:		Line 211:
	====== Device Tree Additions ======		====== Device Tree Additions ======

	Save the DTB-overlay snippet above to a file, e.g. "battery.dts" and then use		Save the [[#Device-Tree Overlay\|DTB-overlay snippet mentioned above]] to a file, e.g. "battery.dts" and then use
	<~~pre~~>		<syntaxhighlight lang="bash" line copy>
	sudo /usr/sbin/armbian-add-overlay battery.dts		sudo /usr/sbin/armbian-add-overlay battery.dts
	</~~pre~~>		</syntaxhighlight>
	in order to compile and add the overlay to "/boot/armbianEnv.txt".		in order to compile and add the overlay to "/boot/armbianEnv.txt".

Rotdrop at 14:09, 10 October 2024

2024-10-10T14:09:07Z

← Older revision		Revision as of 14:09, 10 October 2024
Line 97:		Line 97:
	==== Device-Tree Overlay ====		==== Device-Tree Overlay ====

	On some Linux distributions it may be possible to add the device-tree additions via an overlay, example given for the Renata 2800 mAh battery mentioned above:		On some Linux distributions it may be possible to add the device-tree additions via an overlay, example given for the Renata 2800 mAh battery mentioned above ([[#Device Tree Additions\|see here for Armbian on how to install the overlay]]):

	<pre>		<pre>
Line 187:		Line 187:
	===== Using the patched Device Driver =====		===== Using the patched Device Driver =====

	After applying the patch, reconfiguring the kernel to use the PCIe driver as a module and recompiling and installing the kernel one is almost done. Of course, in order to do this you have to know how to apply patches to source code and how to recompile the kernel. It is beyond the scope of this Wiki page to elaborate on this.		After applying the patch, reconfiguring the kernel to use the PCIe driver as a module and recompiling and installing the kernel one is almost done. Of course, in order to do this you have to know how to apply patches to source code and how to recompile the kernel. It is beyond the scope of this Wiki page to elaborate on this, however, below are some [[#Patching the Kernel\|notes for Armbian]] on this topic.

	Disengaging the PCIe slot prior to power cycling:		Disengaging the PCIe slot prior to power cycling:

Rotdrop: /* Using the pachted Device Driver */

2024-10-10T14:02:41Z

Using the pachted Device Driver

← Older revision		Revision as of 14:02, 10 October 2024
Line 185:		Line 185:
	(sorry for wrapping it into a tar archive, but '''.patch''' files are not allowed by this MediaWiki instance)		(sorry for wrapping it into a tar archive, but '''.patch''' files are not allowed by this MediaWiki instance)

	===== Using the ~~pachted~~ Device Driver =====		===== Using the patched Device Driver =====

	After applying the patch, reconfiguring the kernel to use the PCIe driver as a module and recompiling and installing the kernel one is almost done. Of course, in order to do this you have to know how to apply patches to source code and how to recompile the kernel. It is beyond the scope of this Wiki page to elaborate on this.		After applying the patch, reconfiguring the kernel to use the PCIe driver as a module and recompiling and installing the kernel one is almost done. Of course, in order to do this you have to know how to apply patches to source code and how to recompile the kernel. It is beyond the scope of this Wiki page to elaborate on this.

Rotdrop: /* Recovering the PCIe-Slot after Power Cycling */

2024-10-10T14:02:26Z

Recovering the PCIe-Slot after Power Cycling

← Older revision		Revision as of 14:02, 10 October 2024
Line 184:		Line 184:

	(sorry for wrapping it into a tar archive, but '''.patch''' files are not allowed by this MediaWiki instance)		(sorry for wrapping it into a tar archive, but '''.patch''' files are not allowed by this MediaWiki instance)

	~~Of course, in order to use that you have to know how to apply patches to source code and how to recompile the kernel. It is beyond the scope of this Wiki page to elaborate on this.~~

	===== Using the pachted Device Driver =====		===== Using the pachted Device Driver =====

	After applying the patch, reconfiguring the kernel to use the PCIe driver as a module and recompiling and installing the kernel one is almost done.		After applying the patch, reconfiguring the kernel to use the PCIe driver as a module and recompiling and installing the kernel one is almost done. Of course, in order to do this you have to know how to apply patches to source code and how to recompile the kernel. It is beyond the scope of this Wiki page to elaborate on this.

	Disengaging the PCIe slot prior to power cycling:		Disengaging the PCIe slot prior to power cycling:

Rotdrop: /* Kernel Patch */

2024-10-10T14:01:35Z

Kernel Patch

← Older revision		Revision as of 14:01, 10 October 2024
Line 183:		Line 183:
	[[Media:Kernel-rockchip64-pcie-dwc-module.tar]]		[[Media:Kernel-rockchip64-pcie-dwc-module.tar]]

	(sorry for wrapping it into a tar archive, but '''.patch''' files are not allowed)		(sorry for wrapping it into a tar archive, but '''.patch''' files are not allowed by this MediaWiki instance)

	Of course, in order to use that you have to know how to apply patches to source code and how to recompile the kernel. It is beyond the scope of this Wiki page to elaborate on this.		Of course, in order to use that you have to know how to apply patches to source code and how to recompile the kernel. It is beyond the scope of this Wiki page to elaborate on this.

Rotdrop: /* Basic Idea */

2024-10-10T14:00:58Z

Basic Idea

← Older revision		Revision as of 14:00, 10 October 2024
Line 175:		Line 175:
	===== Basic Idea =====		===== Basic Idea =====

	However, some device drivers in Linux can be compiled as loadable modules which can be removed and reloaded again. The hope was that the device driver for the DW PCIe-controller does some reinitialization during the boot sequence which it does not when ~~the~~ a mere "rescan" request is issued. If the device driver existed as loadable module then removing the driver and reloading it should in some sense simulate the boot initialization.		However, some device drivers in Linux can be compiled as loadable modules which can be removed and reloaded again. The hope was that the device driver for the DW PCIe-controller does some reinitialization during the boot sequence which it does not when a mere "rescan" request is issued. If the device driver existed as loadable module then removing the driver and reloading it should in some sense simulate the boot initialization.

	===== Kernel Patch =====		===== Kernel Patch =====

Rotdrop: /* Recovering the PCIe-Slot after Power Cycling */

2024-10-10T14:00:19Z

Recovering the PCIe-Slot after Power Cycling

← Older revision		Revision as of 14:00, 10 October 2024
Line 159:		Line 159:
	As mentioned above the PCIe-slot is no longer powered when running on battery. The question is then: how to recover the PCIe-controller after power cycling such that a plugged in extension card (e.g. a SATA controller of whatever) is operational again. One use case is kind of a low-power mode, a NAS system with a decent number of hard-disks may consume about 40W-50W even when idle, while the Quartz64 running from battery consumes less than 2W (when idle).		As mentioned above the PCIe-slot is no longer powered when running on battery. The question is then: how to recover the PCIe-controller after power cycling such that a plugged in extension card (e.g. a SATA controller of whatever) is operational again. One use case is kind of a low-power mode, a NAS system with a decent number of hard-disks may consume about 40W-50W even when idle, while the Quartz64 running from battery consumes less than 2W (when idle).

			===== Soft Reset and Rescan (not working) =====
	Unfortunately, the following does not work:		Unfortunately, the following does not work:
	<syntaxhighlight lang="Bash" line copy>		<syntaxhighlight lang="Bash" line copy>
Line 170:		Line 171:
	echo 1 > /sys/bus/pci/devices/0000:00:00.0/rescan		echo 1 > /sys/bus/pci/devices/0000:00:00.0/rescan
	</syntaxhighlight>		</syntaxhighlight>
	does not change improve the situation.		does not change improve the situation. Without power cycle the above mentioned lines actually do work.

			===== Basic Idea =====

	However, some device drivers in Linux can be compiled as loadable modules which can be removed and reloaded again. The hope was that the device driver for the DW PCIe-controller does some reinitialization during the boot sequence which it does not when the a mere "rescan" request is issued. If the device driver existed as loadable module then removing the driver and reloading it should in some sense simulate the boot initialization.		However, some device drivers in Linux can be compiled as loadable modules which can be removed and reloaded again. The hope was that the device driver for the DW PCIe-controller does some reinitialization during the boot sequence which it does not when the a mere "rescan" request is issued. If the device driver existed as loadable module then removing the driver and reloading it should in some sense simulate the boot initialization.

			===== Kernel Patch =====

	Unfortunately, the device driver '''drivers/pci/controller/dwc/pcie-dw-rockchip.c''' has not been designed as loadable module (as of Linux 6.11.3), but the necessary changes are only few. The following source-code patch will add the loadable module feature:		Unfortunately, the device driver '''drivers/pci/controller/dwc/pcie-dw-rockchip.c''' has not been designed as loadable module (as of Linux 6.11.3), but the necessary changes are only few. The following source-code patch will add the loadable module feature:
Line 181:		Line 186:

	Of course, in order to use that you have to know how to apply patches to source code and how to recompile the kernel. It is beyond the scope of this Wiki page to elaborate on this.		Of course, in order to use that you have to know how to apply patches to source code and how to recompile the kernel. It is beyond the scope of this Wiki page to elaborate on this.

			===== Using the pachted Device Driver =====

	After applying the patch, reconfiguring the kernel to use the PCIe driver as a module and recompiling and installing the kernel one is almost done.		After applying the patch, reconfiguring the kernel to use the PCIe driver as a module and recompiling and installing the kernel one is almost done.

Rotdrop: /* Specific Linux Distributions */

2024-10-10T13:57:03Z

Specific Linux Distributions

@@ Line 203: / Line 203: @@
 ===== Armbian =====
 Save the DTB-overlay snippet above to a file, e.g. "battery.dts" and then use
@@ Line 209: / Line 211: @@
 </pre>
 in order to compile and add the overlay to "/boot/armbianEnv.txt".
 [[Category:Quartz64]]

Rotdrop: /* Software */

2024-10-10T13:37:37Z

Software

← Older revision		Revision as of 13:37, 10 October 2024
Line 154:		Line 154:

	* up to kernel version 6.11.2 the value of the temperature sensor is not exposed by the device driver		* up to kernel version 6.11.2 the value of the temperature sensor is not exposed by the device driver

			==== Recovering the PCIe-Slot after Power Cycling ====

			As mentioned above the PCIe-slot is no longer powered when running on battery. The question is then: how to recover the PCIe-controller after power cycling such that a plugged in extension card (e.g. a SATA controller of whatever) is operational again. One use case is kind of a low-power mode, a NAS system with a decent number of hard-disks may consume about 40W-50W even when idle, while the Quartz64 running from battery consumes less than 2W (when idle).

			Unfortunately, the following does not work:
			<syntaxhighlight lang="Bash" line copy>
			echo 1 > /sys/bus/pci/devices/0000:00:00.0/remove
			# turn power off, wait, turn power on
			sleep 5 # or whatever periode
			echo 1 > /sys/bus/pci/rescan
			</syntaxhighlight>
			The PCIe-slot is then "back again" but not quite. The attached extension card is not reinitialized, and also an additional
			<syntaxhighlight lang="Bash" line copy>
			echo 1 > /sys/bus/pci/devices/0000:00:00.0/rescan
			</syntaxhighlight>
			does not change improve the situation.

			However, some device drivers in Linux can be compiled as loadable modules which can be removed and reloaded again. The hope was that the device driver for the DW PCIe-controller does some reinitialization during the boot sequence which it does not when the a mere "rescan" request is issued. If the device driver existed as loadable module then removing the driver and reloading it should in some sense simulate the boot initialization.

			Unfortunately, the device driver '''drivers/pci/controller/dwc/pcie-dw-rockchip.c''' has not been designed as loadable module (as of Linux 6.11.3), but the necessary changes are only few. The following source-code patch will add the loadable module feature:

			[[Media:Kernel-rockchip64-pcie-dwc-module.tar]]

			(sorry for wrapping it into a tar archive, but '''.patch''' files are not allowed)

			Of course, in order to use that you have to know how to apply patches to source code and how to recompile the kernel. It is beyond the scope of this Wiki page to elaborate on this.

			After applying the patch, reconfiguring the kernel to use the PCIe driver as a module and recompiling and installing the kernel one is almost done.

			Disengaging the PCIe slot prior to power cycling:
			<syntaxhighlight lang="Bash" line copy>
			# turn off anything using the PCIe extension card, unmount drives etc. then:
			echo 1 > /sys/bus/pci/devices/0000:00:00.0/remove
			rmmod pcie_dw_rockchip
			</syntaxhighlight>

			Then switch off the 12V main power supply. The PCIe slot will then remain unpowered as mentioned above. In order to recover the PCIe slot and an attached extension card one has -- of course -- to switch on the main power supply and can then proceed as follows:

			<syntaxhighlight lang="Bash" line copy>
			# wait some seconds after reattaching the main power supply
			modprobe pcie_dw_rockchip
			</syntaxhighlight>

			Afterwards there chances that the PCIe bus has been reinitialized and works as before.

	==== Specific Linux Distributions ====		==== Specific Linux Distributions ====