bryanandaimee
Posts: 31
Joined: Fri Sep 14, 2012 4:32 pm

Re: Determining how fast your Pi really is

Fri Aug 15, 2014 8:59 pm

My guess would be that if you set overvolt to 8 (highest setting) you would be able to get to 1200 or 1250 stable. That is a very fast Pi.

Preliminary tests on one of my 2 new Pi B+ gives
3.024 MHz ring osc. at 1.20 V and 975 max stable overclock at that voltage.

I would have taken it to 1.4V but it has a bent USB housing and I didn't want to set the warranty bit on a Pi I'm sending back.

The other B+ is slower but I'll do a full work up on that one even though it won't be as exciting.

Bryan

User avatar
algorithm
Posts: 186
Joined: Mon Nov 25, 2013 9:09 pm
Location: Flatland

Re: Determining how fast your Pi really is

Wed Feb 04, 2015 7:08 pm

New Pi 2! Oscillator value with standard settings, no overclocking or overvoltage: read_ring_osc(2)=2.820MHz (@1.2000V). Overclocking now set to "Pi2" via raspi-config, runs stable. Settings are

Code: Select all

arm_freq=1000
core_freq=500
sdram_freq=500
over_voltage=2
Output is now: read_ring_osc(2)=2.818MHz (@1.2000V). Should the voltage (and frequency) not have been increased by the over_voltage=2 setting?

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5461
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: Determining how fast your Pi really is

Wed Feb 04, 2015 11:00 pm

algorithm wrote:New Pi 2! Oscillator value with standard settings, no overclocking or overvoltage: read_ring_osc(2)=2.820MHz (@1.2000V). Overclocking now set to "Pi2" via raspi-config, runs stable. Settings are

Code: Select all

arm_freq=1000
core_freq=500
sdram_freq=500
over_voltage=2
Output is now: read_ring_osc(2)=2.818MHz (@1.2000V). Should the voltage (and frequency) not have been increased by the over_voltage=2 setting?
Only when busy. When idle you get 1.2V an 600MHz.

PuppetHoundZ
Posts: 170
Joined: Wed Jan 21, 2015 2:57 am

Re: Determining how fast your Pi really is

Thu Feb 05, 2015 12:47 am

I will try this on my B+ before I decide to overclock. Thanks, I didn't know this was available. I would have tried this months ago. I may post my findings later :D on this same post.

Update (default clock):

Code: Select all

read_ring_osc(2)=3.098MHz (@1.2000V)
(this is the median average I get after doing the command like 30+ times to be sure)

I guess I can use turbo mode huh? :lol:

Update 2: I'm using turbo mode with Epiphany using a video from a website I like. It plays 720p in windowed mode and uses on average 93-100 percent of CPU useage! woe! I finally can watch videos really smoothly! :shock: :geek: :ugeek: 8-)

Temperature is exactly 53.0'C (hope that's not bad)

Update 3:
Also I'll update with my post ring results :D I forgot as I was excited that turbo mode worked :geek:

Update 4:
Here are my Results with Raspberry pi running Prboom and also trying out Epiphany watching video with Raspi-config Turbo mode preset, on average it was:

Code: Select all

read_ring_osc(2)=3.722MHz (@1.3500V)
Hope this helps with you're benchmarking program you're working on :geek:

Update 5:
Since using RecalBox has voided my warranty on the Pi I'm proud to say that the following over clock settings work great:

Code: Select all

arm_freq=1100
core_freq=550
sdram_freq=600
over_voltage=8
over_voltage_sdram=6

vcgencmd read_ring_osc
read_ring_osc(2)=3.697MHz (@1.3500V)
Keep in mind this is based on Raspbian. When I'm in RecalBox it has force Turbo. I don't want to do that unless I have to even though my warranty is void. :cry: :geek: :ugeek:
Last edited by PuppetHoundZ on Sun Feb 15, 2015 6:59 am, edited 5 times in total.

ktb
Posts: 1447
Joined: Fri Dec 26, 2014 7:53 pm

Re: Determining how fast your Pi really is

Thu Feb 05, 2015 2:09 am

I'm not sure if this is my highest stable overclock, but it seems fairly stable. I built Qt 5.4 on the B+ using this config:

Code: Select all

arm_freq=1200
core_freq=525
gpu_freq=525
h264_freq=525
isp_freq=525
v3d_freq=525
sdram_freq=525

over_voltage=11
over_voltage_min=7
over_voltage_sdram=8
over_voltage_sdram_c=0
over_voltage_sdram_i=0
over_voltage_sdram_p=0

disable_l2cache=0
force_turbo=1
temp_limit=83
#avoid_pwm_pll=1
current_limit_override=0x5A000020

gpu_mem=128
With the above setttings:
read_ring_osc(2)=3.791MHz (@1.4000V)

If I comment out all of those settings, I get:
read_ring_osc(2)=2.926MHz (@1.2000V)

As others have noted, the value varies from sample to sample. Taking 10 samples, the range was 2.926MHz - 2.933MHz.

I'll post some Pi2B results once I have it running for a bit.

So, some samples with the Pi2B:
read_ring_osc(2)=2.841MHz (@1.2000V)
read_ring_osc(2)=2.846MHz (@1.2000V)
read_ring_osc(2)=2.849MHz (@1.2000V)

and then overclocked:
read_ring_osc(2)=3.655MHz (@1.3940V)
read_ring_osc(2)=3.660MHz (@1.3940V)
read_ring_osc(2)=3.666MHz (@1.3940V)
read_ring_osc(2)=3.670MHz (@1.3940V)

read_ring_osc(0)=2.845MHz (@1.2000V)
read_ring_osc(1)=22.267MHz (@1.3940V)
read_ring_osc(2)=3.658MHz (@1.3940V)

Code: Select all

arm_freq=1100
core_freq=500
gpu_freq=500
sdram_freq=500
over_voltage=7
over_voltage_sdram=7
#disable_l2cache=0
force_turbo=1
temp_limit=83
#avoid_pwm_pll=1
current_limit_override=0x5A000020
gpu_mem=128
Image

gregeric
Posts: 1509
Joined: Mon Nov 28, 2011 10:08 am

Re: Determining how fast your Pi really is

Thu Feb 05, 2015 5:10 pm

New Pi 2B.
read_ring_osc(2)=3.028MHz (@1.2000V)
muhahahaha

Handles the Pi2 1GHz overclock fine.

Up'd the overvolt to 6, clock to 1100MHz, mostly OK, but on stressing the GPU with penguinspuzzle I lose the keyboard after a handful of keypresses.

ARM is still up, penguin still alive, & no voltage droop warning rainbow square. I can ssh in & killall penguinpuzzle, and the keyboard is OK again.

Power is from Lapdock's USB port, will try other.

Edit: I should add that this is with a build of penguinspuzzle fixed for the Motorola Lapdock's enumeration of a phantom keyboard (likely an IR receiver that was never implemented in the final hardware). Peter Derivaz accepted my pull request for this a few months back, but the version bundled with Raspbian is pre-fix.

User avatar
jackjt8
Posts: 31
Joined: Wed Oct 17, 2012 5:16 pm

Re: Determining how fast your Pi really is

Thu Feb 26, 2015 10:51 pm

Code: Select all

$ vcgencmd read_ring_osc
read_ring_osc(2)=4.895MHz (@1.20V)
(Technically it's @1.80V) 
Before applying the voltmod I was able to run Turbo without any trouble. But since the voltmod I can't even do that.. I've checked my soldering and I'm not seeing any possible shorts. I keep getting SD-card corruption which is stopping me from being able to do anything. I've tried two different SD-cards with the same results.

Would setting core_freq & sdram_freq to lower values reduce chances of SD-card corruption?
Beep Boop

RobHenry
Posts: 452
Joined: Fri Sep 21, 2012 9:04 pm
Location: UK

Re: Determining how fast your Pi really is

Fri Feb 27, 2015 1:32 am

jackjt8 wrote:

Code: Select all

$ vcgencmd read_ring_osc
read_ring_osc(2)=4.895MHz (@1.20V)
(Technically it's @1.80V) 
Before applying the voltmod I was able to run Turbo without any trouble. But since the voltmod I can't even do that.. I've checked my soldering and I'm not seeing any possible shorts. I keep getting SD-card corruption which is stopping me from being able to do anything. I've tried two different SD-cards with the same results.

Would setting core_freq & sdram_freq to lower values reduce chances of SD-card corruption?
You may have discovered why people caution that the volt mod is not without risk. Remove all OC options from config.txt and if you still get corruption then you'll need a replacement device.

User avatar
jackjt8
Posts: 31
Joined: Wed Oct 17, 2012 5:16 pm

Re: Determining how fast your Pi really is

Fri Feb 27, 2015 10:58 am

RobHenry wrote: You may have discovered why people caution that the volt mod is not without risk. Remove all OC options from config.txt and if you still get corruption then you'll need a replacement device.
The SD-card(s) are corrupted. Sure once or twice windows could repair the boot sector, but most of the time not even that can be done and a reflash is needed. From what I can tell, It's 'stable' without OC. But for how long is another question. Might need to do some tweaking to see If I can't get it stable.

It's an easy fix either way. The Pi is fine without inductor L5. It's just the extra voltage which seems to be the issue. Fixing it should be as simple as removing the wire I've added.
Beep Boop

User avatar
ric96
Posts: 1253
Joined: Sun Mar 17, 2013 6:03 am
Location: NOIDA, India
Contact: Website

Re: Determining how fast your Pi really is

Tue Dec 01, 2015 7:53 pm

Interesting thread so i apparently have 3 pi2s and here are the output at no overclock:

1) read_ring_osc(2)=3.460MHz (@1.3125V)
2)read_ring_osc(2)=3.042MHz (@1.2000V)
3) read_ring_osc(2)=2.774MHz (@1.2000V)

PS: i have no idea whats with the voltage on the 1st one
My apologies for shameless YouTube Plugs...
youtube.com/sahajsarup
twitter @sahajsarup
skype srics1996
e-mail: [email protected]
Blog: http://www.geektillithertz.com/wordpress
Web: http://www.geektillithertz.com

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5461
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: Determining how fast your Pi really is

Tue Dec 01, 2015 8:10 pm

ric96 wrote: PS: i have no idea whats with the voltage on the 1st one
You are in turbo mode (arm_freq=900) in the first result. Try reading when the Pi has been idle for a while and you should get 1.2V and a lower ring osc value.

hippy
Posts: 7127
Joined: Fri Sep 09, 2011 10:34 pm
Location: UK

Re: Determining how fast your Pi really is

Tue Dec 01, 2015 8:11 pm

Thanks for the bump as I am having problems applying Pi Zero settings to my B+ and wasn't aware of this command. My results -

read_ring_osc(2)=2.889MHz (@1.2000V)
read_ring_osc(2)=3.082MHz (@1.2500V) # over_voltage=2

Has been stable and reliable at 900MHz, raspi-config "Medium" over-clocking, but crashes with Pi Zero settings.

User avatar
ric96
Posts: 1253
Joined: Sun Mar 17, 2013 6:03 am
Location: NOIDA, India
Contact: Website

Re: Determining how fast your Pi really is

Tue Dec 01, 2015 8:14 pm

dom wrote:
ric96 wrote: PS: i have no idea whats with the voltage on the 1st one
You are in turbo mode (arm_freq=900) in the first result. Try reading when the Pi has been idle for a while and you should get 1.2V and a lower ring osc value.
thnx, here is the updated value
read_ring_osc(2)=2.982MHz (@1.2000V)
looks like i might have gotten pretty good bin :D .
My apologies for shameless YouTube Plugs...
youtube.com/sahajsarup
twitter @sahajsarup
skype srics1996
e-mail: [email protected]
Blog: http://www.geektillithertz.com/wordpress
Web: http://www.geektillithertz.com

Return to “Advanced users”