Author

Topic: ANTMINER S3+ Discussion and Support Thread - page 105. (Read 710164 times)

hero member
Activity: 518
Merit: 500
December 16, 2014, 08:49:06 AM
.... Now, can you kindly tell us how to open and read the code in that hex file please?   ....
You can't read it since its compiled.

Not being one to take good advice when given some, after realising the miner_pic.hex file was an ASCII file, I decided to deploy my secret reference material (read google) and seem to have found something, though I can not make any sense of it. I am sure bitsolutions, the clever clogs on our side, can so here goes.

1. My reference material suggested a site to view a hex file: http://en.webhex.net/
On visiting the site, I browsed to the file and uploaded the miner_pic.hex file

2. On the next screen, I scrolled to the bottom of the box and clicked on the Export link

3. When the Export screen was loaded, I un-checked the Headline, Offsets and Readable Characters check-boxes then clicked on the Export button on that screen.

4. I was then presented with the hex data in a web page. I had not mentioned this, but earlier,  my reference material had also suggested to me an online dis-assembler here : http://www2.onlinedisassembler.com/odaweb/

5. I copied all the exported hex data (Ctrl + A then Ctrl + C) then flicked over to the dis-assembler, clicked on the Platform button and changed it to avr (this may b wrong), and in the box below that I pasted the hex data into it.

The page then did a little spinning wheel and after a short while, spewed out something like this:



Now the easy bit, @bitsolutions or any of you clever clogs out there, can you make any sense of that?
sr. member
Activity: 392
Merit: 250
December 16, 2014, 08:24:33 AM
Can somebody please tell me how step by step to do this procedure with putty and windows 8.1 I am new to this forum so forgive me  Embarrassed
hero member
Activity: 786
Merit: 1000
December 16, 2014, 07:57:34 AM
@bitsolutions

".... I recommend everyone stay far far away from antMiner_S320141024 as it greatly increases the chance of you bricking your control card(only way to recover is with ttl) since the reset doesn't work(filesystem issue)...."


I have the bricking problem you mention. Bitmain just told me my warranty has expired. (They must start counting the 90 days from the time they ship instead of teh day I received it Sad )

Questions:

1. Instead of buying another control board, how do i use ttl to recover it? Sorry, I 'm gonna need step by step instructions.

2. My other S3s are running okay on the Oct 24th release. Should i re-flash them to the Oct 13th firmware?
hero member
Activity: 518
Merit: 500
December 16, 2014, 07:17:26 AM
Right, this is getting a bit confusing for me, but never mind, I appreciate all the information.

So to recap, there is absolutely no reason whatsoever to update firmware to the Nov 2014 release aside from the fix to the web UI, which fix can be applied by a single line via ssh.

Am I correct in this or have I missed something that is obvious to you?
I'm not exactly sure if there's any improvements other than the webui fixes. Kind of your choice on whether you prefer to fix the webui or the pic firmware as both appear to have the same end result as far as I can tell however I haven't tested performance differences extensively. I have yet to check if cgminer was updated between those versions either so you may want to do a more detailed comparison.
I do not think that cgminer was updated in the Nov firmware ... but could be wrong. Aside from that, since they made a dog's dinner out of the pic_firmware, I can not for the life of me see else-where performance enhancements could have been made.

Here's an interesting thought, would it not be nice if you wrapped one good bin file firmware update for us mere mortals? Here I mean one that has the correct and properly working hex file plus a working filesystem. that would be nice.

On another note, I managed to extract that hex file from one of my S3's (keep it for a rainy day) using MinGW on Windows. When I call file on the hex, it says it is ASCII text, with CRLF line terminators! I am tempted to open it up in notepad .....
sr. member
Activity: 261
Merit: 257
December 16, 2014, 07:05:33 AM
Right, this is getting a bit confusing for me, but never mind, I appreciate all the information.

So to recap, there is absolutely no reason whatsoever to update firmware to the Nov 2014 release aside from the fix to the web UI, which fix can be applied by a single line via ssh.

Am I correct in this or have I missed something that is obvious to you?
I'm not exactly sure if there's any improvements other than the webui fixes. Kind of your choice on whether you prefer to fix the webui or the pic firmware as both appear to have the same end result as far as I can tell however I haven't tested performance differences extensively. I have yet to check if cgminer was updated between those versions either so you may want to do a more detailed comparison.
hero member
Activity: 518
Merit: 500
December 16, 2014, 06:58:12 AM
Very well then, it seems they have even cleverer people at bitmain than I gave them credit for, my bad.
Now if you do not mind throwing some light on the issue that is perturbing me, so here goes:

Aside from the pic firmware in the Nov release (which you cleverly established to have been fiddled with by bitmain), what advantage has the rest of the update in the Nov release is there to be had over that in the Oct release? Seems to me a simple and complete reset to the  13th Oct 2014 firmware rather than fudging the two would do nicely. Ofcourse, I am speaking from a postion of utter ignorance, so bear with me there).
The pic firmware seems to change every other release or so. For example antMiner_S320140811 and antMiner_S320140826 have the same pic firmware as do antMiner_S320141013 and antMiner_S320141024. Right now the main issue with antMiner_S320141013 is the broken webui, I recommend everyone stay far far away from antMiner_S320141024 as it greatly increases the chance of you bricking your control card(only way to recover is with ttl) since the reset doesn't work(filesystem issue), the latest firmware has the correct filesystem and fixed webui but a bad pic firmware. If you want to use antMiner_S320141013 you should ssh and execute the following command to fix the webui.
Code:
sed -i 's/Save\&Apply/Save\&Apply/g' /usr/lib/lua/luci/model/cbi/cgminer/cgminer.lua
Right, this is getting a bit confusing for me, but never mind, I appreciate all the information.

So to recap, there is absolutely no reason whatsoever to update firmware to the Nov 2014 release aside from the fix to the web UI, which fix can be applied by a single line via ssh.

Am I correct in this or have I missed something that is obvious to you?
sr. member
Activity: 261
Merit: 257
December 16, 2014, 06:47:34 AM
Very well then, it seems they have even cleverer people at bitmain than I gave them credit for, my bad.
Now if you do not mind throwing some light on the issue that is perturbing me, so here goes:

Aside from the pic firmware in the Nov release (which you cleverly established to have been fiddled with by bitmain), what advantage has the rest of the update in the Nov release is there to be had over that in the Oct release? Seems to me a simple and complete reset to the  13th Oct 2014 firmware rather than fudging the two would do nicely. Ofcourse, I am speaking from a postion of utter ignorance, so bear with me there).
The pic firmware seems to change every other release or so. For example antMiner_S320140811 and antMiner_S320140826 have the same pic firmware as do antMiner_S320141013 and antMiner_S320141024. Right now the main issue with antMiner_S320141013 is the broken webui, I recommend everyone stay far far away from antMiner_S320141024 as it greatly increases the chance of you bricking your control card(only way to recover is with ttl) since the reset doesn't work(filesystem issue), the latest firmware has the correct filesystem and fixed webui but a bad pic firmware. If you want to use antMiner_S320141013 you should ssh and execute the following command to fix the webui.
Code:
sed -i 's/Save\&Apply/Save\&Apply/g' /usr/lib/lua/luci/model/cbi/cgminer/cgminer.lua
hero member
Activity: 518
Merit: 500
December 16, 2014, 06:38:55 AM
Turns out this didn't completely fix it, the issue is that the pic firmware from this build is very unstable. You can fix this by flashing the pic firmware from the antMiner_S320141013.bin firmware. To retrieve the stable pic firmware first flash the antMiner_S320141013.bin firmware to your miner, do not retrieve from any other firmware version especially antMiner_S320141024.bin(the pic firmware is identical to antMiner_S320141013.bin but very tricky to retrieve due to the filesystems being built incorrectly).
To retrieve the firmware scp it to your computer using the following command. This assumes your miner is still on the default IP of 192.168.1.99 .
Code:
scp [email protected]:/rom/etc/config/miner_pic.hex miner_pic.hex
Next Flash the latest antMiner_S320141126.bin firmware and upload the file back.
Code:
scp miner_pic.hex [email protected]:/etc/config/miner_pic.hex
Finally reboot your miner to apply the stable pic firmware.
You are a very clever person bitsolutions. Now, can you kindly tell us how to open and read the code in that hex file please? If these jombas from bitmain are not going to be honest with us, their customers, then I think they've earned us the right to pore over their little secrets. I thank you in advance.
You can't read it since its compiled.
Very well then, it seems they have even cleverer people at bitmain than I gave them credit for, my bad.
Now if you do not mind throwing some light on the issue that is perturbing me, so here goes:

Aside from the pic firmware in the Nov release (which you cleverly established to have been fiddled with by bitmain), what advantage has the rest of the update in the Nov release is there to be had over that in the Oct release? Seems to me a simple and complete reset to the  13th Oct 2014 firmware rather than fudging the two would do nicely. Ofcourse, I am speaking from a postion of utter ignorance, so bear with me there).
sr. member
Activity: 261
Merit: 257
December 16, 2014, 06:29:37 AM
Turns out this didn't completely fix it, the issue is that the pic firmware from this build is very unstable. You can fix this by flashing the pic firmware from the antMiner_S320141013.bin firmware. To retrieve the stable pic firmware first flash the antMiner_S320141013.bin firmware to your miner, do not retrieve from any other firmware version especially antMiner_S320141024.bin(the pic firmware is identical to antMiner_S320141013.bin but very tricky to retrieve due to the filesystems being built incorrectly).
To retrieve the firmware scp it to your computer using the following command. This assumes your miner is still on the default IP of 192.168.1.99 .
Code:
scp [email protected]:/rom/etc/config/miner_pic.hex miner_pic.hex
Next Flash the latest antMiner_S320141126.bin firmware and upload the file back.
Code:
scp miner_pic.hex [email protected]:/etc/config/miner_pic.hex
Finally reboot your miner to apply the stable pic firmware.
You are a very clever person bitsolutions. Now, can you kindly tell us how to open and read the code in that hex file please? If these jombas from bitmain are not going to be honest with us, their customers, then I think they've earned us the right to pore over their little secrets. I thank you in advance.
You can't read it since its compiled.
sr. member
Activity: 392
Merit: 250
December 16, 2014, 05:17:24 AM
 Huh Can somebody please tell me how step by step to do this procedure with putty and windows 8.1 I am new to this forum so forgive me.
hero member
Activity: 518
Merit: 500
December 16, 2014, 04:16:26 AM
Turns out this didn't completely fix it, the issue is that the pic firmware from this build is very unstable. You can fix this by flashing the pic firmware from the antMiner_S320141013.bin firmware. To retrieve the stable pic firmware first flash the antMiner_S320141013.bin firmware to your miner, do not retrieve from any other firmware version especially antMiner_S320141024.bin(the pic firmware is identical to antMiner_S320141013.bin but very tricky to retrieve due to the filesystems being built incorrectly).
To retrieve the firmware scp it to your computer using the following command. This assumes your miner is still on the default IP of 192.168.1.99 .
Code:
scp [email protected]:/rom/etc/config/miner_pic.hex miner_pic.hex
Next Flash the latest antMiner_S320141126.bin firmware and upload the file back.
Code:
scp miner_pic.hex [email protected]:/etc/config/miner_pic.hex
Finally reboot your miner to apply the stable pic firmware.
You are a very clever person bitsolutions. Now, can you kindly tell us how to open and read the code in that hex file please? If these jombas from bitmain are not going to be honest with us, their customers, then I think they've earned us the right to pore over their little secrets. I thank you in advance.
sr. member
Activity: 261
Merit: 257
December 16, 2014, 12:37:23 AM
Just fired up an S3+ today which came with the antMiner_S320141126.bin and as prior posts indicate it would stop hashing (~47Gh) after a few hours. I thought it was bad hardware, but I had also upgraded 5 other S3 & S3+ today to the same firmware and they each began doing the same thing.

Uploaded antMiner_S320141024.bin and things are pretty normal.


Try upgrading to the latest antMiner_S320141126.bin firmware and then ssh in and execute this command.
Code:
cp /overlay/etc/config/cgminer /tmp/cgminer.tmp && cp /overlay/etc/config/network /tmp/network.tmp && rm -r /overlay/* && mkdir /overlay/etc && mkdir /overlay/etc/config && cp /tmp/cgminer.tmp /overlay/etc/config/cgminer && cp /tmp/network.tmp /overlay/etc/config/network && reboot
This should clear out most bad configs and preserve your network and cgminer configs.

You may also want to execute this to set your voltage
Code:
uci set cgminer.default.voltage=0725 && uci commit
and this to set your frequency.
Code:
uci set cgminer.default.freq=18:225:0882 && uci commit
These all seemed to fix any low hashing S3+ I had on the newest firmware.

Turns out this didn't completely fix it, the issue is that the pic firmware from this build is very unstable. You can fix this by flashing the pic firmware from the antMiner_S320141013.bin firmware. To retrieve the stable pic firmware first flash the antMiner_S320141013.bin firmware to your miner, do not retrieve from any other firmware version especially antMiner_S320141024.bin(the pic firmware is identical to antMiner_S320141013.bin but very tricky to retrieve due to the filesystems being built incorrectly).
To retrieve the firmware scp it to your computer using the following command. This assumes your miner is still on the default IP of 192.168.1.99 .
Code:
scp [email protected]:/rom/etc/config/miner_pic.hex miner_pic.hex
Next Flash the latest antMiner_S320141126.bin firmware and upload the file back.
Code:
scp miner_pic.hex [email protected]:/etc/config/miner_pic.hex
Finally reboot your miner to apply the stable pic firmware.
hero member
Activity: 786
Merit: 1000
December 15, 2014, 08:40:29 PM
Well maybe it DID finish flashing, HOWEVER, upon restarting I can not access the gui at all.

The web browser never registered a response from the unit so the page showed "flashing" even after the unit had restarted itself (and stopped working).

Rare problems occurring seem to be what happens to me.  Wish there was a way to re set it.  Holding that reset button does nothing.
You are now raising the possiblility that you have not bricked the board ... do you have any other S3+'s on your network and if so is any of them on the default static IP?
When you flash a unit that (usually) is on DHCP, th web UI will NOT register a response because the flashing resets the IP to the default one and turns the network settings to static. Thus you have to log onto the default static IP (192.168.1.99) rather than the on you had on DHCP. And if you have 2 units on the default IP, ofcourse one will not show up on your network, and that will be the last to ry to use that IP (which in this case is the rebooting / reflashed rig).

It's pretty clear to me that the firmware cooked my controller.

Here's what Bitmain replied to me- re: the same issue as Patriotminer:

https://bitcointalksearch.org/topic/m.9845178
     "antMiner_S320141126.bin don't surpport adjust voltage. Hash board's power maybe cut off when you over clock."

and https://bitcointalksearch.org/topic/m.9845434
      "Now miner hardware modified, I want know your hash board's num. Can you help me? Thanks."

I provided him the details here:
https://bitcointalksearch.org/topic/m.9846032

and also sent an RMA request to: [email protected]

Their day should be starting soon. So I anticipate hearing something from them given how many people have posted problems here re; the Nov firmware.

I have 2 S3s and 1 other S3+. They survived the ordeal just fine. In fact, i set back their frequency to the level for a standard S3... as they were all running between 470 and 590 with the Oct firmware. Evenso, one of my standard S3s is still close to 600. Am a bit worried about that one- but it smells ok.




newbie
Activity: 22
Merit: 0
December 15, 2014, 05:51:37 PM
Oh I wish it was that!  Sadly this is my only S3+.
hero member
Activity: 518
Merit: 500
December 15, 2014, 05:42:10 PM
Well maybe it DID finish flashing, HOWEVER, upon restarting I can not access the gui at all.

The web browser never registered a response from the unit so the page showed "flashing" even after the unit had restarted itself (and stopped working).

Rare problems occurring seem to be what happens to me.  Wish there was a way to re set it.  Holding that reset button does nothing.
You are now raising the possiblility that you have not bricked the board ... do you have any other S3+'s on your network and if so is any of them on the default static IP?
When you flash a unit that (usually) is on DHCP, th web UI will NOT register a response because the flashing resets the IP to the default one and turns the network settings to static. Thus you have to log onto the default static IP (192.168.1.99) rather than the on you had on DHCP. And if you have 2 units on the default IP, ofcourse one will not show up on your network, and that will be the last to ry to use that IP (which in this case is the rebooting / reflashed rig).
sr. member
Activity: 261
Merit: 257
December 15, 2014, 05:40:15 PM
Just fired up an S3+ today which came with the antMiner_S320141126.bin and as prior posts indicate it would stop hashing (~47Gh) after a few hours. I thought it was bad hardware, but I had also upgraded 5 other S3 & S3+ today to the same firmware and they each began doing the same thing.

Uploaded antMiner_S320141024.bin and things are pretty normal.


Try upgrading to the latest antMiner_S320141126.bin firmware and then ssh in and execute this command.
Code:
cp /overlay/etc/config/cgminer /tmp/cgminer.tmp && cp /overlay/etc/config/network /tmp/network.tmp && rm -r /overlay/* && mkdir /overlay/etc && mkdir /overlay/etc/config && cp /tmp/cgminer.tmp /overlay/etc/config/cgminer && cp /tmp/network.tmp /overlay/etc/config/network && reboot
This should clear out most bad configs and preserve your network and cgminer configs.

You may also want to execute this to set your voltage
Code:
uci set cgminer.default.voltage=0725 && uci commit
and this to set your frequency.
Code:
uci set cgminer.default.freq=18:225:0882 && uci commit
These all seemed to fix any low hashing S3+ I had on the newest firmware.
legendary
Activity: 3892
Merit: 4331
December 15, 2014, 05:20:47 PM
Well maybe it DID finish flashing, HOWEVER, upon restarting I can not access the gui at all.

The web browser never registered a response from the unit so the page showed "flashing" even after the unit had restarted itself (and stopped working).

Rare problems occurring seem to be what happens to me.  Wish there was a way to re set it.  Holding that reset button does nothing.

It will not be a consolation, but the cause is maybe that you started doing something BEFORE the previous process finished.
You need to RMA the unit. Contact Bitmain warranty if this is a November miner. Warranty is 90 days.
newbie
Activity: 22
Merit: 0
December 15, 2014, 05:14:15 PM
Well maybe it DID finish flashing, HOWEVER, upon restarting I can not access the gui at all.

The web browser never registered a response from the unit so the page showed "flashing" even after the unit had restarted itself (and stopped working).

Rare problems occurring seem to be what happens to me.  Wish there was a way to re set it.  Holding that reset button does nothing.
legendary
Activity: 3892
Merit: 4331
December 15, 2014, 05:06:12 PM
It never stopped flashing.  Does this mean the controller is a goner?


what do you mean by never stopped flashing? If you mean that the 'wheel" never stops turning-it does that, but it does NOT mean that process was not finished (I know, it is kind of counterintuitive). However, i just logout or reset browser after 10 min, then restart the PSU, log in and you should be OK, unless as you posted, controller is not functioning, which is rare.
newbie
Activity: 22
Merit: 0
December 15, 2014, 04:25:18 PM
I don't like this at all.  How can any company continue to exist if they sell a product that they will not stand behind less than 30 days after receipt?

I did NOTHING more than flash to the latest firmware in an attempt to fix a problem.  This caused more problems so I attempted to flash back to an older firmware.  The flash never finished.  I have pressed the RESET button which is supposed to do a factory reset.  My network is 192.168.1.x.  The controller no longer responds and the answer on the official Antminer S3 Discussion and support thread is  "good luck getting a new one"??

There must be someone with an interest in Bitmain as a company that is able to offer a proper and helpful suggestion.  At the very least they should sell replacement parts.

Looks like I won't be buying Bitmain hardware again.  Was about to buy the new water cooled one but if they can't support their simpler units what hope do I have?

No wonder BTC keeps dropping  Between PBmining type scams and crappy mining hardware supported only other users who can only share in the pain.

Jump to: