Sure fire fix assuming hardware is ok and uboot intact is uboot based recovery, interrupt the boot process and set your computers IP to a static IP of 192.168.1.100. Start a TFTP server on your computer serving antMiner_S320141013.bin and run the following commands on your miner.
Code:
tftpboot 0x80000000 antMiner_S320141013.bin
erase 0x9f020000 +0x7c0000
cp.b 0x80000000 0x9f020000 0x7c0000
bootm 0x9f020000
erase 0x9f020000 +0x7c0000
cp.b 0x80000000 0x9f020000 0x7c0000
bootm 0x9f020000
there no need to re-flash the firmware as it is the NVRAM that is corrupt...your suggestion of loading the 20141013.bin will result in being unable to access the config pages as documented in the subsequent release....if anything I would suggest loading the 0826 firmware and then wget the ckolivas cgminer 4.61 but then we are complicating things more than needed...most here seem to have enough problem with putty lets not throw in a tftp server and hex addresses....its a bit of a predicament...0826 firmware with crap cgminer or Russian roulette with the next 3 builds....and all the while BITMAIN leaves the files for MORE people to &$#^&$ their miners up with...well done
on a different note its nice to see the community working together
SSH in and execute the following to fix webui on the oct 13th firmware.
Code:
sed -i 's/Save\&Apply/Save\&Apply/g' /usr/lib/lua/luci/model/cbi/cgminer/cgminer.lua
To fix config pages after flashing a later release execute this command over SSH.
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
TFTP recovery is usually required if the OS doesn't boot and you see it stuck bootlooping at uboot.
is this what I need to do?