sb0_ changed the topic of #m-labs to: https://m-labs.hk :: Logs http://irclog.whitequark.org/m-labs
<sb0> hartytp: how are you measuring that phase? and when does it change, after a power cycle?
<_whitenotifier-c> [m-labs/nmigen] whitequark pushed 3 commits to master [+0/-0/±5] https://git.io/fhulh
<_whitenotifier-c> [m-labs/nmigen] whitequark 9757157 - lib.coding: add width as attribute to all coders.
<_whitenotifier-c> [m-labs/nmigen] whitequark b6cff2c - lib.coding: add GrayEncoder and GrayDecoder.
<_whitenotifier-c> [m-labs/nmigen] whitequark c110fe6 - compat.genlib.cdc: add GrayCounter and GrayDecoder shims.
<_whitenotifier-c> [nmigen] Success. The Travis CI build passed - https://travis-ci.org/m-labs/nmigen/builds/481929350?utm_source=github_status&utm_medium=notification
<_whitenotifier-c> [nmigen] Success. 82.8% (+0.21%) compared to 9de9272 - https://codecov.io/gh/m-labs/nmigen/commit/c110fe6a9ddc1dc151b9132485cff53e7bedd7c4
<_whitenotifier-c> [nmigen] Success. Coverage not affected when comparing 9de9272...c110fe6 - https://codecov.io/gh/m-labs/nmigen/commit/c110fe6a9ddc1dc151b9132485cff53e7bedd7c4
<_whitenotifier-c> [m-labs/nmigen] whitequark pushed 1 commit to master [+0/-0/±1] https://git.io/fhu82
<_whitenotifier-c> [m-labs/nmigen] whitequark 52a9f81 - compat.genlib.cdc: add missing import.
<_whitenotifier-c> [nmigen] Success. The Travis CI build passed - https://travis-ci.org/m-labs/nmigen/builds/481933369?utm_source=github_status&utm_medium=notification
<_whitenotifier-c> [nmigen] Success. 82.8% remains the same compared to c110fe6 - https://codecov.io/gh/m-labs/nmigen/commit/52a9f818f1fa3e1ba56d1adeaa6457e73ae1d176
<_whitenotifier-c> [nmigen] Success. Coverage not affected when comparing c110fe6...52a9f81 - https://codecov.io/gh/m-labs/nmigen/commit/52a9f818f1fa3e1ba56d1adeaa6457e73ae1d176
iwxzr has joined #m-labs
rohitksingh has joined #m-labs
rohitksingh has quit [Ping timeout: 246 seconds]
rohitksingh has joined #m-labs
rohitksingh has quit [Ping timeout: 250 seconds]
rohitksingh has joined #m-labs
hartytp has joined #m-labs
<hartytp> sb0: fast scope triggered from the reference
<hartytp> there is a lot of fancy stuff in this PLL and it looks like it doesn't really behave as an int-N PLL when the fractional words are set to 0
<hartytp> problem is that the documentation isn't really good enough to understand it
<hartytp> look at that ADI article I posted on GitHub about phase sync
<hartytp> it has a cryptic comment about how it is important to disable the VCO automatic calibration to achieve deterministic phase. How does that make sense? VCO is inside a feedback loop, so it shouldn't make a difference
<hartytp> anyway, will poke a bit more on Monday, otherwise it's back to plan (B)
<hartytp> (oh, and answering your other question, the small phase jumps were usually at power on. But sometimes reprogramming the PLL would cause a phase jump. These were relatively rare events. Not consistent with incorrectly reset integer-N dividers)
hartytp has quit [Ping timeout: 256 seconds]
<rjo> i can imagine that the feedback paths involving the different vcos/bands are also physically different. i.e. the difference between vco-to-out and vco-to-pfd is not the same accross the vcos/bands.
rohitksingh has quit [Ping timeout: 250 seconds]
mumptai has joined #m-labs
_whitelogger has joined #m-labs
rohitksingh has joined #m-labs
rohitksingh has quit [Ping timeout: 240 seconds]
_whitelogger has joined #m-labs
rohitksingh has joined #m-labs
proteusguy has quit [Ping timeout: 245 seconds]
<sb0> _florent_: if that helps, here's another gth phy implementation https://gist.github.com/sbourdeauducq/f8061c3628edfac32306ab9c67b9b4eb
<sb0> that one is based on the drtio code, with the parameters changed
<sb0> but that one and the original are both broken, in the same way afaict
<sb0> and when I connect it to kasli, both of them transmitting 1111100000, the data received at both ends makes no sense at all
<sb0> no idea what is going on...
rohitksingh has quit [Ping timeout: 272 seconds]
<sb0> the other phy implementation also works correctly when using a SFP loopback, which is also puzzling
<sb0> (actual hardware loopback)
rohitksingh has joined #m-labs
<GitHub-m-labs> [misoc] sbourdeauducq pushed 1 new commit to master: https://github.com/m-labs/misoc/commit/8e033c2cb77f78c95d2b2e08125324891d07fa34
<GitHub-m-labs> misoc/master 8e033c2 Sebastien Bourdeauducq: ku_1000basex: increase CPLL reset time
<bb-m-labs> build #462 of misoc is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/misoc/builds/462
proteusguy has joined #m-labs
rohitksingh has quit [Ping timeout: 250 seconds]
rohitksingh has joined #m-labs
<_florent_> sb0: so it seems to be transmitting correctly but not receiving?
rohitksingh has quit [Remote host closed the connection]
rohitksingh has joined #m-labs
<GitHub-m-labs> [artiq] klickverbot pushed 2 new commits to master: https://github.com/m-labs/artiq/compare/e165a9a35290...8aac5f7695bb
<GitHub-m-labs> artiq/master 5c62648 David Nadlinger: manual: Minor grammar fixes
<GitHub-m-labs> artiq/master 8aac5f7 David Nadlinger: manual/management_system: Cross-reference frontend tools
rohitksingh has quit [Remote host closed the connection]
<GitHub-m-labs> [artiq] klickverbot opened pull request #1251: scheduler: Add shutdown test, minor refactors (master...scheduler-refactor) https://github.com/m-labs/artiq/pull/1251
<d_n|a> bb-m-labs: force build --branch=pull/1251/merge artiq
<bb-m-labs> The build has been queued, I'll give a shout when it starts
<bb-m-labs> build #2281 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/2281
lkcl has quit [Read error: Connection reset by peer]
<bb-m-labs> build #2282 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/2282
<bb-m-labs> build #2840 of artiq is complete: Failure [failed python_unittest_2] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2840 blamelist: David Nadlinger <code@klickverbot.at>
<bb-m-labs> build forced [ETA 57m46s]
<bb-m-labs> I'll give a shout when the build finishes
lkcl has joined #m-labs
<GitHub-m-labs> [artiq] jordens commented on pull request #1251 4ba4e9c: At this point you probably want to check that the background job has not completed yet. Otherwise you are relying implicitly on some event loop granularity that I can't derive, right? https://github.com/m-labs/artiq/pull/1251#discussion_r249294367
<GitHub-m-labs> [artiq] klickverbot commented on pull request #1251 4ba4e9c: The background job will never complete unless termination is requested. `scheduler.stop()` should kill the workers, which is what this is testing. https://github.com/m-labs/artiq/pull/1251#discussion_r249294771
<d_n|a> (The above blame is vacuous; this is the pulse rate test being flaky again.)
<bb-m-labs> build #2283 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/2283
<bb-m-labs> build #2284 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/2284
<bb-m-labs> build #2841 of artiq is complete: Failure [failed python_unittest_2] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2841
<d_n|a> (... and another spurious failure!)
<GitHub-m-labs> [artiq] klickverbot pushed 3 new commits to master: https://github.com/m-labs/artiq/compare/8aac5f7695bb...4ba4e9c540bc
<GitHub-m-labs> artiq/master e24e893 David Nadlinger: master/scheduler: Fix misleading indentation [nfc]
<GitHub-m-labs> artiq/master 0dab7ec David Nadlinger: master: Include RID in worker exception messages...
<GitHub-m-labs> artiq/master 4ba4e9c David Nadlinger: test_scheduler: Test for hang when exiting with running experiments...
<bb-m-labs> build #2285 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/2285
<bb-m-labs> build #2286 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/2286
<bb-m-labs> build #1000 of artiq-win64-test is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/1000
<bb-m-labs> build #2842 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2842
mumptai has quit [Quit: Verlassend]
futarisIRCcloud has joined #m-labs
X-Scale has quit [Ping timeout: 245 seconds]