| Age | Commit message (Collapse) | Author |
|---|
|
correctly. Now we just need to stop processing whe we should.
|
|
correctly. A state is wrong and memory is read too far.
|
|
interface. A bit more kludgy, esp since we need to use bank switching to be able to provide enough address space. But this removes a possible problem of the streaming address counter running wild.
|
|
things go bad and where the isssues are.
|
|
number of operations. Bad news: All values are wrong.
|
|
are starting to work. As in AES is actually initialized and used.
|
|
correctly.
|
|
doesn't hang. Now for some bug hunting.
|
|
|
|
|
|
rread works correctly.
|
|
|
|
|
|
|
|
|
|
read and write words from and to the dut API.
|
|
|
|
|
|
|
|
do key wrap.
|
|
order in API logic.
|
|
processing. This includes breaking up code statements.
|
|
with short description and copyright, license used in Cryptech.
|
|
|
|
|
|
|
|
|
|
number of nits and bugs. Added address generator for the API.
|
|
|
|
interface. Connected core into the top level wrapper.
|
|
|
|
|
|
needed to get intermediate values. Removed the aes model taken from the aes core.
|
|
be able to bild and run top level simulation as well as linting all rtl code.
|
|
|
|
|
|
|
|
simulate with the AES core. Minor update to header and README. Clarified that it is RFC 5649 we are implementing.
|
|
wrapping using aes_core and the keywrap_mem. (2) Minor cleanup to the keywrap_mem code.
|
|
No problems.
|
|
|
|
|
|
|
|
|
