commit | 5760046b5dfd27b3168996477ca98fa18ffb5e1f | [log] [tgz] |
---|---|---|
author | Konrad Rzeszutek Wilk <konrad@kernel.org> | Sat Jun 19 09:46:21 2021 -0400 |
committer | Konrad Rzeszutek Wilk <konrad@kernel.org> | Sat Jun 19 09:46:21 2021 -0400 |
tree | 9b40b8a9af8e80575ed9d7b965b584937289bfb9 | |
parent | 2092c6d8403fe059e574f768e0bb5f3d4eeabf18 [diff] |
info.yaml: Update with proper project name, and SHA1 for id .. which will be changed later on. Signed-off-by: Konrad Rzeszutek Wilk <konrad@kernel.org>
See a https://github.com/konradwilk/sha1 for the full git history of this code. Branch name is submission-mpw-two.
This is an implementation of [https://www.rfc-editor.org/rfc/inline-errata/rfc3174.html](RFC 3174) of SHA-1 engine.
It is not the most secure one nowadays (it is still used for git commit ids and TPM PCR values), but it looked like the easiest of the SHA engines to implement. The communication channel is via WishBone commands to provide sixteen words after which the engine starts and computes the digest in about 160 cycles. Then digest can be retrieved via the wishbone. There is a IRQ line so when it has completed it will bring it high if that is enabled.
If you want to see this more interactively, I would recommend you clone https://github.com/konradwilk/sha1 and run
make test_wb_logic
which will use the various WishBone commands to program it.
To create the GDS files, there are macros that are being ingested. The best way to do is by checking out the SHA-1 engine:
git clone https://github.com/konradwilk/sha1
And then there are some pre-requisities:
open_mpw_checker
installed as well (and the docker container).From within the sha1
directory execute:
make gds
which will generate the GDS, LEF, etc files. Copy them in the gds
sub-directory. After that, you need to copy them to caravel_user_project
. To do that:
make caravel
which will copy the appropiate files, run the OpenLANE to jam the macros together, and run the checkers.