I have an RPi3B running Windows 10 ARM (not scrappy IoT). I used WOA Deployer RPi to burn the image into SD card. I can boot into desktop, but the system is slow & laggy.
When I looked up Task Manager I found the CPU is running at 0.60 GHz max.
But this makes no sense... When running on Raspbian, it just managed the frequency perfectly. (And by perfectly I mean following)
$ cat /sys/devices/system/cpu/cpufreq/policy0/cpuinfo_min_freq
600000
$ cat /sys/devices/system/cpu/cpufreq/policy0/cpuinfo_max_freq
1200000
Using sys-bench
(Still on Raspbian from apt install sys-bench
), I was able to bench the CPU and meanwhile, I did scripts as follows:
while true; do
cat /sys/devices/system/cpu/cpufreq/policy0/cpuinfo_cur_freq
sleep 0.5
done
And the result seems good...
600000
600000
600000
600000
1200000
1200000
1200000
1200000
1200000
... Back on Windows, it just runs at 0.60 GHz (Task Manager says so), no matter how I bench it, frequency makes no change.
And I tried to find some "corresponding" things like config.txt
(like Raspbian has in /boot
) but no use.
So here's the problem...
Isn't stock max frequency 1.20 GHz? Why it is sitting just at 0.60 GHz on Windows? (Or actually it's the problem with Windows? If this is the case then I can really say nothing about it)
Is there any way to "overclock" or bring the frequency back to 1.20 GHz?
config.txt
in or the equivalent you can follow the usual instructions.windows-10-arm
tag or something along the lines.