Have you try compile and use someone42 cgminer?
Thats the version I use...
Topic: BITBURNER FURY Technical discussion - page 4. (Read 18313 times)
Thats the version I use...
Anyone running odd numbers of bitburners?
I have 7 miners and I'm wondering if I can chain them like such: x2, x2, x3
Anyone running a similar setup? Are you using more than one CGminer? Right now I'm running them all as separate miners (each one has usb plugged in)
What I don't want is 2 different cgminer windows. My pi is running on overdrive already!
I have 7 miners and I'm wondering if I can chain them like such: x2, x2, x3
Anyone running a similar setup? Are you using more than one CGminer? Right now I'm running them all as separate miners (each one has usb plugged in)
What I don't want is 2 different cgminer windows. My pi is running on overdrive already!
Now I also have a problem with one Bitburner Fury out of a stack of 4. It's the only board lacking a Micro USB connector (broken). And its not hashing anymore (It did before). LED is blinking green and yellow, but never red. The other boards are delivering 50Ghs.
As it didn't work at all (tried restarting, power cycling, other order of connecting it to the CAN) I flashed the boards with a Pickit3. My first try with the firmware BitBurnerFury_for_bootloader.hex was not successful, the board didn't blink at all after programming it. In my second try, I used BitBurnerFury_for_production.hex and it worked out. Now the board is blinking again, but still not mining. I know that the other three boards all have BitBurnerFury_for_bootloader.hex.
What could be the problem?
- That the firmware of the board without connector is different?
- How can that be solved?
- Is there other firmware that can be flashed with the Pickit3 than the production firmware?
The first hint leading to solve the problem will be awarded 30$ worth of Bitcoin.
As it didn't work at all (tried restarting, power cycling, other order of connecting it to the CAN) I flashed the boards with a Pickit3. My first try with the firmware BitBurnerFury_for_bootloader.hex was not successful, the board didn't blink at all after programming it. In my second try, I used BitBurnerFury_for_production.hex and it worked out. Now the board is blinking again, but still not mining. I know that the other three boards all have BitBurnerFury_for_bootloader.hex.
What could be the problem?
- That the firmware of the board without connector is different?
- How can that be solved?
- Is there other firmware that can be flashed with the Pickit3 than the production firmware?
The first hint leading to solve the problem will be awarded 30$ worth of Bitcoin.
Have you try compile and use someone42 cgminer?
Instruction below:
https://www.asic-hardware.com/assembly-instructions-part-2/
Now I also have a problem with one Bitburner Fury out of a stack of 4. It's the only board lacking a Micro USB connector (broken). And its not hashing anymore (It did before). LED is blinking green and yellow, but never red. The other boards are delivering 50Ghs.
As it didn't work at all (tried restarting, power cycling, other order of connecting it to the CAN) I flashed the boards with a Pickit3. My first try with the firmware BitBurnerFury_for_bootloader.hex was not successful, the board didn't blink at all after programming it. In my second try, I used BitBurnerFury_for_production.hex and it worked out. Now the board is blinking again, but still not mining. I know that the other three boards all have BitBurnerFury_for_bootloader.hex.
What could be the problem?
- That the firmware of the board without connector is different?
- How can that be solved?
- Is there other firmware that can be flashed with the Pickit3 than the production firmware?
The first hint leading to solve the problem will be awarded 30$ worth of Bitcoin.
As it didn't work at all (tried restarting, power cycling, other order of connecting it to the CAN) I flashed the boards with a Pickit3. My first try with the firmware BitBurnerFury_for_bootloader.hex was not successful, the board didn't blink at all after programming it. In my second try, I used BitBurnerFury_for_production.hex and it worked out. Now the board is blinking again, but still not mining. I know that the other three boards all have BitBurnerFury_for_bootloader.hex.
What could be the problem?
- That the firmware of the board without connector is different?
- How can that be solved?
- Is there other firmware that can be flashed with the Pickit3 than the production firmware?
The first hint leading to solve the problem will be awarded 30$ worth of Bitcoin.
Hi dego,
here we go, all it took was a full reboot
here we go, all it took was a full reboot
Code:
[2013-11-26 22:54:36] Started cgminer 3.5.0
[2013-11-26 22:54:36] BTB0: Reset failed! not an Avalon? (0: c0 2a c3 b6)
[2013-11-26 22:54:37] BTB 0 usb write error: **UNKNOWN**
Could you please post your cgminer.conf?
You should find it in ~/.cgminer/cgminer.conf
It could be that a certain usb bus is set in your config, so if cgminer starts it checks the bus that is set in your config and it will only find something if it has the same bus number...
Hi dego,
no cgminer.conf
Code:
pi@raspberrypi ~ $ ls -la
total 64
drwxr-xr-x 6 pi pi 4096 Nov 26 21:58 .
drwxr-xr-x 3 root root 4096 Sep 25 20:22 ..
-rw------- 1 pi pi 14244 Nov 26 23:42 .bash_history
-rw-r--r-- 1 pi pi 220 Sep 25 20:22 .bash_logout
-rw-r--r-- 1 pi pi 3243 Sep 25 20:22 .bashrc
drwxr-xr-x 12 pi pi 4096 Nov 25 18:52 cgminer
drwxr-xr-x 2 pi pi 4096 Nov 25 20:06 .cgminer
-rwxr-xr-x 1 pi pi 153 Nov 26 23:44 cgminer.sh
drwxr-xr-x 2 pi pi 4096 Sep 25 21:20 Desktop
-rw-r--r-- 1 pi pi 5781 Feb 3 2013 ocr_pi.png
-rw-r--r-- 1 pi pi 675 Sep 25 20:22 .profile
drwxrwxr-x 2 pi pi 4096 Mar 10 2013 python_games
pi@raspberrypi ~ $ ls -la .cgminer/
total 8
drwxr-xr-x 2 pi pi 4096 Nov 25 20:06 .
drwxr-xr-x 6 pi pi 4096 Nov 26 21:58 ..
pi@raspberrypi ~ $
cgminer.sh contains the command to start cgminer I did show you in my previous message.
spiccioli
Hi dego,
here we go, all it took was a full reboot
here we go, all it took was a full reboot
Code:
[2013-11-26 22:54:36] Started cgminer 3.5.0
[2013-11-26 22:54:36] BTB0: Reset failed! not an Avalon? (0: c0 2a c3 b6)
[2013-11-26 22:54:37] BTB 0 usb write error: **UNKNOWN**
Could you please post your cgminer.conf?
You should find it in ~/.cgminer/cgminer.conf
It could be that a certain usb bus is set in your config, so if cgminer starts it checks the bus that is set in your config and it will only find something if it has the same bus number...
Hi dego,
here we go, all it took was a full reboot
Here I have both stacks on the same powered usb hub which connects to the Pi on its upper usb port and powers it as well.
spiccioli
here we go, all it took was a full reboot
Code:
[2013-11-26 22:54:36] Started cgminer 3.5.0
[2013-11-26 22:54:36] BTB0: Reset failed! not an Avalon? (0: c0 2a c3 b6)
[2013-11-26 22:54:37] BTB 0 usb write error: **UNKNOWN**
[2013-11-26 22:54:37] usb_write error on avalon_write
[2013-11-26 22:54:37] BTB 0 usb write error: **UNKNOWN**
[2013-11-26 22:54:37] usb_write error on avalon_write
[2013-11-26 22:54:37] BTB 0 usb write error: **UNKNOWN**
[2013-11-26 22:54:37] usb_write error on avalon_write
[2013-11-26 22:54:37] BTB 0 usb write error: **UNKNOWN**
[2013-11-26 22:54:37] usb_write error on avalon_write
[2013-11-26 22:54:37] BTB 0 usb write error: **UNKNOWN**
[2013-11-26 22:54:37] usb_write error on avalon_write
[2013-11-26 22:54:38] BTB 0 usb write error: **UNKNOWN**
[2013-11-26 22:54:38] usb_write error on avalon_write
Here I have both stacks on the same powered usb hub which connects to the Pi on its upper usb port and powers it as well.
Code:
sudo lsusb
Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 006: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
Bus 001 Device 007: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 005: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Code:
sudo ./cgminer/cgminer -n
[2013-11-26 22:56:31] USB all: found 7 devices - listing known devices
.USB dev 0: Bus 1 Device 7 ID: 0403:6001
Manufacturer: 'Burnin Electronics'
Product: 'BitBurner'
.USB dev 1: Bus 1 Device 6 ID: 0403:6001
Manufacturer: 'Burnin Electronics'
Product: 'BitBurner'
[2013-11-26 22:56:31] 2 known USB devices
spiccioli
Hi,
I have 8 boads in two stacks, first stack is hashing ok at 197 GHs.
BUT I have to connect it to the upper USB port of my RasPi, otherwise boards are not recognized, cgminer -n says it found no boards.
If I put a usb hub on the upper USB port of my RasPi no board is recognized, even if I connect a single board through its usb connector.
I have 8 boads in two stacks, first stack is hashing ok at 197 GHs.
BUT I have to connect it to the upper USB port of my RasPi, otherwise boards are not recognized, cgminer -n says it found no boards.
If I put a usb hub on the upper USB port of my RasPi no board is recognized, even if I connect a single board through its usb connector.
You have 2 stacks of 4 boards, each connected by CAN, right?
You have two USB cables running to the Pi, right?
What does Raspian or whatever Linux you use say if you type
Code:
lsusb
Hi dego,
yes, two stacks of four boards each.
My Pi is able to see them both only if I connect both to a powered usb hub and then I connect the powered usb hub to the upper usb port on the Pi.
If I connect each stack to a different port on the Pi only the stack connected to the upper port is seen and recognized by cgminer -n
Anyway, when both are connected, starting cgminer just throws usb write errors till the Pi freezes.
Here is cgminer -n when both are recognized
Code:
pi@raspberrypi ~ $ sudo ./cgminer/cgminer -n
[2013-11-26 22:27:53] USB all: found 7 devices - listing known devices
.USB dev 0: Bus 1 Device 8 ID: 0403:6001
Manufacturer: 'Burnin Electronics'
Product: 'BitBurner'
.USB dev 1: Bus 1 Device 6 ID: 0403:6001
Manufacturer: 'Burnin Electronics'
Product: 'BitBurner'
[2013-11-26 22:27:53] 2 known USB devices
and lsusb
Code:
pi@raspberrypi ~ $ sudo lsusb
Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 008: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 006: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
Bus 001 Device 007: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Code:
uname -a
Linux raspberrypi 3.6.11+ #538 PREEMPT Fri Aug 30 20:42:08 BST 2013 armv6l GNU/Linux
I've downloaded and compiled cgminer 3.5.0 following site instructions boards are recognized as BTB in cgminer.
I start cgminer like this
Code:
sudo ./cgminer/cgminer -o ... -u ... -p ... --avalon-options 115200:256:10:40:276 --bitburner-voltage 1360 --avalon-cutoff 63 --avalon-fan 75-90 --avalon-temp 55
When both stacks are connected I get this... f**k! this time it found both stacks! I've been trying since this afternoon, but even finding both stacks is not enough, It just reports HW errors and idled miners.
Code:
cgminer version 3.5.0 - Started: [2013-11-26 22:33:39]
--------------------------------------------------------------------------------
(5s):0.000 (avg):0.000h/s | A:0 R:0 HW:414 WU:0.0/m
ST: 0 SS: 0 NB: 1 LW: 18340 GF: 0 RF: 0
Connected to ....
Block: 0000c0aa867da6aa... Diff:609M Started: [22:33:39] Best share: 0
--------------------------------------------------------------------------------
[P]ool management [S]ettings [D]isplay options [Q]uit
BTB 0: 0C 276 0mV | 0.000/ 0.000h/s | A:0 R:0 HW:396 WU:0.0/m
BTB 1: 0C 276 0mV | 0.000/ 0.000h/s | A:0 R:0 HW: 19 WU:0.0/m
--------------------------------------------------------------------------------
[2013-11-26 22:33:28] Started cgminer 3.5.0
[2013-11-26 22:33:29] BTB0: Reset succeeded (Controller version: 2000000001)
[2013-11-26 22:33:31] BTB0: Idling 188 miners
[2013-11-26 22:33:31] BTB0: Core voltage set to 1360 millivolts
[2013-11-26 22:33:31] BTB1: Reset succeeded (Controller version: 2000073504)
[2013-11-26 22:33:33] BTB1: Idling 164 miners
[2013-11-26 22:33:33] BTB1: Core voltage set to 1360 millivolts
[2013-11-26 22:33:33] Probing for an alive pool
[2013-11-26 22:33:38] Pool 0 difficulty changed to 129
[2013-11-26 22:33:39] Network diff set to 609M
[2013-11-26 22:34:37] BTB0: Idled 1 miners
[2013-11-26 22:34:58] BTB1: Idled 1 miners
[2013-11-26 22:35:05] BTB0: Idled 1 miners
[2013-11-26 22:35:12] BTB1: Idled 1 miners
[2013-11-26 22:35:15] BTB0: Idled 1 miners
[2013-11-26 22:35:21] BTB0: Idled 1 miners
[2013-11-26 22:35:31] BTB1: Idled 1 miners
[2013-11-26 22:35:45] BTB1: Idled 1 miners
Any idea?
Thanks
spiccioli
Hi,
I have 8 boads in two stacks, first stack is hashing ok at 197 GHs.
BUT I have to connect it to the upper USB port of my RasPi, otherwise boards are not recognized, cgminer -n says it found no boards.
If I put a usb hub on the upper USB port of my RasPi no board is recognized, even if I connect a single board through its usb connector.
I have 8 boads in two stacks, first stack is hashing ok at 197 GHs.
BUT I have to connect it to the upper USB port of my RasPi, otherwise boards are not recognized, cgminer -n says it found no boards.
If I put a usb hub on the upper USB port of my RasPi no board is recognized, even if I connect a single board through its usb connector.
You have 2 stacks of 4 boards, each connected by CAN, right?
You have two USB cables running to the Pi, right?
What does Raspian or whatever Linux you use say if you type
Code:
lsusb
Here are the instructions on how to flash the Bitburner boards when USB is broken:
https://bitcointalksearch.org/topic/m.3371051
and these are the necessary files:
https://www.dropbox.com/s/nufnkse0ashwirt/Serials_7FFA.num
https://www.dropbox.com/s/yvn8df21v9s3bon/BitBurnerFury_for_production.hex
https://bitcointalksearch.org/topic/m.3371051
and these are the necessary files:
https://www.dropbox.com/s/nufnkse0ashwirt/Serials_7FFA.num
https://www.dropbox.com/s/yvn8df21v9s3bon/BitBurnerFury_for_production.hex
Hi,
I have 8 boads in two stacks, first stack is hashing ok at 197 GHs.
BUT I have to connect it to the upper USB port of my RasPi, otherwise boards are not recognized, cgminer -n says it found no boards.
If I put a usb hub on the upper USB port of my RasPi no board is recognized, even if I connect a single board through its usb connector.
How am I supposed to control two 4-boards stacks? with a RasPi every four boards?
What am I making wrong?
I'm using cgminer 3.5 and boards are recognized as BTB.
Any help truly appreciated!
spiccioli
I have 8 boads in two stacks, first stack is hashing ok at 197 GHs.
BUT I have to connect it to the upper USB port of my RasPi, otherwise boards are not recognized, cgminer -n says it found no boards.
If I put a usb hub on the upper USB port of my RasPi no board is recognized, even if I connect a single board through its usb connector.
How am I supposed to control two 4-boards stacks? with a RasPi every four boards?
What am I making wrong?
I'm using cgminer 3.5 and boards are recognized as BTB.
Any help truly appreciated!
spiccioli
Hey Guys,
We have already the Bitburner Fury Rev. 1.1
USB port is broken and we want to update the Firmware.
We know the steps! But we need the correct pin order on the Programmer Connector.
Can anybody help and know these pins?
THX
We have already the Bitburner Fury Rev. 1.1
USB port is broken and we want to update the Firmware.
We know the steps! But we need the correct pin order on the Programmer Connector.
Can anybody help and know these pins?
THX
I got my bitburners today and was thinking how i would update the firmware without usb. how is it done with the programmer connector?
Hey Guys,
We have already the Bitburner Fury Rev. 1.1
USB port is broken and we want to update the Firmware.
We know the steps! But we need the correct pin order on the Programmer Connector.
Can anybody help and know these pins?
THX
We have already the Bitburner Fury Rev. 1.1
USB port is broken and we want to update the Firmware.
We know the steps! But we need the correct pin order on the Programmer Connector.
Can anybody help and know these pins?
THX
I need a CAN bus cable, to connect two boards,
Can anyone help me where to get one?
CryptX is out of stock with them.
Will a JTAG cable work for 2 boards + termination jumpers? Thanks Can anyone help me where to get one?
CryptX is out of stock with them.
I don't know what the "is not an avalon" message means but it seems to work correctly if it hashes*. Maybe you should delete your cgminer.conf file. Maybe there are old settings in there and also your current settings might be saved in there... maybe thats the reason why changing the *.bat does not work.
I see you use standard values, not overvolted or something. I had around 42 Ghs per board with exactly those values. That would be what you get now. Just play around a bit with frequency and voltage values and I am sure you can get out some Ghs more.
eg, try to use these options on your your BBF ( use this line now and have 201.2 Ghs constantly):
--bitburner-fury-options 115200:128:10:40:282 --bitburner-fury-voltage 1360 --avalon-cutoff 63 --avalon-fan 80 --avalon-temp 55
you could also try these:
115200:128:10:d:280 at 1060
If you do not reach 198Ghs with this, then try to change frequency and voltage in controlled steps, until you find the right settings. just try it out but leave the boards running for at least 50k shares for each try because in the beginning the boards often throw a lot of HW-Errors...
*If you want to find out more here, try to check each board separately, maybe its only one board causing failures...
I see you use standard values, not overvolted or something. I had around 42 Ghs per board with exactly those values. That would be what you get now. Just play around a bit with frequency and voltage values and I am sure you can get out some Ghs more.
eg, try to use these options on your your BBF ( use this line now and have 201.2 Ghs constantly):
--bitburner-fury-options 115200:128:10:40:282 --bitburner-fury-voltage 1360 --avalon-cutoff 63 --avalon-fan 80 --avalon-temp 55
you could also try these:
115200:128:10:d:280 at 1060
If you do not reach 198Ghs with this, then try to change frequency and voltage in controlled steps, until you find the right settings. just try it out but leave the boards running for at least 50k shares for each try because in the beginning the boards often throw a lot of HW-Errors...
*If you want to find out more here, try to check each board separately, maybe its only one board causing failures...
ok i cant frind the cgminer config file, where is suppose to be?
i did the 2 lines you suggested for .BAT file, it worked but only the boards with the usb in them hashed the rest were doing nothing, but they were getting up to 48ghs that would when ran my first single board. hmmmm...
plus by the way BBF voltage 1360 didnt run, isnt 1100 max value for BBf voltage far as i know?
edit: ok just tried something else, flashed the cluster to this https://www.dropbox.com/s/tz9xukd4d75g5uq/BitBurnerFury_for_bootloader.hex, so they are back to BTB in cgminer, difference: cgminer startup it say 'reset succeeded' this time also says 'idling 128 miners' but same thing only the board with usb hashes although at a healthy 52ghs avg, now just need all of them at that speed!!
While moving these guys to upgrade my Saturn yesterday, I heard a crack as I unplugged one of the USB ports with little resistance (Seriously a piss poor job). Now the board doesn't hash at all, the green and yellow lights are blinking right when I CANBUS it to another board, but when I start cgminer, it doesn't blink red anymore and just cycles through yellow and green as if its communicating with the other board but now doesn't work with any of the other boards.
1. Did you terminate the CANBUS correctly? This means that the boards on BOTH ends of the CAN cable need to be terminated by 2 Jumpers each?
2. How many boards are in your stack?
3. What are u using to start cgminer? Please copy&paste the whole line
4. Did you do any firmware upgrades?
5. Did you try to plug mini usb in another board (not the one that might have a defective mini usb)?
I have a stack of 4 successfully CANBUS'ed together ~196Gh/s. Then another pair, the 'dumb' pair. One with flashed firmware to try to get it above that damn 12Gh/s and the one with the broken usb that actually managed to revive itself from the dead last night. I had switched my PSUs for my Saturn and this stack and it must not have liked the switch initially. I went from 1050W XFX to a 750W Seasonic for this stack. Last night it came back online and I have it CANBUS connected with the 12Gh/s to come out to ~61Gh/s.
My settings are:
"avalon-cutoff" : "64",
"avalon-options" : "115200:64:10:50:278",
"bitburner-voltage" : "1360",
"bitburner-fury-options" : "115200:32:10:50:278",
"bitburner-fury-voltage" : "1060",
The underperforming board is also about ~20C cooler than the others. I will try the newest firmware and see if that helps. All my other boards are running the stock firmware so hence the 64 for Avalon options. If it aint broke don't fix it has been my method with the good 4.
Just fyi:
4 boards, connected by CANBus:
This firmware from asic-shop.com: https://www.dropbox.com/s/tz9xukd4d75g5uq/BitBurnerFury_for_bootloader.hex
using this:
cgminer --usb 1:7 --disable-gpu --avalon-options 115200:128:10:45:280 --bitburner-voltage 1360 --avalon-cutoff 63 --avalon-fan 80 --avalon-temp 55
HW-Error Rate is: 3.87
might try to tweak further, will keep you posted..
4 boards, connected by CANBus:
This firmware from asic-shop.com: https://www.dropbox.com/s/tz9xukd4d75g5uq/BitBurnerFury_for_bootloader.hex
using this:
cgminer --usb 1:7 --disable-gpu --avalon-options 115200:128:10:45:280 --bitburner-voltage 1360 --avalon-cutoff 63 --avalon-fan 80 --avalon-temp 55
HW-Error Rate is: 3.87
might try to tweak further, will keep you posted..
Hey what are the improvements with the firmware? Is it worth the effort? Thanks a lot.
I don't know what the "is not an avalon" message means but it seems to work correctly if it hashes*. Maybe you should delete your cgminer.conf file. Maybe there are old settings in there and also your current settings might be saved in there... maybe thats the reason why changing the *.bat does not work.
I see you use standard values, not overvolted or something. I had around 42 Ghs per board with exactly those values. That would be what you get now. Just play around a bit with frequency and voltage values and I am sure you can get out some Ghs more.
eg, try to use these options on your your BBF ( use this line now and have 201.2 Ghs constantly):
--bitburner-fury-options 115200:128:10:40:282 --bitburner-fury-voltage 1360 --avalon-cutoff 63 --avalon-fan 80 --avalon-temp 55
you could also try these:
115200:128:10:d:280 at 1060
If you do not reach 198Ghs with this, then try to change frequency and voltage in controlled steps, until you find the right settings. just try it out but leave the boards running for at least 50k shares for each try because in the beginning the boards often throw a lot of HW-Errors...
*If you want to find out more here, try to check each board separately, maybe its only one board causing failures...
I see you use standard values, not overvolted or something. I had around 42 Ghs per board with exactly those values. That would be what you get now. Just play around a bit with frequency and voltage values and I am sure you can get out some Ghs more.
eg, try to use these options on your your BBF ( use this line now and have 201.2 Ghs constantly):
--bitburner-fury-options 115200:128:10:40:282 --bitburner-fury-voltage 1360 --avalon-cutoff 63 --avalon-fan 80 --avalon-temp 55
you could also try these:
115200:128:10:d:280 at 1060
If you do not reach 198Ghs with this, then try to change frequency and voltage in controlled steps, until you find the right settings. just try it out but leave the boards running for at least 50k shares for each try because in the beginning the boards often throw a lot of HW-Errors...
*If you want to find out more here, try to check each board separately, maybe its only one board causing failures...
Just fyi:
4 boards, connected by CANBus:
This firmware from asic-shop.com: https://www.dropbox.com/s/tz9xukd4d75g5uq/BitBurnerFury_for_bootloader.hex
using this:
cgminer --usb 1:7 --disable-gpu --avalon-options 115200:128:10:45:280 --bitburner-voltage 1360 --avalon-cutoff 63 --avalon-fan 80 --avalon-temp 55
HW-Error Rate is: 3.87
might try to tweak further, will keep you posted..
4 boards, connected by CANBus:
This firmware from asic-shop.com: https://www.dropbox.com/s/tz9xukd4d75g5uq/BitBurnerFury_for_bootloader.hex
using this:
cgminer --usb 1:7 --disable-gpu --avalon-options 115200:128:10:45:280 --bitburner-voltage 1360 --avalon-cutoff 63 --avalon-fan 80 --avalon-temp 55
HW-Error Rate is: 3.87
might try to tweak further, will keep you posted..
hi dego, ive got a 4 board cluster and been trying to get it running last couple of days. crypt x has helped a lot, but i must be missing something.
ok first i couldnt get the four to work with the can bus, so was told to upgrade cgminer to latest version. did that v3.8.2, done many flashes of the firmware, latest one was the https://www.dropbox.com/s/l87xnp5mdfg6f8y/bitburner-fury-firmware_1.2.6_BBF.hex so now it reads as BBF in cgminer.
batch as follows :
cgminer -o http://mint.bitminter.com:80 -u zulover_bitzu2 -p x
--bitburner-fury-options 115200:128:10:50:256 --bitburner-fury-voltage 900
when cgminer starts up it says 'reset failed! not an avalon?'
but goes on t function but only averaging 170ghs.
tried to change the freq and volt setting in BAT file file but they dont take effect it always runs on default.
also crypt x said to only have jumpers on the last board in the cluster and have usb on the first board with cancable used. it seems to work.
any advice most appreciated.
Jump to: