heh you keep adding stuff I need before i can get to installing it due to work at the end of the month...heh all suggestions I needed heh

anyway gotta buy me some coin on coinbase and shoot you some again when i can get off work enough to test this and or at least get you some btc
(main hoard is in paper wallet in safety deposit box)

I'm sure there are more then a few of us that will trickle you some more btc

again i'm sure i include everyone we appreciate your efforts (by the by all my posts till the end of the month will be away from miners at work...no joy to play with toys)

instead of burning the new img file I tried doing a git pull:

cd knc-asic
git stash save --keep-index                (didn't need this line on all rigs)
git pull
cd
./update-webgui.sh

seems to work but did I miss anything??

Can you make your firmware
Work

With rasberry pi 2. Version?


That will be great

Titan firmware

I only have a pi to work on, so no.

AWESOME !!! Thanks a ton!!!
I just uploaded another change for webgui, it now shows bfgminer version in status screen.
Ill look into the delay for ya =)
Ill get to working on auto upscaling of cores that previously were downclocked. Have a busy schedule coming up so may not be released as quickly and this is fairly complex =)

Regarding the soft reset, do you know where the soft reset actually fails? during the waas -s command or when bfgminer is told to reconfigure...?
When u see this behaviour happen can you post the relevant contents ofvar/log/monitordcdc.log? That way I can see exactly what needs delayed.(or tried a few times)

If I had to guess, soft resets I check to see when they fail the waas command. I base the success fail of that on whether a hard reset needs to be issued. So, I could do a timed loop of say up to 5 soft resets(on like a couple second timer) via waas command and if they all fail then perform hard reset, the first one that passes it exits loop then proceeds to tell BFGminer to do its die reconfigure. *NOT: The waas command has to succeed before BFGminer will show a "die successfully configured" message.
How that sound?

Ok, cool yeah "die configuration failed" .. if I would have to assume, means the waas soft reset has failed. At least, when my rig requires a hard reset ... thats the message I get until doing the hard reset. Ill impliment the loop sometime either today or tonight =)
If other people could test out the firmware that would be great and any donations helps =)
Thanks again for ur generous donation TXSteve, I really appreciate it =)

TXSteve, so the way these things work is every loop of the monitoring script it scans how much current is going through the DCDC's and if under 5 amps is going through it basically incriments the valuevar/run/dieXX
oncevar/run/dieXX reaches over the threshold variable it takes action to reset the die. So...basically if the ASICs dont have work due to a shitty pool configuration like when renting... thatvar/run/dieXX will get incrimented, if the pool is shitty enough and it increments over threshold ... no matter what... one of the reset actions will be taken.
Im not exactly sure whats a good way to recode this so it can differentiate between possible pool comm issues vs an actual die needing reset.
I could impliment maybe 2 thresholds, one being a lower one for the pool issues then another maybe being double of the first one? and if thats reached then it performs a hard reset.
I dont know, what do you think?
Or anyone else care to chime in?
Im just kinda doing a ton of trial and error here LOL!


How this all was originally(the way KNC set it up) was on threshold and if that threshold was hit it just performed a soft reset for an eternity.



In the short term, I was thinking, pool issues aside. Now since we have this other stupid mode of failure where the waas command succeeds but it really doesnt bring the die back to life .... I could do another loop which would attempt soft resets up to say 5x sleep after each attempt, run the dcdc function to see if current is over 5A and each incriment its not, of course increasevar/run/dieXX ... then inside that same loop ifvar/run/dieXX goes over the threhold then start a hard reset. I think that would solve the issue I ran into just today =)

Trying to keep this as automated as possible and least user invasive as possible =), its hard for me to code custom stuff for webgui since I dont have much experience w/ all the crazy shit they have going on involving it. LOL

Yeahp, bfgminer cant be running in order for a proper dcdc power down up ... dont know if it has to do w/ bus traffic or what, but seems the dcdc power down up does something but bfgminer will continually ignore them.