Keep in mind I dont have a physical titan so Im just guessing here, but based on my experience w/ everything else in PC land....
The heatsink / fan will be directly attached to the dies. VRM's usually are passively cooled.

Got a picture of the PCB? Ill tell ya.

Well I got a fake 350mhz working HAHAHA!
Its much more complex then simply modifying waas code =(, thats what I attempted and it just gives the appearance of 350mhz =/

So unless someone has clear documentation of modding it to 350mhz ... I aint willing to risk damaging my cubes.

There is absolutely no hint of how to do this on a titan  in that thread.

Sadly, I cant find that script anywhere on titan, so...
Im not about to mess w/ SPI commands directly w/o knowing exactly what Im doing, dont wanna damage my hardware =(
So, 350mhz may be outta the question unless someone knows what to modify ...

Hey all, sorry to bring this thread back from the dead but, question ... whats needed to impliment overclocked settings of the source code?
I see max frequency limits specified in waas code on github, is it really just that easy to change the field or is it more complex then that?
I couldnt easily search / find the info in this thread and wasnt sure if it evolved beyond the initial findings in first few pages.
Thanks

Ive not uploaded any changes yet guys, just documenting my progress =)

UPDATE: can confirm my code fix now works, It properly detects when dies are turned off manually vs when dies are in questionable state and then proceeds to test them & power cycle if needed =) woohoo
Also, Ive updated bfgminer to newest version, testing how well it works w/ titan. Its based on bfgminer stock. Seems working fine so far. Will publish update soon.

I guess next will be to see if I can unlock 350mhz but use EXTREME CAUTION!!!!!.... the single 6pin PCIE CONNECTOR is already at its max physical POWER rating. Many things may melt down when using 350mhz

All these physical dead dies you guys mentions, I cant help but wonder if really bad shipping stresses(throwing boxes around etc...) caused the massive heatsinks to put insane pressure at times on the dies causing them physical damage.

Alright Ive modified the code, think I got it working properly w/ dies that are flagged OFF now.
Ive confirmed it successfull detects dies that are manually turned off and shows it in the logs, therefore it skips the die detection test on that die.
The question is will it work when a die actually drops off still...gotta wait for that  to happen, but if my code is written properly(which I think it is) it should work as expected =)

Question for ya, are those dies permanently damaged or do they just stop randomly working while mining?

I found the issue w/ the script, it seems when dies are manually disabled the script erronously detects that as the dies also have being failed and trying to restart them(the old way before my script) haha
So, Ill have to come up w/ a way to detect them manually being off or not.

Nevermind, I confirmed the behaviour on my titan as well when manually disabling dies. Grrr, I will have to rewrite the fix somehow lol. Ill keep ya posted.

You can SSH into the miner and do this at command line: cat /var/log/monitordcdc.log
Highly the text it spits out, switch window to notepad and paste.

Any chance you can copy n paste /var/log/monitordcdc.log ? post it here?
Thanks

Thats one thing I didnt test was dies which were manually turned off, not sure how my code would react in that case. Ill have to possibly look into it further. My titan has no manually disabled dies.

Please go back through like the last couple pages of this topic and read everything Ive mentioned.
Again, all this firmware does is bring "dropping dies" "sleeping dies" "braindead dies" ... or whatever you wanna call it.... back to life by automatically power cycling the cube that has the dropped die.
I also added more stats to the STATUS page of webgui when you log in.

I made this firmware primarily because of all the complaints about titan owners constantly experiencing dies that stop mining and they have to power cycle the whole miner in order to bring them back up. I experienced the same issue and had a feeling that the DCDC's were programmable and therefore could be issued a command to powercycle themselves and hopefully bring the die back into an operational state w/o any interference from the operator. It was successful and hence I decided to make my own release =)

Future changes may be an updated bfgminer and ability to OC to 350mhz, but Ive seen nowhere on how to do this. I do see some areas in the source code provided on KNC's github that MAY affect clocks but I dont know if simply adding a 350mhz value would do anything at all. I would like to see working documentation or examples of this from known sources OR from KNC's other products and perhaps I can figure it out from that.

Ah, my bad, didnt realize it was changed from default haha...  admin/99e99

I posted this a lil while back:

Quick update my firmware is now available for download here:
https://github.com/GenTarkin/Titan/releases/tag/v.85

Well, as far as I know my titan is a B1 and its stock settings are -.0366v @ 300mhz
Ive deleted the advanced.conf in the image(firmwarE) and Ive tested this does indeed restore the miner to default factory settings(clocks & voltages).

Correct, if you have permanently damaged dies that cant be fixed as a result of powering off the miner and powering it back on... then this patch will do nothing for you. But if your dies randomly drop off while mining sometimes and a power cycle remedies the issue temporarily then ... this mod will do the power cycling of the particular cube having issues for you. In other words u dont have to baby sit the miner.
Also my mod adds way more useful stats under the STATUS webgui.

File is writeable via win32diskimager or dd
2GB SD card required
set to DHCP for address acquiring
Default clocks & voltages will be applied
Settings will not be saved(such as pools)

Any donations would be greatly welcome and appreciated. I hope to receive the .5BTC bounty as well =)
1Px71mWNQNKW19xuARqrmnbcem1dXqJ3At

Im currently updating the img file to github. In the meantime if you want to try the img file out sooner....
---
Download & install bittorrent sync from getsync.com
Once installed, on the upper right of program click Gear icon -> Manual Connection and paste this:

https://link.getsync.com/#f=Titan_Firmware&sz=15E8&t=2&s=L6YEHRGEL3755IV2DVK4SK3MNHQMORDGW6AHYM3LHZMO5N55XLOQ&i=CEFQWBL6C4NVCTJUYOWNE7GEVLK2MYSRJ&v=2.0