<sb0>
_florent_, do you know why we get this warning " Gated clock check: Net CLKB0 is a gated clock net sourced by a combinational pin ISERDESE2_i_1/O, cell ISERDESE2_i_1." on the RTM? that's the serwb serdes
<_florent_>
sb0: i saw it, but haven't been able to understand. It seems related the fact that we are inverting CLKB, but is there another way to do it? (and that's what we are doing on others ISERDESE2 i think)
<sb0>
yes, that's what we are doing on the other ISERDESE2 for Kasli on SDRAM and it works fine there
<sb0>
I seem to be unable to reproduce that warning, too
<sb0>
whitequark, did you disconnect kasli ethernet?
<GitHub-m-labs>
[artiq] sbourdeauducq commented on issue #958: The satellite was resetting the SERDES, but the master was not (this may also cause problems on non-DRTIO targets). Hopefully fixed now! https://github.com/m-labs/artiq/issues/958#issuecomment-375236750
Gurty has quit [Quit: Kooll ~o~ datalove <3³\infty]
Gurty has joined #m-labs
<GitHub-m-labs>
[artiq] marmeladapk commented on issue #908: @jbqubit has (or will soon get) one of our Saymas which had worse results. Our second Sayma is in use by wizath at the moment (he's working on MMC). https://github.com/m-labs/artiq/issues/908#issuecomment-375275235
<marmelada>
I connected kasli to tp-link media converter
<marmelada>
ok, so with new mac no change
<marmelada>
i'll try opticlock now
<rjo>
you are saying the sfp modules, the fiber, the mac, and the media converter worked before?
<rjo>
and that kasli as well?
<marmelada>
we got that kasli from tom, it's the first time i use it
<rjo>
which sfp modules?
<marmelada>
glc-t
<rjo>
original cisco ones?
<marmelada>
no
<marmelada>
I also used tp-link mc220l media converter
<marmelada>
hm, now I get answers to pings
<marmelada>
but artiq_run times out
<marmelada>
ok, so my setup now: kasli 1.0, opticlock variant, urukul on eem 5 and 4, glc-t sfp module connected to switch
<rjo>
that one worked for us. do you have other ones around?
<rjo>
you are using the glv-t and the mc220l? and then another SFP to somewhere?
<rjo>
*glc-t
<rjo>
marmelada: and the sfp module you used with the media converter was which one?
<rjo>
marmelada: both the glc-t and the other sfp with the media converter yield the same result?
<rjo>
marmelada: it should not matter whether you have eems connected or not. but you need different bitstreams for v1.1 and v1.0 (see the --hw-rev switch when building).
<rjo>
but guven that you see the console messages, i think you did the right thing.
<marmelada>
rjo: i've seen that migen defaults to 1.0
<rjo>
yes.
<marmelada>
rjo i've seen that at some point someone removed ethernet information from console, as it was spamming
<marmelada>
infos like rx preamble errors etc
<marmelada>
how can I bring that back?
<rjo>
marmelada: 7afb23e8be261
<marmelada>
hm, silence
<marmelada>
should this worry me? ERROR(runtime::rtio_mgt): unrecognized startup_clock configurat ion entry, using internal RTIO clock
<marmelada>
O.o
<marmelada>
now it works
<marmelada>
ping with 0.3 ms response time
<marmelada>
and artiq run works
<marmelada>
I changed back !debug to !wanr and loaded it once again
<rjo>
no. that message is ok.
<rjo>
maybe some old misoc/migen was used to build the bitstream?
<rjo>
whitequark: if you can see the camera settings (i posted a list of the important things a few weeks ago) through aravis then we should probably go that route. and evaluate the existing python wrappers for aravis.
<rjo>
davidc__: you had experience with GigE vision stuff. any recommendation what to do and use and what not?
<rjo>
davidc__: is aravis a good gigev library to build on?
mumptai has joined #m-labs
kristianpaul has quit [Quit: Lost terminal]
FabM_Cave has quit [Quit: ChatZilla 0.9.93 [Firefox 52.7.2/20180316222652]]