03:49 <sb0> rjo, of course clock it from kasli, but how?

04:09 <sb0> whitequark, any update on the camera driver?

04:15 <sb0> rjo, this was discussed in the SED issue iirc

04:16 <sb0> there are the pipeline stages for the FIFO selector, sorting network, etc.

04:25 <bb-m-labs> build #719 of artiq-win64-test is complete: Warnings [warnings python_coverage] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/719 blamelist: Robert Jordens <rj@m-labs.hk>, Robert Jordens <jordens@gmail.com>

04:28 <bb-m-labs> build #2039 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2039

09:02 <GitHub158> [artiq] jordens pushed 2 new commits to master: https://github.com/m-labs/artiq/compare/b6395a809b60...2adba3ed33ad

09:02 <GitHub158> artiq/master 2adba3e Robert Jordens: urukul: document ad9912, and cpld, fix api

09:02 <GitHub158> artiq/master ede9867 Robert Jordens: ad9910: add documentation

09:31 <bb-m-labs> build #1194 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/1194

09:37 <bb-m-labs> build #720 of artiq-win64-test is complete: Warnings [warnings python_coverage] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/720 blamelist: Robert Jordens <rj@m-labs.hk>

09:40 <bb-m-labs> build #2040 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2040

09:53 <rjo> sb0: connect one of the clock outputs of kasli to urukul. what's the question?

10:00 <rjo> sb0: ack the SED effect. i hadn't realized that was adding so much pipelining between the timestamping and the phys outputs.

11:22 <GitHub140> [artiq] hartytp commented on issue #911: This is currently working fine for me.... https://github.com/m-labs/artiq/issues/911#issuecomment-365573868

11:23 <GitHub59> [artiq] hartytp commented on issue #911: This is currently working fine for me.... https://github.com/m-labs/artiq/issues/911#issuecomment-365573868

12:25 <GitHub143> [artiq] hartytp commented on issue #911: PS like the new diagnostics in artiq_flash. https://github.com/m-labs/artiq/issues/911#issuecomment-365592074

12:32 <rjo> sb0: what kind of testing did you do on SED?

12:33 <rjo> i am seeing weird things on rtio event replacement. sometimes events just get swallowed silently.

12:43 <sb0> rjo, do you have a repro?

12:44 <sb0> rjo, what clock output, how do you set it up, etc.

12:45 <GitHub104> [artiq] sbourdeauducq closed issue #911: building sayma_amc: no rule for libunwind-bare.a https://github.com/m-labs/artiq/issues/911

12:49 <GitHub170> [artiq] hartytp commented on issue #908: @sbourdeauducq Was going to have a look at synchronisation. Built the binaries with the latest ARTIQ, but still see... https://github.com/m-labs/artiq/issues/908#issuecomment-365597552

12:50 <GitHub152> [artiq] hartytp commented on issue #908: @sbourdeauducq Was going to have a look at synchronisation. Built the binaries with the latest ARTIQ, but still see... https://github.com/m-labs/artiq/issues/908#issuecomment-365597552

12:52 <GitHub67> [artiq] hartytp commented on issue #908: @sbourdeauducq Was going to have a look at synchronisation. Built the binaries with the latest ARTIQ, but still see... https://github.com/m-labs/artiq/issues/908#issuecomment-365597552

12:52 <GitHub24> [artiq] hartytp commented on issue #908: @sbourdeauducq Was going to have a look at synchronisation. Built the binaries with the latest ARTIQ, but still see... https://github.com/m-labs/artiq/issues/908#issuecomment-365597552

12:52 <GitHub14> [artiq] hartytp commented on issue #908: @sbourdeauducq Was going to have a look at synchronisation. Built the binaries with the latest ARTIQ, but still see... https://github.com/m-labs/artiq/issues/908#issuecomment-365597552

13:35 <GitHub50> [artiq] hartytp commented on issue #908: No memtest issues without the SAWG, but then I can't test synchronization. @sbourdeauducq thoughts? https://github.com/m-labs/artiq/issues/908#issuecomment-365608287

13:36 <GitHub121> [artiq] hartytp commented on issue #908: No memtest issues without the SAWG, but then I can't test synchronization. @sbourdeauducq thoughts?... https://github.com/m-labs/artiq/issues/908#issuecomment-365608287

13:38 <rjo> sb0: any of the clock outputs from the fanout. i set it up using quartiq/kasli-i2c. you can also use the runtime. and then the urukul example. check the refclock in the device_db and pll_n.

13:40 <GitHub81> [artiq] hartytp commented on issue #908: I do see the usual splodes of red in the terminal during the build, like:... https://github.com/m-labs/artiq/issues/908#issuecomment-365609746

13:40 <GitHub155> [artiq] hartytp commented on issue #908: I do see the usual splodges of red in the terminal during the build, like:... https://github.com/m-labs/artiq/issues/908#issuecomment-365609746

14:19 <GitHub112> [artiq] sbourdeauducq commented on issue #908: > I assume that none of this is an issue. How do you normally process Vivado's output to separate interesting warnings from the usual noise?... https://github.com/m-labs/artiq/issues/908#issuecomment-365620699

14:24 <GitHub126> [artiq] sbourdeauducq commented on issue #908: Are the software-programmed delays the same for the same board when the SDRAM works and when it does not? https://github.com/m-labs/artiq/issues/908#issuecomment-365622210

14:31 <GitHub17> [artiq] sbourdeauducq commented on issue #908: Are the software-programmed delays the same for the same board when the SDRAM works and when it does not? https://github.com/m-labs/artiq/issues/908#issuecomment-365622210

14:33 <GitHub97> [artiq] hartytp commented on issue #908: > Are the software-programmed delays the same for the same board when the SDRAM works and when it does not?... https://github.com/m-labs/artiq/issues/908#issuecomment-365624704

14:38 <sb0> rjo, so this kasli-i2c tool has to be run at each powerup right now?

14:43 <sb0> rjo, if I understand correctly, you are clocking both the fpga and the dds from the si5324, and use the dds pll to get 1GHz?

14:43 <sb0> the si5234 is set up as a free-running 125MHz source?

15:13 <GitHub162> [artiq] hartytp commented on issue #908: Rebuilt the gateware *with* SAWG and rebooted a few times looking at the read delays...... https://github.com/m-labs/artiq/issues/908#issuecomment-365637707

15:20 <GitHub52> [artiq] sbourdeauducq commented on issue #908: The "write leveling" figures are also delays, and we don't know if it's the reads or writes that are failing. https://github.com/m-labs/artiq/issues/908#issuecomment-365639546

15:33 <GitHub0> [smoltcp] whitequark commented on issue #162: @canndrew Um, what?... https://github.com/m-labs/smoltcp/issues/162#issuecomment-365643895

15:50 <GitHub136> [artiq] hartytp commented on issue #908: Rebuilt the gateware *with* SAWG and rebooted a few times looking at the read delays...... https://github.com/m-labs/artiq/issues/908#issuecomment-365637707

15:51 <GitHub35> [artiq] whitequark commented on issue #911: > AFAICT this is a hidden dependency of cargo on libcurl. See the output.... https://github.com/m-labs/artiq/issues/911#issuecomment-365650066

15:56 <GitHub120> [artiq] hartytp commented on issue #908: Rebuilt the gateware *with* SAWG and rebooted a few times looking at the read delays...... https://github.com/m-labs/artiq/issues/908#issuecomment-365637707

15:57 <GitHub109> [artiq] hartytp commented on issue #908: Updated.... https://github.com/m-labs/artiq/issues/908#issuecomment-365651971

16:10 <GitHub63> [artiq] jbqubit commented on issue #910: > And the vivado version we use may change, to work around bugs etc.... https://github.com/m-labs/artiq/issues/910#issuecomment-365656561

16:34 <GitHub23> [artiq] hartytp commented on issue #910: This one I'm not too fussed about. The problem with documenting this kind of thing is that the docs can easily go stale and do more harm than good. I'm pretty happy bugging people on IRC for this kind of thing. https://github.com/m-labs/artiq/issues/910#issuecomment-365664852

16:36 <GitHub110> [artiq] hartytp commented on issue #908: Rebuilt the gateware *with* SAWG and rebooted a few times looking at the read delays...... https://github.com/m-labs/artiq/issues/908#issuecomment-365637707

16:37 <GitHub112> [artiq] hartytp commented on issue #908: And, for comparison, rebuilt *without* SAWG and saw(g):... https://github.com/m-labs/artiq/issues/908#issuecomment-365666062

16:39 <GitHub88> [artiq] hartytp commented on issue #908: And, for comparison, rebuilt *without* SAWG and saw(g):... https://github.com/m-labs/artiq/issues/908#issuecomment-365666062

16:39 <GitHub159> [artiq] hartytp commented on issue #908: So, does seem to be a reasonable difference between the two. https://github.com/m-labs/artiq/issues/908#issuecomment-365666757

16:40 <GitHub52> [artiq] dhslichter commented on issue #910: I think it would be sufficient for the documentation to point out that one should look at the buildbot logs to find out information about things like vivado versions, etc. I agree with @hartytp that this sort of thing goes stale in a hurry. https://github.com/m-labs/artiq/issues/910#issuecomment-365667006

16:46 <GitHub29> [artiq] jordens commented on issue #911: It's still a bug. Maybe not the underlying one here. https://github.com/m-labs/artiq/issues/911#issuecomment-365668918

16:51 <GitHub177> [artiq] jbqubit commented on issue #910: OK. Let's include a link in the documentation to the right [build bot](http://buildbot.m-labs.hk/builders/artiq-board). And instructions to choose a recent build and examine ```stdio``` for ```conda_build build artiq-kc705-nist_clock ```. The Vivado version used by M-Labs is reported as ... https://github.com/m-labs/artiq/issues/910#issuecomment-365670717

18:00 <GitHub197> smoltcp/master b153636 Dan Robertson: Documentation updates...

18:00 <GitHub197> [smoltcp] whitequark pushed 1 new commit to master: https://github.com/m-labs/smoltcp/commit/b153636eb855ab250c412b19561680aba6c977bd

18:00 <GitHub94> [smoltcp] whitequark closed pull request #161: Small doc updates (master...doc_update) https://github.com/m-labs/smoltcp/pull/161

18:05 <whitequark> ha, klickverbot made /r/physics: https://www.reddit.com/r/Physics/comments/7xhcu1/this_remarkable_photo_shows_a_single_atom_trapped/

18:12 <GitHub84> [smoltcp] whitequark closed issue #156: Add simpler and more robust APIs for creating packets https://github.com/m-labs/smoltcp/issues/156

18:12 <GitHub92> [smoltcp] whitequark commented on issue #156: I don't have any more time for this argument. I'll merge your higher level API for creating packets so long as it doesn't involve explicit allocation and is thus usable in all environments smoltcp is expected to function. https://github.com/m-labs/smoltcp/issues/156#issuecomment-365695790

18:27 <travis-ci> m-labs/smoltcp#740 (master - b153636 : Dan Robertson): The build passed.

18:27 <travis-ci> Change view : https://github.com/m-labs/smoltcp/compare/fb96b3cdc1ba...b153636eb855

18:27 <travis-ci> Build details : https://travis-ci.org/m-labs/smoltcp/builds/341553564

19:21 <GitHub145> [artiq] jbqubit opened issue #921: serial over IP for Sayma https://github.com/m-labs/artiq/issues/921

21:19 <GitHub108> [artiq] whitequark commented on issue #921: @jbqubit There's no problem with that at all, it just needs a small adjustment to smoltcp so that it supports other physical layers other than Ethernet. I would prefer to use either SLIP or a custom protocol on the host side. Windows is also doable using [these](https://community.openvpn.net/openvpn/wiki/ManagingWindowsTAPDrivers) drivers, if you want it. https://githu

22:04 <GitHub51> [artiq] jbqubit commented on issue #908: It's challenging to build a memory controller using Xilinx tools. Xilinx's own DDR3 core has a long list of bug (and fixes). https://www.xilinx.com/support/answers/69036.html... https://github.com/m-labs/artiq/issues/908#issuecomment-365760092

23:10 <GitHub27> [artiq] whitequark pushed 2 new commits to master: https://github.com/m-labs/artiq/compare/2adba3ed33ad...d572c0c34d1d

23:10 <GitHub27> artiq/master d572c0c whitequark: artiq_devtool: fix the hotswap action.

23:10 <GitHub27> artiq/master fe50018 whitequark: firmware: make network tracing runtime switchable.

23:19 <GitHub29> [artiq] whitequark pushed 1 new commit to release-3: https://github.com/m-labs/artiq/commit/92c94c1f62c246f54f0a8d782cdcc5b6c15a58dd

23:19 <GitHub29> artiq/release-3 92c94c1 whitequark: firmware: make network tracing runtime switchable.

23:23 <GitHub4> [artiq] whitequark commented on issue #902: Can you please:... https://github.com/m-labs/artiq/issues/902#issuecomment-365778576

23:23 <GitHub95> [artiq] whitequark commented on issue #902: Can you please:... https://github.com/m-labs/artiq/issues/902#issuecomment-365778576

23:34 <GitHub1> [artiq] jbqubit commented on issue #908: Please describe what the MiSoC tests do and how to interpret the test results. ... https://github.com/m-labs/artiq/issues/908#issuecomment-365780548

23:39 <bb-m-labs> build #1195 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/1195

23:43 <GitHub188> [artiq] jbqubit commented on issue #921: The aim is to get an interactive session working over USB between a Linux ARTIQ Master and Sayma as core device. Even if Ethernet is squared away it will be helpful to test Sayma and SAWG without the struggle of applying white wire patches to a bunch of v1 boards. ... https://github.com/m-labs/artiq/issues/921#issuecomment-365782293

23:53 <GitHub113> [artiq] jbqubit commented on issue #919: > there is certainly an issue with this Artix chip... https://github.com/m-labs/artiq/issues/919#issuecomment-365784121

23:56 <GitHub54> [artiq] jbqubit commented on issue #861: > 1.2GHz sent directly to the DAC.... https://github.com/m-labs/artiq/issues/861#issuecomment-365784756