How can i overclock my azbox hd box?

[alinux]

Hello,

im using OpenRSI 3.0 latest version, before that my box was very fast with overclock on.

how can i overlock my box again? i used the HWA in the original firmware before, then flashed OpenRSI 2.0 and the overclock was still there.
now when i installed OpenRSI 3.0 i lost the overclocking because AZup tried to fix it and disable it.

Regards

[Smudger]

how did you overclock?

[alinux]

how did you overclock?

i used the HWA option in the original firmware and i didnt disable it before upgrading to openrsi 2.0 and it stayed there enabled, after i went and upgraded to openrsi 3.0 it was disabled by azupd.

[ManikM]

hmm yes, it would be good, i find the latest f/w quite laggy - i think the firmware is too big for the az to handle, and is pushing it too its limits.

[donki]

Only option at the moment is to go back to an older image as it is not currently supported on 3.0. That is not to say that it won't be in the future but that would be a question for the OpenPLi or OpenRSI Teams. :)

[jubilate]

If you install the opensat firware in a pendrive it still will work with OPENRSI 3.0 firware, then if you boot from old firware and activate the overclock it will work OK until you intall again the firware. I do that and works wery well. Excuse my english.

[pr2]

Hi,

To disable overclocking the command is:


setxenv -f /dev/mtdblock1 -b -k x.pll3 -v 0x01020057

With this value the Azbox is running at: 300375000 Hz

When Azbox is overclocked it runs at: 347625000 Hz with this value:


setxenv -f /dev/mtdblock1 -b -k x.pll3 -v 0x01020065

So it's up to you now to find the right value, don't come and cry if you kill your Azbox. It is you own responsibility if you play with setxenv
If you overclock too much your Azbox, it is possible that it will no longer boot and even the TTL cable won't save you!
But I strongly advice that you have such cable before starting to play with overclocking.

Overclocking is only effective after a cold start (power off/power on).

Please find attached setxenv (in tgz format) send it to your Azbox unpack it:


tar -xvzf setxenv.tgz


Once again playing with it can be dangerous and brick your Azbox. Use at your own risk. I disclaim all responsibility!

Pr2

[j911]

pr2 makes a very good point. I pushed my box too far and ended up having to restore it via jtag. Anyone else who is wondering about overclocking... the values work in hex so setxenv -f /dev/mtdblock1 -b -k x.pll3 -v 0x01020057 gives 300 MHz changing it setxenv -f /dev/mtdblock1 -b -k x.pll3 -v 0x01020060 will give 330 MHz so basically incrementing the last digit by one gives an overclock of ~3MHz hope it stops somebody else from having to go through the pain of restoring from jtag. I have tried my box for over a week with 330Mhz speed and it seems fine not hot to the touch, no freezing or pixellation but I do have a fan in my premium on top of the heatsink inside the case...

[pr2]

Hi,

The value used by Opensat to overclock the Azbox is:

0x01020065

Pr2

[j911]

Yeah and my receiver was unstable at that speed, that's why I stick to 0x01020060 which is fast and stable enough for daily use. I just wish that AZUP could be updated to allow custom partitions for those of us using larger doms and wish to overclock.