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
siruf has quit [Ping timeout: 259 seconds]
siruf has joined #m-labs
Krue has left #m-labs [#m-labs]
mumptai has quit [Remote host closed the connection]
hedgeberg|away is now known as hedgeberg
nurelin has quit [Read error: Connection reset by peer]
sb0 has quit [Quit: Leaving]
hedgeberg is now known as hedgeberg|away
mumptai has joined #m-labs
sb0 has joined #m-labs
AndChat|326081 has quit [Ping timeout: 240 seconds]
mumptai has quit [Remote host closed the connection]
FabM has joined #m-labs
AndChat326081 has joined #m-labs
nurelin has joined #m-labs
<GitHub> [artiq] sbourdeauducq opened issue #681: move reports of asynchronous RTIO errors (esp. busy) to core device log https://github.com/m-labs/artiq/issues/681
nurelin has quit [Read error: Connection reset by peer]
nurelin has joined #m-labs
<GitHub> [artiq] jordens commented on issue #681: How do you get the error status to the core device log without polling? Or do you mean there would be polling on the AUX channel and that would "eventually" get the error status to the core device? Then the gateware would independently submit that to the log and/or abort the current kernel?... https://github.com/m-labs/artiq/issues/681#issuecomment-286094293
<GitHub> [artiq] cjbe opened issue #682: PYONValue default does not work for lists https://github.com/m-labs/artiq/issues/682
<GitHub> [artiq] sbourdeauducq commented on issue #681: I haven't thought of this implementation detail yet, I guess aux polling for errors is the simplest thing to do. https://github.com/m-labs/artiq/issues/681#issuecomment-286113551
<GitHub> [artiq] sbourdeauducq pushed 2 new commits to master: https://github.com/m-labs/artiq/compare/d1b9f9d73716...95ede18809e3
<GitHub> artiq/master 95ede18 Sebastien Bourdeauducq: drtio: support PHY latency compensation
<GitHub> artiq/master 497c795 Sebastien Bourdeauducq: drtio: input support (untested)
<bb-m-labs> build #463 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/463
<bb-m-labs> build #439 of artiq-win64-test is complete: Failure [failed python_unittest] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/439 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>
<bb-m-labs> build #1393 of artiq is complete: Failure [failed] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1393 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>
allen0s has joined #m-labs
<allen0s> hello. setting up artiq for the first time on a kc705 eval board. setup using conda, not source. trying to connect to the serial interface in ubuntu with mincom.
<allen0s> works @ 115200 8n1 but it won't respond to keyboard input -- in this case sending 't' for setup
<whitequark> allen0s: which version?
<allen0s> version of what?
<whitequark> artiq
<allen0s> whitequark: artiq-kc705-nist_qc1, artiq-main, minicom 2.7
<whitequark> which *version* of artiq?
<whitequark> version number.
<allen0s> whitequark: installing from https://m-labs.hk/artiq/manual-release-2/installing.html via anaconda, so whatever that installs
<allen0s> whitequark: how do i get the version #?
<whitequark> conda list
<whitequark> should be version 2.2
<allen0s> 2.1
<allen0s> installed yesterday
<whitequark> okay
<whitequark> try using flterm to interact with the serial interface
<allen0s> flterm wasn't installed
<allen0s> apparently b/c not installed from source
<allen0s> installed and working now
allen0s has quit [Quit: Page closed]
mumptai has joined #m-labs
Krue1 has joined #m-labs