vancenkansas
Newbie
 Offline
Activity: 24
Merit: 0
|
 |
December 19, 2016, 01:36:06 AM |
|
the rest will probably never get a firmware update, it's too risky.
Amen |
|
|
|
|
|
|
|
|
|
|
|
The network tries to produce one block per 10 minutes. It does this by automatically adjusting how difficult it is to produce blocks.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
VentMine
|
|
December 19, 2016, 03:33:23 AM |
|
the rest will probably never get a firmware update, it's too risky.
Amen Do many others echo this thought? I am interested in knowing if updates have really been a pain in the past, if so I will also go with the "If it ain't broke, don't fix it" approach for my own mine. |
1ESSdoVYKm8sNtYMfdkFBajhAe2e6G8keH
|
|
|
takagari
Legendary
Offline
Activity: 1050
Merit: 1000
|
|
December 19, 2016, 03:50:56 AM |
|
Pretty well how i mine.
Did ine uograde for the noise.
But unless the fw is proven to offer a good reason to try. I leave it alone.
|
|
|
|
|
captinkid
Newbie
Offline
Activity: 38
Merit: 0
|
|
December 19, 2016, 06:03:35 AM
Last edit: December 19, 2016, 06:13:44 AM by captinkid |
|
I now just tried with the PICkit3 to: 1. Read a good PIC firmware from a good hash board 2. Write a good PIC firmware to a dead hash board No effect. The dead hash board is still dead. So it is probably not just "soft bricked". So I wait for the answer from BitmainWarranty ( www.bitmainwarranty.com). I have previous experience with the PICkit3. Do you have the image file from the good hash board? I'd like to have a look at it if you could send it to me. In what way is your board dead? Mine died immediately AFTER a firmware update, it never hashed on the new firmware, so I'm pretty sure it's software related, unless the bad software caused something to overheat. Bitmain thinks it's an incompatible firmware, which is weird because they said it was for "all" but we'll see if they can help me. They responded to my first e-mail and I gave them more information, now I'm waiting to hear back. Thankfully I only flashed one of my S9's, the rest will probably never get a firmware update, it's too risky. Here is the HEX-file PIC16F1704_firmware_good_condition_board_S9_11.85ths_model_non-autotune.hex : https://mega.nz/#!4l8HzB7A!R_Fomh8O5uSk8VVqmRseGduxSbvl_ajDNcATl3z22hAMake sure that you know what you are doing. I take no responsibility on this.My board went dead just suddenly without any warning. Fully understood, I appreciate it! I don't intend to use it right away, I want to hear back from Bitmain on a solution, if that route fails I'm going to read mine and compare with yours, look for differences. And then write back as a last resort. If Bitmain can't help, they're dead boards anyway, so nobody to blame for me messing them up more.  |
|
|
|
|
captinkid
Newbie
Offline
Activity: 38
Merit: 0
|
|
December 19, 2016, 06:10:32 AM |
|
the rest will probably never get a firmware update, it's too risky.
Amen Do many others echo this thought? I am interested in knowing if updates have really been a pain in the past, if so I will also go with the "If it ain't broke, don't fix it" approach for my own mine. Most firmware updates from reputable companies have a change list and give you a clear idea that it's had some quality control testing. And in those cases even they usually only recommend to flash new firmware when there is a problem or clear bug. With Bitmain it's different, they toss out whatever code wise, often reportedly violating code licenses and not listing a changelog, and then they try to clean up the mess afterwards. So with this particular company I'd say it's much safer to not update your firmware unless you have a major known problem that you are fixing. |
|
|
|
|
captinkid
Newbie
Offline
Activity: 38
Merit: 0
|
|
December 19, 2016, 07:37:29 PM
Last edit: December 20, 2016, 06:55:47 PM by captinkid |
|
Looks like the PIC firmware, and the software the single-board-test flashes to part of the PIC are different.
19.2kb from the hash_s8_app.txt file
23.1kb from the pic firmware dump
Something like the PIC firmware controls the PIC, and the app file controls the hashing and mining and communication to the controller functions.
It's just a guess right now. But it looks like both have to be properly flashed for it to function.
(UPDATE)
After several troubleshooting steps that I had already done (Such as isolating boards, changing power supplies, and rotating 18 pin data cables) They gave me a canned "Ship defective parts back for repair". I was hoping for a firmware or software patch that hadn't been seen yet, but no luck.
The only helpful thing was they had me go back to the 7/15 firmware, which through my prior testing was the last good firmware for mine. I have the last of the non autotune miners that were released. The one with failed boards looks like it was probably returned as a refurb, because it's an older model than the other three s9's I have,
Guess they're keeping the nice software tools and tricks to themselves. I get my pickit 3 soon, so I'll have a go at figuring out which data on the hash board is munged up, as I'm 99% sure that's the problem. Now that customer support has officially failed me I've got a toy to experiment with.
|
|
|
|
|
|
PeaMine
|
|
December 21, 2016, 05:48:52 AM |
|
I tried updating one of my first S9s I think it was 550mhz I updated first to the new auto tune firmware, but nothing happened even after setting pools and rebooting. So then I loaded the S9 recovery firmware, and it started working again. Then try the new autotune firmware, and I'm getting this (I think one board has always been dead, so that is not a surprise) Is it ever going to start hashing? Been 2 hours. check PIC voltage=940 on chain[0]
check PIC voltage=940 on chain[2]
check PIC voltage=940 on chain[3]
set command mode to VIL
singleBoardTest: AsicType = 1387
singleBoardTest: asicNum = 64
singleBoardTest: real AsicNum = 63
--- check asic number
set_baud=0, ought to be 1
The min freq=700
set real timeout 52, need sleep=379392
search freq for 1 times, completed chain = 3, total chain num = 3
disable_pic_dac on chain[0]
disable_pic_dac on chain[2]
disable_pic_dac on chain[3]
restart Miner chance num=2
waiting for send_func to exit of chain[0]
waiting for send_func to exit of chain[1]
waiting for send_func to exit of chain[2]
waiting for send_func to exit of chain[3]
waiting for send_func to exit of chain[4]
waiting for send_func to exit of chain[5]
waiting for send_func to exit of chain[6]
waiting for send_func to exit of chain[7]
waiting for send_func to exit of chain[8]
waiting for send_func to exit of chain[9]
waiting for send_func to exit of chain[10]
waiting for send_func to exit of chain[11]
waiting for send_func to exit of chain[12]
waiting for send_func to exit of chain[13]
waiting for send_func to exit of chain[14]
waiting for send_func to exit of chain[15]
waiting for receive_func to exit!
waiting for pic heart to exit!
Start bmminer ...
This is C5 board.
Check chain[0] PIC fw version=0x02
Check chain[2] PIC fw version=0x02
Check chain[3] PIC fw version=0x02
Chain[J1] will use highest voltage=940 [6] to open core
Chain[J3] will use highest voltage=940 [6] to open core
Chain[J4] will use highest voltage=940 [6] to open core
Chain[J1] orignal chain_voltage=6 value=940
Chain[J3] orignal chain_voltage=6 value=940
Chain[J4] orignal chain_voltage=6 value=940
Chain[J1] has 0 asic
retry Chain[J1] has 0 asic
retry Chain[J1] has 0 asic |
Datacenter Technician and Electrician. If you have any questions feel free to ask me as I am generally bored looking at logs and happy to help during free time.
|
|
|
|
mamiakimo
|
|
December 21, 2016, 07:59:47 AM |
|
I tried updating one of my first S9s I think it was 550mhz I updated first to the new auto tune firmware, but nothing happened even after setting pools and rebooting. So then I loaded the S9 recovery firmware, and it started working again. Then try the new autotune firmware, and I'm getting this (I think one board has always been dead, so that is not a surprise) Is it ever going to start hashing? Been 2 hours. check PIC voltage=940 on chain[0]
check PIC voltage=940 on chain[2]
check PIC voltage=940 on chain[3]
set command mode to VIL
singleBoardTest: AsicType = 1387
singleBoardTest: asicNum = 64
singleBoardTest: real AsicNum = 63
--- check asic number
set_baud=0, ought to be 1
The min freq=700
set real timeout 52, need sleep=379392
search freq for 1 times, completed chain = 3, total chain num = 3
disable_pic_dac on chain[0]
disable_pic_dac on chain[2]
disable_pic_dac on chain[3]
restart Miner chance num=2
waiting for send_func to exit of chain[0]
waiting for send_func to exit of chain[1]
waiting for send_func to exit of chain[2]
waiting for send_func to exit of chain[3]
waiting for send_func to exit of chain[4]
waiting for send_func to exit of chain[5]
waiting for send_func to exit of chain[6]
waiting for send_func to exit of chain[7]
waiting for send_func to exit of chain[8]
waiting for send_func to exit of chain[9]
waiting for send_func to exit of chain[10]
waiting for send_func to exit of chain[11]
waiting for send_func to exit of chain[12]
waiting for send_func to exit of chain[13]
waiting for send_func to exit of chain[14]
waiting for send_func to exit of chain[15]
waiting for receive_func to exit!
waiting for pic heart to exit!
Start bmminer ...
This is C5 board.
Check chain[0] PIC fw version=0x02
Check chain[2] PIC fw version=0x02
Check chain[3] PIC fw version=0x02
Chain[J1] will use highest voltage=940 [6] to open core
Chain[J3] will use highest voltage=940 [6] to open core
Chain[J4] will use highest voltage=940 [6] to open core
Chain[J1] orignal chain_voltage=6 value=940
Chain[J3] orignal chain_voltage=6 value=940
Chain[J4] orignal chain_voltage=6 value=940
Chain[J1] has 0 asic
retry Chain[J1] has 0 asic
retry Chain[J1] has 0 asic it need 10-25 minutes to open, so be patient |
|
|
|
|
d57heinz
Legendary
Offline
Activity: 1453
Merit: 1011
Bitcoin Talks Bullshit Walks
|
|
December 21, 2016, 12:51:34 PM |
|
@bitmaintech
So I have a batch 11 I believe it was. They run at 550 MHz. My intake air atm is less than 0c. What will happen to this miner come summer if I upgrade to new fw. I was able to downclock to 500 last summer as 30+c was too much for them. So in looking at temps of chips I'm not impressed at the cooling. Pulling in -14c only dropped chips temps to 80c. That's terrible cooling. So if I upgrade to this auto tune fw. What is going to happen to my miner when temps rise. I have a pretty good idea. I just want to hear it from you!
BR
|
As in nature, all is ebb and tide, all is wave motion, so it seems that in all branches of industry, alternating currents - electric wave motion - will have the sway. ~Nikola Tesla~
|
|
|
Biffa
Legendary
Offline
Activity: 3220
Merit: 1220
|
|
December 21, 2016, 12:56:34 PM |
|
Hey guys, anyone got an original copy of the B13 firmware?
I've tried both:
Antminer-S9-201607131442-12.92T-600M-security.tar.gz
Antminer-S9-201607131442-11.85T-550M-security.tar.gz
And they both upload then give the "Incorrect firmware!!!" error
|
|
|
|
philipma1957
Legendary
 Online
Activity: 4116
Merit: 7824
'The right to privacy matters'
|
|
December 21, 2016, 12:56:58 PM |
|
@bitmaintech
So I have a batch 11 I believe it was. They run at 550 MHz. My intake air atm is less than 0c. What will happen to this miner come summer. I was able to downclock to 500 last summer as 30+c was too much for them. So in looking at temps of chips I'm not impressed at the cooling. Pulling in -14c only dropped chips temps to 80c. That's terrible cooling. So if I upgrade to this auto tune fw. What is going to happen to my miner when temps rise. I have a pretty good idea. I just want to hear it from you!
BR
Your gear will not be happy unless it is in a room under 80f. Auto tune really demands a cooler room. But this is just an observation from the 8 units I have used. They need to make auto tune have more choice for setting frequency. It starts with 550-600-650 as your choice once you pick it is stuck there pretty much. It should offer 450-500-550-600-650 |
|
|
|
Biffa
Legendary
Offline
Activity: 3220
Merit: 1220
|
|
December 21, 2016, 12:58:30 PM |
|
@bitmaintech
So I have a batch 11 I believe it was. They run at 550 MHz. My intake air atm is less than 0c. What will happen to this miner come summer if I upgrade to new fw. I was able to downclock to 500 last summer as 30+c was too much for them. So in looking at temps of chips I'm not impressed at the cooling. Pulling in -14c only dropped chips temps to 80c. That's terrible cooling. So if I upgrade to this auto tune fw. What is going to happen to my miner when temps rise. I have a pretty good idea. I just want to hear it from you!
BR
Current;y I wouldn't reccomend it. I upgraded some B13 to the latest firmware (autotune) and event at 550Mhz they are hitting 110+C and one has stopped responding, and the other keeps rebooting itself. |
|
|
|
|
elokk
|
|
December 21, 2016, 01:24:06 PM |
|
Hey guys, anyone got an original copy of the B13 firmware?
I've tried both:
Antminer-S9-201607131442-12.92T-600M-security.tar.gz
Antminer-S9-201607131442-11.85T-550M-security.tar.gz
And they both upload then give the "Incorrect firmware!!!" error
Did you backup the original firmware? I have a file that might work for you that I can email |
t.me/bitcoinasic
|
|
|
d57heinz
Legendary
Offline
Activity: 1453
Merit: 1011
Bitcoin Talks Bullshit Walks
|
|
December 21, 2016, 01:29:25 PM |
|
@bitmaintech
So I have a batch 11 I believe it was. They run at 550 MHz. My intake air atm is less than 0c. What will happen to this miner come summer. I was able to downclock to 500 last summer as 30+c was too much for them. So in looking at temps of chips I'm not impressed at the cooling. Pulling in -14c only dropped chips temps to 80c. That's terrible cooling. So if I upgrade to this auto tune fw. What is going to happen to my miner when temps rise. I have a pretty good idea. I just want to hear it from you!
BR
Your gear will not be happy unless it is in a room under 80f. Auto tune really demands a cooler room. But this is just an observation from the 8 units I have used. They need to make auto tune have more choice for setting frequency. It starts with 550-600-650 as your choice once you pick it is stuck there pretty much. It should offer 450-500-550-600-650 Thanks for the feedback. I was afraid that was what was going to happen. I have two 24 inch fans for my exhaust but still had to clock them down when temps rose north of 90F. @bitmaintech
So I have a batch 11 I believe it was. They run at 550 MHz. My intake air atm is less than 0c. What will happen to this miner come summer if I upgrade to new fw. I was able to downclock to 500 last summer as 30+c was too much for them. So in looking at temps of chips I'm not impressed at the cooling. Pulling in -14c only dropped chips temps to 80c. That's terrible cooling. So if I upgrade to this auto tune fw. What is going to happen to my miner when temps rise. I have a pretty good idea. I just want to hear it from you!
BR
Current;y I wouldn't reccomend it. I upgraded some B13 to the latest firmware (autotune) and event at 550Mhz they are hitting 110+C and one has stopped responding, and the other keeps rebooting itself. Thank you .. THat is what i feared. I also have all the downloads for the old fw if you need. I tried to post them here once before but was told not too. Let me know. I sure dont want to be sued as the guy that burnt up someone rig. Im sure bitmain would tell customer that. Even tho its the firmware that came on the machine lol. BR |
As in nature, all is ebb and tide, all is wave motion, so it seems that in all branches of industry, alternating currents - electric wave motion - will have the sway. ~Nikola Tesla~
|
|
|
|
elokk
|
|
December 21, 2016, 01:43:57 PM |
|
BitmainWarranty in Denver finally emailed me back yesterday. They were able to fix my board after 15 days of messing with it but no explanation of what was wrong with it. $175 repair bill plus $25 to ship back
|
t.me/bitcoinasic
|
|
|
philipma1957
Legendary
Online
Activity: 4116
Merit: 7824
'The right to privacy matters'
|
|
December 21, 2016, 02:00:15 PM |
|
BitmainWarranty in Denver finally emailed me back yesterday. They were able to fix my board after 15 days of messing with it but no explanation of what was wrong with it. $175 repair bill plus $25 to ship back
yeah this is about standard proceedure |
|
|
|
|
elokk
|
|
December 21, 2016, 02:07:33 PM |
|
BitmainWarranty in Denver finally emailed me back yesterday. They were able to fix my board after 15 days of messing with it but no explanation of what was wrong with it. $175 repair bill plus $25 to ship back
yeah this is about standard proceedure Well I previously sent a board and they had it fixed in 2 days and the communication was great. This last go around was not so great, mostly because of poor communication. Maybe Denver needs more employees? I wouldn't mind working in the bitcoin profession myself  |
t.me/bitcoinasic
|
|
|
|
mamiakimo
|
|
December 21, 2016, 03:02:29 PM |
|
@bitmaintech
So I have a batch 11 I believe it was. They run at 550 MHz. My intake air atm is less than 0c. What will happen to this miner come summer. I was able to downclock to 500 last summer as 30+c was too much for them. So in looking at temps of chips I'm not impressed at the cooling. Pulling in -14c only dropped chips temps to 80c. That's terrible cooling. So if I upgrade to this auto tune fw. What is going to happen to my miner when temps rise. I have a pretty good idea. I just want to hear it from you!
BR
Your gear will not be happy unless it is in a room under 80f. Auto tune really demands a cooler room. But this is just an observation from the 8 units I have used. They need to make auto tune have more choice for setting frequency. It starts with 550-600-650 as your choice once you pick it is stuck there pretty much. It should offer 450-500-550-600-650 what will happen in the next summer ? i don't test this auto tune on summer yet, we get hight temp here, more than 100F |
|
|
|
|
Biffa
Legendary
Offline
Activity: 3220
Merit: 1220
|
|
December 21, 2016, 06:10:22 PM |
|
Hey guys, anyone got an original copy of the B13 firmware?
I've tried both:
Antminer-S9-201607131442-12.92T-600M-security.tar.gz
Antminer-S9-201607131442-11.85T-550M-security.tar.gz
And they both upload then give the "Incorrect firmware!!!" error
Did you backup the original firmware? I have a file that might work for you that I can email There is no ability in the interface to backup the original firmware that I can see, only to backup the configuration. |
|
|
|
|
PeaMine
|
|
December 21, 2016, 07:50:22 PM |
|
I tried updating one of my first S9s I think it was 550mhz I updated first to the new auto tune firmware, but nothing happened even after setting pools and rebooting. So then I loaded the S9 recovery firmware, and it started working again. Then try the new autotune firmware, and I'm getting this (I think one board has always been dead, so that is not a surprise) Is it ever going to start hashing? Been 2 hours. check PIC voltage=940 on chain[0]
check PIC voltage=940 on chain[2]
check PIC voltage=940 on chain[3]
set command mode to VIL
singleBoardTest: AsicType = 1387
singleBoardTest: asicNum = 64
singleBoardTest: real AsicNum = 63
--- check asic number
set_baud=0, ought to be 1
The min freq=700
set real timeout 52, need sleep=379392
search freq for 1 times, completed chain = 3, total chain num = 3
disable_pic_dac on chain[0]
disable_pic_dac on chain[2]
disable_pic_dac on chain[3]
restart Miner chance num=2
waiting for send_func to exit of chain[0]
waiting for send_func to exit of chain[1]
waiting for send_func to exit of chain[2]
waiting for send_func to exit of chain[3]
waiting for send_func to exit of chain[4]
waiting for send_func to exit of chain[5]
waiting for send_func to exit of chain[6]
waiting for send_func to exit of chain[7]
waiting for send_func to exit of chain[8]
waiting for send_func to exit of chain[9]
waiting for send_func to exit of chain[10]
waiting for send_func to exit of chain[11]
waiting for send_func to exit of chain[12]
waiting for send_func to exit of chain[13]
waiting for send_func to exit of chain[14]
waiting for send_func to exit of chain[15]
waiting for receive_func to exit!
waiting for pic heart to exit!
Start bmminer ...
This is C5 board.
Check chain[0] PIC fw version=0x02
Check chain[2] PIC fw version=0x02
Check chain[3] PIC fw version=0x02
Chain[J1] will use highest voltage=940 [6] to open core
Chain[J3] will use highest voltage=940 [6] to open core
Chain[J4] will use highest voltage=940 [6] to open core
Chain[J1] orignal chain_voltage=6 value=940
Chain[J3] orignal chain_voltage=6 value=940
Chain[J4] orignal chain_voltage=6 value=940
Chain[J1] has 0 asic
retry Chain[J1] has 0 asic
retry Chain[J1] has 0 asic it need 10-25 minutes to open, so be patient Waited 2 hours, so should have came back up. Re-saved pool settings and did a hard power cycle. Waited 12 hours, nothing, just keeps looping those values like it's crashing and restarting. |
Datacenter Technician and Electrician. If you have any questions feel free to ask me as I am generally bored looking at logs and happy to help during free time.
|
|
|
|
