Restart pc , it shd help and cgminer 3.5.1. At least
Did restart. Nothing. Switched USB ports. And cgminer isn't helping me at all since i can't flash the boards.
Edit: What are the default settings. Maybe they will work with the original firmware.
Topic: Bitburner Fury - Hashrate Protection - page 6. (Read 250127 times)
Did restart. Nothing. Switched USB ports. And cgminer isn't helping me at all since i can't flash the boards.
Edit: What are the default settings. Maybe they will work with the original firmware.
Restart pc , it shd help and cgminer 3.5.1. At least
Hello,
I can`t flash my Fury Burners. Yesterday I´ve got one flashed, but today the other Bitburner Furies aren`t recognized in PIC32 Bootloader.
I see the Bootloader in the Zadig driver tool (before it becomes Bitburner), which has the same USB ID as in PIC32.
But I can`t connect with PIC32, because the USB ID isn`t found.
I´m using Windows 7. Perhaps I`m using the wrong USB driver (WinUSB). Does anybody have a clue?
I can`t flash my Fury Burners. Yesterday I´ve got one flashed, but today the other Bitburner Furies aren`t recognized in PIC32 Bootloader.
I see the Bootloader in the Zadig driver tool (before it becomes Bitburner), which has the same USB ID as in PIC32.
But I can`t connect with PIC32, because the USB ID isn`t found.
I´m using Windows 7. Perhaps I`m using the wrong USB driver (WinUSB). Does anybody have a clue?
Just received my boards and i have the same problem. I can't see the boards in PIC32. I get this error: USB Device with VID=0x4D8 and PID=0x3C is not found. Tried reinstalling zadig drives and same thing. Suggestions?
Hello,
I can`t flash my Fury Burners. Yesterday I´ve got one flashed, but today the other Bitburner Furies aren`t recognized in PIC32 Bootloader.
I see the Bootloader in the Zadig driver tool (before it becomes Bitburner), which has the same USB ID as in PIC32.
But I can`t connect with PIC32, because the USB ID isn`t found.
I´m using Windows 7. Perhaps I`m using the wrong USB driver (WinUSB). Does anybody have a clue?
I can`t flash my Fury Burners. Yesterday I´ve got one flashed, but today the other Bitburner Furies aren`t recognized in PIC32 Bootloader.
I see the Bootloader in the Zadig driver tool (before it becomes Bitburner), which has the same USB ID as in PIC32.
But I can`t connect with PIC32, because the USB ID isn`t found.
I´m using Windows 7. Perhaps I`m using the wrong USB driver (WinUSB). Does anybody have a clue?
For those who are getting "usb_write" errors and are unable to power cycle the boards, here is some firmware:
https://www.dropbox.com/s/x9zhnm86uuzcn05/bitburner-fury-firmware_1.2.6.hex (BTB identifier, for cgminer < 3.6.0)
https://www.dropbox.com/s/l87xnp5mdfg6f8y/bitburner-fury-firmware_1.2.6_BBF.hex (BBF identifier, for cgminer >= 3.6.0)
This adds a soft watchdog which will auto-reset the microcontroller if the main thread blocks. This doesn't fix the cause of the usb_write errors (I'm still working on that), but it means that if they do occur, your boards won't sit there doing nothing.
https://www.dropbox.com/s/x9zhnm86uuzcn05/bitburner-fury-firmware_1.2.6.hex (BTB identifier, for cgminer < 3.6.0)
https://www.dropbox.com/s/l87xnp5mdfg6f8y/bitburner-fury-firmware_1.2.6_BBF.hex (BBF identifier, for cgminer >= 3.6.0)
This adds a soft watchdog which will auto-reset the microcontroller if the main thread blocks. This doesn't fix the cause of the usb_write errors (I'm still working on that), but it means that if they do occur, your boards won't sit there doing nothing.
Thanks someone42, that's great. Do you have a feeling for why we're seeing these errors? I've not had a problem since connecting the fan directly to a 12V supply, which cools the board a lot more effectively. This may be a coincidence, but is the usb_write error potentially due to overheating or is it completely unrelated?
For those who are getting "usb_write" errors and are unable to power cycle the boards, here is some firmware:
https://www.dropbox.com/s/x9zhnm86uuzcn05/bitburner-fury-firmware_1.2.6.hex (BTB identifier, for cgminer < 3.6.0)
https://www.dropbox.com/s/l87xnp5mdfg6f8y/bitburner-fury-firmware_1.2.6_BBF.hex (BBF identifier, for cgminer >= 3.6.0)
This adds a soft watchdog which will auto-reset the microcontroller if the main thread blocks. This doesn't fix the cause of the usb_write errors (I'm still working on that), but it means that if they do occur, your boards won't sit there doing nothing.
https://www.dropbox.com/s/x9zhnm86uuzcn05/bitburner-fury-firmware_1.2.6.hex (BTB identifier, for cgminer < 3.6.0)
https://www.dropbox.com/s/l87xnp5mdfg6f8y/bitburner-fury-firmware_1.2.6_BBF.hex (BBF identifier, for cgminer >= 3.6.0)
This adds a soft watchdog which will auto-reset the microcontroller if the main thread blocks. This doesn't fix the cause of the usb_write errors (I'm still working on that), but it means that if they do occur, your boards won't sit there doing nothing.
tried a lot of configurations but only getting around 19 GH/Sec out of my fury 
that sucks!
that sucks!
How many idled miner when you first start your cgminer? My 4 boards perform badly when there is only 33 idled miners from 64 miners that I specify on avalon options. Have to restart the board again to get it back to 64 miners.
I get: BTB0: Idling 32 miners with 1 board - that seems OK
tried a lot of configurations but only getting around 19 GH/Sec out of my fury
that sucks!
that sucks!
How many idled miner when you first start your cgminer? My 4 boards perform badly when there is only 33 idled miners from 64 miners that I specify on avalon options. Have to restart the board again to get it back to 64 miners.
edited: fedex guy just came - though didnt had any tracking in my mail
tried a lot of configurations but only getting around 19 GH/Sec out of my fury
that sucks!
that sucks!
I've been trying to follow this thread, but may have missed this: Has anyone found the best/cheapest place to order the standoffs to prop these things off the ground, like in the pics?
I don't care
I know the parameters - I asked whether anyone cared. It appears you don't :-)
There is more than 2 parameters for the avalon driver... How do you do if you want different fan speeds and so on ?
So you should duplicate every parameter with 'bitfury' and make a 2 in 1 driver
Or create a new BBF (avalon base) driver ...
So you should duplicate every parameter with 'bitfury' and make a 2 in 1 driver
Or create a new BBF (avalon base) driver ...
Are there other parameters many people really care about?
roy
--avalon-cutoff
--avalon-fan
--avalon-options
--avalon-temp
I don't care , i don't have other avalon hardware
But i you want control BBT and BBF on the same cgminer it make sense
There is more than 2 parameters for the avalon driver... How do you do if you want different fan speeds and so on ?
So you should duplicate every parameter with 'bitfury' and make a 2 in 1 driver
Or create a new BBF (avalon base) driver ...
So you should duplicate every parameter with 'bitfury' and make a 2 in 1 driver
Or create a new BBF (avalon base) driver ...
Are there other parameters many people really care about?
roy
Would it be possible to make it listen to "--bitburner-fury-options" instead of the --avalon-options parameter? That would make it possible to run both Bitburner XX and Bitburner Fury devices in 1 CGminer window.
I think you have to contact Kano or SomeOne42 - should be makeable I think. Just saw there is a new firmware what displays the fury different than the avalon.
I think it should be easy enough. I was planning to submit a patch to do that but won't have time to work on it until the weekend so if someone else (or even someone42 else
has time to do it before me...roy
Just to prevent double work
I've also posted the question here: https://bitcointalksearch.org/topic/m.3357797There is more than 2 parameters for the avalon driver... How do you do if you want different fan speeds and so on ?
So you should duplicate every parameter with 'bitfury' and make a 2 in 1 driver
Or create a new BBF (avalon base) driver ...
[I think somebody mentioned in an earlier post that the fan control on the boards is a bit conservative and the fans on these things run pretty slow most of the time. My experience is that it's definitely worth plugging the fan directly into a 12V supply (using a molex adaptor etc.) It's a bit noisier, but my board temp went down by nearly 10 oC and so far its been stable like this - fingers crossed it stays this way! Is there any chance that the "usb_write error on avalon_write" error is related to one of the components overheating?
I assumed the fan is controlled by cgminer, like on the real Avalon rigs. So if you want the fan to run faster, either set the target temperature lower (e.g. --avalon-temp 40) - but note that it will take longer to cool down again to the target temperature if the unit shuts down due to overheat.
Or alternatively just force the fan to full speed (i.e. --avalon-fan 100)
roy
ETA: Or perhaps it was just my imagination that these made any difference.... and it is all controlled by the firmware?
In any case, I'm hashing fine without either of the above options. My boards usually run about 56-58C, so I've increased the shutdown temperature slightly from 60C to 62C to avoid the very occasional accidental shutdown.... Obviously increasing that is risky so you do this at your own risk.
Is there a way to recover from the dreaded "usb_write error on avalon_write" error without power cycling the miner?
I'm getting it now and I'm not at home to power cycle it. No matter how many times I reboot my pi or restart cgminer seems to fix it.
I'm getting it now and I'm not at home to power cycle it. No matter how many times I reboot my pi or restart cgminer seems to fix it.
+1 fixing this would be great!
This already drove me this angry that I've put the device for sale... However, after seeing the bids I don't think I will sell the device +2 . Would like to upvote this. Running on a PI and then doing a sudo reboot. The only way to get it back is to power cycle the boards
The ironic thing is I had a WeMo attached to it so I could reboot it remotely. But then I noticed my raspberry pi was crashing from time to time (I'm not sure why, my other pis never crash) so I moved the WeMo to the pi. Within an hour the BitBurner had crashed! I didn't have the time to run home yet again to reboot it so it's going to have to wait till after work now. I'll probably lose a quarter of a bitcoin because of it
. Fortunately I have another WeMo, so WeMos are going on both the pi and the miner now.Has anybody else found that recovering after the "usb_write error on avalon_write" error by power cycling the board leaves it in a rather unstable state and likely to give the same error again fairly soon afterwards? This has happened to me a couple of times and only re-flashing the firmware resulted in a stable system (could be coincidence of course) - does this error have anything to do with (or potentially cause) firmware corruption?
I think somebody mentioned in an earlier post that the fan control on the boards is a bit conservative and the fans on these things run pretty slow most of the time. My experience is that it's definitely worth plugging the fan directly into a 12V supply (using a molex adaptor etc.) It's a bit noisier, but my board temp went down by nearly 10 oC and so far its been stable like this - fingers crossed it stays this way! Is there any chance that the "usb_write error on avalon_write" error is related to one of the components overheating?
Is there a way to recover from the dreaded "usb_write error on avalon_write" error without power cycling the miner?
I'm getting it now and I'm not at home to power cycle it. No matter how many times I reboot my pi or restart cgminer seems to fix it.
I'm getting it now and I'm not at home to power cycle it. No matter how many times I reboot my pi or restart cgminer seems to fix it.
+1 fixing this would be great!
This already drove me this angry that I've put the device for sale... However, after seeing the bids I don't think I will sell the device +2 . Would like to upvote this. Running on a PI and then doing a sudo reboot. The only way to get it back is to power cycle the boards
The ironic thing is I had a WeMo attached to it so I could reboot it remotely. But then I noticed my raspberry pi was crashing from time to time (I'm not sure why, my other pis never crash) so I moved the WeMo to the pi. Within an hour the BitBurner had crashed! I didn't have the time to run home yet again to reboot it so it's going to have to wait till after work now. I'll probably lose a quarter of a bitcoin because of it
. Fortunately I have another WeMo, so WeMos are going on both the pi and the miner now. Would it be possible to make it listen to "--bitburner-fury-options" instead of the --avalon-options parameter? That would make it possible to run both Bitburner XX and Bitburner Fury devices in 1 CGminer window.
I think you have to contact Kano or SomeOne42 - should be makeable I think. Just saw there is a new firmware what displays the fury different than the avalon.
I think it should be easy enough. I was planning to submit a patch to do that but won't have time to work on it until the weekend so if someone else (or even someone42 else
has time to do it before me...roy
Just to prevent double work
I've also posted the question here: https://bitcointalksearch.org/topic/m.3357797Well, when I get my XX boards set up and my Fury boards reflashed then either there'll be something already there I can download - or I'll have the incentive to do the work so I can mine with my XX boards :-) I'll be perfectly happy if someone else works on this, since I'm not giving any guarantees I'll work on this this weekend
-roy
ETA: But I have to pluck up the courage to do the reflashing - and that means plugging in another USB cable, which is kinda scary from what I've read here
Would it be possible to make it listen to "--bitburner-fury-options" instead of the --avalon-options parameter? That would make it possible to run both Bitburner XX and Bitburner Fury devices in 1 CGminer window.
I think you have to contact Kano or SomeOne42 - should be makeable I think. Just saw there is a new firmware what displays the fury different than the avalon.
I think it should be easy enough. I was planning to submit a patch to do that but won't have time to work on it until the weekend so if someone else (or even someone42 else
has time to do it before me...roy
Just to prevent double work
I've also posted the question here: https://bitcointalksearch.org/topic/m.3357797 Jump to: