Pages:
Author

Topic: Klondike - 16 chip ASIC Open Source Board - Preliminary - page 33. (Read 435377 times)

member
Activity: 71
Merit: 10
UPDATE FROM AVALON 9/9/13

"Avalon Generation Two Chips 55nm
..Those who have invested in time and money on Avalon Generation One based devices and clones can rejoice in the fact we had the foresight to make Avalon Generation Two chips completely backward compatible in every way with 110nm generation one chips, which can be expect to go on sale Late October 2013 for immediate shipping..

Developers and Hobbyists should keep an close eye on our github account as we will be releasing the 55nm chip specification and reference design soon."

This is excellent news - it will still be possible to complete the Klondike project and put these boards into production. Thank you to everyone working to bring this project into reality.
full member
Activity: 197
Merit: 100
@ BkkCoins. Why keep ignoring my emails and pm's? Where is my order or refund you've promised? My order suppose to be shipped  first week of August and I still got nothing and its September.  No pcbs, no refund. You can be sure that I will never trust you again with any coins and now I regret that I didn't pay with paypal.
member
Activity: 93
Merit: 10
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.

Maybe you may also want to try to use a bigger capacitor for the phase shifter in front of the NOR gate. A circuit should not depend on the propagation delays or fabrication tolerances of logic gates. I also tried to use the internal comparator of the PIC as a NOR gate, which is even better since it has some clock synchronization register. But it has shown that the comparator is not fast enough...

Already tried using bigger capacitor. Does not work. The only work around we have found is using a slower gate, so far.

I'm sorry to tell you, but you're wrong.
I'm using v0.3.1 board with bigger cap (currently about 260pF) and it's hashing quite well.
Without it, the clock signal is not delayed enough - just about 5ns and bad nonces are returned.
BTW terrahash, what modifications did you made to the 4 chip firmware to hash with all 16 chips?

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:

Code:
   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];
They said here how they got it working with 16 chips..?

Yeah the only issue there is, that it's not working and it even can't work with that.
The firmware, in it's early stages, were programmed to send same configuration data to both banks. So you had all 16 chips doing something, the only problem was, that both banks were solving the same problem. So you have higher error rate because of the collisions, and only half of the speed.
So changing the nonce range with the code above isn't going to help here.
And I've asked them again (after that), if they did changed anything else, and got no response.
And the response above I only get because they wanted to know from me, what changes I've made in HW to get it working.
full member
Activity: 232
Merit: 100
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.

Maybe you may also want to try to use a bigger capacitor for the phase shifter in front of the NOR gate. A circuit should not depend on the propagation delays or fabrication tolerances of logic gates. I also tried to use the internal comparator of the PIC as a NOR gate, which is even better since it has some clock synchronization register. But it has shown that the comparator is not fast enough...

Already tried using bigger capacitor. Does not work. The only work around we have found is using a slower gate, so far.

I'm sorry to tell you, but you're wrong.
I'm using v0.3.1 board with bigger cap (currently about 260pF) and it's hashing quite well.
Without it, the clock signal is not delayed enough - just about 5ns and bad nonces are returned.
BTW terrahash, what modifications did you made to the 4 chip firmware to hash with all 16 chips?

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:

Code:
    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];
They said here how they got it working with 16 chips..?
member
Activity: 93
Merit: 10
I don't think everyone needs to.abandon.  For the sake of community development. I'd say we finish the project.  If a handful exist  that's okay. I understand people are MIA as well as nerve racked.  That is why I believe wr need fresh hands and eyes on this project.  

Absolutely! I'm not advocating we abandon the project. But there's no point in continuing the design using first-generation Avalon chips. They are obsolete. At this point, with an assembled board in hand, if you mine forever, you will not make back the cost of the miner. However, we can retarget for a different chip and, at the very least, break even.

The design is fully functional, the only thing that needs to be finished is firmware.
I have two boards hashing with only one side (with 8 chips) at about 3Ghps, ~3% ER (without USB ferrite beads), chips overclocked to 375MHz with no overvolt. Other side on each board has few chips that do not respond, but this is because those chips were poorly soldered. And on every board it's different side. Tried to fix it yesterday, but was unsuccessful, and now waiting for solder wick and isopropylalcohol.
I've also tried some modifications in firmware for 16 chips, but it wasn't really usable. The board with that did hash faster, but had around 20% ER - which is a firmware and poorly assembled chips problem, not the design one. Now waiting with this until I fix the other side, then will continue working on FW.
Tried also to contact one of the companies, that claimed to have fully working board (with firmware that hash with all 16 chips), but they did not respond. Anyone here can guess why.
About the ROI, it really is gone now, but you have to take into account, that BTC price will likely go up, so even if you lose now, you can gain later. Especially if you've already made an investment in the HW, chips etc.

Edit:
And about changing the HW for next gen Avalon chips (or any other chips), who is going to make this? Bkk seems to be gone (probably get sick of all the events regarding chips delivery, companies taking advantage of opensource project and giving nothing back) and there is noone (even in the group of those companies, which started their business on this) who is able to make this change.

Is it not possible for you guys to use TerraHash's stuff? They said they have working k16's with less than 1% error rates.

What Terrahash stuff? They have used stuff that Bkk made as opensource. To be absolutely clear on this, I've wrote to them about mine board with 4 chips assembled hashing at 400MHz with around 0.6% ER, when they were asking me via PM about the changes in HW I made to get it working. They were not able to fix even this for the whole time. They claimed even here on this forum, that the design is wrong.
Later, when they did claimed at 5th of September, that they do have a working board, and the only issue there is I2C, I've wrote them again, asking what firmware changes do they made to hash with all 16 chips and that low error rate.
They didn't even bother to wrote me back.
So what do they actually have? Nothing? Lies?
sr. member
Activity: 392
Merit: 250
♫ A wave came crashing like a fist to the jaw ♫
I don't think everyone needs to.abandon.  For the sake of community development. I'd say we finish the project.  If a handful exist  that's okay. I understand people are MIA as well as nerve racked.  That is why I believe wr need fresh hands and eyes on this project.  

Absolutely! I'm not advocating we abandon the project. But there's no point in continuing the design using first-generation Avalon chips. They are obsolete. At this point, with an assembled board in hand, if you mine forever, you will not make back the cost of the miner. However, we can retarget for a different chip and, at the very least, break even.

The design is fully functional, the only thing that needs to be finished is firmware.
I have two boards hashing with only one side (with 8 chips) at about 3Ghps, ~3% ER (without USB ferrite beads), chips overclocked to 375MHz with no overvolt. Other side on each board has few chips that do not respond, but this is because those chips were poorly soldered. And on every board it's different side. Tried to fix it yesterday, but was unsuccessful, and now waiting for solder wick and isopropylalcohol.
I've also tried some modifications in firmware for 16 chips, but it wasn't really usable. The board with that did hash faster, but had around 20% ER - which is a firmware and poorly assembled chips problem, not the design one. Now waiting with this until I fix the other side, then will continue working on FW.
Tried also to contact one of the companies, that claimed to have fully working board (with firmware that hash with all 16 chips), but they did not respond. Anyone here can guess why.
About the ROI, it really is gone now, but you have to take into account, that BTC price will likely go up, so even if you lose now, you can gain later. Especially if you've already made an investment in the HW, chips etc.

Edit:
And about changing the HW for next gen Avalon chips (or any other chips), who is going to make this? Bkk seems to be gone (probably get sick of all the events regarding chips delivery, companies taking advantage of opensource project and giving nothing back) and there is noone (even in the group of those companies, which started their business on this) who is able to make this change.

Is it not possible for you guys to use TerraHash's stuff? They said they have working k16's with less than 1% error rates.
member
Activity: 93
Merit: 10
I don't think everyone needs to.abandon.  For the sake of community development. I'd say we finish the project.  If a handful exist  that's okay. I understand people are MIA as well as nerve racked.  That is why I believe wr need fresh hands and eyes on this project.  

Absolutely! I'm not advocating we abandon the project. But there's no point in continuing the design using first-generation Avalon chips. They are obsolete. At this point, with an assembled board in hand, if you mine forever, you will not make back the cost of the miner. However, we can retarget for a different chip and, at the very least, break even.

The design is fully functional, the only thing that needs to be finished is firmware.
I have two boards hashing with only one side (with 8 chips) at about 3Ghps, ~3% ER (without USB ferrite beads), chips overclocked to 375MHz with no overvolt. Other side on each board has few chips that do not respond, but this is because those chips were poorly soldered. And on every board it's different side. Tried to fix it yesterday, but was unsuccessful, and now waiting for solder wick and isopropylalcohol.
I've also tried some modifications in firmware for 16 chips, but it wasn't really usable. The board with that did hash faster, but had around 20% ER - which is a firmware and poorly assembled chips problem, not the design one. Now waiting with this until I fix the other side, then will continue working on FW.
Tried also to contact one of the companies, that claimed to have fully working board (with firmware that hash with all 16 chips), but they did not respond. Anyone here can guess why.
About the ROI, it really is gone now, but you have to take into account, that BTC price will likely go up, so even if you lose now, you can gain later. Especially if you've already made an investment in the HW, chips etc.

Edit:
And about changing the HW for next gen Avalon chips (or any other chips), who is going to make this? Bkk seems to be gone (probably get sick of all the events regarding chips delivery, companies taking advantage of opensource project and giving nothing back) and there seems to be noone (even in the group of those companies, which started their business on this) who is able to make this change.
newbie
Activity: 58
Merit: 0
I don't think everyone needs to.abandon.  For the sake of community development. I'd say we finish the project.  If a handful exist  that's okay. I understand people are MIA as well as nerve racked.  That is why I believe wr need fresh hands and eyes on this project.  

Absolutely! I'm not advocating we abandon the project. But there's no point in continuing the design using first-generation Avalon chips. They are obsolete. At this point, with an assembled board in hand, if you mine forever, you will not make back the cost of the miner. However, we can retarget for a different chip and, at the very least, break even.
sr. member
Activity: 574
Merit: 250
As the days pass without shipped chips, it's becoming clear that projects using Avalon's offering will not see a profit, let alone ROI. Many of us have sunk money into board and assembly costs. At this point, there appear to be three options:

1. carry on development and testing, hope Avalon ships chips, keep fingers crossed that difficulty stays low enough to break even
2. abandon the project, demand mass refunds from Bitsyncom, and all take individual losses
3. sue sue sue sue sue sue sue
4. retarget the Klondikes for a more powerful chip

#1 is the equivalent of investing in CPU mining during the GPU revolution. We're paying for fancy space heaters.

I've invested enough that #2 is not an option for me.

Anyone crying "lawsuit" has no experience with the legal system. We entered into this venture knowing there was substantial risk. Tough titties people, throwing money at lawyers will not extract blood from a stone.

That leaves retargeting for another chip. I think this is possible. Functionally, chips do the same thing -- iterate over a range of nonces, computing a hash. The board design will definitely have to change, but I suspect the BOM will not change drastically. At the very least, the expensive parts (PIC, buck regs) will almost certainly not change. Also, there is now an actual market for chips, with different suppliers competing on price and features. We're in a pretty good position to negotiate bulk purchases.

Thoughts?

I don't think everyone needs to.abandon.  For the sake of community development. I'd say we finish the project.  If a handful exist  that's okay. I understand people are MIA as well as nerve racked.  That is why I believe wr need fresh hands and eyes on this project. 
newbie
Activity: 58
Merit: 0
As the days pass without shipped chips, it's becoming clear that projects using Avalon's offering will not see a profit, let alone ROI. Many of us have sunk money into board and assembly costs. At this point, there appear to be three options:

1. carry on development and testing, hope Avalon ships chips, keep fingers crossed that difficulty stays low enough to break even
2. abandon the project, demand mass refunds from Bitsyncom, and all take individual losses
3. sue sue sue sue sue sue sue
4. retarget the Klondikes for a more powerful chip

#1 is the equivalent of investing in CPU mining during the GPU revolution. We're paying for fancy space heaters.

I've invested enough that #2 is not an option for me.

Anyone crying "lawsuit" has no experience with the legal system. We entered into this venture knowing there was substantial risk. Tough titties people, throwing money at lawyers will not extract blood from a stone.

That leaves retargeting for another chip. I think this is possible. Functionally, chips do the same thing -- iterate over a range of nonces, computing a hash. The board design will definitely have to change, but I suspect the BOM will not change drastically. At the very least, the expensive parts (PIC, buck regs) will almost certainly not change. Also, there is now an actual market for chips, with different suppliers competing on price and features. We're in a pretty good position to negotiate bulk purchases.

Thoughts?
member
Activity: 93
Merit: 10
i see the 4.5 GH/sec Modular Board still out of stock......https://terrahash.com/product/4-5-ghsec-module/

will it be sold sometime soon again?

Wrong thread Smiley
JBT
full member
Activity: 165
Merit: 100
i see the 4.5 GH/sec Modular Board still out of stock......https://terrahash.com/product/4-5-ghsec-module/

will it be sold sometime soon again?
sr. member
Activity: 294
Merit: 250


 I'd love to get my hands dirty in this project.  I can work well with firmware and deadlines. I have Avalon Chips I just need a board minus chips or a finished bricked board.  Send one with power problems.  This project needs some fresh eyes.  I'd work we would win and I'd somehow manage to get more beer and waffles in my fridge.



I have a K16 board and PIC chip on order with BkkCoins. I'm not sure what his shipping schedule is though. If we could get him to ship that to you priority, and if you have the rest of the BOM, I'd consider letting you have a go at it.
sr. member
Activity: 574
Merit: 250


 I'd love to get my hands dirty in this project.  I can work well with firmware and deadlines. I have Avalon Chips I just need a board minus chips or a finished bricked board.  Send one with power problems.  This project needs some fresh eyes.  I'd work we would win and I'd somehow manage to get more beer and waffles in my fridge.



Not sure who has boards but there are quite a few people who are holding the bag for fabrication. I would try getting a hold of BKKCoins, SebastianJu, Ryepdx, Terrahash... few others out there as well doing boards I think. Our own team pulled the plug on our K1s and refunded everyone as it was clear chips were not going to arrive on time. We are now working on BitFury One USB miners but ya that be great need to talk to those groups and people still looking to go forward.



Thanks for the quick reply.  I'm glad we have some left who are willing and able.  The potency of this shitstorm is out of control. I praise the efforts of bkk and everyone working on a solution.  I don't want to reinvent the wheel if I don't have to.  And I don't believe we need worry about a serious landmark delay. It can and will work Smiley


The
hero member
Activity: 924
Merit: 1000


 I'd love to get my hands dirty in this project.  I can work well with firmware and deadlines. I have Avalon Chips I just need a board minus chips or a finished bricked board.  Send one with power problems.  This project needs some fresh eyes.  I'd work we would win and I'd somehow manage to get more beer and waffles in my fridge.



Not sure who has boards but there are quite a few people who are holding the bag for fabrication. I would try getting a hold of BKKCoins, SebastianJu, Ryepdx, Terrahash... few others out there as well doing boards I think. Our own team pulled the plug on our K1s and refunded everyone as it was clear chips were not going to arrive on time. We are now working on BitFury One USB miners but ya that be great need to talk to those groups and people still looking to go forward.

sr. member
Activity: 574
Merit: 250


 I'd love to get my hands dirty in this project.  I can work well with firmware and deadlines. I have Avalon Chips I just need a board minus chips or a finished bricked board.  Send one with power problems.  This project needs some fresh eyes.  I'd work we would win and I'd somehow manage to get more beer and waffles in my fridge.

member
Activity: 93
Merit: 10
Zip, that's a great find and explains a lot of mystery. Well done lad ! - post an BTC address so we can tip you

Send that tip to BkkCoins. He deserves all the glory.
And don't get too excited, I've made that mistake couple of times Smiley.
member
Activity: 70
Merit: 10
Zip, that's a great find and explains a lot of mystery. Well done lad ! - post an BTC address so we can tip you
member
Activity: 93
Merit: 10
Ok got that running. I can see identical configuration data being transmitted to both banks. RC7 matches RC4 and RC6 matches RC3. The configuration is a long sequence and I haven't found a way to see the nonce ranges that get sent to each bank yet. Going to look at this later when I get more time.

Edit
The nonce range data is loaded into both banks at the same time. The nonce data is identical between banks except for the MSBit and it is always zero for bank 1 and the MSBit is always one for bank 2.

Thanks for that.
I've looked at the code, and found where the pins are selected.
There is a define in klondike.h - DATA_ONE and DATA_ZERO.
Both these are hex values, which when converted to bin are the ports which are connected to the ASICs. It's done in a way, that those pins are pulled down and high in pairs at both sides.
So it's for sure now, that both sides are by default (even with latest firmware) working on same problem, thus only half of the speed and higher error rate. This also explains, why board with 4 chips has ER < 0.4% (when OCed to 350MHz) and board with 4 chips in each bank (8 chips in total) has around 4-5%, with same hashing speed as the first.
Now the question is, which way to do this would be better:
a) split the work to 16 nonce ranges, feed both sides with half of it one by one - so the whole board will be working on one problem. There would be some delay, because feeding twice the time, so maybe a slightly lower speed (we are talking here probably around 0.5% or so).
b) make two separated work units 8 nonce ranges each, so both sides will be working on a different mathematical problem.

I think, that the a) would be better, and I will start working on firmware mods to do it like this.
About the b) option, I do not know, if there will be some mods also in CGM driver needed, but probably not.

If anyone has any other opinion, let me know.

EDIT
About the feeding twice the time. This could be also done in parralel, but it's harder to code, so will do this one by one for now.
sr. member
Activity: 378
Merit: 250
Ok got that running. I can see identical configuration data being transmitted to both banks. RC7 matches RC4 and RC6 matches RC3. The configuration is a long sequence and I haven't found a way to see the nonce ranges that get sent to each bank yet. Going to look at this later when I get more time.

Edit
The nonce range data is loaded into both banks at the same time. The nonce data is identical between banks except for the MSBit and it is always zero for bank 1 and the MSBit is always one for bank 2.
Pages:
Jump to: