Bitcoin Forum

Other => Off-topic => Topic started by: bonks on June 19, 2012, 07:56:10 PM



Title: BFL Single Failed Diagnostics
Post by: bonks on June 19, 2012, 07:56:10 PM
Anyone know how to fix this? It shipped with the 816 firmware and I noticed the hashrate was double, 1632MH/s, and submitted shares twice.

I changed the firmware to 808 and it still does the same thing. I also tried different psu bricks from my other singles, usb cables, and a different host computer.

Here are the diagnostics result:
https://i.imgur.com/aFZDF.jpg

Any ideas?


Title: Re: BFL Single Failed Diagnostics
Post by: BFL on June 19, 2012, 08:02:37 PM
Anyone know how to fix this? It shipped with the 816 firmware and I noticed the hashrate was double, 1632MH/s, and submitted shares twice.

I changed the firmware to 808 and it still does the same thing. I also tried different psu bricks from my other singles, usb cables, and a different host computer.

Here are the diagnostics result:
https://i.imgur.com/aFZDF.jpg

Any ideas?

It sounds like the firmware upload process isn't completed.  Please try that again to completion and then power cycle your unit.


Title: Re: BFL Single Failed Diagnostics
Post by: yjacket on June 19, 2012, 08:57:14 PM
Right click on the unit and select device information. Post of screenshot of what it says here. I had a similar problem with one of my singles.


Title: Re: BFL Single Failed Diagnostics
Post by: bonks on June 19, 2012, 09:58:04 PM
Looks like I needed to power cycle after firmware change.

It took me a while to get back because I wanted to try a few firmwares.

896 is completely unstable.
832 is unreliable.
816 is the stock firmware and gave me issues.
808 gave me no errors or throttling.

I will run 808 on my main rig and see how it goes.

Thanks guys!

https://i.imgur.com/rFNVu.jpg
https://i.imgur.com/t387e.jpg


Title: Re: BFL Single Failed Diagnostics
Post by: GernMiester on June 19, 2012, 11:13:31 PM
Hmmm...
If your PC is overclocked slow things down a few notches and reflash the BFL with a non experimental firmware. Try another USB hub and or port.
Run the 768 experimental firmware. It should not fail its own diagnostics using the standard firmwares when it is within the proper ambient temperature.
Contact them of course.