Think Isokivi is only acting in an organiser capacity. Aslong as the winner states his bitcoin address I'm sure the rest can be done from there.

Iso,

I am fine with the terms but suggest it be clear that Glasswalker's contribution would qualify even if it his bitstream is released by Enterpoint.  Since he has been working the problem at his own risk with no assured compensation from Enterpoint, I believe that is fair.

Also, if the general terms of the bounty is to withdraw it upon an Enterpoint release, that is the condition I will stand with.  My statement was only that I would support Zefir's proposal if everyone else went with it.

My bonus depends on most board owners contributing to the main bounty.  There are a several people who have openly acknowledged holding large numbers of boards who have not signed on.  I hope that changes soon.

Any tips or advice on getting the hardware stable for more than 2 hours plus. It tells me that both of the units have failed.
I'll get an exact copy of the message next time it occurs. At first I figure maybe it was the usb slot was powering down or something.
But it's also happened in under 30minutes of me running it. I've also set all my usb slots to not turn them off to save power early on in testing these.

The com ports are often what disappears from the device manager, at which point I assume that is why they stop working.
Is their anything that that can help force them to stay... hmm maybe I'll go look.

I've solved all the software stability problems just by moving upto to Cgminer 2.5. That is far more stable than previous versions, good work on that Kano and the team (there is more than 1 of you right?)

All I need to know is if I have the  unmarked SW's  correct when programing the controller. SW 1 and 6 are marked, if you could quickly tell me if they are all on or all off for SW,2, 3, 4, and 5 I would be set.

Or if someone has successfully updated theirs could tell what position they had theirs in that would help too. The board we suspect is broken anyhow always stated the update was successful although I have my doubts.

speaking of ROI, DHL just called me and they said customs wants 400$ some dollars before they can release the shipment. Maybe I should have looked this up but I guess import tax is applied to more expensive shipments in the US?

Ok possibly the return on return characteristics may have changed in the last weeks by *** but of course they may not deliver as promised and then ROI actually doesn't change. Do remember 10 weeks ago we offer a product at 33% discount because it was a development and that was explicitly explained at that point. Even only running at the 50% notional performance that we are today we are not far removed in ROI of other FPGA boards.

The core of the team are already running 100hr+ weeks and have done so since the start of the project. That's part of how we have achieved the timescales. We can't ask more of them than that. Anything that we do that isn't on the plan is a very direct hit on producing the bitsream and other support work for the bulk of our customers. A further point is adding another variable to support i.e. the ET bitstream will further impact progress by virtue of more support calls. If I read it right ET just said he has taken 1 week to get his own very known setup to work again. What's that going to be like for a customer that doesn't have the technical knowledge he has or we have on the products. It's a nightmare basically. We might end up having our team work a week on one customer installation as is and still not have a solution. That's why we are not jumping into the unknown just yet. I'm not in any way saying ET can't do his stuff and sort it out but what I don't what to see is our own progress complete stopped to support a third party. It's not even good for ET to introduce another variable to try and support. As far as I am aware he doesn't even have a Cairnsmore1 to replicate problems on and allow debug of his IP.

To put matters straight we did not say we would start our own bitstream development at the beginning of this process and indeed people we talked to privately we told them we would have very little resources for this in May and only a little in June. I think I said quite a lot of this in this forum as well. We have more or less kept to that schedule and we have only really had a reasonable resourcing on this for 2-3 weeks now. Ok we made a small mistake on the wiring to the second chip and the original plan of dropping in an Icarus bitstream initially into all positions didn't quite work and that was our mistake. However it was a reasonable engineering decision to fix this with our own bitstream as the fastest way to sort the issue. The Icarus bitstream was only ever a temporary solution and I think that was made clear.

I have also said that for bitstream development it isn't easy to put a precise time on and yes I might have said a few days and maybe I should have said a few weeks. This isn't a process we can do a percentage complete number on with any accuracy. Unlike a lot of FPGA things we do this function with either work or it won't there is no partial working stage to give a measure on and it will simply be working one morning when I get in the office. Do remember too it is only 10 weeks and 4 days since we announced the concept and we probably have the best FPGA hardware platform designed but have manufactured and delivered hundreds of them to customers in that timeframe. I don't want to hark on about that but most professional engineers in the electronics business would either say that was either impossible or very unlikely that it could be done.

As to ET's bitstream that has barely been working for more than a handful of days on one of Ztex's boards and has had a pile of problems on there over those days. We are watching how this develops and I am sure he will sort out the issues. We could sink our entire resource into supporting that now but it's no guarantee that it will work any quicker and if it did his server might well collapse under the weight of Cairnsmore1s trying to use the server services. That would also bring our own develop to a complete halt which would not be good and we have a pile of customers that simply don't want to be forced down that route. So this is something we have to balance our time on. When the ET solution is slightly more stable will be the time to some work.

Also as far as I understand ETs solution can't support multiple units working together as yet. We don't have any problems with customers using this bitstream as such and we will do our best to support it. We do believe we have the best chance of any of the FPGA boards of being able to support that bitstream given our power and cooling systems but right now it looks like a pile of development work and server hardware to install before it is actually a viable solution. I will have a look at what he needs once I find a utility to open a jar file and see if we can do anything quickly. If it is days of work then it won't happen this week for an unstable solution the time is better spent stabilising our own product and we have made good progress this week already with the new controller update.

Also yohan can you please fill out the TML BDK? http://www.tricone-mining.com/bdk.html as ET will not implement native usb support without one filled out.

Ok, now I'm even more confused, that's exactly where I got the info from. The problem with the loader PDF document in that zip is it doesn't show you what SW  2, 3, 4, and 5 are supposed to be set to, so I assumed they should all be off. Maybe that's why I never got the last one working.

Can you look at that document and make give me the exact switch settings for the controller update? Id like to try one more time on the broken board. I'm going to drop it off for shipment back to you guys tomorrow as well.

Also I'm using Linux currently and the new board you sent seems to be working great with the FTDI drivers and Cgminer 2.4.3 without any modifications.

Thanks,

Doff