| Age | Commit message (Collapse) | Author |
|---|
|
support for SW to trigger zeroisation of a loaded key.
|
|
|
|
key loaded into the aes core.
|
|
ports in the core to support key status and timeout. Updated core testbench to match the new interface.
|
|
|
|
|
|
|
|
capacity. Does not yet work, but at least the linter is fairly happy.
|
|
|
|
blockRAM. Added test case that checks access to the API regs.
|
|
|
|
ModelSim.
|
|
debug outputs.
|
|
Fixed boundaries for the block counter. Now we don't read mem out of bounds.
|
|
possible to optimize.
|
|
|
|
both wrap and unwrap cases.
|
|
define to something more comprehensible.
|
|
|
|
and implement unwrap.
|
|
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.
|
|
number of operations. Bad news: All values are wrong.
|
|
are starting to work. As in AES is actually initialized and used.
|
|
|
|
|
|
do key wrap.
|
|
order in API logic.
|
|
|
|
number of nits and bugs. Added address generator for the API.
|
|
|
|
interface. Connected core into the top level wrapper.
|
|
|
|
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.
|
|
|
|
|
|
|
