Age | Commit message (Collapse) | Author |
|
|
|
Also remove the auto_zeroise code, since that's behaving badly, and it's
not used anyway in the integrate_mkmif branch.
|
|
problems by not automatically reset the key in the API. Enabled all testcases and disabled excessive debug outputs.
|
|
expected.
|
|
that timeout has occured. Added functionality to zeroise API key registers when timout has happened. Updated all auto_zeroise test cases to check that API key registers are properly zeroised.
|
|
|
|
status register.
|
|
|
|
after the Cryptech audit.
|
|
|
|
|
|
|
|
automatically. It seems to work, but needs a bit more testing.
|
|
|
|
after timeout. Status bits looks fishy though.
|
|
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.
|
|
|
|
|
|
|
|
was under read operation handling. Fixed this and now status write works. We can observe 0xdeadbeef in the memory after status write operation.
|
|
|
|
|
|
|
|
init.
|
|
does not support auto load. Updating the write status test case to use wait_ready() for dut status.
|
|
vendor supplied memory model.
|
|
vendor specific memory model we need here.
|
|
of status word.
|
|
|
|
|
|
target-
|
|
|
|
|
|
|
|
|
|
|
|
debugging...
|
|
|
|
protocol complexity.
|
|
interfaces and registers to be able to pass mkm status to host. Updated dut instantiation in core testbench to.
|
|
keywrap_core to support control of MKM access operations.
|
|
|
|
|
|
|
|
|
|
read and write key handling.
|
|
|