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 joined #m-labs
X-Scale has quit [Ping timeout: 248 seconds]
[X-Scale] is now known as X-Scale
<GitHub143> [artiq] whitequark commented on issue #908: The boot messages are displayed by the `read_bitslip` and `read_delays` functions. Memory check likely fails because write leveling exists for a reason. https://github.com/m-labs/artiq/issues/908#issuecomment-366833431
futarisIRCcloud has joined #m-labs
attie has quit [Ping timeout: 256 seconds]
attie has joined #m-labs
<sb0> whitequark, any update on the camera driver?
attie has quit [Ping timeout: 240 seconds]
attie has joined #m-labs
hozer has quit [Quit: Leaving.]
rohitksingh_work has joined #m-labs
<whitequark> no. I've been looking into the buildbot breakage
<sb0> windows python?
<whitequark> yes, and other issues too
attie has quit [Ping timeout: 268 seconds]
attie has joined #m-labs
attie has quit [Ping timeout: 255 seconds]
attie has joined #m-labs
<GitHub49> [artiq] sbourdeauducq commented on issue #902: @jonaskeller How are things (flashing and panic) with a recent artiq-4 package from master? If everything works I'll backport the changes to release-3 and make a new release. https://github.com/m-labs/artiq/issues/902#issuecomment-366895441
mumptai has joined #m-labs
attie has quit [Ping timeout: 260 seconds]
attie has joined #m-labs
mumptai has quit [Remote host closed the connection]
<sb0> rjo, FYI I'm going to order another kasli for m-labs hk, it's definitely more pleasant to debug/develop drtio there than on kc705 (transceiver bugs) or sayma (no comment), and one of the two kasli we have atm will go to china soon
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
<sb0> those transceivers also seem to guzzle power. heat-sinked FPGA is at 71C with ethernet and drtio running...
<rjo> sb0: ack. it's a really nice board.
<rjo> sb0: be careful with esd though (i2c switch seems sensitive) and i put a 25x25mm 12v fan onto the heat sink. with opticlock it's now at 48c. the amount of LVDS buffers is driving power usage.
<rjo> sb0: care to do a quick code review of the new spi core?
<GitHub38> [misoc] jordens deleted kasli-100mhz at 7126ec4: https://github.com/m-labs/misoc/commit/7126ec4
<sb0> ok
<GitHub110> [artiq] sbourdeauducq pushed 1 new commit to master: https://github.com/m-labs/artiq/commit/ad2c9590d0dedc3da6bccd4d55ede00a291dd6b9
<GitHub110> artiq/master ad2c959 Sebastien Bourdeauducq: drtio: rewrite/fix reset and link bringup/teardown
<GitHub121> [misoc] jordens created spi2 (+1 new commit): https://github.com/m-labs/misoc/commit/e79ea98b2a70
<GitHub121> misoc/spi2 e79ea98 Robert Jordens: spi2: new spi master core...
<rjo> sb0: i'll stage that without disturbing the old core and then transition the upper layers one by one.
<sb0> rjo, is the oxford ad9910 support complete with the current code?
<rjo> documentation still. and i couldn't get it to work at full speed yet (62.5 MHz SPI clock) which bothers me. and it doesn't initialize and lock the plls correctly from time to time.
<GitHub175> [misoc] jordens force-pushed spi2 from e79ea98 to f5b5923: https://github.com/m-labs/misoc/commits/spi2
<GitHub175> misoc/spi2 f5b5923 Robert Jordens: spi2: new spi master core...
<sb0> do you suspect spi core bugs?
<rjo> yes. gateware or mis-usage in the rtio layer or the coredevice support.
<rjo> and the spi core is also failing timing sporadically on kasli. and vivado complains (probably rightly so) about lack of output/input buffers.
<sb0> bb-m-labs, stop build artiq drtio tests
<bb-m-labs> build 2071 interrupted
<bb-m-labs> build #2071 of artiq is complete: Exception [exception interrupted] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2071 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>
<GitHub10> [artiq] sbourdeauducq pushed 1 new commit to master: https://github.com/m-labs/artiq/commit/7d9c7ada713bbf60cce8665b4892dcd7532f0bd6
<GitHub10> artiq/master 7d9c7ad Sebastien Bourdeauducq: drtio: fix test infinite loop
attie has quit [Ping timeout: 240 seconds]
attie has joined #m-labs
<GitHub59> [artiq] hartytp commented on issue #908: @enjoy-digital did you have a chance to fix the timing issues with serwb that @sbourdeauducq mentioned? I know that these are unlikely to be the cause of the SDRAM issues, but it's probably a good idea to mop up all the known issues as a starting point to fixing this.... https://github.com/m-labs/artiq/issues/908#issuecomment-366926989
hartytp has joined #m-labs
<hartytp> rj0: do you have a pair of a Kasli with DRTIO working? If so, would you be interested in doing a phase stability measurement at some point soon? Idea would be to put the output of the Si5324 clocks onto a 2-channel ADC and do a long-term (hours) phase drift measurement
<hartytp> let the DRTIO master free-run and compare the phase wander of the locked slave DRTIO clock relative to the master
<GitHub92> [artiq] gkasprow commented on issue #854: I'm back from holidays in Israel. It's cool place for a car trip.... https://github.com/m-labs/artiq/issues/854#issuecomment-366928238
<GitHub122> [artiq] gkasprow commented on issue #854: I'm back from holidays in Israel. It's cool place for a car trip.... https://github.com/m-labs/artiq/issues/854#issuecomment-366928238
<GitHub82> [artiq] sbourdeauducq commented on issue #854: Could not reproduce the board ping. https://github.com/m-labs/artiq/issues/854#issuecomment-366928472
<GitHub130> [artiq] gkasprow commented on issue #854: so what shall I do to reproduce this issue?... https://github.com/m-labs/artiq/issues/854#issuecomment-366928835
<bb-m-labs> build #1228 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/1228
<GitHub150> [artiq] sbourdeauducq commented on issue #854: As explained before: RX phase tuning and get RX to work, then TX phase tuning.... https://github.com/m-labs/artiq/issues/854#issuecomment-366929714
<bb-m-labs> build #2072 of artiq is complete: Failure [failed python_unittest_2] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2072 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>
<GitHub94> [artiq] sbourdeauducq commented on issue #854: If that doesn't suffice, we can also connect the Sayma to a Kasli and use my Ethernet PHY to look at the 1000BASE-X level directly. https://github.com/m-labs/artiq/issues/854#issuecomment-366931124
FabM has joined #m-labs
hartytp has quit [Quit: Page closed]
<GitHub91> [artiq] gkasprow commented on issue #854: So do you still experience LINK issue? Does the LINK disappear once you reload the firmware? https://github.com/m-labs/artiq/issues/854#issuecomment-366935886
<GitHub43> [artiq] gkasprow commented on issue #854: How can we fix the TX bug in future PCB revision? It does not need any dedicated FPGA pin.. https://github.com/m-labs/artiq/issues/854#issuecomment-366936143
<GitHub196> [artiq] sbourdeauducq commented on issue #854: As I mentioned earlier, the link became stable when I swapped the external media converter with a RJ45 SFP.... https://github.com/m-labs/artiq/issues/854#issuecomment-366936511
<GitHub111> [artiq] gkasprow commented on issue #854: OK, so first I will fix the PAUSE issue to make it working with other media converters. If you want me to look at the PHY signals I can do that - I have low capacitance (<1pf, 1.5GHz) active probes and can observe 4 signals at a time or 8 using 2 scopes. https://github.com/m-labs/artiq/issues/854#issuecomment-366937589
<GitHub192> [artiq] sbourdeauducq pushed 3 new commits to master: https://github.com/m-labs/artiq/compare/7d9c7ada713b...f060d6e1b337
<GitHub192> artiq/master f060d6e Sebastien Bourdeauducq: drtio: increase A7 clock aligner check period
<GitHub192> artiq/master 738654c Sebastien Bourdeauducq: drtio: support remote RTIO resets
<GitHub192> artiq/master f15b4bd Sebastien Bourdeauducq: style
<GitHub83> [artiq] sbourdeauducq commented on commit 738654c: @whitequark How to do that cleanly? https://github.com/m-labs/artiq/commit/738654c783fec3d5940291f00f98ca7c5b40e229#commitcomment-27670737
<bb-m-labs> build #1229 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/1229
attie has quit [Ping timeout: 260 seconds]
attie has joined #m-labs
<bb-m-labs> build #735 of artiq-win64-test is complete: Warnings [warnings python_unittest] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/735 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>
<marbler> sb0: do you habe generic SMD MOSFETS like AO3400?
<marbler> and 0805 LEDs?
<bb-m-labs> build #2073 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2073
<_florent_> sb0: do you have a bistream where ddr3 fails on sayma3? I'd like to do some tests
rohitksingh_work has quit [Read error: Connection reset by peer]
<sb0> marbler, I have many times of sot23 mosfets but iirc no LEDs
<sb0> well, there are probably SMD LEDs to be scavenged from one of the electronics trash boxes
<sb0> *many types
<sb0> _florent_, I don't... and whether it fails or not depends on the board
<sb0> _florent_, you can look at the issue (I posted a few binaries)
<GitHub107> [artiq] enjoy-digital commented on issue #908: I'd like to see if it's an issue with the read leveling algorithm or something else, but i'm not able to reproduce the issue on the HK boards. Can someone that is able to reproduce the issue apply this patch: https://hastebin.com/akoketutut.swift, rebuild the bootloader (use --no-compile-gateware), re-flash the bootloader (artiq_flash ... bootloader) and post the result
rohitksingh has joined #m-labs
rohitksingh has quit [Quit: Leaving.]
rohitksingh has joined #m-labs
rohitksingh1 has joined #m-labs
attie has quit [Ping timeout: 260 seconds]
attie has joined #m-labs
rohitksingh1 has quit [Quit: Leaving.]
<GitHub122> [sinara] gkasprow pushed 1 new commit to master: https://git.io/vARzp
<GitHub122> sinara/master 8004bee Greg: added panel design for Grabber
attie has quit [Ping timeout: 248 seconds]
rohitksingh1 has joined #m-labs
attie has joined #m-labs
rohitksingh has quit [Ping timeout: 240 seconds]
<GitHub37> [artiq] marmeladapk commented on issue #908: ```... https://github.com/m-labs/artiq/issues/908#issuecomment-367002731
<GitHub29> [artiq] marmeladapk commented on issue #908: @enjoy-digital ... https://github.com/m-labs/artiq/issues/908#issuecomment-367002731
<GitHub20> [artiq] hartytp commented on issue #908: > @hartytp: we see on your last 3 failing capture that there are still delay intervasl that are too small (<20).... https://github.com/m-labs/artiq/issues/908#issuecomment-367006997
rohitksingh has joined #m-labs
rohitksingh has quit [Quit: Leaving.]
<GitHub59> [artiq] enjoy-digital commented on issue #908: @marmeladapk : thanks, can you also send the results from the unpatched bootloader?... https://github.com/m-labs/artiq/issues/908#issuecomment-367024284
<GitHub168> [artiq] hartytp commented on issue #908: To be clear, you want me to do the following:... https://github.com/m-labs/artiq/issues/908#issuecomment-367025150
rohitksingh has joined #m-labs
<GitHub110> [artiq] marmeladapk commented on issue #908: @enjoy-digital ... https://github.com/m-labs/artiq/issues/908#issuecomment-367027245
<GitHub32> [artiq] marmeladapk commented on issue #908: @enjoy-digital ... https://github.com/m-labs/artiq/issues/908#issuecomment-367027245
<GitHub127> [artiq] marmeladapk commented on issue #908: @enjoy-digital ... https://github.com/m-labs/artiq/issues/908#issuecomment-367027245
<GitHub169> [artiq] enjoy-digital commented on issue #908: @hartytp: yes that's what i want, please also use write_leveling. (you can also test with deadzone of 16, 32 and then the patched version). ... https://github.com/m-labs/artiq/issues/908#issuecomment-367029929
rohitksingh has quit [Quit: Leaving.]
rohitksingh has joined #m-labs
rohitksingh has quit [Quit: Leaving.]
<GitHub177> [artiq] hartytp commented on issue #908: @enjoy-digital Okay, will do this test in the am. https://github.com/m-labs/artiq/issues/908#issuecomment-367037213
rohitksingh has joined #m-labs
rohitksingh has quit [Ping timeout: 255 seconds]
<GitHub117> [artiq] marmeladapk commented on issue #908: @enjoy-digital With your patch memory test failed again. Without it test passed. https://github.com/m-labs/artiq/issues/908#issuecomment-367045032
<GitHub16> [artiq] enjoy-digital commented on issue #908: @marmeladapk: the patch is not expected to pass, it's just have to be used on board that are failing to investigate. https://github.com/m-labs/artiq/issues/908#issuecomment-367045588
rohitksingh has joined #m-labs
rohitksingh has quit [Read error: Connection reset by peer]
rohitksingh has joined #m-labs
rohitksingh has quit [Read error: No route to host]
jkeller has joined #m-labs
<jkeller> bb-m-labs: force build --props=package=artiq-kc705-nist_qc2 --branch=master artiq-board
<bb-m-labs> build forced [ETA 18m55s]
<bb-m-labs> I'll give a shout when the build finishes
rohitksingh has joined #m-labs
<GitHub120> [artiq] marmeladapk commented on issue #908: @enjoy-digital Our board was failing, that's why I was posting. https://github.com/m-labs/artiq/issues/908#issuecomment-367060927
mumptai has joined #m-labs
<bb-m-labs> build #1230 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/1230
rohitksingh1 has quit [Quit: Leaving.]
<GitHub39> [misoc] jordens force-pushed spi2 from f5b5923 to 84b16a5: https://github.com/m-labs/misoc/commits/spi2
<GitHub39> misoc/spi2 84b16a5 Robert Jordens: spi2: new spi master core...
<GitHub179> [artiq] enjoy-digital commented on issue #908: @marmeladapk: the patch is not expected to pass, it just have to be used on boards that are failing to investigate. https://github.com/m-labs/artiq/issues/908#issuecomment-367045588
rohitksingh1 has joined #m-labs
<GitHub193> [artiq] jonaskeller commented on issue #902: Conda still defaults to `4.0.dev-py_206+git70130847` for the `artiq-kc705-nist_qc2` package. If I try to force either `py_553+git07a31f8d` or `py_582+gitf060d6e1`, it complains about not being able to fulfill the `openocd 0.10.0 4` dependency. https://github.com/m-labs/artiq/issues/902#issuecomment-367074931
jkeller has quit [Quit: Page closed]
rohitksingh has quit [Ping timeout: 240 seconds]
rohitksingh1 has quit [Read error: Connection reset by peer]
rohitksingh has joined #m-labs
rohitksingh has quit [Quit: Leaving.]
Gurty has quit [Ping timeout: 256 seconds]
Gurty has joined #m-labs
Gurty has joined #m-labs
Gurty has quit [Changing host]
<GitHub165> [artiq] marmeladapk commented on issue #908: @enjoy-digital With SAWG:... https://github.com/m-labs/artiq/issues/908#issuecomment-367126984
futarisIRCcloud has joined #m-labs