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
rjo1 has joined #m-labs
sn00n_ has joined #m-labs
stekern_ has joined #m-labs
rjo has quit [*.net *.split]
stekern has quit [*.net *.split]
sn00n has quit [*.net *.split]
balrog has quit [Ping timeout: 240 seconds]
balrog has joined #m-labs
rohitksingh_work has joined #m-labs
sb0 has quit [Quit: Leaving]
sb0 has joined #m-labs
sb0_ has joined #m-labs
sb0_ has quit [Client Quit]
sb0 has quit [Ping timeout: 240 seconds]
FabM has joined #m-labs
sn00n_ is now known as sn00n
X-Scale has joined #m-labs
rohitksingh_work has quit [Read error: Connection reset by peer]
rohitksingh_work has joined #m-labs
rohitksingh_work has quit [Read error: Connection reset by peer]
mumptai has joined #m-labs
rohitksingh has joined #m-labs
rohitksingh has quit [Client Quit]
kmehall has quit [Ping timeout: 252 seconds]
kmehall has joined #m-labs
FelixVi has joined #m-labs
<GitHub170>
[artiq] gkasprow commented on issue #854: I think I know where the problem is. I implemented simple condition in MMC firmware that resets the PHY chip after FPGA gets configured and DONE goes low.... https://github.com/m-labs/artiq/issues/854#issuecomment-348584527
<G33KatWork>
hi, I have a question about litedram. Suppose I have a board with 2 16 bit DDR3 chips on it where the manufacturer tried to save pins and didn't wire up the 4 data mask pins. Now Xilinx' MIG only supports an AXI interface if these pins are actually connected to the chips. Does litedram need them, too for a memory mapped interface? All I want for easy testing right now if everything works is an easy way
<G33KatWork>
to read and write to/from the memory
<G33KatWork>
is that even the right channel to ask such a question?
<X-Scale>
G33KatWork: there's also ##fpga
FabM has quit [Quit: ChatZilla 0.9.93 [Firefox 52.5.0/20171114221957]]
<G33KatWork>
okay, litedram uses the data mask pins. just found it in the code
<GitHub155>
[artiq] enjoy-digital commented on issue #860: It would be interesting to look at the output of the HMC7043 to be sure the clocks are clean. (from the first tests i remember it was not the case, so this could maybe explain the intermittents JESD failures). https://github.com/m-labs/artiq/issues/860#issuecomment-348623163