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
cyrozap has quit [Ping timeout: 240 seconds]
ohama has quit [Ping timeout: 240 seconds]
ohama has joined #m-labs
cyrozap has joined #m-labs
<sb0>
whitequark, considering that you have the bytes 0x01 and 0x00 in your sequence, it's easy to form 256 if it's not shifted correctly
<whitequark>
oh, an off-by-one.
<whitequark>
I haven't considered *that*
rohitksingh_work has joined #m-labs
stekern has quit [Ping timeout: 240 seconds]
stekern has joined #m-labs
stekern has quit [Ping timeout: 264 seconds]
stekern has joined #m-labs
stekern_ has joined #m-labs
stekern has quit [Ping timeout: 256 seconds]
stekern_ is now known as stekern
<GitHub>
[artiq] sbourdeauducq commented on issue #681: > Recording to device log with RTIO time stamp is desired. Aborting kernel may leave experiment in a poorly defined state. Rather, let the user check for and handle errors gracefully as is done for TerminationRequested.... https://github.com/m-labs/artiq/issues/681#issuecomment-286646255
<GitHub>
[artiq] StanleyEDavidsdavid30 commented on issue #683: Yes I am fairly sure I have everything connected properly. So the problem is most likely due to the fact that I am using an Ubuntu Linux Virtual Machine to run ARTIQ and a Windows laptop to run the Intronix Logicport logic analyzer that I am using. The Intronix Logicport software does not seem to be supported by Linux. ... https://github.com/m-labs/artiq/issues/683#issuecomment-286647611
<GitHub>
[artiq] StanleyEDavidsdavid30 commented on issue #683: Yes I am fairly sure I have everything connected properly. So the problem is most likely due to the fact that I am using an Ubuntu Linux Virtual Machine to run ARTIQ and a Windows laptop to run the Intronix Logicport logic analyzer that I am using. The Intronix Logicport software does not seem to be supported by Linux. ... https://github.com/m-labs/artiq/issues/683#issuecomment-286647611