Post
Topic
Board Hardware
Re: Klondike - 16 chip ASIC Open Source Board - Preliminary
by
BkkCoins
on 16/06/2013, 01:02:21 UTC
A few of my saved links as to why this unit is so interesting. I'm sure I also saw that someone completely reversed the PCB as well, but can't find it now.

Are you talking about this?

 http://dangerousprototypes.com/2012/10/10/reverse-engineering-layout-of-tp-link-tl-wr703n-802-11n-router/
That's it. Thanks. I've added it to my links as somehow it got lost (or I did).

Now, back on topic.

I've added a "K16 Assembly Drawing.pdf" (and K1 similar) to the docs directory that shows components reference labels that otherwise seem impossible to fish out of Kicad. This was not so easy as clicking "print" unfortunately due to odd shortcomings and bugs in Kicad. For one, the silkscreen output from Kicad does not include component references even when chosen explicitly. Investigating in the brd file itself I see that component text is on layer 26 not layer 21 as expected. This is an additional drawing layer (ECCO) that Kicad provides no way to include in plot output as far as I can tell. But it does allow printing this text if made visible and done with the File,Print rather than File,Plot.

The catch is that it appears to be buggy when choosing options other than the most basic (obviously not well tested). So I wanted a 2x scale output, and printing to file for postscript causes partial page cutoff. So inspecting the output I had to manually add some postscript commands including a translate to bring it back within the print area. Once done it showed up ok, and a simple run through ghostscript to convert to PDF format. Sigh. Another example of Kicad idiocy is that the K16 only has component references but K1 has the values too, even though they don't show on screen, and I can't remove them.

This was my fist attempt at trying to put together some material I can use for assembly when I pick up the K16 boards, more parts and samples in a couple days.

I was planning to use this later with other material to make a more extensive assembly document for kits. But now I'm not sure if many are actually going to make K16s from kit. Perhaps I could get a show of hands from those who think they would actually buy a kit or board that would require assembly docs?

(I'm not talking about production which requires files for PnP machines)

I added some more to the cgminer driver. Not any real meat yet, just structure I'll need to fill in once I figure out what cgminer expects it to do for multiple chained devices.