and again in red from mittenmining. Trying to fill the thread with good news.....
http://i.imgur.com/T4BjST6.jpg
http://i.imgur.com/T4BjST6.jpg
Indeed I like happy things - great to see the logo on a finished board!
Topic: Klondike - 16 chip ASIC Open Source Board - Preliminary - page 42. (Read 435369 times)
Indeed I like happy things - great to see the logo on a finished board!
Anyone compiled a working cgminer-klondike with libusb for cygwin or mingw-msys? Seems like there are some issues with libusb in this environment as it can detect the klondike device but fails on writing to it...
Read the README in the real cgminer - current version. 
and again in red from mittenmining. Trying to fill the thread with good news.....
NICE! looks racy 
nice for a change from the ol traditional green boards...thx
and again in red from mittenmining. Trying to fill the thread with good news.....
Anyone compiled a working cgminer-klondike with libusb for cygwin or mingw-msys? Seems like there are some issues with libusb in this environment as it can detect the klondike device but fails on writing to it...
I assume you've already tried "run as Administrator", yes?
Anyone compiled a working cgminer-klondike with libusb for cygwin or mingw-msys? Seems like there are some issues with libusb in this environment as it can detect the klondike device but fails on writing to it...
Let the assemblers being, gorgeous in all it's glory.
http://placedroid.com/blogs/news/8625479-place-droid-assembles-first-of-many-klondike-k16-bitcoin-mining-engines
http://placedroid.com/blogs/news/8625479-place-droid-assembles-first-of-many-klondike-k16-bitcoin-mining-engines
god damn.... sexy as fuck... i love the symmetry of this board... everything is mad feng shui
man that is so sweet to see!
Thanks, Everyone for kind words and support.
There's some errors in K1 Nano package footprints on a few parts. I'm going to review them again before posting a parts list update or board revision. Looks like a few parts have 0603 pads for 0402 parts, which is probably workable but not ideal.
My K1 boards have now arrived in Bkk and I should be going to get them within a few days. I'll need to cut them down before packing and shipping.
There's some errors in K1 Nano package footprints on a few parts. I'm going to review them again before posting a parts list update or board revision. Looks like a few parts have 0603 pads for 0402 parts, which is probably workable but not ideal.
My K1 boards have now arrived in Bkk and I should be going to get them within a few days. I'll need to cut them down before packing and shipping.
Which parts, specifically? I'm hoping to order parts for 20 USB units before the end of the month.
Let the assemblers being, gorgeous in all it's glory.
http://placedroid.com/blogs/news/8625479-place-droid-assembles-first-of-many-klondike-k16-bitcoin-mining-engines
http://placedroid.com/blogs/news/8625479-place-droid-assembles-first-of-many-klondike-k16-bitcoin-mining-engines
god damn.... sexy as fuck... i love the symmetry of this board... everything is mad feng shui
Let the assemblers begin, gorgeous in all it's glory.
http://placedroid.com/blogs/news/8625479-place-droid-assembles-first-of-many-klondike-k16-bitcoin-mining-engines
http://placedroid.com/blogs/news/8625479-place-droid-assembles-first-of-many-klondike-k16-bitcoin-mining-engines
So this is just a message to re-affirm that I'm back at it and working to get it done. My fingers are crossed that chips show up and everything can move ahead.
Make them the best damn boards ever.
I know this is old news by now....
From Yifu: this afternoon
at the moment of writing, another 130k chips have gone out, and will proceed to ship more as we get them. ( and no, they are not samples.)https://bitcointalk.org/index.php?topic=269950.1160
From Yifu: this afternoon
at the moment of writing, another 130k chips have gone out, and will proceed to ship more as we get them. ( and no, they are not samples.)https://bitcointalk.org/index.php?topic=269950.1160
Looks like I'm running into a slight delay with my supplier for the IR3895. If anyone has extra, PM me.
Hi BkkCoins,
I've got a full up K16 ready to test, but don't have the firmware (don't have a paid version of the compiler and already used up the demo).
Could I please trouble you for a compiled hex file (if that's allowed) that I can pump into the unit to test. I didn't see one in the repo. I do have MPLAB and an ICD3.
I've applied power to the board and no problems there.
Cool project! I'm super stoked to get it running.
See pic @ http://placedroid.com/blogs/news/8625479-place-droid-assembles-first-of-many-klondike-k16-bitcoin-mining-engines
Thank-you !!!
EDIT: Also just realized I may need a Windows binary of the modded cgminer. Can someone post one ? I don't have a linux box atm and will spin for days trying to get this stuff compiled. I'm rusty. Thx!!
There should be a hex file in github but it's probably just compiled for whatever I was testing last - which would be 1 bank of 4 chips. I haven't updated it recently. I should do a few edits for 16 chips and compile and post a new version. I'm probably going to be running out of my own trial also. I don't recall the date now. On github the hex file resides in the /firmware/Klondike.X/dist/K16/production directory. I'll look this evening at doing a default 16 chip hex file and pushing it to github. I really do need to get some time in on the firmware now.I've got a full up K16 ready to test, but don't have the firmware (don't have a paid version of the compiler and already used up the demo).
Could I please trouble you for a compiled hex file (if that's allowed) that I can pump into the unit to test. I didn't see one in the repo. I do have MPLAB and an ICD3.
I've applied power to the board and no problems there.
Cool project! I'm super stoked to get it running.
See pic @ http://placedroid.com/blogs/news/8625479-place-droid-assembles-first-of-many-klondike-k16-bitcoin-mining-engines
Thank-you !!!
EDIT: Also just realized I may need a Windows binary of the modded cgminer. Can someone post one ? I don't have a linux box atm and will spin for days trying to get this stuff compiled. I'm rusty. Thx!!
I don't have Windows here at all so can't immediately help with that. Hopefully there's someone out there who has compiled it for Windows.
Hi everybody,
I have compiled the cgminer-klondike version (pulled from bkk github) following the windows-build.txt file. It´s working in my desktop PC hashing with my GPU because I don´t have any USB hardware to test (I´m be waiting my K16 boards from Steamboat). I installed too in my laptop and it´s working without hashing (not a good GPU on it) only looking at the pool (BTC Guild).
I gues it may be useless to share the cgminer binaries, because it must be compiled in each PC (with all the dependencies, MinGW, etc). Am I wrong?
Roybitcoin
Interesting stuff. 2 questions.
1) What package/program did you use to compile it and what settings did you use?
2) If it's a standard windows executable, why would it need to be specifically compiled for each machine?
Hi,
I followed the instructions from the windows-build.txt file; in configure option I used ./configure --enable-klondike.
I think I was confused with all the downloaded stuff (MinGW, Libraries, etc) but at the end we need only the cgminer.exe and the .DLLs as shown in the windows-build.txt file:
**************************************************************************************
* Copy files to a build directory/folder *
**************************************************************************************
Make a directory and copy the following files into it. This will be your CGMiner
Folder that you use for mining. Remember the .cl filenames could change on later
releases. If you installed a different version of libcurl then some of those dll's
may be different as well.
cgminer.exe from \MinGW\msys\1.0\home\(username)\cgminer-x.x.x
*.cl from \MinGW\msys\1.0\home\(username)\cgminer-x.x.x
README from \MinGW\msys\1.0\home\(username)\cgminer-x.x.x
libcurl.dll from \MinGW\bin
libidn-11.dll from \MinGW\bin
libeay32.dll from \MinGW\bin
ssleay32.dll from \MinGW\bin
libpdcurses.dll from \MinGW\bin
pthreadGC2.dll from \MinGW\bin
I will test in a "clean" PC just to see if it works fine only with this stuff or there is another DLL that we need
Regards
I didn't realize it but the "dist" sub-directory of the firmware project was not being pushed to github. I've changed that now. The hex file is there. I did a new compile with settings for 16 chips and pushed that up. I'm back coding on the firmware updater now and should have a new release soon.
Despite the doom and gloom surrounding Avalon right now I'm still committed to finalizing the project so that a working solution is ready for when chips arrive. I've kind of fumbled this last week by getting caught up in despair that everything was blowing up. I think a few others are feeling the same. So this is just a message to re-affirm that I'm back at it and working to get it done. My fingers are crossed that chips show up and everything can move ahead.
Despite the doom and gloom surrounding Avalon right now I'm still committed to finalizing the project so that a working solution is ready for when chips arrive. I've kind of fumbled this last week by getting caught up in despair that everything was blowing up. I think a few others are feeling the same. So this is just a message to re-affirm that I'm back at it and working to get it done. My fingers are crossed that chips show up and everything can move ahead.
Great work BkkCoins.
I didn't realize it but the "dist" sub-directory of the firmware project was not being pushed to github. I've changed that now. The hex file is there. I did a new compile with settings for 16 chips and pushed that up. I'm back coding on the firmware updater now and should have a new release soon.
Despite the doom and gloom surrounding Avalon right now I'm still committed to finalizing the project so that a working solution is ready for when chips arrive. I've kind of fumbled this last week by getting caught up in despair that everything was blowing up. I think a few others are feeling the same. So this is just a message to re-affirm that I'm back at it and working to get it done. My fingers are crossed that chips show up and everything can move ahead.
Despite the doom and gloom surrounding Avalon right now I'm still committed to finalizing the project so that a working solution is ready for when chips arrive. I've kind of fumbled this last week by getting caught up in despair that everything was blowing up. I think a few others are feeling the same. So this is just a message to re-affirm that I'm back at it and working to get it done. My fingers are crossed that chips show up and everything can move ahead.
Purple Heart for your persistence on this BKKCoins.
I didn't realize it but the "dist" sub-directory of the firmware project was not being pushed to github. I've changed that now. The hex file is there. I did a new compile with settings for 16 chips and pushed that up. I'm back coding on the firmware updater now and should have a new release soon.
Despite the doom and gloom surrounding Avalon right now I'm still committed to finalizing the project so that a working solution is ready for when chips arrive. I've kind of fumbled this last week by getting caught up in despair that everything was blowing up. I think a few others are feeling the same. So this is just a message to re-affirm that I'm back at it and working to get it done. My fingers are crossed that chips show up and everything can move ahead.
Despite the doom and gloom surrounding Avalon right now I'm still committed to finalizing the project so that a working solution is ready for when chips arrive. I've kind of fumbled this last week by getting caught up in despair that everything was blowing up. I think a few others are feeling the same. So this is just a message to re-affirm that I'm back at it and working to get it done. My fingers are crossed that chips show up and everything can move ahead.
2) If it's a standard windows executable, why would it need to be specifically compiled for each machine?
Correct, Windows binaries are generally standalone, unless they need something like the VisualC++ Runtime.
Hi everybody,
I have compiled the cgminer-klondike version (pulled from bkk github) following the windows-build.txt file. It´s working in my desktop PC hashing with my GPU because I don´t have any USB hardware to test (I´m be waiting my K16 boards from Steamboat). I installed too in my laptop and it´s working without hashing (not a good GPU on it) only looking at the pool (BTC Guild).
I gues it may be useless to share the cgminer binaries, because it must be compiled in each PC (with all the dependencies, MinGW, etc). Am I wrong?
Roybitcoin
If you linked it dynamically, you will probably need to bundle the DLLs it depends on with the binary.
2) If it's a standard windows executable, why would it need to be specifically compiled for each machine?
Correct, Windows binaries are generally standalone, unless they need something like the VisualC++ Runtime.
Jump to: