Search content
Sort by
Showing 2 of 2 results by takeapart
Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
How did you get this page up?
we are able to change fan speed, which here says 70 so why cannot it work for clock speed?
Its not a page, its a disassembly of the sgminer.
70 is not a value but offset to a variable..
I'm almost 99.9% sure that you cannot do anything to baikal without changing its crystal or charing STM firmware.
FInding the right crystal that will only give 10-20% boost would be hard..
Disassembling firmware even harder..
Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
⭐ Merited by phzi (18)
sgminer was hardcoded to report 300Mhz.
Its not picking up the value from STM board, what you see on sgminer interface is hardcoded string, nothing more.
I can make it report anything i want.
Moreover, Mhz setting to baikal_setoption is hardcoded as well, see below.
Changing supplied option to anything (over/undeclock) makes no difference in both calls to baikal_setoption.
I believe this setting is simply ignored by the STM firmware.
Its not picking up the value from STM board, what you see on sgminer interface is hardcoded string, nothing more.
I can make it report anything i want.
Moreover, Mhz setting to baikal_setoption is hardcoded as well, see below.
Code:
BL to_baikal_algorithm
LDRB.W R2, [SP,#0x70+fanspeed]
LDRB.W R3, [SP,#0x70+cutofftemp] ; temp
MOV.W R1, #0x12C ; ; set clock 300Mhz
STR R2, [SP,#0x70+var_70] ; fanspeed
UXTB R2, R0
MOV R0, baikal ; baikal
BL baikal_setoption
LDRB.W R2, [SP,#0x70+fanspeed]
LDRB.W R3, [SP,#0x70+cutofftemp] ; temp
MOV.W R1, #0x12C ; ; set clock 300Mhz
STR R2, [SP,#0x70+var_70] ; fanspeed
UXTB R2, R0
MOV R0, baikal ; baikal
BL baikal_setoption
Changing supplied option to anything (over/undeclock) makes no difference in both calls to baikal_setoption.
I believe this setting is simply ignored by the STM firmware.