Quote from: Bargraphics on September 12, 2013, 06:21:41 PM

Quote from: AtomSea on September 12, 2013, 05:48:39 PM

Quote from: hf_developer on September 12, 2013, 11:41:22 AM

Quote from: zipiju on September 12, 2013, 09:52:36 AM

And between those instructions, is there a one, which changes what PORTC pins to use, when sending data out? Except the DATA_ONE and DATA_ZERO defines?

Therefore please look at the caller, which is in this case AsicPushWork in klondike.c, the argument there is DATA_SPLIT, which does the bits for single bank mode. In double bank mode one bank gets a one, the other a zero for MSB. Please also look what exactly the asm code tells, the last lines in send32 function differ from the others.

Steamboat and Marty's group have been unable to get this design to work.
Have you gotten a K16 working?

He's being very "cryptic" Tongue

Us laymen non coders have no idea of what the significance of what he's saying is.

A very clear "This should make the board work for 16 Chips" would be appreciated hah. Sorry gotta dumb it down for us!

It is not that easy... I was designing my own board based on klondike several weeks ago. (It had some enhancements like software over/undervolting, over/underclocking, just search for "Dynamine D20" in this forum) I was working with klondike firmware and got several chips even with two banks working. Then all this YIFU happend and i stopped development. I can say that klondike firmware is well developed but not functional out of the box. A "This should make the board work for 16 Chips" is not that simple to do. There are also some hardware issues on klondike design with phase shifting NOR clock extractor as this only works for some specific gates from specific manufacturers. To get all that fully working some more work has to be done on this i think.