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
<GitHub31> [artiq] sbourdeauducq commented on commit 24562d2: But did backtrace become less useful with the rust upgrade? https://github.com/m-labs/artiq/commit/24562d232e40ad8a0d66a74888d43c873389c590#commitcomment-26728643
<sb0> whitequark, yes no reset
<GitHub36> [artiq] whitequark commented on commit 24562d2: With the second upgrade (to Rust 1.23.0) I was able to use `debug = 1`, which is just line debug info, without variable/structure debug info. So backtraces should be fine.... https://github.com/m-labs/artiq/commit/24562d232e40ad8a0d66a74888d43c873389c590#commitcomment-26728754
<whitequark> rjo: I've fixed the bootloader issue on kasli btw
<GitHub73> [artiq] whitequark closed issue #886: rust ethernet/sdram init code breaks support for artix 7 phys (Kasli) https://github.com/m-labs/artiq/issues/886
<GitHub115> [artiq] whitequark commented on issue #886: Fixed in 3bfb128a99909c932c9bf46a466c9651ce7d1284. https://github.com/m-labs/artiq/issues/886#issuecomment-356162363
<whitequark> erm, not pushed, sec
<GitHub24> [artiq] whitequark commented on issue #886: Fixed in 3bfb128a99909c932c9bf46a466c9651ce7d1284. https://github.com/m-labs/artiq/issues/886#issuecomment-356162363
<GitHub176> [artiq] whitequark reopened issue #886: rust ethernet/sdram init code breaks support for artix 7 phys (Kasli) https://github.com/m-labs/artiq/issues/886
rohitksingh has joined #m-labs
<GitHub175> [artiq] whitequark closed issue #886: rust ethernet/sdram init code breaks support for artix 7 phys (Kasli) https://github.com/m-labs/artiq/issues/886
<GitHub190> [artiq] whitequark commented on issue #874: @jonaskeller FWIW #885 has been fixed. https://github.com/m-labs/artiq/issues/874#issuecomment-356162992
<GitHub98> [misoc] sbourdeauducq pushed 1 new commit to ethdebug: https://github.com/m-labs/misoc/commit/889c036ff29a10f18b1a121cf9bab985a61a9e85
<GitHub98> misoc/ethdebug 889c036 Sebastien Bourdeauducq: a7_gtp: fix RX init FSM
<sb0> rjo, do you have a SFP loopback plug?
<sb0> can you put it on sfp2 and the switch on sfp0?
<bb-m-labs> build #1037 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/1037
<sb0> it seems the transceiver trash just keeps outputting 0x7805c on rxdata, regardless of what is on the input pins...
<bb-m-labs> build #679 of artiq-win64-test is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/679
<bb-m-labs> build #1914 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1914
<GitHub89> [misoc] sbourdeauducq pushed 1 new commit to ethdebug: https://github.com/m-labs/misoc/commit/87f167e9428f2301c73835d8d5f808abb93d33d9
<GitHub89> misoc/ethdebug 87f167e Sebastien Bourdeauducq: a7_1000basex: remove internal_loopback parameter...
<GitHub106> [misoc] sbourdeauducq pushed 1 new commit to ethdebug: https://github.com/m-labs/misoc/commit/8286be43c9e56283e0aa91ab79b8482f35fcbb4f
<GitHub106> misoc/ethdebug 8286be4 Sebastien Bourdeauducq: a7_1000basex: disable integrated comma circuit
rohitksingh has quit [Read error: Connection reset by peer]
rohitksingh has joined #m-labs
rohitksingh_work has joined #m-labs
<whitequark> sb0: you can go ahead and release 3.2, I think
<sb0> ok
sb0 has quit [Quit: Leaving]
attie has quit [Remote host closed the connection]
dlrobertson has quit [Ping timeout: 240 seconds]
sb0 has joined #m-labs
<sb0> whitequark, what are you working on now? can you help with kasli or sayma?
dlrobertson has joined #m-labs
<GitHub88> [misoc] sbourdeauducq pushed 5 new commits to master: https://github.com/m-labs/misoc/compare/3bfb128a9990...5a19315e76a1
<GitHub88> misoc/master 8b4d9fd Sebastien Bourdeauducq: 1000basex: fix drpaddr width
<GitHub88> misoc/master 124ed9b Sebastien Bourdeauducq: a7_gtp: fix RX init FSM
<GitHub88> misoc/master 5481cd2 Sebastien Bourdeauducq: 1000basex: fix gearbox instantiation
<bb-m-labs> build #337 of misoc is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/misoc/builds/337
<GitHub58> [migen] sbourdeauducq tagged 0.6 at master: https://github.com/m-labs/migen/commits/0.6
<GitHub28> [misoc] sbourdeauducq tagged 0.8 at master: https://github.com/m-labs/misoc/commits/0.8
<sb0> bb-m-labs, force build migen
<bb-m-labs> build forced [ETA 3m02s]
<bb-m-labs> I'll give a shout when the build finishes
<sb0> bb-m-labs, force build misoc
<bb-m-labs> build forced [ETA 3m21s]
<bb-m-labs> I'll give a shout when the build finishes
<whitequark> sb0: sure, what needs to be done exactly?
<sb0> there are many things...
<sb0> program the attenuator on allaki
<sb0> prepare a simulation with the xilinx proprietary simulator of the 1000basex transceiver code
FabM has joined #m-labs
<bb-m-labs> build #338 of misoc is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/misoc/builds/338
<sb0> modify artiq_flash, runtime & co to add a flash area with the future rtm bitstream (fbi format, accessible from runtime)
<sb0> develop gateware and firmware to load said bitstream into the rtm
<GitHub156> [artiq] sbourdeauducq pushed 1 new commit to release-3: https://github.com/m-labs/artiq/commit/6641f4c1ac9e946e5ddac929dcd58b56121e7584
<GitHub156> artiq/release-3 6641f4c Sebastien Bourdeauducq: conda: use tagged migen/misoc
<bb-m-labs> build #229 of migen is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/migen/builds/229
cr1901_modern has quit [Read error: Connection reset by peer]
ohsix has quit [Ping timeout: 240 seconds]
<whitequark> sb0: ok, let's say allaki
<whitequark> can you fill me in?
ohsix has joined #m-labs
<bb-m-labs> build #1038 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/1038
<bb-m-labs> build #680 of artiq-win64-test is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/680
<sb0> whitequark, the allaki has a RF attenuator on it with a serial interface (see schematics in the sinara repository)
<sb0> for the first version we want to program it with a fixed value. it is currently on a GPIO core on the RTM FPGA, accessible over serwb
<sb0> whitequark, so the runtime should toggle those GPIO pins at startup to set a reasonable attenuation value.
<sb0> for the hardware test, there is sayma1 with an allaki in the first slot, with the outputs connected to the scope. with a lot of luck, there might be RF output (with the ramp generator that Robert added) after the attenuator is set ...
<whitequark> ok, I will look at it
<bb-m-labs> build #1915 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1915
<sb0> is there a source of low-cost SMP cables?
<sb0> bb-m-labs, force build artiq
<bb-m-labs> build forced [ETA 42m18s]
<bb-m-labs> I'll give a shout when the build finishes
<GitHub12> [artiq] sbourdeauducq tagged 3.2 at 244d4d0: https://github.com/m-labs/artiq/commits/3.2
<GitHub18> [artiq] sbourdeauducq commented on issue #877: @jonaskeller Please update to 3.2 to get those backtraces. https://github.com/m-labs/artiq/issues/877#issuecomment-356214380
<GitHub61> [artiq] sbourdeauducq commented on issue #845: > I've updated the master branch of ARTIQ so that the core device logs are now more useful... https://github.com/m-labs/artiq/issues/845#issuecomment-356214844
<GitHub6> [artiq] sbourdeauducq commented on issue #845: > I've updated the master branch of ARTIQ so that the core device logs are now more useful... https://github.com/m-labs/artiq/issues/845#issuecomment-356214844
<sb0> bb-m-labs: force build --props=package=artiq-kc705-nist_qc2 --branch=release-3 artiq-board
<bb-m-labs> build forced [ETA 17m59s]
<bb-m-labs> I'll give a shout when the build finishes
<sb0> bb-m-labs: force build --props=package=artiq-kc705-phaser --branch=release-3 artiq-board
<bb-m-labs> The build has been queued, I'll give a shout when it starts
<bb-m-labs> build #1039 of artiq-board is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/1039
<bb-m-labs> build forced [ETA 17m59s]
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #1040 of artiq-board is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/1040
<sb0> bb-m-labs: force build --props=package=artiq-kc705-nist_qc2 --branch=release-3 artiq-board
<sb0> bb-m-labs: force build --props=package=artiq-kc705-phaser --branch=release-3 artiq-board
<bb-m-labs> The build has been queued, I'll give a shout when it starts
<bb-m-labs> The build has been queued, I'll give a shout when it starts
halfr1 has quit [Remote host closed the connection]
<GitHub3> [artiq] whitequark commented on issue #845: I think those improvements were in smoltcp, but I do not remember exactly any more. https://github.com/m-labs/artiq/issues/845#issuecomment-356218615
<bb-m-labs> build #1041 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/1041
<bb-m-labs> build forced [ETA 18m12s]
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #1042 of artiq-board is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/1042
<sb0> whitequark, do you know what causes this conda problem?
<whitequark> never seen it
<sb0> bb-m-labs: force build --props=package=artiq-kc705-nist_qc2 artiq-board
<bb-m-labs> build forced [ETA 18m12s]
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #681 of artiq-win64-test is complete: Warnings [warnings python_coverage] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/681
<GitHub27> [artiq] sbourdeauducq deleted 3.2 at 244d4d0: https://github.com/m-labs/artiq/commit/244d4d0
<GitHub183> [artiq] sbourdeauducq pushed 1 new commit to release-3: https://github.com/m-labs/artiq/commit/a4337944835df8c18e860d9cde5e654d50286af7
<GitHub183> artiq/release-3 a433794 Sebastien Bourdeauducq: Work around another conda bug.
<sb0> bb-m-labs, stop build artiq
<bb-m-labs> try 'stop build WHICH <REASON>'
<sb0> bb-m-labs, stop build artiq conda
<bb-m-labs> build 1916 interrupted
<GitHub196> [artiq] sbourdeauducq tagged 3.2 at db6cc8c: https://github.com/m-labs/artiq/commits/3.2
<sb0> bb-m-labs, stop build artiq conda
<bb-m-labs> build 1916 interrupted
<sb0> bb-m-labs, stop build artiq-board conda
<bb-m-labs> build 1043 interrupted
<bb-m-labs> build #1043 of artiq-board is complete: Exception [exception interrupted] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/1043
<sb0> bb-m-labs, stop build artiq conda
<bb-m-labs> build 1916 interrupted
<sb0> bb-m-labs, stop build artiq conda
<bb-m-labs> build 1916 interrupted
<bb-m-labs> build #1916 of artiq is complete: Exception [exception interrupted] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1916
<sb0> bb-m-labs, stop build artiq conda
<bb-m-labs> build 1917 interrupted
<bb-m-labs> build #1917 of artiq is complete: Exception [exception interrupted conda_remove] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1917 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>
<sb0> bb-m-labs, force build artiq
<bb-m-labs> build forced [ETA 42m18s]
<bb-m-labs> I'll give a shout when the build finishes
<sb0> bb-m-labs, stop build artiq conda
<bb-m-labs> build 1918 interrupted
<bb-m-labs> build #1918 of artiq is complete: Exception [exception interrupted conda_remove] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1918
<sb0> bb-m-labs, force build --branch=release-3 artiq
<bb-m-labs> build forced [ETA 42m18s]
<bb-m-labs> I'll give a shout when the build finishes
<sb0> oh it's not conda, pebkac
<sb0> bb-m-labs: force build --props=package=artiq-kc705-phaser --branch=release-3 artiq-board
<bb-m-labs> build forced [ETA 18m12s]
<bb-m-labs> I'll give a shout when the build finishes
<sb0> bb-m-labs: force build --props=package=artiq-kc705-nist_qc2 --branch=release-3 artiq-board
<bb-m-labs> The build has been queued, I'll give a shout when it starts
<whitequark> sb0: WTF?
<whitequark> why did that work?
<sb0> I was building the wrong branch for artiq before
<sb0> the build system should have produced a clearer error, though, but that's a minor issue
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
cr1901_modern has joined #m-labs
cr1901_modern has quit [Read error: Connection reset by peer]
<bb-m-labs> build #1044 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/1044
<bb-m-labs> build forced [ETA 20m47s]
<bb-m-labs> I'll give a shout when the build finishes
cr1901_modern has joined #m-labs
<sb0> rjo, right now, the ethernet phy works when the transceiver is in PCS loopback mode, and breaks in the same way (rx_data stuck at either 0 or 0x7805c) with PMA loopback or regular connection to the switch
<sb0> transceiver TX cannot be tested at the moment unless your switch has some advanced diagnostic modes
<sb0> _florent_, do you remember any special parameters that have to be set or other xilinx rigmaroles we have to follow through when the rx buffer is used?
<sb0> does the PCS loopback involve the rx buffer?
<bb-m-labs> build #1045 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/1045
<sb0> _florent_, did you test the DRTIO code on non-ES silicon and without the DRP workaround? did it work anyway?
<sb0> according to fig 1-3 in the xilinx doc the rx buffer is involved in PCS loopback. so it shouldn't be the problematic element ...
<sb0> the PMA is a relatively simple component, why does it crap out like that?
<sb0> clocking differences with/without loopback?
<bb-m-labs> build #1046 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/1046
<bb-m-labs> build #682 of artiq-win64-test is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/682
sb0 has quit [Quit: Leaving]
cr1901_modern has quit [Quit: Leaving.]
cr1901_modern has joined #m-labs
<bb-m-labs> build #1919 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1919
attie has joined #m-labs
sb0 has joined #m-labs
<sb0> rjo, kasli jtag broke
<sb0> Error: JTAG scan chain interrogation failed: all zeroes
<sb0> and with the xilinx cable it's "No JTAG Chain found"
sb0 has quit [Quit: Leaving]
<_florent_> sb0: yes i tested DRTIO between KC705 and Artix7 some time ago
<_florent_> sb0: but i also did some tests with sdi recently, and figured out that with my code (wrong initialization), the change you suggested: https://github.com/enjoy-digital/transceiver_test/commit/3e85100d96eebdf7a464cdd640e7af1fce2fd19b break things and i had to revert it to have something working
<_florent_> sb0: for info, i'm going to use the sayma1 board, i need to power off/power on boards...
rohitksingh_work has quit [Read error: Connection reset by peer]
rohitksingh has quit [Quit: Leaving.]
rohitksingh has joined #m-labs
rohitksingh has quit [Client Quit]
rohitksingh has joined #m-labs
rohitksingh has quit [Quit: Leaving.]
rohitksingh has joined #m-labs
rohitksingh has quit [Read error: Connection reset by peer]
rohitksingh has joined #m-labs
<GitHub122> [artiq] hartytp commented on issue #727: Not really my field of expertise, but I believe it was this: https://github.com/analogdevicesinc/hdl/tree/dev/library/jesd204. @enjoy-digital is probably the person to ask about these things... https://github.com/m-labs/artiq/issues/727#issuecomment-356294300
<GitHub104> [artiq] enjoy-digital commented on issue #727: @hartytp: yes we can look at the core from ADI and see if we are doing initialization correctly. https://github.com/m-labs/artiq/issues/727#issuecomment-356298945
sb0 has joined #m-labs
<sb0> _florent_, going to take the boards offline in a moment to reflash sayma2 mmc
<sb0> _florent_, by the way, we have lockfiles, as explained in DEVELOPER_NOTES
<_florent_> sb0: ok, please tell me when it's done
<sb0> _florent_, taking boards offline now. should be quick.
<_florent_> sb0: btw with the boards i have, i'm not able to get serwb failing. With the ones on your server it's very easy to get it failing.
<sb0> _florent_, done.
<sb0> _florent_, yes, I noticed that ...
<sb0> okay I got those exar dumps
<_florent_> sb0: also my boards never get the 1.8v issue and I'm not doing anything for cooling
<GitHub185> [artiq] sbourdeauducq commented on issue #854: @gkasprow With the firmware you posted here: https://github.com/m-labs/sinara/issues/358#issuecomment-356007854 the link is still not detected by my media converter. Here's the dump I get from the MMC.... https://github.com/m-labs/artiq/issues/854#issuecomment-356319501
sb0 has quit [Quit: Leaving]
<GitHub61> [smoltcp] phil-opp commented on issue #94: > Having to proxy poll_at and egress through the PacketFilter trait should have been enough of an indication for me that this is trying to cut the abstractions that aren't really suited for this.... https://github.com/m-labs/smoltcp/pull/94#issuecomment-356320931
<GitHub181> [smoltcp] whitequark commented on issue #94: > For example, imagine a custom packet processor that immediately reacts to certain UDP control messages and passes all other packets to an internal SocketSet.... https://github.com/m-labs/smoltcp/pull/94#issuecomment-356322141
<_florent_> sb0: just curious, what are you using for powering the boards?
sb0 has joined #m-labs
<sb0> rjo, ping
<sb0> _florent_, PC ATX power supply and (60A switching) lab power supply.
<sb0> 1v8 problem is present in both cases
<_florent_> ok
<sb0> right now they're on the ATX, since it's easier to power-cycle, the lab one was just for testing and seeing if it made a difference for the 1v8 bug
<_florent_> hmm, it seems sayma1 is only working less than a minute correctly after power up...
<_florent_> is it expected?
<sb0> it's quite random, sometimes it crap out at startup, sometimes after seconds, sometimes after hours
<_florent_> sb0: do you know if the update you did can have impact board behaviour? because i seems more difficult than before to do something with the boards...
<sb0> _florent_, I only updated sayma2, did not touch sayma1
<sb0> and yes, those random board failures are a PITA
<_florent_> i'm wondering is serwb issue and 1.8v issue could be related...
<_florent_> is/if
<sb0> the main difference I see with Greg's board is the big input voltage drop
<sb0> the exar chip reports 11.20V instead of 12V on Greg's board
<sb0> could be shitty cables, which I used both with the lab PSU and the ATX PSU
<_florent_> is there a way for me to get this info with my board?
<_florent_> just to see if i also have the voltage drop or not
<sb0> reflashing it with the new MMC firmware...
<sb0> I'm not in the lab anymore
<sb0> for the one you have at your place, do you have a ARM-JTAG cable with the 10-pin connector?
<_florent_> no
<GitHub19> [smoltcp] phil-opp commented on issue #94: > Define "react"? If you don't need to reply then my proposed abstraction works.... https://github.com/m-labs/smoltcp/pull/94#issuecomment-356345595
<_florent_> at least i can try to measure the 12v voltage with a multimeter
<_florent_> for info, right now i'm not able to do anything with the sayma1, it's crashing before i can load what i need...
<sb0> yes, that happens sometimes
<sb0> sayma2 also has a rtm, you can try that one
<sb0> _florent_, if you leave your board powered for a long time (days), what happens?
<_florent_> i just measured 12V on my boards with 2 different ATX power supplies, i get ~11.90V with both
<_florent_> that's not reported by the exar chip by you 12v seems indeed to be low compared to what i and greg have
<_florent_> maybe you should have a closer look at that, or at least measure it with a multimeter
<_florent_> i haven't tested with board powered for a very long time
<_florent_> but at least it's powerd up for 6-8 hours now and still working fine
kyak has quit []
kyak has joined #m-labs
<GitHub154> [artiq] enjoy-digital pushed 2 new commits to master: https://github.com/m-labs/artiq/compare/267c69983510...2009734b3c61
<GitHub154> artiq/master 9c6a7f7 Florent Kermarrec: serwb/kusphy: use same serwb_serdes_5x reset than s7phy
<GitHub154> artiq/master 2009734 Florent Kermarrec: serwb/phy: get 625Mbps linerate working, increase timeout
rohitksingh has quit [Quit: Leaving.]
<bb-m-labs> build #1047 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/1047
<bb-m-labs> build #1920 of artiq is complete: Failure [failed python_coverage_1] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1920 blamelist: Florent Kermarrec <florent@enjoy-digital.fr>
felix_ has quit [Ping timeout: 264 seconds]
kristianpaul has quit [Quit: leaving]
felix_ has joined #m-labs
kristianpaul has joined #m-labs
bluebugs is now known as cedric
mumptai has joined #m-labs
mumptai has quit [Quit: Verlassend]
<GitHub185> [sinara] gkasprow pushed 1 new commit to master: https://git.io/vNmZJ
<GitHub185> sinara/master d693a97 Greg: Zotino rev 1.1 schematics
<GitHub20> [sinara] gkasprow pushed 1 new commit to master: https://git.io/vNmZ9
<GitHub20> sinara/master 2d67367 Greg: schematic logo update