sb0 changed the topic of #m-labs to: ARTIQ, Migen, MiSoC, Mixxeo & other M-Labs projects :: fka #milkymist :: Logs http://irclog.whitequark.org/m-labs
<GitHub93> [artiq] sbourdeauducq pushed 3 new commits to rtio-sed: https://github.com/m-labs/artiq/compare/6c049ad40ccf...893be82ad167
<GitHub93> artiq/rtio-sed 5f083f2 Sebastien Bourdeauducq: rtio/dma: fix signal width
<GitHub93> artiq/rtio-sed a9c9d57 Sebastien Bourdeauducq: rtio/dma: add full-stack test with connection to RTIO core
<GitHub93> artiq/rtio-sed 893be82 Sebastien Bourdeauducq: rtio/dma: raise underflow in test
sb0 has joined #m-labs
<sb0> whitequark, I've been trying to reproduce the DMA/SED issue in gateware simulation but could not. it would seem that the gateware is behaving itself.
<sb0> on the other hand I don't see any firmware change that could have caused this
<sb0> it's really annoying
<whitequark> sb0: I'll get back to poking firmware in a bit, let's see if I can verify some of my guesses
sb0 has quit [Quit: Leaving]
rohitksingh_work has joined #m-labs
_whitelogger has joined #m-labs
<GitHub63> [artiq] jordens commented on issue #793: With `f_data = 600 MHz` and 4x DAC interpolation to 2.4 GHz, from the `0.2 f_data` transition skirt width of the AD9154 interpolation we have:... https://github.com/m-labs/artiq/issues/793#issuecomment-335080384
FabM has joined #m-labs
rohitksingh_work has quit [Ping timeout: 248 seconds]
rohitksingh_work has joined #m-labs
<GitHub44> [artiq] hartytp commented on issue #793: @jordens @jbqubit Last lime we spoke about this, I though we agreed to go for:... https://github.com/m-labs/artiq/issues/793#issuecomment-335096743
<mithro> What is misoc/cores/mxcrg.v used for?
rohitksingh_work has quit [Ping timeout: 246 seconds]
Gurty has joined #m-labs
Gurty has quit [Changing host]
Gurty has joined #m-labs
rohitksingh_work has joined #m-labs
rohitksingh_wor1 has joined #m-labs
rohitksingh_work has quit [Ping timeout: 248 seconds]
rohitksingh_wor1 has quit [Ping timeout: 240 seconds]
rohitksingh_work has joined #m-labs
<rjo> mixxeo crg i'd guess.
<GitHub150> [artiq] sbourdeauducq commented on issue #793: @jordens Again, the backplane for DRTIO is limited to 5G. So that would be 3beG, not 6. https://github.com/m-labs/artiq/issues/793#issuecomment-335141537
<GitHub194> [artiq] sbourdeauducq commented on issue #793: @jordens Again, the backplane for DRTIO is limited to 5G. So that would be 3G, not 6. https://github.com/m-labs/artiq/issues/793#issuecomment-335141537
<GitHub152> [artiq] jordens commented on issue #793: @sbourdeauducq ack.... https://github.com/m-labs/artiq/issues/793#issuecomment-335142059
<GitHub133> [artiq] hartytp commented on issue #793: > or the 150-260 MHz use case 600 MHz f_data has the best performance (200 MHz +- 60 MHz from f1/f2 without the AA filter kicking in)... https://github.com/m-labs/artiq/issues/793#issuecomment-335143580
Gurty has quit [Ping timeout: 255 seconds]
<GitHub105> [artiq] jordens commented on issue #793: @hartytp In the old minutes there was a statement about 1 GHz. I still thing 600 MHz is better for the reasons mentioned above.... https://github.com/m-labs/artiq/issues/793#issuecomment-335146008
rohitksingh_work has quit [Read error: Connection reset by peer]
<GitHub177> [artiq] jordens commented on issue #793: They were worried about spur free dynamic range within 150-260 MHz. Since the AA filter only suppresses to 58 dB, that will be limiting for f_RTIO=125 MHz.... https://github.com/m-labs/artiq/issues/793#issuecomment-335146871
shuffle2 has joined #m-labs
Gurty has joined #m-labs
<shuffle2> i'd like to use migen+zedboard to make a design that exposes bram to the arm core. is that (bram, various axi, ...) already usable from migen somehow? or would i need to lift the verilog/vhdl out of vivado somehow and wrap it?
<shuffle2> also migen defaults to using ISE with zedboard atm. i changed it to vivado and it works fine for some simple thing...(really, maybe migen should just try both for xilinx targets?)
<GitHub45> [artiq] jordens commented on issue #793: With `f_data = 600 MHz` and 4x DAC interpolation to 2.4 GHz, from the `0.2 f_data` transition skirt width of the AD9154 interpolation we have:... https://github.com/m-labs/artiq/issues/793#issuecomment-335080384
<GitHub115> [artiq] hartytp commented on issue #793: > They were worried about spur free dynamic range within 150-260 MHz. Since the AA filter only suppresses to 58 dB, that will be limiting for f_RTIO=125 MHz.... https://github.com/m-labs/artiq/issues/793#issuecomment-335149546
<GitHub116> [artiq] jordens commented on issue #793: I don't see a roadblock. It will just take longer and more fiddling/trial and error to deliver a 1 GHz f_data bitstream than 600 MHz. And once there are problems with e.g. DRTIO there will be a need to exclude electrical issues and hence the need for a slower design anyway. https://github.com/m-labs/artiq/issues/793#issuecomment-335153967
<rjo> shuffle2: bram is inferred (i.e. integrated). redpid has some code you can reuse for that.
kristianpaul has quit [Remote host closed the connection]
kristianpaul has joined #m-labs
rohitksingh has joined #m-labs
<GitHub122> [artiq] sbourdeauducq commented on issue #793: Can we just do the 600 MHz for now? There have been way enough feature explosions and delays already. https://github.com/m-labs/artiq/issues/793#issuecomment-335219974
<GitHub178> [artiq] jordens commented on issue #793: That's what I would like to do as well. https://github.com/m-labs/artiq/issues/793#issuecomment-335228533
cr1901 has quit [Ping timeout: 258 seconds]
rohitksingh has quit [Quit: Leaving.]
<shuffle2> rjo: cool :) any idea about the arm core interface?
mumptai has joined #m-labs
mumptai has quit [Remote host closed the connection]
<GitHub77> [sinara] gkasprow pushed 1 new commit to master: https://github.com/m-labs/sinara/commit/a18981ba6d9957a763358d09973deb249a4fef1d
<GitHub77> sinara/master a18981b Greg: fixed #325, #322, #319, #310, #309