Antminer D3 Blissz firmware (10/12 v1.12 update)

[detonyle]

Speaking of new firmware bitmain have finally fixed the xxx issue in a new update , interesting timing.

You mean firmware 20171102 ?
I still have the problem even after upgrade. every 12h -15h card goes XXX

[1715209188]

1715209188

[1715209188]

1715209188

[1715209188]

1715209188

[1715209188]

1715209188

[digital$]

have only 2 boards hashing after latest upgrade...ran fine for a day then this issue developed



https://imgur.com/6NSr4mk

[D3 Antminer]

Hi guys, I am working on finalizing the first version of the firmware now. The first release will not contain any new algorithms yet, but will add some nice features to quiet the beast
It's still uncertain if adding other algo's is possible but I will definitely give it a try after the first firmware runs stable

Hi blissz
I want to share the link at change.org   . As of now nearly 600 angry bitmain customer  looking for a solution. Up to me , additional algo's with a custom firmware is the solution because X11 can not afford the current D3 demand.
I am sure that it is not a easy job but I also know that someone who will do this job will make good money.

We all expect the good news .

https://www.change.org/p/https-twitter-com-bitmaintech-d3-antminer-firmware-update-for-additional-mining-algorithms?recruiter=831205993&utm_source=share_petition&utm_medium=copylink&utm_campaign=share_petition&utm_term=share_petition

[stugots2]

Best Thread EVER

[diab]

it seems exactly what we need like

https://github.com/bitmaintech/cgminer-dash/blob/master/x11/groestl.c

yes in this folder you have the 11 algo code used for X11....
so need to recompile something with only groestl or other.... but i think something more will be needed ^^

I have a feeling that the X11 algo that you're looking at is the CPU implementation of it. What ASICS (most likely) do is that you load a bunch of data into their buffer, fire the hashing engine and you get the hashed data out so all the magic happens inside the ASIC. Look at different asic drivers and you'll see that there is hardly any business logic in there - it's reading temps, resetting / setting up the asic and sending "stuff" to it.

Bottom line - it's not at all trivial (if it is even possible) to change the ALGO. X13 is 2 extra sub-algos in addition to the 11 ones in X11. D3s communicate using some sort of serial protocol (not USB, I think, by the looks of the driver code) so we could theoretically dump some GPUs into a mining rig, connect D3 ASICS to it via a serial port then run the X11 "part" of the algo on D3s then the rest (2 algos) on GPUs. The whole point of ASICS is that they have a very limited feature set and I'd be surprised if we could hack it to something else (especially without documentation).

[Ryancope123]

it seems exactly what we need like

https://github.com/bitmaintech/cgminer-dash/blob/master/x11/groestl.c

yes in this folder you have the 11 algo code used for X11....
so need to recompile something with only groestl or other.... but i think something more will be needed ^^

I have a feeling that the X11 algo that you're looking at is the CPU implementation of it. What ASICS (most likely) do is that you load a bunch of data into their buffer, fire the hashing engine and you get the hashed data out so all the magic happens inside the ASIC. Look at different asic drivers and you'll see that there is hardly any business logic in there - it's reading temps, resetting / setting up the asic and sending "stuff" to it.

Bottom line - it's not at all trivial (if it is even possible) to change the ALGO. X13 is 2 extra sub-algos in addition to the 11 ones in X11. D3s communicate using some sort of serial protocol (not USB, I think, by the looks of the driver code) so we could theoretically dump some GPUs into a mining rig, connect D3 ASICS to it via a serial port then run the X11 "part" of the algo on D3s then the rest (2 algos) on GPUs. The whole point of ASICS is that they have a very limited feature set and I'd be surprised if we could hack it to something else (especially without documentation).

you sound like you know what your talking about lol

[ScottShelby]

Hi guys, I am working on finalizing the first version of the firmware now. The first release will not contain any new algorithms yet, but will add some nice features to quiet the beast
It's still uncertain if adding other algo's is possible but I will definitely give it a try after the first firmware runs stable

Super excited to test your work and want to sincerely thank you for all that you are doing for the community!!

[stugots2]

Hi guys, I am working on finalizing the first version of the firmware now. The first release will not contain any new algorithms yet, but will add some nice features to quiet the beast
It's still uncertain if adding other algo's is possible but I will definitely give it a try after the first firmware runs stable

Super excited to test your work and want to sincerely thank you for all that you are doing for the community!!

did you register TO say that? lol

[dashcoin1]

Hi guys, I am working on finalizing the first version of the firmware now. The first release will not contain any new algorithms yet, but will add some nice features to quiet the beast
It's still uncertain if adding other algo's is possible but I will definitely give it a try after the first firmware runs stable

thanks

[exsexs1]

It will be possible that the value must be an Hex and not a Dec value?

Below the string I found in the bitmain-driver.c file:
"Invalid bitmain-options for voltage data, must be hex now: %s"

driver_btm_DASH.c

Code:

int opt_bitmain_DASH_freq = 100;
int opt_bitmain_DASH_voltage = 176;

Looks like integer value.
Hmm... I'll test it tomorrow with some hex voltage numbers

Tested, don't worked.

[blissz]

Almost finished: the webinterface is modified as well now. Only need to test for a proper voltage range, and make a package.
The first release will have a fairly save voltage range, as I don't want you guys to brick your miners, so please have a bit more patience

[Searing]

Almost finished: the webinterface is modified as well now. Only need to test for a proper voltage range, and make a package.
The first release will be on the save side, as I don't want you guys to brick your miners, so please have a bit more patience

at the prices, we are getting now...and 4 or more batches of D3's in the wind yet to arrive and the corresponding difficulty pump

bricking them at this point may not matter much

Indeed, I should send mine to the company that 'bronzes baby shoes'

just to have a small trophy, when they stick me in the old folks home someday on a reminder of my 'silly youth'

[exsexs1]

Almost finished: the webinterface is modified as well now. Only need to test for a proper voltage range, and make a package.
The first release will have a fairly save voltage range, as I don't want you guys to brick your miners, so please have a bit more patience

OK, I have some Antheater to make a brick.

[blissz]

has i see no one try to help ... i just remove the warranty of my brand new D
don't know if it will be good for you , it seem to be at 9.50~ at startup and then 7.99~8.00 when mining




please let us have basic set up or how to do... to dont hear those damm fans ...

the r80 is very little , i m scared to touch it ...

Thanks for this by the way, it would be nice if someone can confirm the original ohm resistance of R80. I thought it was 4.58K, but I am not 100% sure.
You can just measure it with the board turned off and you will be fine

[micha_b]

If one can tell me the code on the resistor I can tell you the exact resistor value.

[cryptonitro]

has i see no one try to help ... i just remove the warranty of my brand new D
don't know if it will be good for you , it seem to be at 9.50~ at startup and then 7.99~8.00 when mining




please let us have basic set up or how to do... to dont hear those damm fans ...

the r80 is very little , i m scared to touch it ...

Thanks for this by the way, it would be nice if someone can confirm the original ohm resistance of R80. I thought it was 4.58K, but I am not 100% sure.
You can just measure it with the board turned off and you will be fine

this is the c948 i took

[cryptonitro]

If one can tell me the code on the resistor I can tell you the exact resistor value.

this is the r80 , the one in place where blissz conntect blue and red cable
c948  revealing it if i m right , in do not let my cable on c948 , i cant took it

[boyservice]

Hi guys, I am working on finalizing the first version of the firmware now. The first release will not contain any new algorithms yet, but will add some nice features to quiet the beast
It's still uncertain if adding other algo's is possible but I will definitely give it a try after the first firmware runs stable

Great news  I happy  to hear it thanks for hard works.

[DIMESECO]

Maybe bad news...

Here is an example code to build an X11 hash:

void x11_hash(const char* input, char* output, uint32_t len)
{
    sph_blake512_context     ctx_blake;
    sph_bmw512_context       ctx_bmw;
    sph_groestl512_context   ctx_groestl;
    sph_skein512_context     ctx_skein;
    sph_jh512_context        ctx_jh;
    sph_keccak512_context    ctx_keccak;

    sph_luffa512_context      ctx_luffa1;
    sph_cubehash512_context      ctx_cubehash1;
    sph_shavite512_context      ctx_shavite1;
    sph_simd512_context      ctx_simd1;
    sph_echo512_context      ctx_echo1;

    //these uint512 in the c++ source of the client are backed by an array of uint32
    uint32_t hashA[16], hashB[16];   

    sph_blake512_init(&ctx_blake);
    sph_blake512 (&ctx_blake, input, len);
    sph_blake512_close (&ctx_blake, hashA);

    sph_bmw512_init(&ctx_bmw);
    sph_bmw512 (&ctx_bmw, hashA, 64);
    sph_bmw512_close(&ctx_bmw, hashB);

    sph_groestl512_init(&ctx_groestl);
    sph_groestl512 (&ctx_groestl, hashB, 64);
    sph_groestl512_close(&ctx_groestl, hashA);

    sph_skein512_init(&ctx_skein);
    sph_skein512 (&ctx_skein, hashA, 64);
    sph_skein512_close (&ctx_skein, hashB);

    sph_jh512_init(&ctx_jh);
    sph_jh512 (&ctx_jh, hashB, 64);
    sph_jh512_close(&ctx_jh, hashA);

    sph_keccak512_init(&ctx_keccak);
    sph_keccak512 (&ctx_keccak, hashA, 64);
    sph_keccak512_close(&ctx_keccak, hashB);
   
    sph_luffa512_init (&ctx_luffa1);
    sph_luffa512 (&ctx_luffa1, hashB, 64);
    sph_luffa512_close (&ctx_luffa1, hashA);   
   
    sph_cubehash512_init (&ctx_cubehash1);
    sph_cubehash512 (&ctx_cubehash1, hashA, 64);   
    sph_cubehash512_close(&ctx_cubehash1, hashB); 
   
    sph_shavite512_init (&ctx_shavite1);
    sph_shavite512 (&ctx_shavite1, hashB, 64);   
    sph_shavite512_close(&ctx_shavite1, hashA); 
   
    sph_simd512_init (&ctx_simd1);
    sph_simd512 (&ctx_simd1, hashA, 64);   
    sph_simd512_close(&ctx_simd1, hashB);
   
    sph_echo512_init (&ctx_echo1);
    sph_echo512 (&ctx_echo1, hashB, 64);   
    sph_echo512_close(&ctx_echo1, hashA);

    memcpy(output, hashA, 32);
   
}

As u can see, there are many sub algos affected to make an x11 hash. These algos are hardcoded in bitmains asic chips. So you can input some work and get outputted the result of the complete x11 hash.

I took a deep look into cgminer (also the newest version) and what i found was only to put work into asic and get results back. My hope was, that it could work like Baikalminer, but i was wrong here.

Good Luck

[jelin1984]

with the first firmware that will be out
can we run d3 at 700 watt with 15gh speed or not?