terrahash
Member
 Offline
Activity: 86
Merit: 10
|
 |
June 14, 2013, 02:49:02 AM |
|
BkkCoins,
We have received Avalon sample chips. We did get about 10 K16 boards manufactured locally as well. We want to assemble one board to help with development and testing. We have resources here that can help push the project forward.
Can you upload the silk screen for the components (those nice little labels that indicate which component is to be placed where on the board)? And if possible XY data that can be fed to an SMT machine?
Wow. This is news to me. And frankly it terrifies me that so much has been invested in my design when I haven't even been able to verify it. However, I'm not going to stand in the way despite the feeling that control is being wrestled away. I'm ready to release everything I have along with a proper open source license but first I would need two things - 1. A public commitment that any info derived from testing/debugging will be submitted back quickly so that everyone has access in a timely fashion. 2. A disclosure regarding any independent firmware and driver development and whether you plan to use proprietary code to enter the market first. The lack of past communication makes me concerned that your main goal is to gaining competitive advantage, and that my materials will be used towards shutting everyone else committed to assembling units, and who have been communicating with me daily, out of the market. I assure you, we are doing the business on minimum margins, and will actually be providing a great alternative to DIY assemblers. Putting those chips on the boards manually is next to impossible, and getting it done from an SMT facility is very expensive if done in small quantity. Our purpose is to not wrestle the control out of your hands at all. 1. We are publicly committing here that any information we get from the testing/debugging the circuit, we will submit it back here on this forum, and to BkkCoins so that he could update his designs. Any changes we make to the circuit will also be submitted back. 2. We won't be using any proprietary code. We will be licensing the code from you. If we do make any changes, we will release them to public. We are committed to pay a royalty fee for every board we sell to you. We actually have the resources to design our own circuit, but we wanted to help the open source initiative by expanding it further. I have offered my help for the firmware in the past as well, but wasn't replied to. |
|
|
|
|
terrahash
Member
Offline
Activity: 86
Merit: 10
|
|
June 14, 2013, 02:50:40 AM |
|
Are you going to release your PC-PIC protocol? I'd like to use the same protocol in my project to reduce the amount of work needed on the miner side.
It's already up on github in the Technical Reference PDF. I still need to add some data format details. I have just the beginnings of a cgminer driver but my work there stalled after I got more focussed on the hardware. I have some plans in that area but have been unable to get back to them. Again, we can help with the firmware/cgminer driver side of the code, and you can focus on the hardware. |
|
|
|
|
|
BkkCoins (OP)
|
|
June 14, 2013, 03:05:06 AM |
|
BkkCoins,
We have received Avalon sample chips. We did get about 10 K16 boards manufactured locally as well. We want to assemble one board to help with development and testing. We have resources here that can help push the project forward.
Can you upload the silk screen for the components (those nice little labels that indicate which component is to be placed where on the board)? And if possible XY data that can be fed to an SMT machine?
Wow. This is news to me. And frankly it terrifies me that so much has been invested in my design when I haven't even been able to verify it. However, I'm not going to stand in the way despite the feeling that control is being wrestled away. I'm ready to release everything I have along with a proper open source license but first I would need two things - 1. A public commitment that any info derived from testing/debugging will be submitted back quickly so that everyone has access in a timely fashion. 2. A disclosure regarding any independent firmware and driver development and whether you plan to use proprietary code to enter the market first. The lack of past communication makes me concerned that your main goal is to gaining competitive advantage, and that my materials will be used towards shutting everyone else committed to assembling units, and who have been communicating with me daily, out of the market. I assure you, we are doing the business on minimum margins, and will actually be providing a great alternative to DIY assemblers. Putting those chips on the boards manually is next to impossible, and getting it done from an SMT facility is very expensive if done in small quantity. Our purpose is to not wrestle the control out of your hands at all. 1. We are publicly committing here that any information we get from the testing/debugging the circuit, we will submit it back here on this forum, and to BkkCoins so that he could update his designs. Any changes we make to the circuit will also be submitted back. 2. We won't be using any proprietary code. We will be licensing the code from you. If we do make any changes, we will release them to public. We are committed to pay a royalty fee for every board we sell to you. We actually have the resources to design our own circuit, but we wanted to help the open source initiative by expanding it further. I have offered my help for the firmware in the past as well, but wasn't replied to. Ok. Acknowledged. I'll work today on preparing my work for release on github. I would rather have released a working version as inevitably some people are going to see this and think they can jump on it and start using it, and others are going to be critical of my design choices and I won't be able to say "hey, it works". For the record - this is both untested hardware and non-debugged software but the advantages of allowing others to feedback and fix my mistakes appears to outweigh that of keeping it back longer until a working version is available. My main fear is that now I'll spend most of my time supporting user problems instead of coding/testing. So - be aware, I may not respond to issues unless fixes are also provided. |
|
|
|
|
Tornate
|
|
June 14, 2013, 03:07:23 AM |
|
This one only has the markings for the Avalon chips, and fan/i2c/icsp header. Doesn't have any other components. Yes, I am interested in that too. BkkCoins, can you please upload the silkscreen "used the print those little label (C1, C2, R1, R2 etc) on the board, so that the people assembling the board can know which Capacitor goes where and which Resistor goes where etc." |
|
|
|
|
terrahash
Member
Offline
Activity: 86
Merit: 10
|
|
June 14, 2013, 03:30:07 AM |
|
Ok. Acknowledged. I'll work today on preparing my work for release on github.
I would rather have released a working version as inevitably some people are going to see this and think they can jump on it and start using it, and others are going to be critical of my design choices and I won't be able to say "hey, it works". For the record - this is both untested hardware and non-debugged software but the advantages of allowing others to feedback and fix my mistakes appears to outweigh that of keeping it back longer until a working version is available.
My main fear is that now I'll spend most of my time supporting user problems instead of coding/testing. So - be aware, I may not respond to issues unless fixes are also provided.
Awesome. Thanks. Just put a big bold red warning on the first page of the project indicating that its a work in progress and use at your own risk, etc. |
|
|
|
|
crazyates
Legendary
Offline
Activity: 952
Merit: 1000
|
|
June 14, 2013, 03:56:09 AM |
|
Just put a big bold red warning on the first page of the project indicating that its a work in progress and use at your own risk, etc.
Psh. People don't read those.  Glad to see some serious progress on this front, from both BKK and TerraH. |
|
|
|
|
daemondazz
|
|
June 14, 2013, 05:28:02 AM |
|
We have decided to re-base our Caterpillar project around the Klondike PIC instead of a ATMega328+CPLD: https://bitcointalk.org/index.php?topic=204699.msg2470767#msg2470767 It will still be a custom design apart from this. @BkKCoin's - (just want to check) do you have any issues with this? Do you know when you might make the PIC firmware source available? (I did check github first!) |
Computers, Amateur Radio, Electronics, Aviation - 1dazzrAbMqNu6cUwh2dtYckNygG7jKs8S
|
|
|
|
marto74
|
|
June 14, 2013, 06:39:52 AM |
|
We have decided to re-base our Caterpillar project around the Klondike PIC instead of a ATMega328+CPLD: https://bitcointalk.org/index.php?topic=204699.msg2470767#msg2470767 It will still be a custom design apart from this. @BkKCoin's - (just want to check) do you have any issues with this? Do you know when you might make the PIC firmware source available? (I did check github first!) it will be fair if you decide to pay some kind of design fee for the efforts BKK puts in the project |
|
|
|
|
daemondazz
|
|
June 14, 2013, 06:43:49 AM |
|
it will be fair if you decide to pay some kind of design fee for the efforts BKK puts in the project
Definitely, we'll probably do something similar to what other's have suggested, point the first hour or three burn in testing at Bkk. |
Computers, Amateur Radio, Electronics, Aviation - 1dazzrAbMqNu6cUwh2dtYckNygG7jKs8S
|
|
|
|
dan99
|
|
June 14, 2013, 07:16:47 AM |
|
BkkCoins,
We have received Avalon sample chips. We did get about 10 K16 boards manufactured locally as well. We want to assemble one board to help with development and testing. We have resources here that can help push the project forward.
Can you upload the silk screen for the components (those nice little labels that indicate which component is to be placed where on the board)? And if possible XY data that can be fed to an SMT machine?
Wow. This is news to me. And frankly it terrifies me that so much has been invested in my design when I haven't even been able to verify it. However, I'm not going to stand in the way despite the feeling that control is being wrestled away. I'm ready to release everything I have along with a proper open source license but first I would need two things - 1. A public commitment that any info derived from testing/debugging will be submitted back quickly so that everyone has access in a timely fashion. 2. A disclosure regarding any independent firmware and driver development and whether you plan to use proprietary code to enter the market first. The lack of past communication makes me concerned that your main goal is to gaining competitive advantage, and that my materials will be used towards shutting everyone else committed to assembling units, and who have been communicating with me daily, out of the market. I agreed watch out for the greedy ones .. who want take everything |
|
|
|
|
|
erk
|
|
June 14, 2013, 07:29:14 AM |
|
I would rather have released a working version as inevitably some people are going to see this and think they can jump on it and start using it, and others are going to be critical of my design choices and I won't be able to say "hey, it works". For the record - this is both untested hardware and non-debugged software but the advantages of allowing others to feedback and fix my mistakes appears to outweigh that of keeping it back longer until a working version is available.
My main fear is that now I'll spend most of my time supporting user problems instead of coding/testing. So - be aware, I may not respond to issues unless fixes are also provided.
Do what you think it right, gut feelings are important. If you think you would rather wait until you have tested, debugged, before releasing specific detail, then I think people will generally stick by your informed choice. Just don't feel pressured to swing one way or the other. |
|
|
|
|
|
newmars
|
|
June 14, 2013, 07:35:24 AM |
|
waiting to see the exciting results soon  |
|
|
|
|
villex
Full Member
Offline
Activity: 154
Merit: 100
Mining hardware assembler and administrator.
|
|
June 14, 2013, 07:39:09 AM |
|
BkkCoins,
We have received Avalon sample chips. We did get about 10 K16 boards manufactured locally as well. We want to assemble one board to help with development and testing. We have resources here that can help push the project forward.
Can you upload the silk screen for the components (those nice little labels that indicate which component is to be placed where on the board)? And if possible XY data that can be fed to an SMT machine?
Wow. This is news to me. And frankly it terrifies me that so much has been invested in my design when I haven't even been able to verify it. However, I'm not going to stand in the way despite the feeling that control is being wrestled away. I'm ready to release everything I have along with a proper open source license but first I would need two things - 1. A public commitment that any info derived from testing/debugging will be submitted back quickly so that everyone has access in a timely fashion. 2. A disclosure regarding any independent firmware and driver development and whether you plan to use proprietary code to enter the market first. The lack of past communication makes me concerned that your main goal is to gaining competitive advantage, and that my materials will be used towards shutting everyone else committed to assembling units, and who have been communicating with me daily, out of the market. I agreed watch out for the greedy ones .. who want take everything +1 I talked with some assemblers and I see them reluctant to help. I can't purchase large order from them with all the contacts because I'm competition, since in my area there's no near PCB or quality electronics available I have to rely on those who do, or trust in some phantom website. |
|
|
|
|
|
BkkCoins (OP)
|
|
June 14, 2013, 08:19:22 AM
Last edit: June 14, 2013, 08:47:13 AM by BkkCoins |
|
*********************
Initial Release 0.1.0
*********************
Just pushed to GitHub.
Please read the RELEASE NOTES as it explains a bit about why the schematic is the way it is.
The README has been updated to try and keep up with the current TODO list and license files have been added, and updated in the source code. I cleaned up the firmware project files a bit so that not as much USB SDK sample junk is left behind. I'll probably be fixing a few things for a while yet.
I think I'm taking a bit of a plunge of faith here in the Bitcoin community. I know it's full of all types, from both ends of the spectrum here - those who will hack and steal everything and those who contribute and support the efforts that made Bitcoin even exist. Everyone in the Klondike thread has been very supportive and I choose to give back what I can - maybe everything will work out and having this out will give everyone the best chance to have working mining boards when ASICs arrive. I'll be continuing my efforts to make that happen.
As I started this project hoping to expand my own mining from GPUs and keep up with changes I couldn't afford to buy into, I'm trusting I wouldn't have been better off keeping it all secret.
NOTE - This is not final code or design at all. I will be writing and re-writing parts, and adapting. If you're wondering how it's possible for something to work when you can't find it, then it's probably because it hasn't been written yet.
|
|
|
|
WynX
Member
Offline
Activity: 77
Merit: 10
|
|
June 14, 2013, 08:36:28 AM |
|
Awesome work Bkk, I admire your faith . I'm sure I won't break your faith...and I hope the majority of people share that opinion. |
|
|
|
|
|
KS
|
|
June 14, 2013, 08:46:57 AM |
|
*********************
Initial Release 0.1.0
*********************
Just pushed to GitHub.
Please read the RELEASE NOTES as it explains a bit about why the schematic is the way it is.
The README has been updated to try and keep up with the current TODO list and license files have been added, and updated in the source code. I cleaned up the firmware project files a bit so that not as much USB SDK sample junk is left behind. I'll probably be fixing a few things for a while yet.
I think I'm taking a bit of a plunge of faith here in the Bitcoin community. I know it's full of all types, from both ends of the spectrum here - those who will hack and steal everything and those who contribute and support the efforts that made Bitcoin even exist. Everyone in the Klondike thread has been very supportive and I choose to give back what I can - maybe everything will work out and having this out will give everyone the best chance to have working mining boards when ASICs arrive. I'll be continuing my efforts to make that happen.
As I started this project hoping to get expand my own mining from GPUs and keep up with changes I couldn't afford to buy into, I'm trusting I wouldn't have been better off keeping it all secret.
NOTE - This is not final code or design at all. I will be writing and re-writing parts, and adapting. If you're wondering how it's possible for something to work when you can't find it, then it's probably because it hasn't been written yet.
There will always be cheaters, but we've got your back. |
|
|
|
|
|
marto74
|
|
June 14, 2013, 08:47:36 AM |
|
Thank you for the trust.
I'm not going to let you down
|
|
|
|
freedomno1
Legendary
Offline
Activity: 1834
Merit: 1094
Learning the troll avoidance button :)
|
|
June 14, 2013, 09:14:19 AM |
|
Rarely can I comment without feeling like I am spamming this thread
That said I believe that while there are people who would take it for profit
There are just as many that will build on it and I trust in your judgement and everyone who is contributing to it
To a growing community
To all the people working here on this project
Thank You
|
Believing in Bitcoins and it's ability to change the world
|
|
|
|
evilscoop
|
|
June 14, 2013, 11:05:09 AM |
|
thx bkk... I also needed the XY data, but felt it was too early to ask for it... I wont be going to assembly until you have a working board anyway  Or at least till after you have tried it with the sample chips As stated before, I will be pushing a % of profit to bkk from my assembly's |
|
|
|
|
|
Bicknellski
|
|
June 14, 2013, 04:30:25 PM |
|
*********************
Initial Release 0.1.0
*********************
Just pushed to GitHub.
Please read the RELEASE NOTES as it explains a bit about why the schematic is the way it is.
The README has been updated to try and keep up with the current TODO list and license files have been added, and updated in the source code. I cleaned up the firmware project files a bit so that not as much USB SDK sample junk is left behind. I'll probably be fixing a few things for a while yet.
I think I'm taking a bit of a plunge of faith here in the Bitcoin community. I know it's full of all types, from both ends of the spectrum here - those who will hack and steal everything and those who contribute and support the efforts that made Bitcoin even exist. Everyone in the Klondike thread has been very supportive and I choose to give back what I can - maybe everything will work out and having this out will give everyone the best chance to have working mining boards when ASICs arrive. I'll be continuing my efforts to make that happen.
As I started this project hoping to expand my own mining from GPUs and keep up with changes I couldn't afford to buy into, I'm trusting I wouldn't have been better off keeping it all secret.
NOTE - This is not final code or design at all. I will be writing and re-writing parts, and adapting. If you're wondering how it's possible for something to work when you can't find it, then it's probably because it hasn't been written yet.
Frigging Canadians... too nice. Thanks.  |
|
|
|
|
