Topic: Swedish ASIC miner company kncminer.com - page 7. (Read 3049520 times)

There is a market for this to be developed right? So lets source the 6btc and get it done?

Yeah I can fix that, it requires patience, epoxy glue, 24 gauge wire wrap wire, and .10tc to fix :-)

But I will say if someone can figure out the beaglebone thing that is the right way. I spent a weekend whacking away on it, and got 99% of the way there. Just seems to be a problem in how fucking bfgminer is built because there is knc code, knc-auto code, and knc-titan code and the options just don't seem to work right. I have gotten it to at least see the titan dies, but it flunks loading them which drove me up a c wall.

I know the spi lines and everything else is good (and the new spimux on titans can run neptunes) because I have bfgminer running compiled with neptunes. Something's fucked in the titan code though or one library is stepping on another..

The rest of it is mostly some symbolic links to get waas and the web site to work, but that's not a big deal and I can post my raw notes.

The bridgeboard is also nuts, there are three components on the damn thing and the issue is the crystals I can get just. don't. work. I have no idea in my head why, but I am going to take apart one guy's board to find out. Because another guy managed to kill his bb somehow and we need to fix this.

Want to take a crack at it?

C

Happy new year everyone despite our titan failures

I have a new issue where i've taken off the bridge board from the controller board and the connector has come off and loosened others so now the like 5 of the 10 or so pads have detached.

As you know its almost impossible to repair on these bridge boards so i don't mind shooting that to you but i have a beagle bone from a neptune and would love if everyone could focus on actually getting firmware to control the titan to work on a beagle. Because we don't then need a damn bridge board.

Is that possible mate? Seems like it would cut out all of this bridge board mess we all seem to be in.




Dammit! Gentarkin have you thought to reach out to this guy/girl? If not and you do think to then keep in mind they want it to be a easy transition.

I was paid .5 btc so likely that is not enough. Perhaps if those interested tossed in 20 bucks each
just to know a real clone bridge work around is out there might get you where you need to be

If enough want such or just assurances on future what they have bridge board fixes. ie you get
proper info from such a fund by getting a BB the 20 bucks is kinda an insurance to get you over such a
hump

Yes. I think the problem is the later model B+ chips use a new GPU/IPL loader that does not support Wheezy. This is a real bitch.

Question: Does anyone have a blown out bridgeboard that I can buy? I have just about everything working on the qberty boards but I need to move a component on an original BB to check a trace and I don't want to wreck my reference bridgeboard to do it. Will pay .1btc plus shipping.

Meantime more boards repaired, few more brought back to life. Don't run them too hot; don't burn out the plugs.

So the connector that plugs into the Raspberry Pi is actually 40-pins?

If so, then they must have developed their flash image on a Model B+. As I recall, MOST of the first 26-pins of the GPIO map directly onto the 40-pin GPIO, but there a couple of small differences that don't matter to many applications.

molex pins I mean the where the power comes...did I use wrong term.
I bought some replacements on mouser, had a guy at real old time electronics shop take off burnt one and solder in new one.
he was intrigued as to a machine that would generate such heat.... so I gave him a brief primer on blockchain technology and distributed ledgers.
pic maybe dark but here goes

It's a B+, but I think their code was developed on a B unit. The earlier B+ units could support the code releases from KNC, but those boot images will not work with RPI3 or (this is what I seem to be running into here) later model B+ because the video chip (which does the IPL loading) is different.

Add that to Rpi changing how SPI devices are enumerated and zero development on the KNC code and you have a bit of a problem.

C

While I know approximately zero about the KNC hardware, the very Original Raspberry Pi Model B (512 MB), had a 26 pin GPIO header. The subsequent Model B+ that are shown above has a 40-pin GPIO header. My recollection is that the Pi microcode, NOT the stuff supplied by KNC, had to be changed to support the Model B+ and it's expanded GPIO [pins.

So what king of connector is on the KNC hardware? If it's a 26-pin variety, in which case the microcode that's included within their flash image is likely meant for just the original Model B, and may not support the Model B+ (nor the Pi 2 or Pi3).

My apologies if this obvious to everyone else.

How did he replace the molex pins? Can you shoot a pic of the front and back?

Pins 1,3,5,7,9 should not have low resistance. If you see low there then the buffers are damaged.
Pins 4 and 6 are the power supply pins for the main chip logic. If either is shorted you're sunk.
Test relative to ground (the top pins on the Molex).

I have digital multi meter I picked up years ago...not really sure how to use it. 

other wise I could always bring to guy who replaced molex pin connector and ask him follow your instruction.

are either of those two problems fixable ? and do you think they be costly?

thanks appreciate help

Cube either has shorted CPU lines or blown buffers. Can you check resistance with a meter between each of the pins on the 10 pin connector and ground?

I have a titan cube that melted where psu connects...I had it replaced and after that the cube was running fine for about a month( I have two others where I replaced connection and those have been running for 3- 6 months)
at some point system stopped hashing, so I shut down and restarted. now system does not boot up when this one cube is connected.
cube seems to be getting power as fan comes on
I have tried a number of combinations but routine always seems to get hung up at point in boot when really bright led lights up and IP info start flashing on screen....in current scenario screen lights but no text is being output as to status.
when I remove the one cube and boot with the three other cubes everything boots up normal.
any suggestions.?

How much can that chip mine?

The qberty board has a short on its' 3.3 volt line where it runs through the crystal. That keeps the Pi from even powering up (and might blow up the Pi if your PSU was big enough). I've cleared the short on a test board, but am also fiddling with the crystals.

C

I'll put some time on it this weekend, been testing your cube (the cap is back on, the solder was bad, 64mh as seen below) and on a separate controller Johnny's (fun little project, was totally dead, now running fine but occasionally resets the power supply. Run it on its' own supply and it is happy). His other cube is a mystery: Supplies now come up (two shorted), communications restored, but the chip doesn't hash.

As for the BB's I was waiting for a need for more fpga's so I don't do a 5 buck order. Sure enough got another one in for fixing, so order going out for higher pf crystals.

C

 bfgminer version 5.4.2-titan-2.02 - Started: [2016-12-02 20:21:48] - [  0 days 17:18:49]
 [M]anage devices [P]ool management Settings [D]isplay options                                                                               [H]elp [Q]uit
 Pool 0: us.litecoinpool.or  Diff:125m  +Strtm  LU:[13:40:26]  User:Well yeah, right....
 Block: ...2a7ab326c9461e01  Diff:67.7k (484.8G)  Started: [13:38:43]  I: 1.22mBTC/hr
 ST:21  F:0  NB:411  AS:0  BW:[ 24/ 14 B/s]  E:0.77  BS:485
 1/4           | 66.05/64.25/64.14Mh/s | A:7304 R:42+0(.57%) HW:1207/.50%
-------------------------------------------------------------------------------------------------------------------------------------------------------------
 KNC 0a:       | 13.98/13.57/13.57Mh/s | A:1543 R: 6+0(.39%) HW: 203/.40%
 KNC 0b:       | 10.91/13.59/13.56Mh/s | A:1514 R: 9+0(.59%) HW: 221/.44%
 KNC 0c:       | 24.05/18.56/18.52Mh/s | A:2146 R:14+0(.65%) HW: 415/.60%
 KNC 0d:       | 19.57/18.52/18.48Mh/s | A:2102 R:13+0(.61%) HW: 368/.53%
-------------------------------------------------------------------------------------------------------------------------------------------------------------
 [2016-12-03 13:35:56] Accepted 0005a5a2 KNC 0c Diff 177m/125m

Damn..it would help us greatly if you could become WEALTHY as well as eccentric...to keep the BBB project and others going on here..don't ya know Work on that will ya?

By the By I assume the Qberty 2nd batch PI fix attempts are also 'dead' at this time? (going for 100% in the wrong direction..its a theme I tell ya.. ..ho ya ..)

That's a problem. I put the BB port on the side for a bit, if someone really wants me to blow a weekend hacking a version of Debian/Pi that will boot let me know.

Problem is, I dont have physical interaction w/ my Titan and henceforth its RPI...so, I cant really chance updating anything that would cause it to not easily be recoverable =(

Why didn't those pricks use a beaglebone? RB pi nothing but problems.