Bitcoin Forum
May 12, 2024, 10:55:57 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Has the K32 / K64 actually been designed yet?  (Read 960 times)
alexuk (OP)
Sr. Member
****
Offline Offline

Activity: 322
Merit: 250


View Profile
June 11, 2013, 10:59:43 PM
 #1

I cant seem to find any hard references to it yet...

second question - can you string / chain K16's together ?

thanks!
1715511357
Hero Member
*
Offline Offline

Posts: 1715511357

View Profile Personal Message (Offline)

Ignore
1715511357
Reply with quote  #2

1715511357
Report to moderator
1715511357
Hero Member
*
Offline Offline

Posts: 1715511357

View Profile Personal Message (Offline)

Ignore
1715511357
Reply with quote  #2

1715511357
Report to moderator
1715511357
Hero Member
*
Offline Offline

Posts: 1715511357

View Profile Personal Message (Offline)

Ignore
1715511357
Reply with quote  #2

1715511357
Report to moderator
Once a transaction has 6 confirmations, it is extremely unlikely that an attacker without at least 50% of the network's computation power would be able to reverse it.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
eroxors
Legendary
*
Offline Offline

Activity: 924
Merit: 1000


Think. Positive. Thoughts.


View Profile WWW
June 11, 2013, 11:06:47 PM
 #2

I cant seem to find any hard references to it yet...

second question - can you string / chain K16's together ?

thanks!

There really is no K32/K64 per se, they are just K16s connected, same design.

fasmax
Sr. Member
****
Offline Offline

Activity: 378
Merit: 250


View Profile
June 11, 2013, 11:25:05 PM
 #3

I cant seem to find any hard references to it yet...

second question - can you string / chain K16's together ?

thanks!
There is a I2C bus to chain multiple K16 together.
BitCsByBit
Sr. Member
****
Offline Offline

Activity: 252
Merit: 250


View Profile
June 12, 2013, 12:03:23 AM
 #4

Any idea what is the maximum number of K16 boards that can be chained together with the I2C bus to a single USB connection on the controller?

Tipsy jar: 1HgfLMXiJQj9KZ7abLRh9rWuR7dgeSyub4
alexuk (OP)
Sr. Member
****
Offline Offline

Activity: 322
Merit: 250


View Profile
June 12, 2013, 07:33:42 AM
 #5

bump

how are the K16's chained together? is there a male/female port configuration?
emanymton
Full Member
***
Offline Offline

Activity: 219
Merit: 106


View Profile
June 12, 2013, 07:51:55 AM
 #6

Any idea what is the maximum number of K16 boards that can be chained together with the I2C bus to a single USB connection on the controller?
Check out this: https://bitcointalk.org/index.php?topic=190731.msg2195835;topicseen#msg2195835
marto74
Hero Member
*****
Offline Offline

Activity: 728
Merit: 500



View Profile WWW
June 12, 2013, 07:58:27 AM
 #7

Here is my sample design of 4 x K32 (4x2xK16) in a box

http://technobit.eu
tips : 12DNdacCtUZ99qcP74FwchaCPzeDL9Voff
BitCsByBit
Sr. Member
****
Offline Offline

Activity: 252
Merit: 250


View Profile
June 13, 2013, 01:52:20 AM
 #8

Any idea what is the maximum number of K16 boards that can be chained together with the I2C bus to a single USB connection on the controller?
Check out this: https://bitcointalk.org/index.php?topic=190731.msg2195835;topicseen#msg2195835

Oh wow, I initially read the 000-112 as 000-012.

So there are 113 addresses on a I2C 7 bit addressing that is planned for the K16. I like it.  Grin

Tipsy jar: 1HgfLMXiJQj9KZ7abLRh9rWuR7dgeSyub4
Bicknellski
Hero Member
*****
Offline Offline

Activity: 924
Merit: 1000



View Profile
June 13, 2013, 09:22:25 AM
 #9

K1, K16, and K64 all possible and "designed".

Yes they can be K16s and K64s can be chained together. Klondike Lego or Klego.

Quote
The address is always 000 for the primary USB board, and >= 001 for subsequent chained boards. For chained boards it simply relays the cmd to the I2c bus.

The primary board auto-detects what chained boards are present using "serial# as address" arbitration and assigns a unique I2C 7 bit address. So the possible range for destinations the host can talk to is 000-112 (some I2C addresses are reserved). This would be the max boards per chain. I didn't go with 10 bit addressing as it would probably be beyond the limits of what even 400kbps could support on I2C, and at first I'll be working with 100kbps until there's time to test faster. And there's no real need either - at the USB level having 100+ boards on each port of a hub is economically cheap, and more flexible.

Each PIC also auto-detects how many chips are on board and adjusts it's work splitting to match. The number of chips is relayed as status info for the host but the host doesn't really need to know - more for user overview, monitoring problems. - BKKCoins



https://github.com/bkkcoins/klondike

Quote
Bitcoin ASIC mining board project

WARNING:

This project is incomplete and in progress. There may be errors, mistakes, incomplete portions at this time. Do NOT use these project files to order circuit boards until they have been finished and confirmed to work.

SUMMARY:

This is an open source effort to design and build a Bitcoin mining board based on the Avalon ASIC. The final goal is to have a small 10cm x 10cm board that holds 16 ASIC chips. This board can be controlled via USB or I2C communication. An example host would be a PC, Raspberry Pi or TP-Link WR703N router. The host will run cgminer with a custom driver based on the Avalon one and control the board via USB. The I2C interface allows chaining together more than one board consolidating control by the host system using only one USB connection.

Each board has a 6 pin PCI Express power connector allowing efficient powering of many boards from an ATX PSU. A 16 chip board should be capable of 4512 MH/s and consume about 32W power. A low cost Corsair CX-600 PSU should easily power 16 boards using readily available power splitters. This provides for 72 GH/s off one low cost ATX PSU.

STATUS:

The PCB routing is currently done and I'm making small changes to tidy up, improve and double check the design while waiting on the Avalon communication protocol docs. After they come out I'll finalize any changes and order first prototype boards. During the waiting period for boards to arrive I'll be coding / debugging the firmware and hope to have something workable to program into a test board when it arrives.

COMING SOME DAY:

Kicad Schematic and Board files

MPLAB-X Project and source files

Dogie trust abuse, spam, bullying, conspiracy posts & insults to forum members. Ask the mods or admins to move Dogie's spam or off topic stalking posts to the link above.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!