RPiconfig - Revision history

Mikerr: Added camera option

2013-06-16T21:48:44Z

Added camera option

Nudin: /* Overclocking */ sticky bit is not set anymore, als long you don't go higher than 'turbo'

2013-06-04T22:03:47Z

‎Overclocking: sticky bit is not set anymore, als long you don't go higher than 'turbo'

Popcornmix: /* Overclocking options */

2013-05-20T14:14:38Z

‎Overclocking options

Popcornmix: Tidy avoid_pwl_pll description

2013-05-20T14:12:59Z

Tidy avoid_pwl_pll description

Popcornmix: Describe warranty setting options

2013-05-20T14:10:32Z

Describe warranty setting options

Popcornmix: Add description of hdmi_force_edid_3d

2013-05-15T16:36:21Z

Add description of hdmi_force_edid_3d

Mahjongg at 12:04, 5 May 2013

2013-05-05T12:04:12Z

Mahjongg at 12:03, 5 May 2013

2013-05-05T12:03:39Z

RichardNeill: hold shift during boot to disable O/C

2013-04-25T19:49:15Z

hold shift during boot to disable O/C

RichardNeill: /* Overclock stability Test */

2013-04-25T19:39:00Z

‎Overclock stability Test

@@ Line 60: / Line 60: @@
 The following options need to be in cmdline.txt for CMA to work:
    coherent_pool=6M smsc95xx.turbo_mode=N
 =Video=

@@ Line 374: / Line 374: @@
 =Overclocking=
-'''NOTE:''' Setting any of the parameters which overvolt your Raspberry Pi will set a permanent bit within the SOC, making it posibly to detect that you Pi has been overclocked. This was meant to void warranty if the device has been overclocked. Since 19th of September 2012 you can overclock your Pi without affecting your warranty<ref>[http://www.raspberrypi.org/archives/2008 Introducing turbo mode: up to 50% more performance for free]</ref>
+'''NOTE:''' Setting parameters other than that available by 'raspi-config' will set a permanent bit within the SOC, making it posibly to detect that you Pi has been overclocked. This was meant to void warranty if the device has been overclocked. Since 19th of September 2012 you can overclock your Pi without affecting your warranty<ref>[http://www.raspberrypi.org/archives/2008 Introducing turbo mode: up to 50% more performance for free]</ref>
 The latest kernel has a [http://www.pantz.org/software/cpufreq/usingcpufreqonlinux.html cpufreq] kernel driver with the "ondemand" governor enabled by default. It has no effect if you have no overclock settings.

@@ Line 411: / Line 411: @@
 |-
 !align="right"|over_voltage
-| ARM/GPU core voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.025V steps. <ref name=voltages>What this means is that you can specify -16 and get 0.8V as the GPU/core voltage, and specify 8 and get 1.4V. Default is 0 (1.2V). Values above 6 are only allowed when force_turbo or current_limit_override are specified (which set the warranty bit)</ref>
+| ARM/GPU core voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.025V steps. <ref name=voltages>What this means is that you can specify -16 and get 0.8V as the GPU/core voltage, and specify 8 and get 1.4V</ref> Default is 0 (1.2V). Values above 6 are only allowed when force_turbo or current_limit_override are specified (which set the warranty bit)
 |-
 !align="right"|over_voltage_sdram

@@ Line 405: / Line 405: @@
 |-
 !align="right"|avoid_pwm_pll
-| Unlink core_freq from the rest of the gpu. Can cause low quality analog audio, which should be fixed with latest firmware. Default 0
+| Don't dedicate a pll to PWM audio. This will reduce analogue audio quality slightly. The spare PLL allows the core_freq to be set independently from the rest of the gpu allowing more control over overclocking. Default 0
 |-
 !align="right"|sdram_freq

@@ Line 411: / Line 411: @@
 |-
 !align="right"|over_voltage
-| ARM/GPU core voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.025V steps. force_turbo will allow values higher than 6. Default 0 (1.2V) <ref name=voltages>What this means is that you can specify -16 and expect about 0.8V as the GPU/core voltage. This is 0.4V below the normal value of 1.2. If you specify 16, you'd get 0.4V ABOVE the normal value of 1.2V, or 1.6V. The fact that someone carefully specified "8" and "1.4V" as the upper limit in the examples leads me to think that it is likely to shorten the life of your raspberry pi significantly if you would specify values above "8".  So: don't specify values above zero, but if you do, don't go above 8.</ref>
+| ARM/GPU core voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.025V steps. <ref name=voltages>What this means is that you can specify -16 and get 0.8V as the GPU/core voltage, and specify 8 and get 1.4V. Default is 0 (1.2V). Values above 6 are only allowed when force_turbo or current_limit_override are specified (which set the warranty bit)</ref>
 |-
 !align="right"|over_voltage_sdram
@@ Line 426: / Line 426: @@
 |-
 !align="right"|force_turbo
-| Disables dynamic cpufreq driver and minimum settings below. Enables h264/v3d/isp overclock options. Default 0
+| Disables dynamic cpufreq driver and minimum settings below. Enables h264/v3d/isp overclock options. Default 0. May set warranty bit.
 |-
 !align="right"|initial_turbo
@@ Line 447: / Line 447: @@
 |-
 !align="right"| current_limit_override
-| Disables SMPS current limit protection when set to "0x5A000020". Can help if you are currently hitting a reboot failure when overclocking too high. <ref name=current_limit_override>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=29&t=6201&start=325#p170793</ref>
+| Disables SMPS current limit protection when set to "0x5A000020". Can help if you are currently hitting a reboot failure when overclocking too high. May set warrany bit.<ref name=current_limit_override>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=29&t=6201&start=325#p170793</ref>
 |}

@@ Line 88: / Line 88: @@
 '''hdmi_force_edid_audio''' Pretends all audio formats are supported by display, allowing passthrough of DTS/AC3 even when not reported as supported.
    hdmi_force_edid_audio=1
 '''avoid_edid_fuzzy_match''' Avoid fuzzy matching of modes described in edid. Picks the standard mode with matching resolution and closest framerate even if blanking is wrong.

← Older revision		Revision as of 12:04, 5 May 2013
Line 2:		Line 2:

	As the raspberry PI doesn't have a conventional BIOS, the various system configuration parameters that would normally be kept and set using the BIOS are now stored on a text file named "config.txt".		As the raspberry PI doesn't have a conventional BIOS, the various system configuration parameters that would normally be kept and set using the BIOS are now stored on a text file named "config.txt".
		+
	The Raspberry Pi config.txt file is read by the GPU before the ARM core is initialised.		The Raspberry Pi config.txt file is read by the GPU before the ARM core is initialised.

@@ Line 1: / Line 1: @@
 [[Category: RaspberryPi]]
-The Raspberry Pi config.txt file is read by the GPU before the ARM core is initialised.  It can be used to set various system configuration parameters.
+As the raspberry PI doesn't have a conventional BIOS, the various system configuration parameters that would normally be kept and set using the BIOS are now stored on a text file named "config.txt".
-This file is an optional file on the boot partition.  It would normally be accessible as /boot/config.txt from Linux.
+This file is an optional file on the boot partition.  It would normally be accessible as /boot/config.txt from Linux, but from Windows (or OS X) it would be seen as a file in the accessible part of the card.
 To edit the configuration file, see the instructions at [[R-Pi_ConfigurationFile]].

@@ Line 519: / Line 519: @@
 == Overclock stability test ==
 Most overclocking issues show up right away with a failure to boot, but it is possible to get filesystem corruption that arises over time. Here is a script to stress-test the stability of the system, specifically the SD-card. If this script runs to completion, without any errors showing in <code>dmesg</code>, then the Pi is probably stable with these settings.
   #!/bin/bash

← Older revision		Revision as of 19:39, 25 April 2013
Line 516:		Line 516:

	It's generally a good idea to keep the core temp below 70 degrees, and the voltage above 4.8V. (Note that some, not necessarily cheap, USB power supplies fall as low as 4.2V, this is because they are usually designed to charge a 3.7V LiPo battery, rather than to supply a solid 5V to a computer). Also, a heatsink can be helpful, especially if the Pi is to be run inside a case. A suitable heatsink is the self-adhesive BGA (ball-grid-array) 14x14x10 mm heatsink, part 674-4756 from RS Components.		It's generally a good idea to keep the core temp below 70 degrees, and the voltage above 4.8V. (Note that some, not necessarily cheap, USB power supplies fall as low as 4.2V, this is because they are usually designed to charge a 3.7V LiPo battery, rather than to supply a solid 5V to a computer). Also, a heatsink can be helpful, especially if the Pi is to be run inside a case. A suitable heatsink is the self-adhesive BGA (ball-grid-array) 14x14x10 mm heatsink, part 674-4756 from RS Components.
		+
		+	== Overclock stability test ==
		+
		+	Most overclocking issues show up right away with a failure to boot, but it is possible to get filesystem corruption that arises over time. Here is a script to stress-test the stability of the system, specifically the SD-card. If this script runs to completion, without any errors showing in <code>dmesg</code>, then the Pi is probably stable with these settings.
		+
		+	#!/bin/bash
		+	#Simple stress test for system. If it survives this, it's probably stable.
		+	#Free software, GPL2+
		+
		+	echo "Testing overclock stability..."
		+
		+	#Max out the CPU in the background (one core). Heats it up, loads the power-supply.
		+	nice yes >/dev/null &
		+
		+	#Read the entire SD card 10x. Tests RAM and I/O
		+	for i in `seq 1 10`; do echo reading: $i; sudo dd if=/dev/mmcblk0 of=/dev/null bs=4M; done
		+
		+	#Writes 512 MB test file, 10x.
		+	for i in `seq 1 10`; do echo writing: $i; dd if=/dev/zero of=deleteme.dat bs=1M count=512; sync; done
		+
		+	#Clean up
		+	killall yes
		+	rm deleteme.dat
		+
		+	#Print summary. Anything nasty will appear in dmesg.
		+	echo -n "CPU freq: " ; cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
		+	echo -n "CPU temp: " ; cat /sys/class/thermal/thermal_zone0/temp
		+	dmesg \| tail
		+
		+	echo "Not crashed yet, probably stable."

	=References=		=References=