Pages:
Author

Topic: Klondike - 16 chip ASIC Open Source Board - Preliminary - page 98. (Read 435369 times)

hero member
Activity: 714
Merit: 500
Which is kind of dumb since why bother using 0402 parts if using as much space as 0603.

Are you talking about the C1005X7S1A474K? (The one with 192 pieces on the BOM.) Because that would be pretty awesome, considering stock of the 0402 version is starting to run low at most places. Could we use a 0603 version instead, then?
sr. member
Activity: 294
Merit: 250
K16 is live. All 5 voltage regs appear to be outputting correct voltages. The 32MHz oscillator is outputting 32 Mhz as expected on the scope. I'm about to hook up the laptop and program the PIC. Will report back in a while... but first, dinner.

Great news! :-) Each time I see a Bkk post, I get really excited - it's like reading a thriller in daily installments Smiley

+1 - This thread is the most fun I've had vicariously in a long time!  haha
newbie
Activity: 29
Merit: 0
BKK, if your able to deliver everything that it takes to get these boards up and running that doesn't cause TH's timeframe to slip, my first BTC mined with them is yours, even if TH's timeframe slips because of something on their end.
legendary
Activity: 1470
Merit: 1000
Want privacy? Use Monero!
can you give a screenshot of the cgminer mining? how is the speed ?
Dude , don't you see there are no Avalon chips on the board yet?

lol indeed Cheesy
people just don't realise that it takes time to produce the boards AND test them xD
hero member
Activity: 728
Merit: 500
can you give a screenshot of the cgminer mining? how is the speed ?
Dude , don't you see there are no Avalon chips on the board yet?
hero member
Activity: 854
Merit: 500
Fantastic work Bkk, I as the rest of the community really appreciate the great work you are doing. And BTW, it does feel like opening a Xmas present reading your progress updated, along with the other great contributors to the project.

Cheers

+1
member
Activity: 99
Merit: 10
can you give a screenshot of the cgminer mining? how is the speed ?
sr. member
Activity: 406
Merit: 250
Awesome work. Thanks Smiley
newbie
Activity: 15
Merit: 0
Fantastic work Bkk, I as the rest of the community really appreciate the great work you are doing. And BTW, it does feel like opening a Xmas present reading your progress updated, along with the other great contributors to the project.

Cheers
hero member
Activity: 784
Merit: 1009
firstbits:1MinerQ
Excellent progress! Thanks for the great updates. What do you have the USB cable connect to ?
Thanks!!
It's connected to my Acer Notebook running Ubuntu.
Once the cgminer driver is working I'll try it out on a RasPi.
sr. member
Activity: 378
Merit: 250
Excellent progress! Thanks for the great updates. What do you have the USB cable connect to ?
Thanks!!
hero member
Activity: 784
Merit: 1009
firstbits:1MinerQ
That was easy. PIC programmed and working as expected.
Time for new snapshot. A few things to notice:
I don't have a spare PCIe cable and don't want to shut down mining so I just soldered on power leads. The glare circle is from my ring mag light I need to actually see pins when probing. You can see the green power LED, and when I send a ktest cmd the red LED blinks. The 330uF caps are too small - that's because I got them locally and they ran out of the 10mm ones. And finally at the top of the PIC you can see the power fix lead tapping onto the nearest 3.3V by the NOR gate. It's the little gray worm-like thing.

hero member
Activity: 728
Merit: 500
K16 is live. All 5 voltage regs appear to be outputting correct voltages. The 32MHz oscillator is outputting 32 Mhz as expected on the scope. I'm about to hook up the laptop and program the PIC. Will report back in a while... but first, dinner.


Kewl, how many ASIC chips you putting on it to test?

none i think
He'll first test the pic firmware and comuniction.
He'll put asics on the board as soon he is confident everything else is working properly
That's right. I want to be sure I can talk to the PIC before I have it talking to the ASICs. Working incrementally makes it much easier to know what part isn't behaving, even if it seems slower. After the PIC is working as well as my tests last week, then I'll add 1 ASIC and see how that responds. When I have some confirmation it's accepting data and finding nonces, then I'll add another to test ASIC chaining. And so on, until I can fill a board to test full power load.

I'll also build 2x K1 soon, maybe tomorrow, as chaoztc may be ready with new code, and use them to test master/slave I2C chaining.
Please keep on K16 it's more important
We'll continue on K1 later today and tonight.
If there are some usefull for K! updates let me know
member
Activity: 62
Merit: 10
K16 is live. All 5 voltage regs appear to be outputting correct voltages. The 32MHz oscillator is outputting 32 Mhz as expected on the scope. I'm about to hook up the laptop and program the PIC. Will report back in a while... but first, dinner.

Great news! :-) Each time I see a Bkk post, I get really excited - it's like reading a thriller in daily installments Smiley
hero member
Activity: 784
Merit: 1009
firstbits:1MinerQ
K16 is live. All 5 voltage regs appear to be outputting correct voltages. The 32MHz oscillator is outputting 32 Mhz as expected on the scope. I'm about to hook up the laptop and program the PIC. Will report back in a while... but first, dinner.


Kewl, how many ASIC chips you putting on it to test?

none i think
He'll first test the pic firmware and comuniction.
He'll put asics on the board as soon he is confident everything else is working properly
That's right. I want to be sure I can talk to the PIC before I have it talking to the ASICs. Working incrementally makes it much easier to know what part isn't behaving, even if it seems slower. After the PIC is working as well as my tests last week, then I'll add 1 ASIC and see how that responds. When I have some confirmation it's accepting data and finding nonces, then I'll add another to test ASIC chaining. And so on, until I can fill a board to test full power load.

I'll also build 2x K1 soon, maybe tomorrow, as chaoztc may be ready with new code, and use them to test master/slave I2C chaining.
hero member
Activity: 728
Merit: 500
K16 is live. All 5 voltage regs appear to be outputting correct voltages. The 32MHz oscillator is outputting 32 Mhz as expected on the scope. I'm about to hook up the laptop and program the PIC. Will report back in a while... but first, dinner.


Kewl, how many ASIC chips you putting on it to test?

none i think
He'll first test the pic firmware and comuniction.
He'll put asics on the board as soon he is confident everything else is working properly
hero member
Activity: 728
Merit: 500
K16 is live. All 5 voltage regs appear to be outputting correct voltages. The 32MHz oscillator is outputting 32 Mhz as expected on the scope. I'm about to hook up the laptop and program the PIC. Will report back in a while... but first, dinner.

lunch here Wink
erk
hero member
Activity: 826
Merit: 500
K16 is live. All 5 voltage regs appear to be outputting correct voltages. The 32MHz oscillator is outputting 32 Mhz as expected on the scope. I'm about to hook up the laptop and program the PIC. Will report back in a while... but first, dinner.


Kewl, how many ASIC chips you putting on it to test?
hero member
Activity: 784
Merit: 1009
firstbits:1MinerQ
K16 is live. All 5 voltage regs appear to be outputting correct voltages. The 32MHz oscillator is outputting 32 Mhz as expected on the scope. I'm about to hook up the laptop and program the PIC. Will report back in a while... but first, dinner.
hero member
Activity: 784
Merit: 1009
firstbits:1MinerQ
In case you're wondering, this is almost always caused by improper pad geometry.  From the pictures, it looks like there is a bit too much space between the 0402 pads.
Enigma
I was wondering about how far apart and big the pads are for 0402. This was the 0402 part from the Kicad library but I did at one point check it and it seemed to be right for at least some 0402 parts I checked against. But when I was placing them I thought these pads are far enough to take 0603 as well. Which is kind of dumb since why bother using 0402 parts if using as much space as 0603.

I only had 2 of those "tombstones" out of over 210 0402 placed so it's probably my placement inaccuracy combined with a wide gap between pads.

Pages:
Jump to: