thealamenthe20 has quit [Remote host closed the connection]
rohitksingh_work has joined #m-labs
rohitksingh_wor1 has joined #m-labs
rohitksingh_work has quit [Ping timeout: 245 seconds]
<GitHub-m-labs>
[artiq] whitequark commented on issue #1162: > note that it fails with `import artiq.language.core; @artiq.language.core.kernel`, as well. So just accounting for `import as` won't fix it.... https://github.com/m-labs/artiq/issues/1162#issuecomment-425316996
rohitksingh_work has joined #m-labs
rohitksingh_wor1 has quit [Ping timeout: 260 seconds]
drewes has joined #m-labs
misinformed has joined #m-labs
misinformed has quit [Remote host closed the connection]
drewes has quit [Remote host closed the connection]
ScottK15 has joined #m-labs
ScottK15 has quit [Remote host closed the connection]
sb0 has joined #m-labs
RoBo_V10 has joined #m-labs
RoBo_V10 has quit [Remote host closed the connection]
cnu-8 has joined #m-labs
cnu-8 has quit [Remote host closed the connection]
gnufan has joined #m-labs
feltnerm_ has joined #m-labs
bbolli26 has joined #m-labs
feltnerm_ has quit [Remote host closed the connection]
bbolli26 has quit [Ping timeout: 272 seconds]
ndkT has joined #m-labs
ndkT has quit [Remote host closed the connection]
teecee has joined #m-labs
kujo has joined #m-labs
teecee has quit [Remote host closed the connection]
<hartytp>
"After configuring the CDR circuit, reset it and then release the reset by writing 1 and then 0 to Register 0x206, Bit 0"
<hartytp>
AFAICT we are resetting the CDR circuit before programming it, but the data sheet says we should do the opposite
<hartytp>
or am I missing something?
<hartytp>
nope, I'm being dumb
<hartytp>
ignore that
<hartytp>
sorry
<hartytp>
been tracking down obscure bugs in Sayma for so long now that I can't read straight. There is a ghost in there somewhere
m4ssi has joined #m-labs
imacdonn22 has joined #m-labs
imacdonn22 has quit [Remote host closed the connection]
darksider3_ has joined #m-labs
darksider3_ has quit [Remote host closed the connection]
SergioAtSUSE19 has joined #m-labs
SergioAtSUSE19 has quit [Remote host closed the connection]
jxself17 has joined #m-labs
Kulgur has joined #m-labs
jxself17 has quit [Remote host closed the connection]
Kulgur has quit [Remote host closed the connection]
olus27 has joined #m-labs
olus27 has quit [Remote host closed the connection]
atriv has joined #m-labs
atriv has quit [Remote host closed the connection]
lemmu has joined #m-labs
lemmu has quit [Remote host closed the connection]
Bercik0 has joined #m-labs
Bercik0 has quit [Remote host closed the connection]
goddess has joined #m-labs
goddess has quit [Remote host closed the connection]
blackheart28 has joined #m-labs
blackheart28 has quit [Remote host closed the connection]
<sb0>
hartytp: have you been able to test drtio switching at all?
<hartytp>
no, that's next on my list
<hartytp>
built the bitstreams
<hartytp>
and am running the master, but that's it so far
<hartytp>
as soon as I get sayma running properly I'll move on to that
GoldenNeko7 has joined #m-labs
GoldenNeko7 has quit [Remote host closed the connection]
<hartytp>
for some reason on this board AD9154 always gives me a SYSREF PLL locked error
<hartytp>
sometimes 2
<hartytp>
then it starts working
drewbeer has joined #m-labs
drewbeer has quit [Remote host closed the connection]
<hartytp>
anyway, I now have sayma booting happily at 2.4GHz DAC clock and a nice sysref generator with excellent phase control
<hartytp>
so, in theory all I need to do is solder some coax onto sayma (onto 0402 pads, which isn't ideal) and it will be synchronised
rohitksingh_work has quit [Read error: Connection reset by peer]
pete__ has joined #m-labs
pete__ has quit [Remote host closed the connection]
<sb0>
did you get the delay line chip to work too?
<sb0>
what does your setup look like atm? do you have a pic?
<hartytp>
yes
<hartytp>
do you want to see an eye diagram??
<hartytp>
modulo shitty loose joints on sayma and my ropey HDL, that worked first time
<hartytp>
delay line is just a shift register so even I can't mess it up
rohitksingh has joined #m-labs
<hartytp>
sb0: posted
<sb0>
nice, thanks!
mueslo0 has joined #m-labs
mueslo0 has quit [Killed (Sigyn (Spam is off topic on freenode.))]
zhhuabj_ has joined #m-labs
xPsycho13 has joined #m-labs
xPsycho13 has quit [Remote host closed the connection]
zhhuabj_ has quit [Ping timeout: 268 seconds]
<hartytp>
sb0: over an hour or so, I saw about 100ps of drift in the phase of the signal on my scope. I don't have a fan on the phase shifter so the stability there is probably not great...
inimino` has joined #m-labs
inimino` has quit [Read error: Connection reset by peer]
rohitksingh has quit [Quit: Leaving.]
rohitksingh has joined #m-labs
trisk22 has joined #m-labs
trisk22 has quit [Ping timeout: 244 seconds]
KNERD28 has joined #m-labs
KNERD28 has quit [Remote host closed the connection]
MarkusDBX9 has joined #m-labs
MarkusDBX9 has quit [Remote host closed the connection]
jpirko1 has joined #m-labs
jpirko1 has quit [Remote host closed the connection]
rohitksingh has quit [Quit: Leaving.]
cloudhead5 has joined #m-labs
cloudhead5 has quit [Remote host closed the connection]
m4ssi has quit [Remote host closed the connection]
<GitHub122>
[smoltcp] whitequark commented on issue #256: @jhwgh1968 You can't call `s.rx_buffer.dequeue*` if you want to continue using the socket afterwards. Take a look at the implementation of `TcpSocket::recv`; you're skipping `TcpSocket::recv_impl`, which means `s.remote_seq_no` doesn't get updated, and the assembler gets confused afterwards.... https://github.com/m-labs/smoltcp/issues/256#issuecomment-425508970
vaninwagen0 has joined #m-labs
vaninwagen0 has quit [Remote host closed the connection]
heeen15 has joined #m-labs
heeen15 has quit [Remote host closed the connection]