Joachim Strömbergson

Note the status in the README file: "Not done Does not work."

Thank you for the reporting. There are several bugs in the design. It is far from complete. Unfortunately I haven't had time for a long while to complete the core.

It should work, but I need to investigate. 64 bit XOR is implemented in one layer of LUT/slices.

The core did not work as expected. I'm reworking the core from the bottom up. I've also added a reference model from the RFC to drive the testing. I have...

A possibly related issue is that on MacOS, when running hexyl without any input the application can't be terminated. Like this: This is with hexyl 0.6.0 on MacOS 10.14.6

Hi! You need to be more precise. What are you trying to accomplish? And what do you mean with "run the verilog correctly?". Do you get an incorrect result? There...

Good to hear that you've made progress! "I have successfully got the yosys result. It is pretty big." The size of the core is comparable in size to other iterative...

For the complete sha256 functionality you need these files: sha256_core.v sha256_k_constants.v sha256_w_mem.v The sha256_core instantiates the sha256_k_constants and the sha256_w_mem modules internally. Without them the design will contain black boxes...

Yes. You can just run something like: read_verilog sha256_core.v sha256_k_constants.v sha256_w_mem.v

No, that does not seem right. There are build results for SHA-256 and md5 in their repos, and SHA-256 is normally 2-3 times bigger when it comes to gates, cells....