Quote from: tolip_wen on November 25, 2014, 06:48:24 AM

Quote from: Mysil2 on November 24, 2014, 09:50:01 PM

Quote from: jdape on October 08, 2014, 07:39:48 PM

Quote from: Prelude on October 08, 2014, 06:10:16 PM

Quote from: vesperwillow on October 08, 2014, 05:38:23 PM

Try changing the voltage/speed of the others? I have some KNC gear that would act like that and required I actually raise the speed of the bum ones above stock, and in some cases lowering voltage. I've also noticed sometimes neighboring DC's if running too high, would shut down the bum ones. Almost seemed as if they were pulling current away from them.

Thanks for the tips, I'll try that. Can't raise clocks above stock, though. 300MHz is the highest selectable speed.

I found a config file in the Titan SD image that had a preconfigured max speed of 475Mhz for the Titan. To overclock the Titan edit waas.c, recompile and install.

Edit: /home/pi/knc-asic/waas/waas.c

Change this line from 300 to 475:

Code:

#define MAX_DIE_FREQ_TITAN 475

Then:

Code:

cd /home/pi/knc-asic/
make raspberry
cp waas/waas /usr/bin/

Next time you restart bfgminer the advanced page will have selectable speeds up to 475 mhz.

FYI: I had a titan cube overclocked to 400Mhz and was getting about 100Mh/s but the hashrate slipped down quickly over time (even though dcdc's were fine). Not sure why, temps were decentsand everything was working fine.

Might try again at some point.

Note if you are overlocking you had better have damn good connections at the PSU and the Titan. The one I was overclocking was soldered directly to the Titan cube using TWO high quality 6x PCI-E connections (NOT the cheap square pins with the split down the middle).

Anyone have any luck with overcloking? I have now soldered on the power cables after haveing all my cubes turn the pci-e connectors brown. Tried this with 1.11 and can choose up to 475MHz, but whatever I choose above 325MHz, it is not setting the frequency.

Maybe there is some other files that needs to be changed aswell?

The FPGA on the controller quietly ignores clocks above whatever "IT" has programmed as maximum.
The file that is programmed into the FPGA is
spimux.rbf
It is a proprietary Altera format that is not readily reverse engineered.

There is a possibility that the
spimux.rbf
from a neptune would work on a Tit.
If it did you could go to 500 if there was enough power.
(the problem with the Nep is there is no power even if you did manage to set it higher)

You could also end up with a bricked controller!

YMMV

Yeah, thanks, I see it now. spimux-titan.rbf changed in version 1.05... So would have to run 1.04 to get overclocking to work again. Since 1.11 fixed a lot of restarts for my miner, I don't think I will try that old image.

Could build my own image with fixes from latest firmware and spimux-titan.rbf from 1.04, but don't know if it will be compatible... I see there is e.g. flush optimizations in later releases of spimux-titan.rbf.