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
forrestv has joined #m-labs
<GitHub175> [artiq] sbourdeauducq commented on issue #818: @mntng No, ``sys.executable`` cannot be replaced with ``"python"``. There can be multiple Python interpreters available on the system, and on a number of them (e.g. Debian) ``"python"`` refers to Python 2.7, which would break the test.... https://github.com/m-labs/artiq/pull/818#issuecomment-325069729
sb0 has joined #m-labs
_whitelogger has joined #m-labs
rohitksingh has joined #m-labs
<sb0> _florent_, there shouldn't be ascii-art in __repr__
<sb0> _florent_, I don't like the get_pads()/GTHPads hack. why not have a list of p/n pairs directly, with those pairs coming from the migen platform system directly (write platform description appropriately)?
<sb0> I don't see why you had to take clock domain creation out of TransceiverInterface
<sb0> use_cpll | use_qpll0 -> use_cpll or use_qpll0
<_florent_> sb0: ok, I'll do the changes
<sb0> _florent_, thanks
<_florent_> sb0: but what do you want me to do in the __repr__, remove the ascii-art? should I keep it somewhere else? I'm fine to do what it convenient for you but I need to know what you want :)
<sb0> _florent_, also I think the priority is to get the bridge to actually work with artiq
<_florent_> sb0: yes, that's what I'm going to do
<sb0> __repr__ should be a single-line thing. the ascii-art itself is fine, maybe keep it in source comments?
<_florent_> sb0: I'll do the others things, can you change the __repr__ while integrating and do what you think is best for you?
<sb0> ok
<_florent_> ok thanks
rohitksingh has quit [Ping timeout: 240 seconds]
<sb0> well. bridge or jesd. both are important
<_florent_> sb0: I expect to have the bridge working on monday
<_florent_> sb0: it was working with misoc with my old delay finding procedure
<GitHub65> [artiq] sbourdeauducq commented on pull request #818 abf3ce8: ditto https://github.com/m-labs/artiq/pull/818#discussion_r135393309
<GitHub148> [artiq] sbourdeauducq commented on pull request #818 abf3ce8: import os... https://github.com/m-labs/artiq/pull/818#discussion_r135393320
<GitHub96> [artiq] sbourdeauducq commented on pull request #818 abf3ce8: Are the default values ``description=None, builtin_terminate=False, allow_parallel=False`` not working? If they are working then please use them. https://github.com/m-labs/artiq/pull/818#discussion_r135393304
<GitHub107> [artiq] sbourdeauducq commented on pull request #818 abf3ce8: 2 blank lines to separate. https://github.com/m-labs/artiq/pull/818#discussion_r135393307
wingdu has joined #m-labs
<sb0> wingdu, hi
<wingdu> hey
wingdu has quit [Quit: wingdu]
wingdu has joined #m-labs
sb0 has quit [Quit: Leaving]
wingdu has quit [Quit: wingdu]
wingdu has joined #m-labs
rohitksingh has joined #m-labs
<rjo> _florent_: thanks. fyi: the other amc/rtm pair will be with greg again next week.
<rjo> _florent_: CODEGRPSYNC was always 0x00 in my tests. doesn't that indicate that it fails cgs?
sb0 has joined #m-labs
wingdu has quit [Quit: wingdu]
rohitksingh has quit [Quit: Leaving.]
wingdu has joined #m-labs
<wingdu> some where up ?
<sb0> wingdu, ?
<forrestv> why is migen simulation so slow compared to e.g. MyHDL? it seems like i'm getting at least a 10x slowdown with some MyHDL code ported to migen
<sb0> I guess, because no one optimized the migen simulation and it's as straightforward as it can get
<sb0> likely doing things like optimizing combinatorial loops/logic will bring about significant improvements
<sb0> a simple way to speed up the migen simulation is to run it in pypy
<sb0> maybe you can also look into compiling the comb/sync statements into llvm ir and then running standard llvm optimization passes on them
wingdu has quit [Quit: wingdu]
wingdu has joined #m-labs
wingdu has quit [Client Quit]
<sb0> _florent_, can you also clean up the bridge user API? (see comments in the artiq/sinara target files)
<GitHub10> [misoc] sbourdeauducq pushed 3 new commits to master: https://git.io/v53Wr
<GitHub10> misoc/master 517c25e Sebastien Bourdeauducq: csr: add pretty __str__'s
<GitHub10> misoc/master d49a452 Sebastien Bourdeauducq: integration: use '.' to separate region and CSR names unambiguously in CSR CSV
<GitHub10> misoc/master 584c73d Sebastien Bourdeauducq: wishbone: style
<GitHub139> [artiq] sbourdeauducq pushed 1 new commit to sinara: https://github.com/m-labs/artiq/commit/dbc12540dae24f5ca4a37af6f4cbdaeeb115eace
<GitHub139> artiq/sinara dbc1254 Sebastien Bourdeauducq: sayma_amc: register RTM CSR regions from CSV
<bb-m-labs> build #242 of misoc is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/misoc/builds/242
<sb0> wondering how many hours of Joe drama we will get about the requirement to compile the RTM before the AMC
<GitHub95> [sinara] gkasprow pushed 2 new commits to master: https://github.com/m-labs/sinara/compare/534e9464a692...31f344366bb6
<GitHub95> sinara/master 31f3443 Greg: Merge branch 'master' of https://github.com/m-labs/sinara
<GitHub95> sinara/master b4feedb Greg: simplified schematics & initial version of PCB finished
<sb0> _florent_, also I think the master core could just keep retrying when init fails
<sb0> if we want to check that the link is consistently up, we can add a register that is reset to 0 by the CPU and set to 1 whenever the link is restarted
<sb0> _florent_, and when the link is down and a transaction comes - are you asserting the wb error signal?
<sb0> _florent_, "need m-labs support to generate csr for rtm in amc header?" << done
<sb0> _florent_, rjo: is it correct that the hmc830 has active-high CS and hmc7043 has active-low CS?
<sb0> well. according to the datasheets both are active-low
<sb0> so why this code: If(hmc_spi_sel,
<sb0> hmc830_spi_cs.eq(~self.hmc_spi.core.cs_n),
<sb0> ).Else(
<sb0> hmc7043_spi_cs.eq(self.hmc_spi.core.cs_n)
<sb0> hmc830_spi_cs.eq(0),
<sb0> hmc7043_spi_cs.eq(1)
<sb0> ),
<sb0> maybe this is why the 830 doesn't work?
<GitHub49> [migen] sbourdeauducq pushed 1 new commit to master: https://git.io/v53B6
<GitHub49> migen/master 96844e8 Sebastien Bourdeauducq: sayma_rtm: add pins for HMC clocking chips
<GitHub6> [artiq] sbourdeauducq pushed 1 new commit to sinara: https://github.com/m-labs/artiq/commit/9194402ea5eb5f3c249cb37f3384a2e9f6d7318f
<GitHub6> artiq/sinara 9194402 Sebastien Bourdeauducq: sayma_rtm: expose HMC SPI bus
<bb-m-labs> build #183 of migen is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/migen/builds/183
<_florent_> sb0: hmc830 spi is working fine
<sb0> what is the logic behind that code?
<GitHub98> [migen] sbourdeauducq pushed 2 new commits to master: https://git.io/v53Ro
<GitHub98> migen/master e745f7c Sebastien Bourdeauducq: sayma_rtm: add DAC pins
<GitHub98> migen/master 185c3c6 Sebastien Bourdeauducq: sayma_rtm: add clock mux pins
<sb0> _florent_, rjo: do we need to pulse the DAC reset signal?
<bb-m-labs> build #184 of migen is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/migen/builds/184
_whitelogger has joined #m-labs
<GitHub156> [artiq] sbourdeauducq pushed 2 new commits to sinara: https://github.com/m-labs/artiq/compare/9194402ea5eb...26a11a296cdb
<GitHub156> artiq/sinara 26a11a2 Sebastien Bourdeauducq: sayma_rtm: drive DAC control signals
<GitHub156> artiq/sinara d609c67 Sebastien Bourdeauducq: sayma_rtm: set clock mux pins