Topic: BITBURNER FURY Technical discussion (Read 18264 times)

Is that in perfect working condition? hashrate?

Unfortunately I'm in the states, so shipping would be a bitch. Thanks for the offer though.

I got one that I am willing to sell.
within EU to avoid customs troubles etc.

Would these still be a good buy today? Looking at the kw/Gh/s they still look pretty competitive with the Antminer S1's out there.

I am pretty sure this isn't being manufactured at this time. You may be able to find use ones available in the marketplace.

whether the stock for this item is out of stock?

Somebody can make iso of SD card? , my card is broken, and i need working image...

No i mean the can termination Jumpers:
https://www.asic-hardware.com/assembly-instructions-part-2/

You need 2 per board to get them to work.

You mean to power both the boards?

I have a seperate powerupply for each board.

Did you put in the jumper's?
Without jumper the can-bus wont work...

Need some help,
So I had a bitburner fury a while back just a single board and after about a week the USB snapped off.

Recently I have recieved another 2 boards in the hope of mining using the other board using a ribbon cable.

I have plugged the ribbon cable intot he one with the missing usb port and the other end into one with a usb port and tried to mine but it just wont. The light on the miner stays a steady flashing green and refuses to mine. I have read that you need to update the firmware on the device to get it working but I can remember doing so before the port snapped off, If you need to do it again with the ribbon cable in what should i do? the usb port has snapped off so there is no way of upadting the board. Right now it is as useful as a flashing vegtable.

thanks for any help guys!

You could try to "CANBUS" it to a working board

It happened to me  too 1 week ago when just stopped out of the blue.The board  turns on ok, green led blinking but no pc can detect it anymore . I'd like to mention that my micro usb connector is firm and tight, soldered onto the board as I ironed & hot glued it first time after I unpacked  6 months ago. Any suggestions are welcomed, thx!

Hi guys,

I have the same problem with my Bitburner Fury. Green LED is blinking and my pc can't detect Bitburner board. But, when I moving USB cable on USB port I noticed this in my syslog (connected, disconnected, conencted, disconnected): http://pastebin.com/pVZTshqg and then red LED comes up and after that green LED and so on (device reboot )
Any clues ? Is there a usb port problem, firmware issue ?
Thanks for your answer in advance.

This is all AFAIK as a second hand BBF owner.  I don't think there is any reason to update boards with broken USB port.  To connect a board without a USB port you will need a board with a USB port, 4 jumpers and a CANBUS cable.   You only need to update boards with a USB port that you want to connect to the latest cgminer versions.

Hi, guys,
  I tried to pawn off my Bitburner Fury with the broken USB port and the buyer is shipping it back. I'd love to use this thing if I could, but following the steps to use the PickIt don't seem to work. What mining software do you all use?

Any tips for me? Even if I buy a second one with an unbroken USB port, I'd be happy. Unless I screwed up the firmware trying to fix this one.

I used the information in this article: https://bitcointalksearch.org/topic/m.3371051

If you've been successful at this kind of installation, please let me know. Otherwise, want my miner when the buyer ships it back?

--Mpellet771

Does this solve the 12~14 GHs issue?  

Pickit instructions from ASIC-HARDWARE

Here are some guidelines to install the firmware onto the board:

If there was an install CD, you should install the drivers.
You will need to install MPLAB X IPE ( http://www.microchip.com/mplabx-ide-windows-installer ).

Startup MPLABX IPE (if you have version 1.9, you will need to downgrade to v1.8 as it has a bug).
You can downgrade by replacing the ipe.jar (in attachment) located in C:\Program Files (x86)\Microchip\MPLABX\mplab_ide\bin

If downgrade is successful, start up MPLABX IPE again, select 'Settings' -> 'Advanced Mode' -> enter password 'microchip' -> 'logon'

on the screen select the following options:
- Family: 32-Bit MCUs
- Device: PIC32MX564F128H
- Tool: select available PICKIT3 tool (make sure it is inserted into the USB)

Press 'Apply'

Source: use the browse button to select the 'BitBurnerFury_for_production.hex' file (see attachment)
SQTP / Serial: use the browse button to select 'Serials_7FFA.num' file

Power up the board and place the PicKit3 on the 5 pins on the board (you see 5 pins aligned on the board, first pin is the one closest to you, the front-side of the pickKit3 (side with the text ans arrow) should be faced towards the left side of the board (the side where the CAN-BUS is located).

Press 'Connect'.
If connection is succesfull, press 'Program'

After 'Program' is completed, the new firmware is installed and you can disconnect the PicKit and use your board for mining.

Hi, I have two boards which run at approximately 12-15 GHs no matter what firmware or connection I use.

Upon thermal inspection I noticed that only less than half of the ASIC chips actually warm up when CGMiner runs.

Any hints on fixing the problem?

Hi guys,
Unfortunately my BBF a while ago has stopped working - its not detectable anymore on USB bus, however LEDs are suggesting that device itself it fine.  I found this thread - https://bitcointalksearch.org/topic/m.3371051
I bought PIcKIT3 programmer, downloaded firmwares from this thread (URLs are some posts above)
But unfortunately Im unable to fix the device properly - while trying to load Serials_7FFA.num file Im getting such messages :

2014-03-31T22:13:52+0200- Loading hex file. Please wait...
Loading code from C:\Users\voyo\Downloads\bitburnet fury\BitBurnerFury_for_production.hex...
2014-03-31T22:13:54+0200- Hex file loaded successfully.

2014-03-31T22:13:56+0200- Loading SQTP file. Please wait...
2014-03-31T22:13:56+0200- The SQTP file contains address which is invalid for this device.

Seems I have wrong SQTP file ?  Please advice ....