Thanks Ashitank.
...
Thanks for pointing that out.
Another tip, if you want to hardcode all engines to be running (regardless it's functional or not) change __TOTAL_DIAGNOSTICS_RUN from 10 to 0. It will skip all tests on the engines. Beware of the high HW error rate.
Next thing I wanna try is to change DO_NOT_USE_ENGINE_ZERO and overclocking it to 350mhz on the frequency and see what will happen. Hopefully it won't brick
Last but not least to max out the fan speed (FAN_CONTROL_BYTE_REMAIN_FULL_SPEED) if the above is successful.
Tested comment out DO_NOT_USE_ENGINE_ZERO and the jally won't start up....
Thanks for pointing that out.
Another tip, if you want to hardcode all engines to be running (regardless it's functional or not) change __TOTAL_DIAGNOSTICS_RUN from 10 to 0. It will skip all tests on the engines. Beware of the high HW error rate.
Next thing I wanna try is to change DO_NOT_USE_ENGINE_ZERO and overclocking it to 350mhz on the frequency and see what will happen. Hopefully it won't brick
Last but not least to max out the fan speed (FAN_CONTROL_BYTE_REMAIN_FULL_SPEED) if the above is successful.
Attempted to change the frequency from 291 to 350 but it still falls back to 280+. So I went to look into the codes and found that there is a method that detects the frequency and write it back. So I hardcoded the frequency to 350MHz. Starts up and runs @ 9GH/s but has near to 50% HW errors. So it's a fail.
I guess that's all for me know until my new jallies are shipped.
Regards
EP
I can't seem to find the area where you can hardcode the frequency to set number, IE my jallys get up to 266 and 274 on each one. I would like to get them up to like 280 and see what happens from there and tune as needed.
Thanks for all the rest of the info!