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
<GitHub-m-labs>
[artiq] sbourdeauducq commented on issue #854: I have never tried this openmmc firmware with Ethernet, and considering how everything goes with Sayma in general and the MMC in particular it is safe to assume it is broken. Please use the same firmware as me.... https://github.com/m-labs/artiq/issues/854#issuecomment-378094956
<bb-m-labs>
I'll give a shout when the build finishes
rohitksingh_work has quit [Read error: Connection reset by peer]
futarisIRCcloud has joined #m-labs
<sb0>
bb-m-labs: force build --props=package=artiq-board,artiq_target=kasli,artiq_variant=opticlock artiq-board
<sb0>
bb-m-labs: force build --props=package=artiq-board,artiq_target=kasli,artiq_variant=sysu artiq-board
<bb-m-labs>
The build has been queued, I'll give a shout when it starts
<bb-m-labs>
The build has been queued, I'll give a shout when it starts
<sb0>
idea: compile the kasli bitstream for 125MHz, then edit the MMCM after place-and-route to set the frequency to whatever the vivado trash gives us
<GitHub-m-labs>
[artiq] sbourdeauducq commented on issue #977: > heMgmtTutorial1 is the name it changed fromrtio.py, and Mgmt_Tutorial.py is the name of the file I use to test the dashboard(print hello world)... https://github.com/m-labs/artiq/issues/977#issuecomment-378236679
<GitHub-m-labs>
[artiq] hartytp commented on issue #967: @sbourdeauducq With the caveat that I'm not aware of the precise details of any of the relevant contracts, and with apologies if this is treading on peoples' toes here, but...... https://github.com/m-labs/artiq/issues/967#issuecomment-378239721
<GitHub-m-labs>
[artiq] sbourdeauducq commented on issue #977: That's not enough for me to reproduce it, e.g. I don't have your experiments. I need detailed instructions that start from a *blank* ARTIQ installation. https://github.com/m-labs/artiq/issues/977#issuecomment-378242418
<GitHub-m-labs>
[artiq] sbourdeauducq commented on issue #977: I see three experiments in your screenshot. Are they all needed to reproduce the problem? if yes then I need all three. If no then please delete the other ones and give me minimal instructions. https://github.com/m-labs/artiq/issues/977#issuecomment-378247537
<GitHub-m-labs>
[artiq] mingshenli commented on issue #977: no. actually I make a python3.5 environment as the documentation says. should I create a python 3.6 environment use `conda create -n py36 python=3.6 anaconda`? https://github.com/m-labs/artiq/issues/977#issuecomment-378268579
<felix_>
only a part of the gaisler stuff is open source. when i worked on a project based on the grlib, at least the leon4 core and the l2 cache weren't part of the open source part and the debugger is only available as a binary. if you don't have component in your design that aren't in the open source part of grlib, you can use an evaluation version of the debugger that only runs for a few months, otherwise you
<felix_>
need to buy a debugger license that will require a usb dongle to run
_whitelogger has joined #m-labs
<GitHub-m-labs>
[artiq] mingshenli commented on issue #977: ok. after installing 3.6 as the order you give, I will try it on a new version, hoping the new version will solve the problem. the installing will take a long time, I will let you know once I reproduce the step above.... https://github.com/m-labs/artiq/issues/977#issuecomment-378276884
<GitHub-m-labs>
[artiq] sbourdeauducq commented on issue #977: The software also behaves correctly when I make a copy of the experiment ``Management tutorial`` (renames one of them, they both can still run, and there is no bug when rescanning the repository). https://github.com/m-labs/artiq/issues/977#issuecomment-378277036
<GitHub-m-labs>
[artiq] sbourdeauducq commented on issue #977: It should fix the cygwin one, but nothing has changed regarding repository management, so I think the experiment name issue will persist. https://github.com/m-labs/artiq/issues/977#issuecomment-378278332
<GitHub-m-labs>
[artiq] jordens commented on issue #978: Thanks! Also for the clean repro. I think I have seen this as well in December with Kasli. So likely reproduced/ible (back then there were more pressing issues so I didn't isolate it). https://github.com/m-labs/artiq/issues/978#issuecomment-378298039
<GitHub-m-labs>
[artiq] jordens commented on issue #978: Thanks! Also for the clean repro. I think I have seen this as well in December with Kasli (back then there were more pressing issues so I didn't isolate it). Therefore likely reproduced/ible and maybe SED-related. https://github.com/m-labs/artiq/issues/978#issuecomment-378298039
<GitHub-m-labs>
[artiq] jbqubit commented on issue #854: Is there somebody at your lab that can tell me the model number for the SFP-RJ45 transceiver and Ethernet switch? If I can't reproduce your setup exactly we can't move beyond blaming the parts external to Sayma. https://github.com/m-labs/artiq/issues/854#issuecomment-378307578
<hartytp>
IIUC, t_restart is basically the delay that gets added to the ADC + IIR pipeline stage to make it take the same duration as the DDS update stage
<rjo>
hartytp: i don't think that would be correct. t_cycle is the duration of the longest stage. i don't think your change would make the case t_adc + t_iir > t_dds work.
<Hartytp_>
And we can increase rtt to 19 without slowing down the servo
<Hartytp_>
So that's about 10m cable at max speed
<bb-m-labs>
build #2239 of artiq is complete: Failure [failed python_unittest] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2239 blamelist: Florent Kermarrec <florent@enjoy-digital.fr>
<bb-m-labs>
build #2240 of artiq is complete: Failure [failed python_unittest] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2240 blamelist: Florent Kermarrec <florent@enjoy-digital.fr>
rqou_ has joined #m-labs
rqou has quit [*.net *.split]
rqou_ is now known as rqou
X-Scale has quit [Ping timeout: 276 seconds]
X-Scale has joined #m-labs
hartytp has quit [Quit: Page closed]
hartytp has joined #m-labs
<hartytp>
rjo: what am I missing here.
<hartytp>
assume t_adc + t_iir > t_dds
<hartytp>
but {t_adc, t_iir} < t_dds
<hartytp>
e.g. if we increase the rtt to something like 24
<hartytp>
so I don't expect there to be an issue here
<rjo>
that's faster than ultra 320 scsi. and those are lucky to work over 12 m with carefully impedance controlled cables.
<rjo>
give it a try. if 20m idc pass bert incl crosstalk, i'll make sure that su-servo won't be the bottleneck.
<hartytp>
okay, so long as there isn't anything else I'm missing in the code then everything I want to do is supported
<hartytp>
by increasing the rtt
<hartytp>
so, we can just stick it to 19 and then use cables limited by si
<hartytp>
cool, thanks
<rjo>
the rtt could in theory be permitted to be arbitrarily high by decoupling the cnv/clk part from the clkout/ado[a-d] part ans placing the former somewhere else in the cycle.
<hartytp>
yes, it wouldn't be a huge change.
<hartytp>
but, so long as I've understood the current timings, that's not going to be an issue
<rjo>
it would be great if you or someone would determine the limit of the idc length for 125 MHz DDR (or even 62.5 MHz SDR).
<hartytp>
it would
<hartytp>
it's on the to do list
<hartytp>
but that list seems to be growing atm
<hartytp>
faster than I can tick things off
<rjo>
welcome to our world.
<hartytp>
I assume the pay is better :)
<rjo>
if it was we could hire the people we want to hire.
<hartytp>
yes
<hartytp>
anyway, thanks for clearing up the servo stuff
<rjo>
sure.
<hartytp>
any thoughts about when it will land?
<hartytp>
not chasing there as I'm aware of the number of things on the go atm
<hartytp>
just curious
<hartytp>
marmeladpk: do you have any updates about the sayma mmc firmware?
<hartytp>
I had a few emails saying it was about to arrive, but the time seemed to be getting longer with each email so I stopped asking :(
<rjo>
it's near the top of my list together with the driver for the princeton emccd cam, a bunch of sayma stuff, and a few miscellaneous items.
<hartytp>
cool
hartytp has quit [Quit: Page closed]
mumptai has quit [Quit: Verlassend]
<rjo>
pretty high on the list of items that bother me is the quality of the wiki pages. to varying degree but generally all of them. i'd like to be able to print the pdfs and ship them with the hardware and not be embarrassed by the content, the orthography, and the style.
X-Scale has joined #m-labs
<cr1901_modern>
rjo: Use pandoc-flavored markdown and just compile to wiki markup, Tex, etc?
<rjo>
yes.
<rjo>
the technical side and the layout are good enough for me already. it's about the rest.
<cr1901_modern>
Oh oops, I misread your initial sentence. The wiki has the information you want already and you want to convert it to PDF
<cr1901_modern>
but the wiki pages are of varying quality