Dollemizer Firmware ASICBOOST Comming! [custom s9, s9i, t9 Firmware upgrade]

[numnutz2009]

So the fee is totally out of balance on this firmware. I have been running for 21 hours and these are my results.

748 shares mined to my pools.

1394 shares mined to dev fee pools.

That's more like a 150% fee...

I mean I can manually remove the dev fee pool using the cgminer api and it works fine. But I don't mind the dev fee if its as advertised.

Are there fixes coming for this?

to be fair ur post is misleading. the share count isnt the number u should look at. u can if the diff of each share is the same between both pools but some have a much higher diff so u cant compare one to the other.

either way i wouldnt use this firmware. folks should have known the same firmware used on s9's shouldnt be used with the t9 versions. i dont really consider this part their fault even if they said it might work with the t9 model. its well known that the models are completely different and have different power requirements and firmware configs. it sucks that it happened but take this as a chance to learn and be sure to read up on the machines ur plannin on moddin via software and hardware.

if u want to force the old firmware back onto the machine use the antminer manager app that bitmain has on their site. it seems to get around the wrong firmware error when flashing custom firmware images. just download the app and the official firmware for ur model miner and connect to it using the app. u have to import the firmware u downloaded to the apps repo but u can figure that stuff out. i have used this to force flash miners that wouldnt accept the official update so i know it works but i havent used this threads custom firmware but it should have the same result.

[taserz]

to be fair ur post is misleading. the share count isnt the number u should look at. u can if the diff of each share is the same between both pools but some have a much higher diff so u cant compare one to the other.

either way i wouldnt use this firmware. folks should have known the same firmware used on s9's shouldnt be used with the t9 versions. i dont really consider this part their fault even if they said it might work with the t9 model. its well known that the models are completely different and have different power requirements and firmware configs. it sucks that it happened but take this as a chance to learn and be sure to read up on the machines ur plannin on moddin via software and hardware.

if u want to force the old firmware back onto the machine use the antminer manager app that bitmain has on their site. it seems to get around the wrong firmware error when flashing custom firmware images. just download the app and the official firmware for ur model miner and connect to it using the app. u have to import the firmware u downloaded to the apps repo but u can figure that stuff out. i have used this to force flash miners that wouldnt accept the official update so i know it works but i havent used this threads custom firmware but it should have the same result.

That won't fix a hashboard pic programmed for a different miner from a malicious firmware update aka this firmware here.

[numnutz2009]

That won't fix a hashboard pic programmed for a different miner from a malicious firmware update aka this firmware here.

hes sayin he cant revert to the original firmware. that can mean 2 things...either the board firmware or the controller firmware. if he is havin issues flashin the controller i provided a way around that. alot of miners wont let u go back from a modded version unless you force it and since he kinda left it open to assumption i thought i would pass that info along. he can also try flashin it to see if it also forces flashin of the board firmware too. its not like he has ne thing to lose but as it sits they dont work.

what i find confusin is 2 boards dont work for him...if the firmware did in fact kill his boards all of them would be dead not just some of them.

[bitsolutions]

The GPLv3 states that you need to show us that you run our software and then we can send you the source code. We do not have to make the source code public.
If you would like the source code, send us that you are running our software and share your contact details.

I've never heard of a GPLv3 requirement to run it(if there is one please point me to the specific line in the GPLv3 license), GPLv3 requirements are based on distribution of the software(ie downloading it) not running it. You can contact me via PM.
Here's proof I downloaded it:

Code:

$ shasum -a 256 Dollemizer875-USA.gz 
ee4386b018901799c205788bf0fb15db21b1599e4c4bf3a0d2e6abdd1d618d7e  Dollemizer875-USA.gz

[taserz]

I've never heard of a GPLv3 requirement to run it(if there is one please point me to the specific line in the GPLv3 license), GPLv3 requirements are based on distribution of the software(ie downloading it) not running it. You can contact me via PM.
Here's proof I downloaded it:

Code:

$ shasum -a 256 Dollemizer875-USA.gz 
ee4386b018901799c205788bf0fb15db21b1599e4c4bf3a0d2e6abdd1d618d7e  Dollemizer875-USA.gz

This is true GPL requirements are based off distribution NOT usage. Requesting source code or thread being closed.

[nokapol]

Low hashrate and not temperature monitoring.
http://dl4.joxi.net/drive/2018/08/03/0013/1525/910837/37/231f0acad1.png

[fanatic26_]

Its been common knowledge for YEARS not to mess with bitmains firmware yet you people are bricking your units left and right for no good reason at all. Pushing these machines past the rated hash rate decreases efficiency and eats away at any extra profits you think you are squeezing out of the machine.

Just plug your miner in and run it the way it was built to run. Stop being stupid and letting greed take you down a wrong path.

[minefarmbuy]

Its been common knowledge for YEARS not to mess with bitmains firmware yet you people are bricking your units left and right for no good reason at all. Pushing these machines past the rated hash rate decreases efficiency and eats away at any extra profits you think you are squeezing out of the machine.

Just plug your miner in and run it the way it was built to run. Stop being stupid and letting greed take you down a wrong path.

It's weird. Sometimes the hard way is the best way to learn. Asics aren't gpu's their CPU's that will burn your house down. Enjoy.

Always love me a fanatic post though. Need people like you around. Balance in the force and what not. 

[taserz]

It's weird. Sometimes the hard way is the best way to learn. Asics aren't gpu's their CPU's that will burn your house down. Enjoy.

Always love me a fanatic post though. Need people like you around. Balance in the force and what not.  

Meh this is just a shit firmware. If you do it right you can keep the efficiency curve the same without blowing away your profits and profit more

[Kossack]

I did the same to my T9+ but the firmware wiped all 3 of my boards!

Has anyone got a PIC hex code of the T9+ hashboard for a manual reprogram using a pickit3?

[Gabrics]

This firmware works for me so far(S9, will try on a T9). A few questions I have:

- Do you guys have a thermal protection limit? I mean do you stop mining if chips are getting too hot? If yes at what temperature?

- According to the docs I found AsicBoost should give ~25% extra hashrate. The hashrate increase I can reproduce only coming from different frequency (on Slush). If I get this right I should see higher hashrates at stock frequency. Is this actually working?

Thanks

[taserz]

This firmware works for me so far(S9, will try on a T9). A few questions I have:

- Do you guys have a thermal protection limit? I mean do you stop mining if chips are getting too hot? If yes at what temperature?

- According to the docs I found AsicBoost should give ~25% extra hashrate. The hashrate increase I can reproduce only coming from different frequency (on Slush). If I get this right I should see higher hashrates at stock frequency. Is this actually working?

Thanks

It's just marketing you cant add asic boost to an S9. He just wants you to use his firmware to take a dev fee.

[Gabrics]

Thanks, that's what I though too. As far as I get you need AsicBoost ASIC which is not "no asic boost"/normal compatible.

Still adjustable Mhz and voltage is a nice add-on. But flat out price would be better as slush always alert when this FW switches to "self mining".

[zacocity]

everyone who has a broken T9+ can feel free to contact me over PM or Discord or Telegram

[Instatic]

is this working for S9j ?

[vonRau]

is this working for S9j ?

Our software is running stable on S9j

[taserz]

Our software is running stable on S9j

Someone posted in the discord group that it broke their S9J and they had to send it back to bitmain.

[vonRau]

Someone posted in the discord group that it broke their S9J and they had to send it back to bitmain.

Are you sure?
S9j??
I rather believe it was a T9+, but anyway, why should it break with our software? You exactly know, that changes in the shell can easily set back to default.
I testet it with several miner types: e.g. I flashed D3 firmware on my X3 and A3. Sure, did not work, but when flashed the original FW from Bitmain´s download website, the miner was like "new".

[sahinkod]

hi @DolleTeam  ı m problem

Code:

Chain[J6] PIC temp offset=62,0,0,0,0,0,35,28
Chain[J6] chip[244] use PIC middle temp offset=0 typeID=55
New offset Chain[5] chip[244] local:8 remote:9 offset:27 
Chain[J6] chip[244] get middle temp offset=27 typeID=55
Chain[J6] chip[136] use PIC middle temp offset=28 typeID=01
Warning: Chain[J6] has no temp offset in PIC! will fix it
New offset Chain[5] chip[244] local:8 remote:9 offset:27 
Chain[J6] chip[244] get middle temp offset=27 typeID=55
Chain[J7] PIC temp offset=62,0,0,0,0,0,35,28
Chain[J7] chip[244] use PIC middle temp offset=0 typeID=55
New offset Chain[6] chip[244] local:7 remote:8 offset:27 
Chain[J7] chip[244] get middle temp offset=27 typeID=55
Chain[J7] chip[136] use PIC middle temp offset=28 typeID=00
Warning: Chain[J7] has no temp offset in PIC! will fix it
New offset Chain[6] chip[244] local:7 remote:8 offset:27 
Chain[J7] chip[244] get middle temp offset=27 typeID=55
Chain[J8] PIC temp offset=62,0,0,0,0,0,35,28
Chain[J8] chip[244] use PIC middle temp offset=0 typeID=55
New offset Chain[7] chip[244] local:7 remote:8 offset:27 
Chain[J8] chip[244] get middle temp offset=27 typeID=55
Chain[J8] chip[136] use PIC middle temp offset=28 typeID=00
Warning: Chain[J8] has no temp offset in PIC! will fix it
New offset Chain[7] chip[244] local:7 remote:8 offset:27 
Chain[J8] chip[244] get middle temp offset=27 typeID=55
Chain[J6] set working voltage=800 [245]
Chain[J7] set working voltage=800 [245]
Chain[J8] set working voltage=800 [245]
setStartTimePoint total_tv_start_sys=86 total_tv_end_sys=87
restartNum = 2 , auto-reinit enabled...
Fatal Error: Fan lost!
Fatal Error: Fan lost!
Fatal Error: Fan lost!
Fatal Error: Fan lost!
do read_temp_func once...
do check_asic_reg 0x08

get RT hashrate from Chain[5]: (asic index start from 1-63)

get RT hashrate from Chain[6]: (asic index start from 1-63)

get RT hashrate from Chain[7]: (asic index start from 1-63)
Check Chain[J6] ASIC RT error: (asic index start from 1-63)
Asic[25]=131.030000
Check Chain[J7] ASIC RT error: (asic index start from 1-63)
Asic[29]=131.030000
Asic[57]=123.966000
Check Chain[J8] ASIC RT error: (asic index start from 1-63)
Asic[26]=131.181000
Asic[51]=123.966000
Done check_asic_reg
do read temp on Chain[5]
Chain[5] Chip[62] TempTypeID=55 middle offset=27
read failed, old value: Chain[5] Chip[62] local Temp=13
read failed on Chain[5] Chip[62] middle Temp old value:16
Done read temp on Chain[5]
do read temp on Chain[6]
Chain[6] Chip[62] TempTypeID=55 middle offset=27
read failed, old value: Chain[6] Chip[62] local Temp=16
read failed on Chain[6] Chip[62] middle Temp old value:28
Done read temp on Chain[6]
do read temp on Chain[7]
Chain[7] Chip[62] TempTypeID=55 middle offset=27
read failed, old value: Chain[7] Chip[62] local Temp=11
read failed on Chain[7] Chip[62] middle Temp old value:11
Done read temp on Chain[7]
set FAN speed according to: temp_highest=28 temp_top1[PWM_T]=28 temp_top1[TEMP_POS_LOCAL]=16 temp_change=0 fix_fan_steps=0
FAN PWM: 0
read_temp_func Done!
CRC error counter=39

I'm oily cooling.My devices do not have a fan.What is the reason for not working ? Help me:) Have a nice day

[tim-bc]

I'm oily cooling.My devices do not have a fan.What is the reason for not working ? Help me:) Have a nice day

In the code you posted you can see the error "Fatal Error: Fan lost!" four times. So, you need to either fake the fan input with some hardware timer or recompile your firmware to not check for fans.