How to "manually edit" the overclock on RPi Zero

[dh04000]

I don't want to use the options in the menu (those settings are targeted to the original pi, not the zero) to overclock my RPi Zero, but instead want to test its temperatures while running at its "factory clocks" vs a couple of overclocks. I know I have to edit the config.txt, and I know how to edit it, but I don't know if that override the menu setting, or what to put in to make it "factory" again.

I'm just a bit confused, does anyone have experience doing this? Thanks.

[Substring]

@dh04000 why don't you simply edit /boot/config.txt and comment clocks/voltages ? This would just set it to default values. Remember to mount -o remount, rw /boot before

[rockaddicted]

In Emulationstation once on none overclock settings, /boot/config.txt file is stock, no overclock settings inside.
Anyways, I don't really think rpi zero is overclockable. It is a rpi1 soc, overclocked in factory.
So rpi0 = rpi1 overclocked in extreme mod.

[dh04000]

@rockaddicted said in How to "manually edit" the overclock on RPi Zero:

In Emulationstation once on none overclock settings, /boot/config.txt file is stock, no overclock settings inside.
Anyways, I don't really think rpi zero is overclockable. It is a rpi1 soc, overclocked in factory.
So rpi0 = rpi1 overclocked in extreme mod.

Does the NONE setting in ES set the RPi Zero to 700 MHz (+ RPi1 ram and gpu settings) or its factory 1000 MHz?

[rockaddicted]

As I said none = stock config.txt file, so the stock rpi frequency you are using.

[dh04000]

@rockaddicted Ok, thank you, so stock speeds is NONE. If i want to test other settings then, I need to manually edit the config.txt for overclock. Can I just do it all in the config.txt, using hashes?

So, the config would look it this.

#Stock Config
arm_freq=1000
gpu_freq=300
core_freq=400
sdram_freq=450

#Overclock Config
arm_freq=1000
gpu_freq=500
core_freq=500
sdram_freq=500
sdram_schmoo=0x02000020
over_voltage=2
sdram_over_voltage=2

With either every item in the stock or overclock configs # (hashed) out to run the other? Or would the ES menu setting rule over this?