Does overclocking via /boot/env.txt and max_freq_a53= and max_freq_a73= work for anyone? I tried to change the frequencies as documented here, but it seems to be ignored. cpufreq-info returns just the default frequencies.
I have the latest VIM3_Ubuntu-server-focal_Linux-5.7-rc7_arm64_SD-USB_V0.9-20200530.
Well, I did do-fenix-full-upgrade (I think it contains the two previous steps already), but since I’m on mainline kernel 5.7-rc7 it didn’t upgrade much and the overclocking is still not working.
I’m now using the latest 4.9 and still no luck with overclocking. The lower than default frequencies work, for example setting max_freq_a53=1704 and max_freq_a73=2100 works, cpufreq-info shows the correct frequencies 1704 and 2100.
But anything above the default frequencies does not work. E.g. max_freq_a53=1908 and max_freq_a73=2304, cpufreq-info shows just the default frequencies 1800 and 2208.
Do the higher than default frequencies work for someone?
I think maybe you need to tune up the core voltage.
I have tried for a whole day, and I want to control the temperature of the vim3 board but I failed
I upgrade the os to 20200814, and set the max_freq to 1200, which means the cpu frequency is under 1.2Ghz, but the temperature will go to over 60 degree all the same.
What exactly do you have in mind? I see that Fenix produces also kernel 4.9.232 as the one I’m running now. Maybe it is the dtb file?
I’m a bit confused as I see and old file /boot/dtb.img (88587 May 30) and a newer file under /boot/dtb/kvim3_linux.dtb (88879 Sep 28). Which one is actually used?
Fenix produces also a file kvim3_linux.dtb with length 88879.
There is apparently a variable BUILD_TYPE=release or BUILD_TYPE=develop. I suppose the default is release. Are you using develop?
I think the updater somehow missed /boot/dtb.img and left an old file there. When I copy the new file /boot/dtb/kvim3_linux.dtb to /boot/dtb.img overclocking works!
I just checked the mainline image and it seems the dtb.img is the correct one meson-g12b-a311d-khadas-vim3.dtb (50964 Jun 2). Slightly older than the one on 4.9, which explains, why overclocking does not yet work there.