_florent_ changed the topic of #litex to: LiteX FPGA SoC builder and Cores / Github : https://github.com/enjoy-digital, https://github.com/litex-hub / Logs: https://freenode.irclog.whitequark.org/litex
tpb has quit [Remote host closed the connection]
tpb has joined #litex
gregdavill has joined #litex
kgugala has joined #litex
kgugala_ has quit [Ping timeout: 256 seconds]
Degi has quit [Ping timeout: 258 seconds]
Degi has joined #litex
peepsalot has quit [Quit: Connection reset by peep]
peepsalot has joined #litex
jaseg has quit [Ping timeout: 272 seconds]
jaseg has joined #litex
CarlFK has quit [Quit: Leaving.]
scanakci has quit [Quit: Connection closed for inactivity]
CarlFK has joined #litex
gregdavill_ has joined #litex
gregdavill has quit [Read error: Connection reset by peer]
CarlFK has quit [Quit: Leaving.]
CarlFK has joined #litex
john_k[m] has quit [Ping timeout: 256 seconds]
guan has quit [Ping timeout: 256 seconds]
lf has quit [Ping timeout: 256 seconds]
lf_ has joined #litex
john_k[m]1 has joined #litex
guan has joined #litex
carlomaragno has quit [Ping timeout: 256 seconds]
carlomaragno has joined #litex
_whitelogger has joined #litex
st-gourichon-fid has joined #litex
TMM has quit [Remote host closed the connection]
TMM has joined #litex
st-gourichon-fid has quit [Ping timeout: 272 seconds]
_whitelogger has joined #litex
st-gourichon-fid has joined #litex
st-gourichon-fid has quit [Ping timeout: 258 seconds]
<_florent_> lf_: i just wrote a wiki page about the Migen/nMigen situation: https://github.com/enjoy-digital/litex/wiki/Migen-nMigen
<tpb> Title: Migen nMigen · enjoy-digital/litex Wiki · GitHub (at github.com)
st-gourichon-fid has joined #litex
HoloIRCUser has joined #litex
dasdgw has quit [Ping timeout: 246 seconds]
kgugala_ has joined #litex
kgugala has quit [Ping timeout: 272 seconds]
gregdavill_ has quit [Ping timeout: 260 seconds]
kgugala_ has quit [Read error: Connection reset by peer]
kgugala has joined #litex
kgugala_ has joined #litex
kgugala has quit [Ping timeout: 260 seconds]
kgugala has joined #litex
kgugala has quit [Read error: Connection reset by peer]
kgugala has joined #litex
kgugala_ has quit [Ping timeout: 240 seconds]
HoloIRCUser1 has joined #litex
HoloIRCUser has quit [Ping timeout: 256 seconds]
jordigw has quit [Quit: leaving]
lf_ is now known as lf
<lf> _florent_: ah thx i will take a look at the minerva integration
jaseg has quit [Ping timeout: 260 seconds]
jaseg has joined #litex
gregdavill_ has joined #litex
<zyp> the way I see it, while integrating a nmigen core by treating it as a black box is easy, it has some disadvantages like not being able to easily hook up litescope to internal signals
<zyp> that's what's been keeping me on migen so far
loxodes has quit [Quit: WeeChat 1.4]
loxodes has joined #litex
<loxodes> I'm running into problems writing a burst of words to SRAM over wishbone in a Migen module in a LiteX SoC, and I'm looking for ideas what the cause might be or on how to approach debugging.
<loxodes> I've copied the wishbone writing approach from litex/soc/cores/uart.py (My wishbone writing code is here: https://github.com/loxodes/vna/blob/devel/breakouts/adc_32xx/software/ddr_test.py#L203)
<tpb> Title: vna/ddr_test.py at devel · loxodes/vna · GitHub (at github.com)
<loxodes> Currently I'm writing the same incrementing number to SRAM, i.e I write "1" 1024 times and then the next time I trigger a burst I'll write "2" 1024 times.
<loxodes> The first 16 words writes are always sucessful, however after that blocks of writes fail in some multiple of 8 words. I.e, on the second pass I might see "1" on the first 16 words in memory then "0" for the next 8, then "1" for the next 8.
<loxodes> If I read N words from different portion of memory in C in the firmware memory prior to writing a burst of words, the first N writes during a burst from the Migen module to SRAM work. (Where working is that I read back the expected value for that memory location from the firmware.)
<loxodes> Do y'all have any ideas on what might be the source of this behavior? (Is there caching or buffering happening when writing to memory somewhere that might overflow but still pass back a high ACK over wishbone but discard a write attempt? Are long bursts of writes over wishbone not expected work?)
<mithro> _florent_: It might also be worth mentioning that the most popular RISC-V core used with LiteX is not written in Migen but in-fact SpinalHDL
_whitelogger has joined #litex
lf has quit [Ping timeout: 260 seconds]
lf has joined #litex