Bitmain Antminer E3 Firmware Update to Extend the Miner’s Life

30 Mar
2020

It seems that Bitmain has taken seriously the issue with their Antminer E3 ASIC miners intended for Ethash stopping to mine Ethereum Classic (ETC) recently and their upcoming inability to mine ETH as well in the very near future. To ensure Bitmain can provide efficient mining equipment for the Ethereum community, it has launched a new firmware to support the Antminer E3. This new firmware has apparently been designed to allow miners to continue using the Antminer E3, even after March 2020. This new firmware addresses the prior issue of the growth of directed acyclic graph (DAG) files, which limited the capability of the Antminer E3s for mining ETH or ETC. This new firmware will expand the usage of Double Date Rate (DDR) Memory, as more space is needed to process DAG files according to the company.

So, how long will the Antminer E3 last with the new firmware? The new firmware has been designed to better support the Antminer E3, and so Bitmain is confident that miners can continue using the hardware past April 2020. With the new firmware update, the final approximate block height of the Antminer E3 is 11,400,000, so according to calculations, mining can continue until October of 2020. ETC mining will stop again earlier than ETH due to the current DAG Epoch for Ethereum Classic being ahead with about 10 Epochs. Regardless, the new DAG size that the E3 miners would be able to handle seems to be increased to 3.97 GB based on the block number data released by Bitmain. So if you have Bitmain Antminer E3 miners you should make sure to update them with the latest firmware released to be able to extend their life to the maximum possible.

To download the latest Bitmain Antminer E3 Firmware Update extending Ethash mining support…






Check Some More Similar Crypto Related Publications:

11 Responses to Bitmain Antminer E3 Firmware Update to Extend the Miner’s Life

admin

March 30th, 2020 at 13:09

Upgrading to the new firmware seems a bit problematic, we have tested on 8 E3 miners out of which only 4 were successfully upgraded, the rest gave the following errors:

413 – Request Entity Too Large

mount: mounting ubi1:rootfs on /mnt/config failed: Invalid argument mkdir: can’t create directory ‘/mnt/config/home/usr_config’: No such file or directory cp: can’t create ‘/mnt/config/home/usr_config/’: No such file or directory umount: can’t umount /mnt/config: Invalid argument mount: mounting ubi1:rootfs on /mnt/upgrade failed: No such file or directory runme.sh: cd: line 122: can’t cd to /mnt/upgrade/upgrade umount: can’t umount /mnt/upgrade: No such file or directory

Elchely25

April 10th, 2020 at 07:01

Jiri

April 11th, 2020 at 01:46

I followed Bitmain’s SD card instructions. But fw cannot be read from the SD card and the red and green LEDs are still on. I tried 10 different 4-8GB SD cards.
As if Bitmain was making fun of us. Over the years, I have encountered several similar problems. They are not able to produce trouble-free products.

Jiri

April 11th, 2020 at 01:57

All 8 pieces of my E3 will also show when uploading fw via LAN:
413 – Request Entity Too Large
I just think that almost no one can upgrade the E3 fw.
Horribly!

stiphel

April 11th, 2020 at 21:33

I have two of these miners. The first had no issues with the the website updated, but the second gave me the following error:

mount: mounting ubi1:rootfs on /mnt/config failed: Invalid argument mkdir: can’t create directory ‘/mnt/config/home/usr_config’: No such file or directory cp: can’t create ‘/mnt/config/home/usr_config/’: No such file or directory umount: can’t umount /mnt/config: Invalid argument mount: mounting ubi1:rootfs on /mnt/upgrade failed: No such file or directory runme.sh: cd: line 122: can’t cd to /mnt/upgrade/upgrade umount: can’t umount /mnt/upgrade: No such file or directory

Looking at the file contents of the tar file, seemed like it should be possible to run this directly on the server via ssh.

I was able to ssh into the server using default credentials (root:admin). I was not able to scp files to the server. I noticed wget is installed, but it does not support https, so can’t download the file directly from bitmain.

Eventually I got the tar onto the system by setting up a http download via a public website. I played around and discovered I did not have enough free space to download the tar and extract it’s contents. So I deleted the tar and manually downloaded the tar file contents directly to the ~/ (home directy) of the root user using the same file structure as the tar.

next I updated the runme.sh script to the following:

#!/bin/sh -e

path=$(pwd)
cp_config="all"
if [ ! -d /mnt/upgrade ];
then
mkdir /mnt/upgrade
fi

if [ -e /usr/bin/ctrl_bd ]; then
ret='cat /usr/bin/ctrl_bd | grep "XILINX" | wc -l'
else
ret=0
fi

if [ $ret -eq 1 ];then
cd ./xilinx

if [ -e BOOT.bin ]; then
flash_erase /dev/mtd0 0x0 0x80 >/dev/null 2>&1
nandwrite -p -s 0x0 /dev/mtd0 ./BOOT.bin >/dev/null 2>&1
rm -rf BOOT.bin
fi

if [ -e rootfs.jffs2 ]; then
if [ -f /dev/mtd3 ];then
flash_erase /dev/mtd2 0x0 0x1E0 >/dev/null 2>&1
else
flash_erase /dev/mtd2 0x0 0x280 >/dev/null 2>&1
fi
nandwrite -p -s 0x0 /dev/mtd2 ./rootfs.jffs2 >/dev/null 2>&1
rm rootfs.jffs2
fi

if [ -e /dev/ubi_ctrl ];then

cd $path

flash_erase /dev/mtd0 0x1040000 0x1 >/dev/null 2>&1
nandwrite -p -s 0x1040000 /dev/mtd0 ./xilinx/upgrade-marker.bin >/dev/null 2>&1
sync
fi
else
mount -t jffs2 /dev/mtdblock4 /mnt/upgrade/
cd /mnt/upgrade/upgrade
rm -rf ./c5/*
cd $path

cp -rf ./c5/* /mnt/upgrade/upgrade

flash_erase /dev/mtd2 0x0 0x1 >/dev/null 2>&1
nandwrite -p -s 0x0 /dev/mtd2 /mnt/upgrade/upgrade/upgrade-marker.bin >/dev/null 2>&1

sync
umount /dev/mtdblock4
fi

rm -rf *.tar.gz

#/sbin/reboot -f &

After this I rebooted via the Web console

After the reboot, I waited 2 minutes and pressed the reset on the actual device. This did a factory reset.

I noticed the IP of the DHCP changed, so I logged into that web console.

On the status page I see:
CGminer Version 5.4.0

Everything is working as it should, no more issues.

Hope this helps someone, was a solid 4 hours of my day.

admin

April 13th, 2020 at 18:36

There is now a new version of the updated firmware that brings CGMiner from version 5.2.0 to 5.4.0, not sure about what is changed though… still does not flash directly on problematic E3s that do not have enough space available… though one of the other suggested variants above might work, so give them a try if you have issues as well.

Henry

April 16th, 2020 at 06:26

Hi stiphel,

You mean to put the file inside ~/ and reboot? I cant get it to work. After reboot does not change anything.

Henry

April 16th, 2020 at 11:27

Ok found a silly method to do it.

First download the old firmware for SD installation: E3-SD-20180806.zip
Then download the lastest firmware: E3_V540_0327.tar

Format a SD card with FAT32 unzip the ES-SD-20180806.zip into it. Untar the E3_V540_0327.tar into the same SD card.

Go to xilinx directory copy all the files there into BIN directory created by E3-SD-20180806.zip.

Eject the card and put into the E3 (Follow this instruction https://support.bitmain.com/hc/en-us/articles/360008618093-How-to-upgrade-E3-firmware-via-SD-card)

When done, remove the SD card and boot the E3. At this point your previous setting will all be gone. Find the E3 on your network.

Go to upgrade firmware and select the E3_V540_0327.tar and flash again. Once done the system will reboot and your cminer will be updated to 5.4.0 version.

Thats it.

Good luck!

admin

April 23rd, 2020 at 14:34

Cel mai bun cod de recomandare Binance

October 18th, 2024 at 08:47

Thank you for your sharing. I am worried that I lack creative ideas. It is your article that makes me full of hope. Thank you. But, I have a question, can you help me?

binance-ны алдым-ау бонусы

November 7th, 2024 at 04:12

Thank you for your sharing. I am worried that I lack creative ideas. It is your article that makes me full of hope. Thank you. But, I have a question, can you help me?

Leave a Reply

Your email address will not be published. Required fields are marked *

top