Fix etherbone reads
Since https://github.com/enjoy-digital/litex/pull/1999, etherbone reads might result in garbage being output. This is caused by `be` not being set during the read. Fixes https://github.com/enjoy-digital/litex/issues/2031 Signed-off-by: Matthias Breithaupt <m.breithaupt@vogl-electronic.com>
This commit is contained in:
parent
583137eaf3
commit
7b4429e814
|
@ -251,6 +251,7 @@ class LiteEthEtherboneRecordReceiver(LiteXModule):
|
||||||
source.last.eq(count == fifo.source.rcount-1),
|
source.last.eq(count == fifo.source.rcount-1),
|
||||||
source.last_be.eq(source.last << 3),
|
source.last_be.eq(source.last << 3),
|
||||||
source.count.eq(fifo.source.rcount),
|
source.count.eq(fifo.source.rcount),
|
||||||
|
source.be.eq(fifo.source.byte_enable),
|
||||||
source.base_addr.eq(base_addr),
|
source.base_addr.eq(base_addr),
|
||||||
source.addr.eq(fifo.source.data[2:]),
|
source.addr.eq(fifo.source.data[2:]),
|
||||||
fifo.source.ready.eq(source.ready),
|
fifo.source.ready.eq(source.ready),
|
||||||
|
|
Loading…
Reference in New Issue