sb0_ changed the topic of #m-labs to: https://m-labs.hk :: Logs http://irclog.whitequark.org/m-labs
mumptai has quit [Remote host closed the connection]
<sb0> okay, sayma 2.0GHz clocking seems to work just fine (or at least not worse than other frequencies)
<sb0> whitequark: nope, .sqrt() is not available
<whitequark> sb0: let me check
<sb0> whitequark: that's in libboard_artiq, I want to compute a standard deviation
<sb0> that's going to be used in both runtime and satman, but I don't want to bloat the BRAM satman (which won't use this code) with a math library
<sb0> only Sayma AMC with DAC sychronization will use it
<whitequark> sb0: ok, open bug: https://github.com/rust-lang/rfcs/issues/2505
<whitequark> we aggressively prune dead code
<whitequark> so you should not see any bloat
<GitHub-m-labs> [artiq] sbourdeauducq pushed 2 new commits to master: https://github.com/m-labs/artiq/compare/74fdd04622a6...443d6d868800
<GitHub-m-labs> artiq/master 3b6f478 Sebastien Bourdeauducq: firmware: print more info on DDMTD stability error
<GitHub-m-labs> artiq/master 443d6d8 Sebastien Bourdeauducq: sayma_amc: pass RTIO clock frequency to SiPhaser
<bb-m-labs> build #2349 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/2349
proteusguy has quit [Remote host closed the connection]
<bb-m-labs> build #2350 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/2350
<bb-m-labs> build #1012 of artiq-win64-test is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/1012
<bb-m-labs> build #2874 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2874
proteusguy has joined #m-labs
proteusguy has quit [Ping timeout: 246 seconds]
rohitksingh_work has joined #m-labs
<sb0> hartytp: one downside to init by kernels is the startup time of the boards
<sb0> right now the firmware takes 12s to initialize (and test) clocking chips and DACs
<sb0> in a 12-board system with kernels, that's going to be almost 3 minutes of startup, whereas the firmware solution can boot boards in parallel
<sb0> (but we can still use pure DRTIO with firmware)
_whitelogger has joined #m-labs
<GitHub-m-labs> [artiq] sbourdeauducq pushed 3 new commits to master: https://github.com/m-labs/artiq/compare/443d6d868800...2b0d63db23cc
<GitHub-m-labs> artiq/master bdd4e52 Sebastien Bourdeauducq: ad9154: support 125MHz RTIO
<GitHub-m-labs> artiq/master 47312e5 Sebastien Bourdeauducq: sayma: set RTIO_FREQUENCY in MasterDAC
<GitHub-m-labs> artiq/master 2b0d63d Sebastien Bourdeauducq: hmc830_7043: support 125MHz RTIO
proteusguy has joined #m-labs
futarisIRCcloud has joined #m-labs
proteusguy has quit [Ping timeout: 245 seconds]
proteusguy has joined #m-labs
<bb-m-labs> build #2351 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/2351
<bb-m-labs> build #2352 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/2352
_whitelogger has joined #m-labs
zng has quit [Ping timeout: 246 seconds]
zng_ has joined #m-labs
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
m4ssi has joined #m-labs
futarisIRCcloud has joined #m-labs
cr1901_modern1 has quit [Quit: Leaving.]
cr1901_modern has joined #m-labs
<GitHub-m-labs> [artiq] jordens opened issue #1254: Kasli: supoprt 10 MHz reference input https://github.com/m-labs/artiq/issues/1254
<GitHub-m-labs> [artiq] sbourdeauducq pushed 7 new commits to master: https://github.com/m-labs/artiq/compare/2b0d63db23cc...1a42e23fb491
<GitHub-m-labs> artiq/master cfe6654 Sebastien Bourdeauducq: jesd204sync: cleanup DDMTD averaging code
<GitHub-m-labs> artiq/master 3acee87 Sebastien Bourdeauducq: firmware: improve DDMTD resolution using dithering/averaging
<GitHub-m-labs> artiq/master ba21dc8 Sebastien Bourdeauducq: jesd204sync: improve messaging
<GitHub-m-labs> [artiq] sbourdeauducq pushed 1 new commit to master: https://github.com/m-labs/artiq/commit/7a5d28b73d6607320f391b28301103fde32efce1
<GitHub-m-labs> artiq/master 7a5d28b Sebastien Bourdeauducq: jesd204sync: test SYSREF period
proteusguy has quit [Remote host closed the connection]
<bb-m-labs> build #2875 of artiq is complete: Failure [failed python_unittest_2] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2875 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
<bb-m-labs> build #2353 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/2353
<bb-m-labs> build #2354 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/2354
rohitksingh_work has quit [Read error: Connection reset by peer]
<bb-m-labs> build #1013 of artiq-win64-test is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/1013
<bb-m-labs> build #2876 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2876
rohitksingh has joined #m-labs
<GitHub-m-labs> [artiq] jordens pushed 1 new commit to master: https://github.com/m-labs/artiq/commit/90c9fa446f79a942cec961dcca6e711f7f6eadc7
<GitHub-m-labs> artiq/master 90c9fa4 Robert Jördens: test: add array transfer test...
<GitHub-m-labs> [artiq] jordens opened issue #1255: array network transfer speed https://github.com/m-labs/artiq/issues/1255
proteusguy has joined #m-labs
<bb-m-labs> build #2355 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/2355
dlrobertson has joined #m-labs
<bb-m-labs> build #2356 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/2356
qclab has joined #m-labs
qclab has left #m-labs [#m-labs]
qclab has joined #m-labs
jason has joined #m-labs
rohitksingh has quit [Read error: Connection reset by peer]
jason is now known as Guest10102
rohitksingh has joined #m-labs
<Guest10102> Hello. I have followed the exact instructions from https://m-labs.hk/artiq/manual-release-2/installing.html#installing-the-artiq-packages
<Guest10102> up to artiq_flash -t kc705 -m nist_clock
<Guest10102> First of all, -m is not recognized anymore. So I used artiq_flash -t kc705 instead
<Guest10102> Then I got the following error:
<sb0> Guest10102: use the manual that corresponds to your artiq release
<sb0> Guest10102: what board do you have?
<Guest10102> kc705
<Guest10102> So I get the same error
<Guest10102> I am using artiq_flash -t kc705 -V nist_clock
<Guest10102> from the forth release
<Guest10102> I reconnected the usb and rebooted couple of times as well.
<Guest10102> I am using ubuntu 16.04 LTS
<Guest10102> I realized that although I have installed openocd (using $conda install openocd) I do not have an openocd in the directory /usr/local/share/
<Guest10102> Could that be the reason?
<Guest10102> Nah I still get the same error. Any ideas sb0 ?
<_whitenotifier-c> [nmigen] jfng opened issue #32: back.verilog: Memory with asynchronous transparent read port needs a CLK signal ? - https://git.io/fhPU3
<sb0> openocd obviously start
<sb0> did you use the correct usb port? does the jtag adapter show up in lsusb?
dlrobertson has quit [Quit: WeeChat 2.3]
<Guest10102> @sb0 no I don't see Digilent or Xilinx in lsusb. What shall I do from here?
<Guest10102> For one thing I am not using the original USB cable from Xilinx box. It is another USB cable which is functioning. But could that be the problem? What else can I do?
rohitksingh has quit [Ping timeout: 244 seconds]
Guest10102 has quit [Ping timeout: 256 seconds]
joson has joined #m-labs
<acathla> joson, check in dmesg after you plugged your USB cable to see if there are any error or launch "udevadm monitor" just before you plug the cable, you should see some events. If not, your cable is dead (power only, no data maybe?)
qclab has left #m-labs [#m-labs]
<joson> acathla, you were right! The cable was power only. It worked with a new cable. Thanks!
<acathla> joson, it's a classic =)
joson has quit [Ping timeout: 256 seconds]
jason has joined #m-labs
jason is now known as Guest85846
<Guest85846> acathla, now I successfully flashed the device and set the IP and MAC address. The connections from the computer to the router and from the router to the kc705 board seems to be ok. But I cannot ping. Do you know how to troubleshoot this?
bluebugs has joined #m-labs
bluebugs has quit [Changing host]
bluebugs has joined #m-labs
cedric has quit [Ping timeout: 250 seconds]
<acathla> Guest85846, I don't know much about your device but, like for the usb cable, the classic bug is probably your windows firewall if you sadly use windows.
<Guest85846> acathla, I use ubuntu!
<Guest85846> And my firewall is inactive
Guest85846 has quit [Ping timeout: 256 seconds]
jason has joined #m-labs
jason is now known as Guest84785
<Guest84785> acathla, sb0, Also running $nmap -sn 192.168.1.0/24 gives no ip addresses in the local network. Any ideas?
Guest84785 has quit [Ping timeout: 256 seconds]
jason1 has joined #m-labs
<jason1> Actually it gives the ip address of the interface on my pc (which I set) but not the kc705 device. Any ideas?
<jason1> I am the same user as Guest84785
mumptai has joined #m-labs
jason1 has quit [Ping timeout: 256 seconds]
jason1 has joined #m-labs
<jason1> I can ping the router. But still cannot ping the kc705 board..
bluebugs is now known as cedric
<GitHub177> [smoltcp] kevinis commented on issue #269: Hello! Any suggestion on how I can help in this issue? https://github.com/m-labs/smoltcp/issues/269#issuecomment-458333430
futarisIRCcloud has joined #m-labs