[Cryptech-Commits] [core/sha256] 01/01: Adding more info about the core.

git at cryptech.is git at cryptech.is
Tue Feb 25 09:20:09 UTC 2014


This is an automated email from the git hooks/post-receive script.

joachim at secworks.se pushed a commit to branch master
in repository core/sha256.

commit 19918044375794d90b9fa7d960b50d1832115c4e
Author: Joachim Strömbergson <joachim at secworks.se>
Date:   Tue Feb 25 10:20:02 2014 +0100

    Adding more info about the core.
---
 README.md | 10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/README.md b/README.md
index d27d280..10150df 100644
--- a/README.md
+++ b/README.md
@@ -25,12 +25,14 @@ The actual core consists of the following files:
 - sha256_w_mem.v - W message block memort and expansion logic.
 - sha256_k_constants.v - K constants ROM memory.
 
-The top level entity is called sha256_core.
+The top level entity is called sha256_core. This entity has wide
+interfaces (512 bit block input, 256 bit digest). In order to make it
+usable you probably want to wrap the core with a bus interface.
 
-Unless you want to provide your own interface you also need to select
-one top level wrapper. There are two wrappers provided:
+Unless you want to provide your own interface you therefore also need to
+select one top level wrapper. There are two wrappers provided:
 - sha256.v - A wrapper with a 32-bit memory like interface.
-- wb_sha256.v - A wrapper that implement a [Wishbone](http://opencores.org/opencores,wishbone) interface.
+- wb_sha256.v - A wrapper that implements a [Wishbone](http://opencores.org/opencores,wishbone) interface.
 
 ***Do not include both wrappers in the same project.***
 




More information about the Commits mailing list