[libre-riscv-dev] daily kan-ban update 09jun2020

Cole Poirier colepoirier at gmail.com
Tue Jun 9 22:01:14 BST 2020

On Jun 9 2020, at 1:15 pm, Luke Kenneth Casson Leighton <lkcl at lkcl.net> wrote:

> with michael having added the qemu-execution thing, you should now
> first be able to add a "twi" (or tdi) instruction unit test to that,
> first.

This is filling in the pseudo-code for the soc/decoder/isa/caller.py?

> this will allow you to check that the *simulator* is correct.

How do I use qemu to verify that the simulator is correct? Sorry I've
looked on the bug report and the wiki? Is there a wiki page with the
procedure? If not, what's the procedure I should follow?
> then after you know that the *simulator* is correct, the same unit
> test can be used in test_pipe_caller.py, and in that way you will then
> be able to test that the *hardware* is correct.

Sounds like a plan.


More information about the libre-riscv-dev mailing list