[libre-riscv-dev] daily kan-ban update 26jun2020
Luke Kenneth Casson Leighton
lkcl at lkcl.net
Fri Jun 26 20:46:44 BST 2020
On Fri, Jun 26, 2020 at 8:39 PM Michael Nolan <mtnolan2640 at gmail.com> wrote:
> > ok that will be becauuuse.... x_busy_o is not being passed out to pi.busy_o.
> Nah, lsmem is never busy, it responds to a read on the following cycle.
ok. FSMs do my head in.
> I think the test case starts the second read on the same cycle as the
> first read finishes (which is fine), but it sees that ld.ok is true and
> assumes that it means the second read is finished. I think I got it
> working now
ha! excellent. ok. so, the only other thing is, where the pimem.py
test puts data into the 1st row (row 0) of the underlying 64-bit-wide
Memory, pi2lsui is dropping the 1st read into row 0 and the 2nd read
into row *one*.
i'm adding a quick unit test on that one.
More information about the libre-riscv-dev