Quote from: nitrox1 on December 16, 2014, 02:08:01 PM

Very new here.But seem like I'm another the latest firmware as bricked my control board.
It was flashed over WIFI network, and had the message that the firmware was ready to flash.
Now I have the red flashing LED of death.
Latest firmware took on my two other units.
I'm able to open a telnet connection on the old IP address, but that is it. I'm lost from here.
I see some HEX stuff going on, but it is way beyond me. Is the hex file able to be flashed through ethernet?
Any solutions to get firmware flashed over again maybe over LAN1, Debug???

If you can't get to the webui or ssh in try the reset button, latest firmware shouldn't brick control board, its just somewhat unstable. The hex file has nothing to do with this issue.

Quote from: pekatete on December 16, 2014, 01:49:06 PM

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?

Lol, this is not the "easy bit", its a compiled file, you aren't going to get much further than this unless you know how to read assembly.

Quote from: ATCkit on December 16, 2014, 12:57:34 PM

@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?

TTL recovery is tricky if you haven't done that type of thing before and requires special adapters. Just send the control card to the US warranty address with your return address phone and email and they will let you know if it can be recovered.
Bitmain Warranty
3700 Quebec Street #100239
Denver, Colorado 80207
USA
Yes, you probably want to flash the older firmware or latest firmware with the pic fix.