02:36 <GitHub-m-labs> [artiq] sbourdeauducq commented on issue #1149: @enjoy-digital thanks, do you have an idea of what exactly is causing this behavior? https://github.com/m-labs/artiq/issues/1149#issuecomment-438895135

05:30 <GitHub-m-labs> [artiq] sbourdeauducq commented on issue #1193: Looks good. https://github.com/m-labs/artiq/pull/1193#issuecomment-438922791

05:30 <GitHub-m-labs> [artiq] sbourdeauducq closed pull request #1193: gui,scan: add CenterScan Scannable variant (master...centerscan) https://github.com/m-labs/artiq/pull/1193

05:50 <GitHub-m-labs> [artiq] dhslichter commented on issue #1193: @jordens a couple of thoughts: ... https://github.com/m-labs/artiq/pull/1193#issuecomment-438925917

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

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

06:55 <bb-m-labs> build #2690 of artiq is complete: Exception [exception python_unittest_2 board_unlock_1] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2690 blamelist: Robert J?rdens <rj@quartiq.de>

07:13 <GitHub-m-labs> [artiq] enjoy-digital commented on issue #1149: @sbourdeauducq: no, but i'll spend an hour this morning trying to go in the other direction (patched version that is working to the one not working) and try to find it if you want a minimal patch for now.... https://github.com/m-labs/artiq/issues/1149#issuecomment-438940823

07:55 <GitHub-m-labs> [artiq] sbourdeauducq commented on issue #1149: I'm mostly interested in understanding what caused such strange behavior. It is pretty puzzling that the read leveling window becomes smaller when the frequency decreases, and I want to avoid similar issues in the future. https://github.com/m-labs/artiq/issues/1149#issuecomment-438949646

08:10 <GitHub-m-labs> [artiq] meyerbernd opened issue #1194: problems with tune_sync_delay https://github.com/m-labs/artiq/issues/1194

08:12 <GitHub-m-labs> [artiq] enjoy-digital commented on issue #1149: @sbourdeauducq: i'm on it. https://github.com/m-labs/artiq/issues/1149#issuecomment-438953795

09:57 <GitHub-m-labs> [buildbot-config] sbourdeauducq pushed 1 new commit to master: https://git.io/fpsoV

09:57 <GitHub-m-labs> buildbot-config/master 5aadf58 Sebastien Bourdeauducq: fix board locking separation

09:58 <sb0> bb-m-labs: force build artiq

09:58 <bb-m-labs> build #2691 forced

09:58 <bb-m-labs> I'll give a shout when the build finishes

10:15 <GitHub-m-labs> [artiq] enjoy-digital commented on issue #1149: The minimal misoc patch is here: https://github.com/enjoy-digital/kasli_sdram/blob/master/0001-cores-sdram_phy-a7ddrphy-change-rdphase-rdcmdphase-r.patch... https://github.com/m-labs/artiq/issues/1149#issuecomment-438988917

10:15 <GitHub-m-labs> [artiq] enjoy-digital commented on issue #1149: The minimal misoc patch is here: https://github.com/enjoy-digital/kasli_sdram/blob/master/0001-cores-sdram_phy-a7ddrphy-change-rdphase-rdcmdphase-r.patch... https://github.com/m-labs/artiq/issues/1149#issuecomment-438988917

10:18 <GitHub-m-labs> [artiq] enjoy-digital commented on issue #1149: Note: on Kasli, you could also set bitslip by software to 1 to be sure to be in the best read window (leading and trailing zeroes):... https://github.com/m-labs/artiq/issues/1149#issuecomment-438989799

10:18 <GitHub-m-labs> [artiq] sbourdeauducq commented on issue #1149: Ah okay, I did suspect the delay maxing out at some point, but I thought that the reset was setting it to 0, not the gateware ``IDELAY_VALUE``...... https://github.com/m-labs/artiq/issues/1149#issuecomment-438989831

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

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

11:17 <GitHub-m-labs> [artiq] sbourdeauducq commented on issue #1149: > m0, b1: |00000000000111111111111100000000| delays: 17+-06... https://github.com/m-labs/artiq/issues/1149#issuecomment-439006088

11:18 <GitHub-m-labs> [artiq] sbourdeauducq commented on issue #1149: > m0, b1: |00000000000111111111111100000000| delays: 17+-06... https://github.com/m-labs/artiq/issues/1149#issuecomment-439006088

11:20 <GitHub-m-labs> [artiq] sbourdeauducq commented on issue #1149: > m0, b1: |00000000000111111111111100000000| delays: 17+-06... https://github.com/m-labs/artiq/issues/1149#issuecomment-439007084

11:26 <bb-m-labs> build #2691 of artiq is complete: Failure [failed python_unittest_2] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2691

11:26 <GitHub-m-labs> [artiq] sbourdeauducq commented on issue #1149: okay, another I/O block reset issue... https://github.com/m-labs/artiq/issues/1149#issuecomment-439008583

11:30 <GitHub-m-labs> [misoc] sbourdeauducq pushed 1 new commit to master: https://github.com/m-labs/misoc/commit/128750aa74aa8f0b54822918575253f6aea8d02d

11:30 <GitHub-m-labs> misoc/master 128750a Florent Kermarrec: cores/sdram_phy/a7ddrphy: change rdphase/rdcmdphase, remove idelay_value initialization....

11:31 <GitHub-m-labs> [artiq] sbourdeauducq commented on issue #1149: No more SDRAM issue on any board here! Thanks again for the debugging @enjoy-digital https://github.com/m-labs/artiq/issues/1149#issuecomment-439009822

11:33 <bb-m-labs> build #450 of misoc is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/misoc/builds/450

11:41 <GitHub-m-labs> [artiq] sbourdeauducq pushed 1 new commit to master: https://github.com/m-labs/artiq/commit/d3483c1d26ad8049384e656ad773b5637517df52

11:41 <GitHub-m-labs> artiq/master d3483c1 Sebastien Bourdeauducq: kasli: fix SDRAM read delay reset/wrap issue. Closes #1149

11:44 <GitHub-m-labs> [artiq] sbourdeauducq commented on issue #1113: > I am ok with leaving them as is for now and add warnings.... https://github.com/m-labs/artiq/issues/1113#issuecomment-439012891

11:57 <GitHub-m-labs> [artiq] hermitdemschoenenleben opened issue #1195: Connection fails: unknown packet 0x3 https://github.com/m-labs/artiq/issues/1195

11:57 <GitHub-m-labs> [artiq] jordens commented on issue #1113: Yes. https://github.com/m-labs/artiq/issues/1113#issuecomment-439016136

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

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

13:46 <d_n|a> rjo/sb0: Are you going to have any sort of presence at ECTI? We are considering putting a short note/ad about ARTIQ on one of our posters.

13:47 <d_n|a> (mostly the Sinara hardware, that is)

14:12 <bb-m-labs> build #2692 of artiq is complete: Failure [failed python_unittest_2] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2692 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>

16:50 <sb0__> d_n|a: yes, we'll have a booth. greeting from tel aviv!

20:45 <d_n|a> sb0__: Great to hear - if you don't mind, we'll put one of the Sinara glamour shots pictures on the poster and stick a note there to visit your booth

22:17 <GitHub-m-labs> [artiq] jordens commented on issue #1193: There are multiple ways to parametrize a scan. `start, stop` and `center, span` are a conjugate. As are `span, step` and `span, npoints`. If you are in a situation where you are searching for a feature that has a known size (e.g. fourier limited) and is located in a certain span, the parametrization implemented here is the suitable and convenient one. Another use case i

22:17 <GitHub-m-labs> [artiq] jordens deleted centerscan at 4d62e4e: https://github.com/m-labs/artiq/commit/4d62e4e

22:33 <rjo> d_n|a: sounds good. thanks.

22:41 <GitHub-m-labs> [artiq] jordens created fix-scanwidget-size (+1 new commit): https://github.com/m-labs/artiq/commit/ea5346f88412

22:41 <GitHub-m-labs> artiq/fix-scanwidget-size ea5346f Robert Jördens: RangeScan: remove minimum/fixed size...

22:46 <GitHub-m-labs> [artiq] jordens commented on issue #1180: I can't reproduce that here. On my systems it's not resizable to a width where they would collide. But I found a couple suspicious size related lines in the UI. They also have pixel based sizes which doesn't work well for HIDPI displays. Could you give this a try:... https://github.com/m-labs/artiq/issues/1180#issuecomment-439218003

23:31 <whitequark> sb0__: https://twitter.com/kbeckmann/status/1063212542443556864

23:31 <whitequark> 2 hours from starting to use migen to a working glasgow applet

23:31 <whitequark> i'd say this is very good