|
Just wanted to say thanks to everyone here.
We have a strong & free Litecoin and Bitcoin mining site because of your work.
Very, very appreciative.
|
|
|
|
|
BKK,
I hope you are ok.
If you are, please come back,
Aside from the need for a strong open-source Bitcoin asic ecosystem, I miss your nerdy talk.
Peace & Love,
AtomSea
|
|
|
|
Interesting. Can you elaborate? |
|
|
|
Bar & Atomic working together. The end of the world is nigh. Or the dawn of a glorious new empire has begun. . .  Thanks for your work guys. Much appreciated. |
|
|
|
|
Agreed.
And can this thread be locked?
|
|
|
|
|
I really see this design being the precursor for an opensource board that will eventually hold an opensource chip.
And no reason that chip couldn't be 14nm or better someday.
Bitcoin needs checks and balances.
Without a strong-transparent-opensource mining community Bitcoin could descend into an old Star Trek episode where they end up on some random planet, that just went all wrong, and the weird fight music comes on, but at least Kirk gets laid.
So good work peeps - with you there is hope.
|
|
|
|
Regarding the project as a whole. Since Yifu is offering chip refunds now, we can go that route. But as you know, chips were only about 50-60% cost in our operation, that is all we would be able to refund everyone.
Another option is to get a refund now, and buy the Gen 2 chips in October. Yifu has announced that the Gen 2 chips will be fully compatible with Gen 1. So, we would be able to use the current boards, heat sinks, cases and most (if not all) of the components. And everyone will get about 8-10 times more hashing power for same price. (This is just an estimate, we will get more details once he releases the specs.) And we'll get another month and a half to sort out the issues with the current design. Instead of depending upon BkkCoins this time, we will hire people here to build upon and improve his design. We will open source everything we do.
Terrahash, Please indicate what your plan is moving forward. I understand things can be difficult. If Avalon is not giving info on the 55nm, please indicate that. If you are in a quandary regarding the k16 or k64 - please be forthcoming on the Klondike page - there are more minds working on the project now, they will assist. If you are open-source, be open-source. I suggest the following: ~Come completely clean on your current k16/k64 situation. (Post on the Klondike boards your progress) ~State what was done with all the Avalon 110nm orders. (I assume you saw the wisdom in cancelling and refunding those orders) ~Move forward publicly with an upgrade option to the 55nm. (Even if you don't have all the specs yet from Avalon, or a fully efficient board with 110nm, the Klondike with Avalon chips is the best open-source option out there at this time for Asics - many will continue to support it) ~Refunds must become an option for those that want them. (If you can only go 1/2 now and 1/2 later, then so be it, just make it happen) I can promise, we will be more open and be better with customer service this time!
Please live up to this and respond with your plan within 48 hours. Thank you. |
|
|
|
As I understand it individual K16s only work with NOR gates from particular manufacturers.
interesting - where was this discussed? It was discussed here: Hey Guys. Im trying to do some testing with ktest but don't seem to get any desirable results. At one point, I got the "W" command to work, but it resulted in a BAD response , which I would think should be accepted, if Im reading the code right using Below Var: Work = ["4375c3b7a27cc936f295a6140358e965319322e7cfd11e137df42ea60864a675", "218d522051d547d51a00c94e", "b2cc9f74", "accept"]
Now, I run W command (aftere restarting ktest) and I get no response at all! Trying to find out if theres a proper method to using ktest or if there could be something wrong with the K16. I added a small debug output in sendcmd under the dev.write line: dev.write(0x01, cmd + chr(addr) + data, 0, 500)
print "tried %s %s %s" % (cmd,addr,data)
python ktest
Klondike device opened
tried I 0
Version:10, ProductID:K16, Serial#:deadbeef
Cmds [WAISCE.Q]:
S
State:R, ASICs:16, Slaves:0
WorkQ:0, WorkID:04, Temp:158, Fan:0, ErrCount:0, HashCount:2048, MaxCount:2048tried S 0
Cmds [WAISCE.Q]:
w
tried W 0 Cu÷?|?6?X?e1?"???}?.d?u!?R Q?G??N
State:W, ASICs:16, Slaves:0
WorkQ:0, WorkID:01, Temp:158, Fan:0, ErrCount:0, HashCount:0, MaxCount:2048
Cmds [WAISCE.Q]:
Is there something I am missing here, or something else I should be checking out? thanks It is most likely a hardware bug in the circuit. During our testing we realized that the Dual NOR gates used in the design are too fast, and there needs to be some propagation delay. Using a cheap NOR gate chip from Fry's did the trick. We are still trying to see if this can be fixed in the firmware. |
|
|
|
And between those instructions, is there a one, which changes what PORTC pins to use, when sending data out? Except the DATA_ONE and DATA_ZERO defines?
Therefore please look at the caller, which is in this case AsicPushWork in klondike.c, the argument there is DATA_SPLIT, which does the bits for single bank mode. In double bank mode one bank gets a one, the other a zero for MSB. Please also look what exactly the asm code tells, the last lines in send32 function differ from the others. Steamboat and Marty's group have been unable to get this design to work. Have you gotten a K16 working? |
|
|
|
|
Terrahash,
Please let us know what our options are regarding returns or upgrades.
You have merely told us some possibilities.
In the meantime Avalon may ship the chips and that would leave us NO options except for very expensive paperweights.
Please respond today with concrete options and how to submit our choice back to you.
Thank you.
|
|
|
|
Can the remaining developers chime in and settle a debate?
Does anybody have a working 16 chip klondike running at 333*16?
To clarify on this, it would be a 16 chip Klondike at 282*16 (4.5GH as Advertised) with low HW Errors. Also if whoever did this, did so using Terrahash's code. You are using 260pF for C274 right? In order to hash with 16 chips, you need to make the following modifications in klondike.c, from line 159: Status.ChipCount = 16;
// pre-calc nonce range values
BankSize = (Status.ChipCount+1)/2;
Status.MaxCount = WORK_TICKS / BankSize / 2;
NonceRanges[0] = 0;
for(BYTE x = 1; x < BankSize; x++)
NonceRanges[x] = NonceRanges[x-1] + BankRanges[BankSize-1];
If you look at that code, you see, that only 8 nonce ranges are defined. How could this work with 16 chips? Any idea? Also, the NonceRanges were defined as NonceRanges[8]. And for everyone here, fully populated board with 16 chips IS NOT WORKING with those firmware modifications that Terrahash posted above. Look at asic.c especially in SendAsicData function. You will get your answer there and in the end of send32 function. But it is a bit tricky how its done there... In fact you only need 8 nonce ranges What are you implying  The question is: Does it work? I can find NO ONE that can get the K16 to work. |
|
|
|
|
Can anyone prove to me that there exists a single functioning k16 anywhere?
(one that is based on BKKcoin's last update that Terrahash verified that worked)
|
|
|
|
Has TechnoBit been able to get the k16 working?
Has anyone?
No We made prototype boards based on last rev from BKKcoins, populated one but the firmware did not worked properly , so we left it in order to push our own design ahead , because K16 is limited in OC due to power regulators limitation Thank you for your information. I find it very interesting. BKKcoin never tested the k16 after Terrahash claimed to have gotten it to work based on that last rev. BKKcoin trusted Terrahashs' assessment and moved on at that point. I am starting to wonder why Terrahash gave the ok on that design, and why no one double checked it. It now appears that no one has been able to get the k16 working based on those specs. No one in the Klondike thread, nor has Steamboat, and even the video Terrahash released as "proof" clearly shows their miner only hashing at 2gig thus only 8 chips. Very peculiar. Thanks again for your input  I am trying to figure out where this open-source project went wrong - I hope it can be solved because I feel Bitcoin needs to adopt more open-source mining projects Peace. |
|
|
|
|
Has TechnoBit been able to get the k16 working?
Has anyone?
|
|
|
|
We do not however have a fully functioning K16 at this time.
We have organized the collaborative efforts of ourselves, two Klondike based assembly companies, and several individuals within the community with software and hardware debugging experience to troubleshoot the design. As a result, we have determined the source of and corrected the hardware flaw resulting in proof of work not being read correctly, and the units are now hashing on a single bank of 8 chips at a time. We are actively troubleshooting the firmware issue which causes errors when both banks of chips are used at the same time. We will continue to debug the design until it is fully functional, and will be sending units to several people working on the project, in addition to those we have already shipped, for further troubleshooting. Currently updating the firmware does require a PIC programmer and does not support updating via USB.
Question for everyone: Does anyone have a fully functioning k16 anywhere? |
|
|
|
Terrahash, Thank you for your work. I want to continue to support an open-sourced project, but to make an informed decision on how to proceed with my multiple orders I need more data: 1. What is the hashrate of the gen 2 Avalon chip? 2. When can they ship? 3. When would you be able to ship the finished units to us? 4. Do you consider your k16 solution stable and a solid fix for production? Your video appears to show (I could be wrong) only a 2 gig machine? Implying you only solved it for 8 chips? https://www.youtube.com/watch?v=GOZ22GfUdzsCan you address this? 5. Can you show a working model of a k64? 6. What will be the price of a k16 & a k64 with 55nm Avalon chips? 7. If the 110nm chips are delivered to you while we are waiting for these vital questions to be answered, will we be subject to taking current 110nm orders with no other options? Thank you for your time & work, it is much appreciated Peace. |
|
|
|
|
Based on the lack of data, it is impossible to make an informed decision at this point.
We need to ask them for more information, then get a tally.
|
|
|
|
|
No, it doesn't.
I want more information.
|
|
|
|
|
The problem is that one can't make a rational decision when all the facts are not known.
Unknowns:
1. We don't know the hash rate of the Avalon generation 2 chip.
2. We don't know when the chips can be shipped. (according to Steamboat it may be late November)
3. We still do not have any proof that the k16, let alone the k64, actually work. (Steamboat himself admits they still don't have a working k16, Terrahash has never proved it (code is not necessarily proof) and no one on the entire Klondike open-source thread has claimed victory and shown proof)
Question:
If while we are waiting for more information to answer 1-3, the 110nm chips are mailed off to Terrahash, does this lock us into the agreement and we have no chance to upgrade?
Other Issues:
A. It appears that the open-source Klondike group has fallen apart (BKKcoin, the one that was the brains behind it, states that he doesn't even have a floor to work on, amongst other family stresses, and has appeared to have backed out), and the work isn't completed yet.
B. Even if they are 2.5gig, Avalon has shown they can't meet shipping deadlines.
Thoughts:
I want to help out with research & development to support open-source projects, but a complete systemic failure is occurring here.
|
|
|
|
|
Show Posts
