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
X-Scale has quit [Ping timeout: 248 seconds]
X-Scale has joined #m-labs
sn00n has quit [Ping timeout: 264 seconds]
sb0 has joined #m-labs
<sb0> _florent_, cool! did you try with artiq? have you implemented the multi-channel transceiver init and the clocking API I was proposing?
<GitHub137> [artiq] sbourdeauducq opened issue #861: Sayma JESD intermittent initialization failure https://github.com/m-labs/artiq/issues/861
<sb0> ah clocking API seems fine
<sb0> _florent_, yea basically need to check/implement that all TXOUTCLK's are the same.
FelixVi has quit []
<GitHub141> [artiq] sbourdeauducq pushed 1 new commit to master: https://github.com/m-labs/artiq/commit/66e089b37649d31bfa71722c5e01cc05c7792b8d
<GitHub141> artiq/master 66e089b Sebastien Bourdeauducq: libboard/serwb: more explicit retry log message
<GitHub1> [artiq] sbourdeauducq closed issue #791: Wishbone bridge between Sayma AMC and RTM FPGAs https://github.com/m-labs/artiq/issues/791
<bb-m-labs> build #928 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/928
<bb-m-labs> build #1812 of artiq is complete: Failure [failed] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1812 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>
mumptai_ has joined #m-labs
mumptai has quit [Ping timeout: 268 seconds]
mumptai_ has quit [Remote host closed the connection]
<_florent_> sb0: I haven't tried with drtio with full artiq design, but at least it was tested on sayma_amc
<_florent_> sb0: I'll implement the multi-lane initialization procedure soon
mumptai has joined #m-labs
sn00n has joined #m-labs
sb0_ has joined #m-labs
sb0 has quit [Ping timeout: 260 seconds]
<sb0_> G33KatWork, without the data mask pins, you're going to need read-modify-write cycles to the DRAM to access with less than full burst granularity
<sb0_> no impact on reads
<sb0_> and that's intrinsic to the DRAM interface, the controller cannot do anything about it
<sb0_> G33KatWork, if your "memory mapped interface" includes a write-back cache with a line length >= the dram burst length, then you don't need the DM.
<sb0_> (>= and multiple of)
<G33KatWork> yeah, I was looking for an easy way to test my RAM on that board with easy memory writes from my processor, because I had to reverse engineer the pinout. Without an AXI interface generated by the MIG that's still possible of course, but more work ;)
<G33KatWork> I thought that maybe litedram generally doesn't use the DM pins and always does full burst writes and all the infrastructure for a whishbone interface which abstracts all that away is alrady there
<G33KatWork> and litedram looks way simpler than the stuff the MIG generates
<sb0_> for an even simpler controller there is minicon in misoc
<sb0_> you can just strip out the DM stuff from it and from the PHY
<sb0_> then make sure you always use the full burst (i.e. no use of wishbone sel signals on minicon)
<sb0_> removing DM is very simple, those pins aren't use for anything else
<G33KatWork> awesome, thanks. I'll check it out
<sb0_> then use the cache module to connect to another wishbone bus. then you can use sel on the interface to the cache module.
<GitHub184> [artiq] gkasprow commented on issue #854: In my media converter it shows LINK state when I plug SFP, even with AMC power supply off.... https://github.com/m-labs/artiq/issues/854#issuecomment-348690122
<GitHub190> [artiq] sbourdeauducq commented on issue #854: Why do I still get autonegotiation to work, then? Is that PHY chip still doing autonegotiation while in reset? https://github.com/m-labs/artiq/issues/854#issuecomment-348660942
<GitHub69> [artiq] sbourdeauducq commented on issue #854: What is the MII LED? https://github.com/m-labs/artiq/issues/854#issuecomment-348690981
<GitHub96> [artiq] sbourdeauducq commented on issue #861: This is at initialization, though we don't know at the moment if the link is reliable afterwards when the initialization succeeds. The boards are hot and I don't know if it happens with a cold board. What @enjoy-digital was suggesting you check is whether the HMC830 outputs clean clocks or not. https://github.com/m-labs/artiq/issues/861#issuecomment-348691456
<sb0_> whitequark, how is ethernet?
<GitHub136> [artiq] sbourdeauducq commented on issue #861: My understanding of the HMC830 is that if the PLL unlocks, it will not automatically try to relock or it will do so only once (depending on a bit in a configuration register). https://github.com/m-labs/artiq/issues/861#issuecomment-348693873
sb0_ has quit [Ping timeout: 268 seconds]
sb0_ has joined #m-labs
rohitksingh has joined #m-labs
FelixVi has joined #m-labs
<FelixVi> Is the 4 x Ad9912 version of Urukul currently available?
rohitksingh has quit [Quit: Leaving.]
<GitHub73> [smoltcp] whitequark commented on issue #87: I don't think FnOnce works in this signature. It's really unclear to me how this is supposed to work lifetime-wise too... https://github.com/m-labs/smoltcp/issues/87#issuecomment-348707076
hdante has joined #m-labs
hdante has quit [Read error: Connection reset by peer]
hdante has joined #m-labs
<whitequark> sb0_: working on it. will try to finish artiq_devtool changes today.
hdante has quit [Quit: My iMac has gone to sleep. ZZZzzz…]
X-Scale has quit [Ping timeout: 260 seconds]