smartass111,

To get you started on adding additional functionality, here is a quick summary of what I did, and what you would need to add in.

A PE file has many segments in it (varies by file), like .data, .bss, .text ... .text is where strings are stored. From the .text segment, with a good disassembler will break those out and point you back to the assembly for the function(s) that reference those strengths.

So, I started backward.

.text -> "frequency" -> function calling it. Then I spent some time exploring that function, it's callers and callees, and started mapping out the code path around it.

In that, I found the setup functions which took in the frequency and passed it down to a function I could readily tell was calld "set_frequency_chain". Using hexrays I was able to track that back to the fact it takes a chain and a frequency as an argument (as an aside...).

The fact that bitmain limited this to 2 frequencies made it easier than it should have been.  In the calling function, I found their 2 hardcoded constansts for 500 and 550.

Initially I just modified 550 to 650 (simplest byte changes), and realized it could do 650/500 -- that's basically what the free one is. 575+500.

The "paid" version is different in that the constants are not changed, but rather the conditionals that limit it are removed.
That allows you to pass anything you want down to set_frequency_chain.

Now, to enable per-board frequency control, we can continue from there.

That same set_frequency_chain has a calling function (this is about the per-board stuff) which bitmain neutered. Right now it iterates over 4 boards (a constant) and calls set_frequency_chain for eacho f those 4 boards with the frequency passsed in.

To enable per-board freuqency, that function calling set_frequency_chain needs to be completely rewritten and the binary patched. From some research papers, I found how how to add segments to a PE file (this wasn't possible a couple of years ago). So a new function can be written to read the config file, just reeanble finding/processing bitmain-freqX, then simply iterate over the number of boards and initialize each chain. The original iterator has to be skipped, so you have to jump into what you add, then jump back.

That'll enable freq-per-board. For bonus points, an API call can be added to enable calling bitmain_ZCASH_reinit_chain on a given chain if you change the frequency. That'll overload the 'reset' condition for a board to enable changing frequency on the fly.

Add some intelligence to tune the frequencies based on observations of the data in the system, and boom, you'll have a self-tuning, maximally overclockable image.

Some of these tactics will work for any cgminer reverse engineering activity.

Thanks,

Jason

Awesome! Thank you for sharing freely and openly.

.... and for the record, any one responding to my post and providing feedback, did it of their own volition. While that was 'good marketing', it was not driven by me and was completely organic.
.... and as far as comments about donations, you can see for yourself by checking the addresses for donation. The only funds sent to those were funds I mined myself during testing, and funds someone sent before talking to me asking to get the full version..

I've updated my post pointing people to you. Enjoy!

I'll stop working on per-hashboard-frequency management that would have worked on every single cgminer based miner Bitmain has released.

To do it, just add 2 more segments to cgminer, code up the frequency management reading functions back from cgminer.conf, then go into the main loop that handles frequency setting for the hashboards, jump the current function into your code, set up the same registers, and jump back into the function that actually sets the board frequencies.
Second, modify cgminer to support updating the frequencies across the boards by not having it restart. To do this, hook into bitmain_ZCASH_reinit_chain, but don't step on the functionility int he check_miner_status() function.

Also, please update the image to support auto-tuning of the frequencies once you have this done so the end users do not have to worry about the clocking manually. Many do not know how to SSH/etc.

Back to my day job!

-j

Hi all,

Based on community feedback, and taking into consideration the 25% tariff many of us had to pay, difficulty increases, etc., I have decided to add a single node option that is 25% less than the 2 node option (which has stayed the same).

This means for 25% less you can get up to 25% more (and those rare systems that can go well above 650Mhz can gain up to 50% more than factory... but this is _RARE_) for a single Z9; it is like adding a Z9 mini to your Z9!

Thank you,

Jason

Are you a unix-type-person? In other words, could you tar up the filesystem and share it with me?

0j

Unfortunately, I cannot. At this point my Z9 access is not physical but remote only.

-j

@avi2 - no direct plans. I'd need a donor mini at a minimum to attempt. I need to get other features done first tho, I think.

psycho, did you happen to count the # of fins on the heatsinks? By smaller, do you mean they are thinner fins? heat dissipation there is about surface area, so if htey increased fin count by making them thinner, it might be a neat gain.. but thermodynamics isn't my area of expertise.

psychosunshine - I try to stay 75C or less, personally. So you are in good shape. These are not temp limited, but rather voltage limited on higher overclocks... although it's possible that with exceptional cooling, you can get away with higher frequencies.

This is all supposition, but there are more ASICs per board, a longer board, and the same fans, times 2 (well, i think thye are the same, I didn't verify). I think thermal management (heat dissipation in this case) may be more of a challenge on the Z9s vs. minis.

Those numbers are excellent though if you are getting that. I personally couldn't ever go over 681Mhz on any of mine. Good job!

-j

badbart, awesomeminer is simply automating editing the /config/cgminer.conf file. That's the simplest way to do it, and how I actually managed my Z series miners.

It may be that psychosunshine just has an exceptional set of ASICs.

-j

@Matt - hopefully unlock it if it has more potential. See my other thread on the Z9 for example: https://bitcointalk.org/index.php?topic=5036968

Jason

ltdray -- A full refund has been provided to the return address you gave me. I am sorry this did not work out for you. I honestly think you may have a hardware problem with the machine given the information provided. I would use the stock firmware and test on 500/550Mhz.

I will recommend, going forward, anyone wanting to use the full firmware, try the demo firmware first.

Thank you for your patience and if you happen to be able to figure things out with your machine, the overclock firmware I provided will still work, as my gift to you for  your patience and troubles.

Jason

ltdray -

To answer your question, You are the only person I know of who was apparently unable to get even the lowest of frequencies working.

I thought you were going to downgrade to factory firmware since, if memory serves, you said yours does not even work at 550Mhz. I offered you a refund, and then it appeared your image was enabled at another location so I did not process the refund. Rather than jumping to a conclusion, I reached out to you via email to understand both the extra download as well as the other issues you were having.

I responded "I do not believe your machine can handle an overclock" after you sent me this message from your logfile "Sep 28 15:23:39 (none) local0.notice cgminer[21054]: recheck: chainid 0 exist 1 asicnum 0 realnum 16". That message, as best I can interpret it, states "the firmware was expecting 16 ASICs, but when trying to initialize it, none responded". I didn't have the full log, and just that single line from this event, so that is my best guess.

Where we last left our conversation, I told you that per the screenshot, you had not yet reloaded the factory firmware. I've since followed up with another email after that, but have not heard back.

Thank you,

Jason

So.... if it provides +2%, and they take 2%, it is net 0. Why would we want this?

"HI, PLEASE USE OUR SOFTWARE. IT GAINS 2% FOR US."

Awesome -- you are doing better than mine did! My "good" z9 would do 681, but would not do 675! lol.... and you are getting the same/better sol at a lower wattage.

win!

-j

I am now caught up with PMs/emails - If I have missed yours, please reach out to me again and I apologize for missing you.

Thanks!

Jason

sukitars,

Your download has been pulled from 4 distinct locations and has been disabled. Please PM/DM me to discuss.

EDIT: Thank you for reaching out to me. This has been resolved.

Thank you,

Jason

Ouch - my brain doesn't want to even process this!

Thank you!

Jason

Got it. I just joined their discord and will see if I can get an engagement.

Thank you!

-j

Hmmm. Do you have a contact(s) at nicehash? I'd love to know what needed to be changed...

EDIT: I sent a note to nicehash to see if I can get in touch with a technical contact. I think this would be a great addition.

-j