Quote from: Kenshin on November 18, 2013, 09:17:30 PM

Quote from: onryo on November 17, 2013, 11:00:57 PM

Thx OutCast3k
SSH'd into the Debian armhf SoC about a day or two after kick off.
The Fury is doing Avg 2.77/ 2.58 Ghs. Just dropped a 0-25k SMD pot parallel over R15. With no fan I get about 4.5% HW error. With a fan HW Error is about 3.2%. Ill set it for about 2.7 GH/s and that will improve the error rate even more. No need to flash as Luke's code quills a lot of the issues.

http://i.imgur.com/gp8Lb8K.png

This is just a little side toy I am playing with. 3 BE, 1 "Blue Fury" and a 30 GH/s BFL on ARM SoC with a little Dlink DUB-H7. The OS is my own brew of Debian with a git pull from Luke-Jr from a few days back. Rock solid.

Might mod it by chaining in a a few more fury chips with their own power supplies and pcb board just for the tinker factor.
You don't have any bare bitfury chips to sell do you?

All the best
Onryo

How did you managed to get it to 2.7? I am also using the latest bfgminer. What commands are you using?

I had about 2.23 GH/s at first like most here. Took a look at the PCB and realized the fury chip was a bit choked to prevent heat and USB power issues. R15 next to the button was set at 22k. Read that a value of 10k would be fine. By paralleling another resistor you get R= 1 /(1/R1 + 1/R2). Set a tiny SMD pot to about 19k (careful not to set to low!) and bridged the the 22k resistor for a total of about 10k. Did a reboot and was seeing about 2.84 GH/s. High error rate and the heat sink was getting really hot. A little increase on the pots resistance landed me at at an Avg of 2.78 GH/s and a report of 2.61 GH/s. Error 4.6%

So you have an idea of what you should be listing in your rc.local (using Debian armhf on a SoC)

Code:

ls /dev/tty*

To make sure you are really listing the right device (a /dev/ttyACMx) on the port see what is there.

Code:

udevadm info --query=all -n /dev/ttyACM0 | grep ID_VENDOR

A fury will show:

Code:

E: ID_VENDOR=BFMG
E: ID_VENDOR_ENC=BFMG
E: ID_VENDOR_FROM_DATABASE=Atmel Corp.
E: ID_VENDOR_ID=03eb

This is even more important for ttyUSB devices since BE and BFL etc all will show up as /dev/ttyUSB* stuff.

Just change the ttyUSB0 to ttyUSB1,2,3 n. In my case this is the cmd in my;

Code:

/etc/rc.local

Code:

/usr/bin/screen -dmS bfgminer ./bfgminer -S bigpic:/dev/ttyACM0 -S erupter:/dev/ttyUSB0 -S erupter:/dev/ttyUSB1 -S erupter:/dev/ttyUSB2 --config /home/zion/.bfgminer/bfgminer.conf

If ports start changing on you give the -S noauto a read

This is even more important for ttyUSB* devices since BE and BFL etc all will show up as /dev/ttyUSB* stuff.
Just change the ttyUSB0 to ttyUSB1,2,3 n.

Using screen like this with the -dmS will just kick off the command and detach while the S parameter gives it a nice name bfgminer.

Anyway I have my fury set at 2.7 GH/s now and that seems to be the sweet spot on this thing. More or less what I got with a fury chip setup I built running at 0.84V @ 2.5A clocked at 230MHz. This thing should be easy to chain fury chips on...idk. If I can get hold of some bare chips Ill give it a shot...that is if I don't get some ANT (BM1380) chips sent to me first for another project.

Somebody said something about "the pencil mod cmd" lol, sure that might work too. Not sure I personally would do it that way.

onryo

Posts

Merits