[beagleboard] BeagleBoard xM at 1GHz


I'm trying to make the BB xM run at 1Ghz with no luck so far.

I've created a Debian Wheezy arnhf boot image containing 3.6.2-x3 kernel
according to instructions on eLinux wiki on BeagleBoard. Over that image I
managed to load all the GCC toolchain and built from source ZoneMinder and

Now, I realize the BB-xM is running at 600MHz instead of the theoretically
maximum of 1GHz, that I checked is reached when booting with the demo
Angstrom image that came with the board. Following instructions on this
group, I upgraded my kernel to the latest available (testing) with no change
on cpu speed (it, fact got worst. Now cpufreq starts at 300MHz by default)

It's not "worse" it's better, as since in that version we fixed the
"reset" hardlock problem on the older omap3530 Beagle C4, we could
then renable the ONDEMAND cpufreq governor.. So the Beagle XM will
now correctly change frequencies between 300/600Mhz based on load..

BTW: it actually boots with the "PERFORMANCE" govenor, so the core is
running at 600Mhz till late in the system v init, when libcpufeq is
loaded and the governor is switched to "ONDEMAND"...

Linux beagleboard 3.6.7-x4 #1 SMP Mon Nov 19 05:55:30 UTC 2012 armv7l

Before trying to rebuild all the job done over the Angstrom dsitro, is there
any way to make the Debian image run at full speed of 1GHz ?

Yeah, use the Angstrom v3.0.x or v2.6.32 based kernels.. (those
Patches will not work with v3.6.x).

I've seen some info saying I have to patch the kernel (I assume patch source
code and rebuild, isn't it ?) to allow the BB-xM to run at full speed. Is
there any pre-built kernel image I can use ?

Do I have to start from scratch on my Debian image ? Or I can just change
the kernel and leave the rest of the LInux image as it currently is ?

Debian doesn't care what the kernel version is, just have tmpdev
enabled in what ever version you build..

Any help would be greatly appreciated !!!

Some info about my currently running Linux:

Kernel: Linux beagleboard 3.6.7-x4 #1 SMP Mon Nov 19 05:55:30 UTC 2012
armv7l GNU/Linux

Distributor ID: Debian
Description: Debian GNU/Linux testing (wheezy)
Release: testing
Codename: wheezy

root@beagleboard:~# cpufreq-info
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
  driver: omap
  CPUs which run at the same hardware frequency: 0
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency: 300 us.
  hardware limits: 300 MHz - 600 MHz
  available frequency steps: 300 MHz, 600 MHz
  available cpufreq governors: conservative, powersave, ondemand, userspace,
  current policy: frequency should be within 300 MHz and 600 MHz.
                  The governor "userspace" may decide which speed to use
                  within this range.
  current CPU frequency is 600 MHz (asserted by call to hardware).
  cpufreq stats: 300 MHz:0.23%, 600 MHz:99.77% (36)

^^^ see it's spending 99.77% at 600Mhz..

root@beagleboard:~# cat /proc/cpuinfo
Processor : ARMv7 Processor rev 2 (v7l)
processor : 0
BogoMIPS : 342.43

This is useless measurement, as it is not updated with cpufreq changes...

Bascily 1Ghz is broken on mainline (even 800Mhz is now broken as of
v3.6.x).. So complain to TI... There are recent patches for v3.8-rc,
but I haven't tested them fully yet for 800/1Ghz operation..



is the CPU cold running at 300MHz?

300Mhz should be the low power state when idle...