Asic.to Firmware 17Series • Optimized efficiency/Performance •

[Artemis3]

That is how our firmware was loaded via SD prior to version 2. We made it flash to and because everyone ended up keeping it. Also we don't write to the eeprom that's hive/msk. Talk to Edward about this if your confused I even clarified this to him. Hence corrupt eeprom they flashed some shit firmware when the PIC can do it all. Also a mod would use the eprom. A full driver rewrite what we do and what you guys copied to get our features doesn't utilize the eeprom. The thing about bashing us is your in the wrong for stealing someone else's work and rewriting it to be your own. Think about that.

I didn't say it was yours in particular that corrupts the eeproms, did i? But have fun twisting my words for your convenience.

There are no pissing contests, the results are out there. Next time, read Bitmain's documentation on how to reflash their firmware from sd and stop blaming it on others. Its a different OS duh. Why don't you blame Apple when your Windows game doesn't "install easy" in your Mac OS?.

None of my words were specifically meaning your firmware in particular, for you taking it this personally that is your own personal issue.

"Autotuning" is a "feature", beyond the name, there are zero similarities. You don't even use the Rust language. Are you using your own miner or Con Kolivas work? Did you comply with his license? If you did, good for you...

Notice that its you mentioning other firmware by name, i never mentioned yours in particular, so there is no confusion on MY part, read very well what i wrote in that thread which was conveniently locked before i could even reply.

I did object of you saying that Braiins OS is "making it hard to remove it", no it isn't. Its ANOTHER OS, not based on Bitmain's, and the flash image facility simply doesn't work because its incompatible, it is NOT locked. Can YOU make a flash image compatible with Openwrt/Braiins OS to directly flash your own firmware from the Braiins OS UI? Then why YOU don't do it? There is no signature checking, nothing is stopping you, and you even have access to the source code.

[1714482982]

1714482982

[1714482982]

1714482982

[1714482982]

1714482982

[1714482982]

1714482982

[1714482982]

1714482982

[1714482982]

1714482982

[taserz]

Just because you rewrote what we wrote in another language doesn't make it different. You can write yours in rust, javascript fucking assembly it's still copying our IP the Zero similarities claim you just made is far from correct and we all know this. I can pull up chat logs where braiins has stated we corrupt eeproms so it's irrelevant you are taking back your words now...

Also sure you can it's not like your using the whole entire nand and using an open source bootloader is not the end of the world. Hell linux has Wine for a reason If you're going to offer someone a product they can just throw a sd card into to install you should make it just that easy to uninstall. The industry is not all neck beards and I had to make a canned response for directing people how to uninstall...

No signature checking... I won't even go down that road now.

[Artemis3]

I don't know what chat logs are you talking about, but they don't involve me personally. So, whatever taserz. Your personal agenda is not my problem. You seem to be confusing me with somebody else... Since you are so confused and cant stop somehow making strange accusations, I'll just leave you in peace, i said what i wanted to say and ideally my previous message would have gone into that locked thread.

[taserz]

Let me tell you something interesting. Unlike some other firmware, We do NOT write to the eeprom of the hashboards. Should a bug, or a power failure occur during this, you may end with an apparently unusable miner, as certain firmware mods are known to corrupt the eeprom when writing their "tuning values" (Essentially copying out method of tuning machines). Instead, we talk directly to the chip using the PIC.

We won't lie to you unlike other stating how there are nasty values in the eeprom... lmfao

You can mix and match hasboards and basic chips as long as it is the same model unlike our competitors allowing quicker and easier repairs.

Our autotuning algorithm and features pioneered this industry which our competitors take advantage from and copy how they adjust chips in the same ways we do. We really appreciate your business and thank you for support the original firmware group not any of the copycats.

Also, another fun fact unlike all of our competitors we do not trigger one of the methods bitmain uses to identify if the firmware was loaded onto the machine (Not the eeprom for those who think that is the only way they can identify).


Also a little fun fact S19 in testing right now running at 160T on air cooling, WM m20s pushing 86T on air. stay tuned for the tuned results and the stress tests where we push the big numbers talking 200+ th/s!!!!

[taserz]

Our new update is almost ready. Just wanted to point out our sister service anthill.farm will soo be included with the current firmware fee at no extra cost

[GenTarkin]

Where's the miner source code for the firmware you are selling and distributing?

Oh Kano you know how this answer goes haha. The source code for the panel can easily be found on github. The drivers are though not public since they took many months to make from scratch to figure out how to talk to the control board and chips. Sadly because of this I can't just opensource it.

I was waiting for you to chime in on this haha

Correct me if Im wrong but , Im assuming you had to modify cgminer to make your drivers or modified drivers work with it? If so, wouldnt GPL dictate you must share said source?
Also, I havent read this whole thread ... but is it correct to assume that your modifications and / or vnish's mods are part of the L3+ nh firmware / cgminer?  I dont know who wrote the original devfee threads part but yeah ... I think GPL requires sharing almost, if not all of this source.

I personally take issue w/ the designed forced devfee part. As in, Ive seen miners "failover" to devfee indefinitely until said miner was restarted, The fact cgminer wont even start up unless devfee pools are alive...    its one thing to have a devfee mechanic ... its another to potentially have it steel a majority of hashrate / prevent mining of folks miners at large.

[kano]

Yes he even explicitly admits to violating the license in that reply.

[taserz]

Where's the miner source code for the firmware you are selling and distributing?

Oh Kano you know how this answer goes haha. The source code for the panel can easily be found on github. The drivers are though not public since they took many months to make from scratch to figure out how to talk to the control board and chips. Sadly because of this I can't just opensource it.

I was waiting for you to chime in on this haha

Correct me if Im wrong but , Im assuming you had to modify cgminer to make your drivers or modified drivers work with it? If so, wouldnt GPL dictate you must share said source?
Also, I havent read this whole thread ... but is it correct to assume that your modifications and / or vnish's mods are part of the L3+ nh firmware / cgminer?  I dont know who wrote the original devfee threads part but yeah ... I think GPL requires sharing almost, if not all of this source.

I personally take issue w/ the designed forced devfee part. As in, Ive seen miners "failover" to devfee indefinitely until said miner was restarted, The fact cgminer wont even start up unless devfee pools are alive...    its one thing to have a devfee mechanic ... its another to potentially have it steel a majority of hashrate / prevent mining of folks miners at large.

It will not get stuck on devfee indefinitely I have not seen that happen before. Source code is public.

[GenTarkin]

Where's the miner source code for the firmware you are selling and distributing?

Oh Kano you know how this answer goes haha. The source code for the panel can easily be found on github. The drivers are though not public since they took many months to make from scratch to figure out how to talk to the control board and chips. Sadly because of this I can't just opensource it.

I was waiting for you to chime in on this haha

Correct me if Im wrong but , Im assuming you had to modify cgminer to make your drivers or modified drivers work with it? If so, wouldnt GPL dictate you must share said source?
Also, I havent read this whole thread ... but is it correct to assume that your modifications and / or vnish's mods are part of the L3+ nh firmware / cgminer?  I dont know who wrote the original devfee threads part but yeah ... I think GPL requires sharing almost, if not all of this source.

I personally take issue w/ the designed forced devfee part. As in, Ive seen miners "failover" to devfee indefinitely until said miner was restarted, The fact cgminer wont even start up unless devfee pools are alive...    its one thing to have a devfee mechanic ... its another to potentially have it steel a majority of hashrate / prevent mining of folks miners at large.

It will not get stuck on devfee indefinitely I have not seen that happen before. Source code is public.

Source code is avail? where at?

[Moeter81]

I have installed BraiinOs on my S17 + miners.

I would like to use a different firmware, but I cannot get it installed. I tried it with an SD card but it doesn't work.

Can you help me?

[kano]

I have installed BraiinOs on my S17 + miners.

I would like to use a different firmware, but I cannot get it installed. I tried it with an SD card but it doesn't work.

Can you help me?

Don't use this one - it violates the cgminer license.

[georgibln89]

Hello,

I would like to ask you is that normal for T17 frequency to be a 720MHz and get 43TH/s?

Thanks!

[taserz]

I have installed BraiinOs on my S17 + miners.

I would like to use a different firmware, but I cannot get it installed. I tried it with an SD card but it doesn't work.

Can you help me?

You need to uninstall braiins. They make it hard to uninstall.

I have installed BraiinOs on my S17 + miners.

I would like to use a different firmware, but I cannot get it installed. I tried it with an SD card but it doesn't work.

Can you help me?

Don't use this one - it violates the cgminer license.

no go away your racist

Hello,

I would like to ask you is that normal for T17 frequency to be a 720MHz and get 43TH/s?

Thanks!

What is power draw? How many boards?

[georgibln89]

Hello,

I would like to ask you is that normal for T17 frequency to be a 720MHz and get 43TH/s?

Thanks!

What is power draw? How many boards?

I have one miner (T17) with 3 boards x30 chips (BM1397) in total 90pcs. Power consumption is 2290W, voltage on each board is 17V, frequency is 720MHz. Temperatures are 60 to 72 degrees for chips and 40 to 52 degrees for PCB.

Thanks!

[kano]

I have installed BraiinOs on my S17 + miners.

I would like to use a different firmware, but I cannot get it installed. I tried it with an SD card but it doesn't work.

Can you help me?

Don't use this one - it violates the cgminer license.

no go away your racist

Unexpected reply ... not sure how that's implied in anything I've ever posted on the forum in the last 10 years ...

But I will point out that since I am the 2nd main developer of cgminer, I certainly do know the license and how it's being violated by asic.to

[taserz]

S19, S19 Pro, T19, S19j, S19j pro, S19 Hydro firmware about to hit the shelves. Whole new system too

Also 2 other miners that are not to be named 

[kano]

S19, S19 Pro, T19, S19j, S19j pro, S19 Hydro firmware about to hit the shelves. Whole new system too

Also 2 other miners that are not to be named  

Hmm - posting lies about me above to further your illegal agenda ...

--

So I went to your site asic.to listed in the first post and there's a blue download link at the top.
I clicked on it.
This shows a list of firmware I can download.
So I clicked on one and it took me to your downloads here:
https://mega.nz/folder/n88URC4J#_WPlCR-AV38JVjVJia-d7Q

There I downloaded Antminer-T17+-2.0.3-.tar.gz

In the tar file there's an image file for the firmware: fw.tar.gz
In that tar file there's an image file for to the miner: uramdisk.image.gz

Decompressing that file gives the image file that contains usr/bin/cgminer

Please provide me with the source code download for the cgminer you are distributing in your firmware.
It is a requirement of my cgminer license that you provide it.

[HagssFIN]

@Taserz
Earlier you've claimed the source code is public. And also the cgminer license requires it to be public.

Where can we see the source code?

The alternative miner firmware providers are no better in their actions than Bitmain, if they keep violating the license.
If you can't respect the license, then I think you should write your own mining software.
But that's something only few people have been able to do so far.

[taserz]

S19, S19 Pro, T19, S19j, S19j pro, S19 Hydro firmware about to hit the shelves. Whole new system too

Also 2 other miners that are not to be named  

Hmm - posting lies about me above to further your illegal agenda ...

--

So I went to your site asic.to listed in the first post and there's a blue download link at the top.
I clicked on it.
This shows a list of firmware I can download.
So I clicked on one and it took me to your downloads here:
https://mega.nz/folder/n88URC4J#_WPlCR-AV38JVjVJia-d7Q

There I downloaded Antminer-T17+-2.0.3-.tar.gz

In the tar file there's an image file for the firmware: fw.tar.gz
In that tar file there's an image file for to the miner: uramdisk.image.gz

Decompressing that file gives the image file that contains usr/bin/cgminer

Please provide me with the source code download for the cgminer you are distributing in your firmware.
It is a requirement of my cgminer license that you provide it.

That is bitmains cgminer. well bmminer.. Ask them for the source code. Code injection != having the source code... You can open it up and try to dump cgminer from bitmain but it doesn't work that way since it is compiled code by bitmain. You can inject code though

@Taserz
Earlier you've claimed the source code is public. And also the cgminer license requires it to be public.

Where can we see the source code?

The alternative miner firmware providers are no better in their actions than Bitmain, if they keep violating the license.
If you can't respect the license, then I think you should write your own mining software.
But that's something only few people have been able to do so far.

Yes it is on github. Otherwise ask bitmain they compiled it they have source. If you hex edit a file do you have the source no...So you must contact bitmain for latest source. If you like I can give you email you can contact about this.

[kano]

S19, S19 Pro, T19, S19j, S19j pro, S19 Hydro firmware about to hit the shelves. Whole new system too

Also 2 other miners that are not to be named  

Hmm - posting lies about me above to further your illegal agenda ...

--

So I went to your site asic.to listed in the first post and there's a blue download link at the top.
I clicked on it.
This shows a list of firmware I can download.
So I clicked on one and it took me to your downloads here:
https://mega.nz/folder/n88URC4J#_WPlCR-AV38JVjVJia-d7Q

There I downloaded Antminer-T17+-2.0.3-.tar.gz

In the tar file there's an image file for the firmware: fw.tar.gz
In that tar file there's an image file for to the miner: uramdisk.image.gz

Decompressing that file gives the image file that contains usr/bin/cgminer

Please provide me with the source code download for the cgminer you are distributing in your firmware.
It is a requirement of my cgminer license that you provide it.

That is bitmains cgminer. well bmminer.. Ask them for the source code. Code injection != having the source code... You can open it up and try to dump cgminer from bitmain but it doesn't work that way since it is compiled code by bitmain. You can inject code though
...

You know what the license is, you know this isn't relevant.

The GPLv3 license quite clearly states that if you distribute cgminer, you must provide source code on request.

You are distributing cgminer, you must provide source code on request.

That also includes the code you are clearly stating you are injecting.