A hardware limit.hojnikb wrote:is it possible to have overvoltage over 8 (eg. over 1.4V) or is this somehow hardcoded limit in hardware ?
A hardware limit.hojnikb wrote:is it possible to have overvoltage over 8 (eg. over 1.4V) or is this somehow hardcoded limit in hardware ?
thanks. I'll try another power supply. Currently I have noname 1A supply, how much amperes you can recommend for overclocking?dom wrote: That would be perfectly explained by a power supply that gives up at that level.
Unfortunately it's not that simple. A lot of cheap chargers may claim 1A or 2A, but the voltage dips when a significant amount of current is drawn.make/install wrote:thanks. I'll try another power supply. Currently I have noname 1A supply, how much amperes you can recommend for overclocking?dom wrote: That would be perfectly explained by a power supply that gives up at that level.
Yes, no need for a scope there...make/install wrote:yep. I made voltage measurement between TP1 and TP2 and it shows me only 4.4V - not enough for successful overclocking
Code: Select all
hdmi_force_hotplug=1
hdmi_mode=32
arm_freq=1050
core_freq=500
sdram_freq=450
over_voltage=6
disable_overscan=0
gpu_mem=150
start_file=start_x.elf
fixup_file=fixup_x.dat
Have you actually gotten your Pi up to 1500 MHz?a9971256 wrote:I get ~700 BMIPS at 1500MHz arm 550MHz GPU and 550 CORE/SDRAM
Yes, and it is very stable under the newest wheezy distro. However, it crashes while booting with berryboot installedwallarug wrote:Have you actually gotten your Pi up to 1500 MHz?a9971256 wrote:I get ~700 BMIPS at 1500MHz arm 550MHz GPU and 550 CORE/SDRAM
I find this incredulous. Either your config.txt entry is being ignored or the device is never being pushed to full load. Or you have a uniquely powerful device.a9971256 wrote:Yes, and it is very stable under the newest wheezy distro. However, it crashes while booting with berryboot installedwallarug wrote:Have you actually gotten your Pi up to 1500 MHz?a9971256 wrote:I get ~700 BMIPS at 1500MHz arm 550MHz GPU and 550 CORE/SDRAM
Runa9971256 wrote:I used raspi-config to set overclock to turbo. Then I started editing arm_freq
btw, how do i post config.txt. .txt isnt allowed
Code: Select all
vcgencmd measure_clock arm
vcgencmd measure_clock is definitive. It runs a counter off the clock for a fixed period of time.XBMCantgetenough wrote: Dom I would love to hear your thoughts on this. Is vcgencmd accurate and can core go past 600. Its funny because with the core being at 700 it was fine but when I went like 720 it woudn't boot so whats happening? And also if I set my core at say 580 then it shows in vcgencmd thats its at 580 and it crashes after a while so then Its correct that setting at 580 is actually higher than setting it at 700 and looking at the framerate its correct I get higher frame rates at 560 than 700. But then what happened with the h264 and vcgencmd
Yes its stable in the sense that I can run it for hours without problem them when after it starts to reboot every half an hour but this leads me to think its the combined effect of heat and also I've heard that reboots are caused by drop in voltage (I'm running charger for nexus 4) And I can tell you its lightning. I'm getting 90 frames per second, it won't go below that. The reason why I get so high Ram is because I've got overvolatge_sdram at 8 (my post said 7, its unstable at that voltage and the its actually 8 that works good) which no one has tried to go that high but it works and I I've ran measure_voltage and get the correct 1.4 volts. But saying that theres no command to check the sdram.hojnikb wrote:thats a massive OC on the ram dude![]()
![]()
Is it stable though ?
Code: Select all
core_freq=550
sdram_freq=550
gpu_freq=550
arm_freq=1400
over_voltage=6
# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
disable_overscan=1
# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16
# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720
# uncomment if hdmi display is not detected and composite is being output
#hdmi_force_hotplug=1
# uncomment to force a specific HDMI mode (this will force VGA)
#hdmi_group=1
#hdmi_mode=1
# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
#hdmi_drive=2
# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=4
# uncomment for composite PAL
#sdtv_mode=2
#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800
# for more options see http://elinux.org/RPi_config.txt
No way! GPU frequencies and Arm run off the overvolatge and to get 550!!GPU and 1400!!Arm from a paltry 6 over volts (1.35 volts). You should be atleast using current_limit_override=0x5A000020. Its either a troll or I'm impressed. Are you running of a USB3?a9971256 wrote:my config.txt
Code: Select all
core_freq=550 sdram_freq=550 gpu_freq=550 arm_freq=1400 over_voltage=6 # uncomment this if your display has a black border of unused pixels visible # and your display can output without overscan disable_overscan=1 # uncomment the following to adjust overscan. Use positive numbers if console # goes off screen, and negative if there is too much border #overscan_left=16 #overscan_right=16 #overscan_top=16 #overscan_bottom=16 # uncomment to force a console size. By default it will be display's size minus # overscan. #framebuffer_width=1280 #framebuffer_height=720 # uncomment if hdmi display is not detected and composite is being output #hdmi_force_hotplug=1 # uncomment to force a specific HDMI mode (this will force VGA) #hdmi_group=1 #hdmi_mode=1 # uncomment to force a HDMI mode rather than DVI. This can make audio work in # DMT (computer monitor) modes #hdmi_drive=2 # uncomment to increase signal to HDMI, if you have interference, blanking, or # no display #config_hdmi_boost=4 # uncomment for composite PAL #sdtv_mode=2 #uncomment to overclock the arm. 700 MHz is the default. #arm_freq=800 # for more options see http://elinux.org/RPi_config.txt
I have to agree with you here. It is almost impossible to get that sort of clock out of the ARM. It would probably burn itself out due to the over-voltage required out before reaching that speed.No way! GPU frequencies and Arm run off the overvolatge and to get 550!!GPU and 1400!!Arm from a paltry 6 over volts (1.35 volts). You should be atleast using current_limit_override=0x5A000020. Its either a troll or I'm impressed. Are you running of a USB3?
I find it amusing some wanting or claiming to get a high over clock with such perfect rounded off numbers as 1400, Why not 1410 or 1395? abit suspicious, because anyone seriously trying to squeeze as much juice out as possible will know to at least go by 5 intervals until you reached the peak before it becomes unstable? Anyone else think the same?