| Age | Commit message (Collapse) | Author |
|---|
|
and ciphers. Fixed copy crimes. Disabled hash cores for the time being since we want to debug the rng.
|
|
minor copy crimes. (3) autmagically removed trailing whitespace.
|
|
|
|
|
|
|
|
Add local SHA core wrappers, due to the need for registered outputs.
Remove unused demo-adder code, and reorganize sw directory.
|
|
1. EIM arbiter was updated to take advantage of 3 additional address
lines, that bunnie routed from the CPU to the FPGA. Now we have 19 address
lines instead of 16, that means 19-2=17 effective bits when using 32-bit
access.
2. In the doc directory there's a draft version of current EIM memory map.
3. I've figured out why you guys could not use read and write signals from
the arbiter the way they were supposed to be used. I was wrong when I
expected Joachim's cores to have registered outputs. They have a
combinatorial output in fact. EIM arbiter's minimum latency is 1 cycle, so
we have to register data coming out of cores. I've added these three lines
to every core wrapper (sha1.v, sha256.v and sha512.v):
reg [31 : 0] tmp_read_data_reg;
always @(posedge clk) tmp_read_data_reg <= tmp_read_data;
assign read_data = tmp_read_data_reg;
4. Joachim told me, that we are going to have different types of cores
(HASH, RNG, CIPHER and so on), so I redesigned EIM multiplexor to have
separate modules for every core type. RNG and CIPHER selectors right now
are just templates with some dummy registers. Here is what was modified in
the HASH multiplexor:
4a. Core number 0 was added. It is not an actual HASH core, but a set of
global (board-level) registers. I've added three registers so far: board
type, bitstream version and one writeable dummy general-purpose register.
4b. Core instantiation was made conditional to allow selecting of what
cores to actually implement. We can have a project that offers a large
number of cores, so people can disable unnecessary cores to speed up
compile time and to save some slices for something else.
4c. I have disconnected .error() output from cores. As far as I understand
it gets asserted when some non-existent register is being addressed. In
most projects that I've seen writes to empty regions of memory are
discarded and reads return zeroes. If you really need this kind of error
checking, please re-connect this output as needed.
4d. core_selector.v has an instruction on how to add new HASH cores to our
design.
5. TC11() was added to hash_tester.c to check that we can read global
board-level registers and that we have access to segments other than
HASH. The last check reads dummy registers from RNG and CIPHER segments
(which are just templates now), this effectively tests the 3 new added
address bits.
|
|
Cryptech blinkenlights logic into core select.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
that is able to talk to the sha256 core and perform a hash operation.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
inports called ootput etc. Read and write is better.
|
|
board. Fixed layout.
|
|
|
|
|
|
|
|
|
|
|
|
|
