jkiv

Also move testing over to formal verification, rather than `#1 clk = ~clk` and `$display` calls.

See [ecppool-board](https://github.com/jkiv/ecppool-board)

Started `ecp5` branch, targetting the [OrangeCrab r0.2](https://gregdavill.github.io/OrangeCrab/r0.2/)

`top_*.v` should be per-board, knowing the chip and capabilities...

Eh, not clear from datasheet if this is supported at a high level...

It's probably easy enough to manage with address pointers. Might be worthwhile to try.

Only really makes sense for the message body. Would need to detect/select/redirect those bytes to RAM.

[Each ice40 device has between 8 and 32 256x16 (4kbits) RAM blocks.](http://www.latticesemi.com/view_document?document_id=47775) Currently using two for K[t] (32-bits). For M[t], could use another two, leaving 4 to 28 remaining.