00:57 <GitHub-m-labs> [artiq] sbourdeauducq commented on issue #1080: @gkasprow Can you check SI and jitter on GTP_CLK1 and GTP_CLK2 on a board that exhibits this problem? And generally investigate this? https://github.com/m-labs/artiq/issues/1080#issuecomment-401216281

02:24 <GitHub-m-labs> [artiq] sbourdeauducq opened issue #1085: DHCP support https://github.com/m-labs/artiq/issues/1085

02:30 <GitHub-m-labs> [artiq] sbourdeauducq commented on issue #1060: The RTM gateware is the same for all variants. https://github.com/m-labs/artiq/issues/1060#issuecomment-401229073

02:30 <GitHub-m-labs> [artiq] sbourdeauducq commented on issue #1060: The RTM gateware is the same for all variants (at least for now, and until we support other AFEs). https://github.com/m-labs/artiq/issues/1060#issuecomment-401229073

02:32 <GitHub-m-labs> [artiq] sbourdeauducq commented on issue #1007: @whitequark ping https://github.com/m-labs/artiq/issues/1007#issuecomment-401229450

06:41 <GitHub-m-labs> [artiq] hartytp commented on issue #1083: > Ok, applied patch linked in op against 0483b8d, board produced this beefy (almost 1 MB) log.... https://github.com/m-labs/artiq/issues/1083#issuecomment-401262862

06:44 <GitHub-m-labs> [artiq] sbourdeauducq commented on issue #1083: The results on my board are not deterministic, it just "works most of the time".... maybe run it a few times. https://github.com/m-labs/artiq/issues/1083#issuecomment-401263410

07:32 <GitHub-m-labs> [artiq] sbourdeauducq commented on issue #1083: > move the SYSREF by one cycle of the 1.2GHz clock, so 34 delay taps (25ps each tap)... https://github.com/m-labs/artiq/issues/1083#issuecomment-401273036

07:34 <GitHub-m-labs> [artiq] sbourdeauducq commented on issue #1083: > move the SYSREF by one cycle of the 1.2GHz clock, so 34 delay taps (25ps each tap)... https://github.com/m-labs/artiq/issues/1083#issuecomment-401273036

07:34 <GitHub-m-labs> [artiq] sbourdeauducq commented on issue #1083: > move the SYSREF by one cycle of the 1.2GHz clock, so 34 delay taps (25ps each tap)... https://github.com/m-labs/artiq/issues/1083#issuecomment-401273036

07:43 <GitHub-m-labs> [artiq] hartytp commented on issue #1083: > The results on my board are not deterministic, it just "works most of the time".... maybe run it a few times.... https://github.com/m-labs/artiq/issues/1083#issuecomment-401275529

07:43 <GitHub-m-labs> [artiq] hartytp commented on issue #1083: > @hartytp Note that due to the combination of the analog and 1/2 CLKIN digital delay (which is made necessary by the limited range of the analog delay), some "taps" are not 25ps. The average is about 24.5ps per tap.... https://github.com/m-labs/artiq/issues/1083#issuecomment-401275581

08:49 <GitHub-m-labs> [artiq] gkasprow commented on issue #1080: I have a few more ideas to verify.... https://github.com/m-labs/artiq/issues/1080#issuecomment-401291706

08:49 <GitHub-m-labs> [artiq] gkasprow commented on issue #1080: I have a few more ideas to verify.... https://github.com/m-labs/artiq/issues/1080#issuecomment-401291706

08:52 <GitHub-m-labs> [artiq] gkasprow commented on issue #1060: There are board revision pullup/pulldown resistors installed.... https://github.com/m-labs/artiq/issues/1060#issuecomment-401292330

09:05 <GitHub-m-labs> [artiq] sbourdeauducq commented on issue #1060: That's about the ARTIQ variant, not hardware versions. https://github.com/m-labs/artiq/issues/1060#issuecomment-401295610

09:10 <GitHub-m-labs> [artiq] gkasprow commented on issue #1060: OK, but to get rid of confusion when next HW releases arrives, we should check the board ID before loading ARTIQ. https://github.com/m-labs/artiq/issues/1060#issuecomment-401296910

09:11 <GitHub-m-labs> [artiq] sbourdeauducq commented on issue #1080: This doesn't sound related to me:... https://github.com/m-labs/artiq/issues/1080#issuecomment-401297029

09:13 <GitHub-m-labs> [artiq] sbourdeauducq commented on issue #1060: Alternatively: avoid breaking compatibility, or deprecate the current set of boards - they have plenty of bugs and fragile reworks anyway. https://github.com/m-labs/artiq/issues/1060#issuecomment-401297760

09:15 <GitHub-m-labs> [artiq] sbourdeauducq commented on issue #1060: Alternatively: avoid breaking compatibility (though that won't be possible in some instances), or deprecate the current set of boards - they have plenty of bugs and fragile reworks anyway. https://github.com/m-labs/artiq/issues/1060#issuecomment-401297760

09:39 <GitHub-m-labs> [artiq] marmeladapk commented on issue #1080: @gkasprow These PRBS errors are there no matter which AMC I use. https://github.com/m-labs/artiq/issues/1080#issuecomment-401304194

09:42 <GitHub-m-labs> [artiq] marmeladapk commented on issue #1080: @gkasprow These PRBS errors (DAC jesd) are there no matter which AMC I use. https://github.com/m-labs/artiq/issues/1080#issuecomment-401304194

10:03 <GitHub-m-labs> [artiq] hartytp commented on issue #1060: Let's depreciate them. Maintaining software support for old boards gets very expensive and isn't worth it for a handful of quite hacked prototypes. https://github.com/m-labs/artiq/issues/1060#issuecomment-401310416

10:05 <GitHub-m-labs> [artiq] hartytp commented on issue #1080: > Yes, today I got these errors once.... https://github.com/m-labs/artiq/issues/1080#issuecomment-401310782

10:19 <GitHub-m-labs> [artiq] gkasprow commented on issue #1060: I mean protection feature that won't enable loading i.e. old firmware to new boards. Then user will get clear message instead of frustration that something does not work. https://github.com/m-labs/artiq/issues/1060#issuecomment-401313966

21:21 <omid> sa

21:21 <omid> rjo: I can ping now. But when I run command $artiq_flash -f flash_storage.img proxy storage start it tells me Binaries directory kc705-nist_clock does not exist.

21:23 <omid> How can I get it to use my binary directory named kc705-phaser ?