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
<sb0> then 0x70000000 does not conflict
<sb0> was there just the problem of the boot address? I do remember the remapped spiflash core would only read back 0xffff....
<GitHub181> [artiq] sbourdeauducq commented on issue #854: I don't have a cable. https://github.com/m-labs/artiq/issues/854#issuecomment-351565507
<GitHub137> [artiq] sbourdeauducq commented on issue #854: I don't have a cable and I'd rather not install the crappy Xilinx drivers. https://github.com/m-labs/artiq/issues/854#issuecomment-351565507
<GitHub171> [artiq] sbourdeauducq commented on issue #854: I don't have a cable and I'd rather not install the crappy Xilinx drivers. They never work and typically waste a few hours of yak-shaving every time. https://github.com/m-labs/artiq/issues/854#issuecomment-351565507
<GitHub186> [artiq] sbourdeauducq commented on issue #854: I don't have a cable and I'd rather not install the crappy Xilinx drivers. They never work and typically waste a few hours on yak-shaving every time. https://github.com/m-labs/artiq/issues/854#issuecomment-351565507
X-Scale has quit [Ping timeout: 248 seconds]
<GitHub45> [artiq] hartytp commented on issue #867: @sbourdeauducq All over the place. Lots of variable names like i, o, a, b, c, m, j, k etc and functions with names like spline.tri.... https://github.com/m-labs/artiq/issues/867#issuecomment-351583219
X-Scale has joined #m-labs
<GitHub162> [artiq] sbourdeauducq commented on issue #854: So, I will try other things first. https://github.com/m-labs/artiq/issues/854#issuecomment-351585765
balrog has quit [Ping timeout: 240 seconds]
kyak has quit [*.net *.split]
ChanServ has quit [*.net *.split]
ChanServ has joined #m-labs
kyak has joined #m-labs
<GitHub66> artiq/master 71db953 Sebastien Bourdeauducq: artiq_flash: add srcbuild option to look into MiSoC source build trees. Closes #868
<GitHub66> [artiq] sbourdeauducq pushed 1 new commit to master: https://github.com/m-labs/artiq/commit/71db953ea0a31c69871ac2e014bede50b2704505
<GitHub147> [artiq] sbourdeauducq closed issue #868: .bit build, file location expected by artiq_flash https://github.com/m-labs/artiq/issues/868
<GitHub155> [artiq] sbourdeauducq commented on issue #869: #813 https://github.com/m-labs/artiq/issues/869#issuecomment-351591198
<GitHub51> [artiq] sbourdeauducq closed issue #869: artiq_flash support for Sayma_RTM https://github.com/m-labs/artiq/issues/869
balrog has joined #m-labs
<bb-m-labs> build #948 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/948
<bb-m-labs> build #620 of artiq-win64-test is complete: Warnings [warnings python_coverage] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/620 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>
<bb-m-labs> build #1832 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1832
rohitksingh_work has joined #m-labs
rohitksingh_wor1 has joined #m-labs
rohitksingh_work has quit [Ping timeout: 248 seconds]
<GitHub95> [artiq] whitequark commented on issue #868: IMO conda package layout should not differ from source builds, this is just needless complexity. I have encountered this issue as well. https://github.com/m-labs/artiq/issues/868#issuecomment-351603571
<GitHub144> [artiq] sbourdeauducq commented on issue #868: Conda and source builds layouts have pretty different requirements. But I'd be fine changing the conda layout if you insist. https://github.com/m-labs/artiq/issues/868#issuecomment-351603828
<GitHub79> [artiq] sbourdeauducq closed issue #846: spiflash core on Sayma not working https://github.com/m-labs/artiq/issues/846
kyak has quit [Ping timeout: 264 seconds]
<sb0> anyway I cannot find any sayma flash problem anymore
sb0 has quit [Quit: Leaving]
kyak has joined #m-labs
_whitelogger has joined #m-labs
<GitHub21> [artiq] jordens commented on issue #867: A lot of those single letter variables follow just follow signal names that are as old as the flip flop itself. You have to address that critique to the inventors of the flip-flop and everybody else after them. I see no reason to comment that.... https://github.com/m-labs/artiq/issues/867#issuecomment-351624219
<GitHub132> [artiq] jordens commented on issue #867: Migen and misoc do need more documentation. I think we already have issues filed there.... https://github.com/m-labs/artiq/issues/867#issuecomment-351624625
<cr1901_modern> migen/misoc still has the stream stuff? Thought that went away w/ the 2015 api change
sb0 has joined #m-labs
<sb0> rjo, phaser uses ref_period=5e-9/6 in the device db, where does that come from?
<rjo> sb0: from 150 MHz
<rjo> sb0: unless my math weakness hit me again.
<sb0> rjo, why write it with the /6?
<sb0> it's 1/150MHz/8
<sb0> and the /8 comes from the fine timestamp of the SERDES TTL
<sb0> rjo, does the sawg have a fine timestamp and how much?
<rjo> sure. that's the same number. 5e9/6 is how i remember the value.
<rjo> sawg doesn't have a fine timestamp.
<sb0> okay so without any IOSERDES TTL on Sayma, that value is 1/150MHz
<rjo> yes.
<GitHub193> [artiq] sbourdeauducq pushed 3 new commits to master: https://github.com/m-labs/artiq/compare/71db953ea0a3...100c2b17698b
<GitHub193> artiq/master 5809e08 Sebastien Bourdeauducq: runtime: no startup_clock config is not an error
<GitHub193> artiq/master 569484f Sebastien Bourdeauducq: remove phaser, adapt SAWG example to Sayma
<GitHub193> artiq/master 100c2b1 Sebastien Bourdeauducq: add Sayma LED blinker example
<GitHub198> [artiq] sbourdeauducq pushed 1 new commit to release-3: https://github.com/m-labs/artiq/commit/df2f0ead4aea64c227cbe882b2d6069c618b1be5
<GitHub198> artiq/release-3 df2f0ea Sebastien Bourdeauducq: runtime: no startup_clock config is not an error
<bb-m-labs> build #949 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/949
<sb0> first artiq kernel on sayma!
<sb0> building sawg now ...
<GitHub55> [artiq] sbourdeauducq pushed 1 new commit to master: https://github.com/m-labs/artiq/commit/2e74ce25d841db702079eb5f4b11a5f36c7a09e4
<GitHub55> artiq/master 2e74ce2 Sebastien Bourdeauducq: examples/sayma: make LED blink pattern more peculiar
<GitHub31> [artiq] sbourdeauducq pushed 1 new commit to master: https://github.com/m-labs/artiq/commit/77977932f2cd5d9c3b9619d0723a9871085fe2fa
<GitHub31> artiq/master 7797793 Sebastien Bourdeauducq: firmware: remove AD9516 support...
<bb-m-labs> build #621 of artiq-win64-test is complete: Warnings [warnings python_coverage] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/621 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>
<bb-m-labs> build #1833 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1833
<sb0> where are the rf outputs on allaki?
<sb0> not a good idea to put the IN/OUT silkscreen on the RTM PCB side...
<bb-m-labs> build #950 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/950
<sb0> whitequark, any progress on the network slowness bugs? FYI I have removed the Oxford switch
<bb-m-labs> build #622 of artiq-win64-test is complete: Warnings [warnings python_coverage] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/622 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>
<bb-m-labs> build #1834 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1834
Gurty has quit [Ping timeout: 272 seconds]
Gurty has joined #m-labs
Gurty has quit [Changing host]
Gurty has joined #m-labs
<bb-m-labs> build #951 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/951
<sb0> ultrascale productivity multiplied, more like ultrascale compilation time multiplied ...
<bb-m-labs> build #623 of artiq-win64-test is complete: Warnings [warnings python_coverage] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/623 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>
rohitksingh_wor1 has quit [Read error: Connection reset by peer]
<bb-m-labs> build #1835 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1835
<rjo> sb0: idle_kernel?
<sb0> startup
<sb0> but yes
<sb0> flat scope trace, of course...
<sb0> are there switches, pgias, etc. that need to be set from the fpga?
<sb0> _florent_, did you get the PRBS test to work in firmware?
rohitksingh has joined #m-labs
<sb0> on the other sayma, the hmc830 won't lock anymore
sb0 has quit [Quit: Leaving]
<rjo> sb0: could you do a bit of triage on issues? labels, assign?
sb0 has joined #m-labs
kyak has quit []
kyak has joined #m-labs
kyak has joined #m-labs
<GitHub160> [artiq] jbqubit commented on issue #868: ARTIQ should be internally self consistent. Please change the layout. https://github.com/m-labs/artiq/issues/868#issuecomment-351741044
<GitHub40> [artiq] jbqubit commented on issue #813: What's the status of this? https://github.com/m-labs/artiq/issues/813#issuecomment-351741863
<GitHub66> [artiq] jbqubit commented on issue #854: Doesn't HK have flea markets selling things like JTAG cables? Please go get a cable. https://github.com/m-labs/artiq/issues/854#issuecomment-351742772
<GitHub95> [artiq] jbqubit commented on issue #870: Which LED? https://github.com/m-labs/artiq/issues/870#issuecomment-351743231
<GitHub34> [artiq] sbourdeauducq commented on issue #868: What does this have to do with "self-consistency"? https://github.com/m-labs/artiq/issues/868#issuecomment-351743567
<GitHub81> [artiq] sbourdeauducq commented on issue #868: What does this have to do with "internal self-consistency"? https://github.com/m-labs/artiq/issues/868#issuecomment-351743567
<sb0> ah the allaki needs SPI commands before it lets RF through
<sb0> sigh
<GitHub3> [artiq] sbourdeauducq commented on issue #870: Top layer, green, near the FMC connector and the top edge. And maybe "3 seconds" is not enough. https://github.com/m-labs/artiq/issues/870#issuecomment-351746431
<GitHub8> [artiq] whitequark commented on issue #854: These things aren't sold on flea markets, or at least you or I wouldn't know where to find or how to use them. https://github.com/m-labs/artiq/issues/854#issuecomment-351757052
<GitHub1> [artiq] whitequark commented on issue #868: I agree with @jbqubit that the filesystem layout of artiq_flash (which, only by coincidence, is what conda packages use) should match the output of `python -m artiq.gateware.targets.xxx`. This also makes it easier to do things like building everything but the bitstream locally, which unfortunately are also blocked because of similarly poor design decisions in regards to paths
<GitHub45> [artiq] sbourdeauducq commented on issue #868: What design decisions exactly? https://github.com/m-labs/artiq/issues/868#issuecomment-351758101
<GitHub184> [artiq] whitequark commented on issue #868: @sbourdeauducq using absolute paths, assuming that if a script is generated it needs to be run immediately, assuming that a generated file will be run on the same host. I was trying to make it possible to make misoc build process network transparent, but wasted nearly a week of time and gave up in the end, it would require too many changes in misoc. Maybe another time... 
<GitHub1> [artiq] whitequark commented on issue #868: @sbourdeauducq using absolute paths, assuming that if a script is generated it needs to be run immediately, assuming that a generated file will be run on the same host. I was trying to make it possible to make misoc build process network transparent, but wasted nearly a week of time and gave up in the end, it would require too many changes in misoc. Maybe another time......
<GitHub40> [artiq] sbourdeauducq commented on issue #868: It was never intended to be a network build system. If we start doing complicated things like that, maybe there are existing build systems that can be reused? https://github.com/m-labs/artiq/issues/868#issuecomment-351759964
<GitHub14> [artiq] sbourdeauducq commented on issue #868: Anyway, to go back to the original topic:... https://github.com/m-labs/artiq/issues/868#issuecomment-351763084
<GitHub83> [artiq] whitequark commented on issue #868: There are, but I wanted to hack together something that would mainly just let me test gateware changes without having Xilinx. Actually, maybe it is easier to just give up and install Xilinx junk on my laptop. Is it possible for me to borrow M-Labs' license using their flexlm crap? https://github.com/m-labs/artiq/issues/868#issuecomment-351763293
<GitHub72> [artiq] jordens commented on issue #868: I'd be fine with packaging the binaries as `gateware/top.bit`, `software/runtime/runtime.fbi`, `software/bios/bios.bin`. The added directories are a minor inconvenience. https://github.com/m-labs/artiq/issues/868#issuecomment-351763976
stekern_ is now known as stekern
<GitHub53> [migen] sbourdeauducq pushed 1 new commit to master: https://git.io/vbVwO
<GitHub53> migen/master 8e87a14 Sebastien Bourdeauducq: sayma_rtm: add Allaki control pins
<bb-m-labs> build #212 of migen is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/migen/builds/212
rohitksingh has quit [Read error: Connection reset by peer]
rohitksingh has joined #m-labs
<GitHub78> [artiq] gkasprow commented on issue #854: you can buy it on aliexpress, ebay, just 10$ per piece
<davidc__> sb0: my RGA arrived, though it was packed terribly. Filament seems intact though. I'll take (external) pictures and figure out a pinout later today
<davidc__> sb0: it'll probably be a few weeks until I have time to machine connectors/adapters for it.
<sb0> davidc__, just stick pins like Amphenol AT62-16-0122 into it + flying wires (keep the rf ones short and the collector one shielded)
<sb0> unless you have a competent machinist + lots of equipment on hand, machining sounds like a royal PITA
<sb0> collector one should be reasonably short as well, otherwise capacitance will reduce your scan speed
<davidc__> sb0: I'm an (in)competent machinist, and have a lathe and mill sufficient to work SS :)
<davidc__> sb0: I meant more for the vac side. I
rohitksingh has quit [Quit: Leaving.]
<GitHub42> [artiq] jbqubit opened issue #871: instructions for using ARTIQ with Sayma https://github.com/m-labs/artiq/issues/871
<GitHub27> [artiq] jordens commented on issue #854: Just to summarize the options, there are a couple of more or less viable paths to get experiments loaded onto Sayma dynamically:... https://github.com/m-labs/artiq/issues/854#issuecomment-351793482
<rjo> larsc: nice. i guess you'll be there?
<larsc> no
<larsc> no tickets, no time
<larsc> but I'll try to watch the stream
<rjo> ack. me neither.
<GitHub57> [artiq] jbqubit opened issue #872: Sayma_AMC artiq_flash :: Unknown flash device (ID 0x00000000) https://github.com/m-labs/artiq/issues/872
<cr1901_modern> That makes three of us
<cr1901_modern> 'cept in addition to no tickets or time, I have no way to get there
<GitHub144> [artiq] jordens commented on issue #872: What does the idcode scan report that happens before that? https://github.com/m-labs/artiq/issues/872#issuecomment-351819100
<GitHub152> [artiq] jordens commented on issue #872: I.e. always provide full logs... https://github.com/m-labs/artiq/issues/872#issuecomment-351819182
ashafir has quit [Ping timeout: 260 seconds]
<GitHub46> [artiq] jbqubit opened issue #873: Sayma_AMC: MMC doesn't init power ICs https://github.com/m-labs/artiq/issues/873
<GitHub110> [artiq] jbqubit commented on issue #873: @gkasprow https://github.com/m-labs/artiq/issues/873#issuecomment-351829150
<GitHub147> [artiq] jbqubit commented on issue #872: ```... https://github.com/m-labs/artiq/issues/872#issuecomment-351830063
<GitHub192> [artiq] jbqubit commented on issue #868: Ok. I can better rephrase what I'm asking for now. I'd like to be able to use ```artiq_flash``` with both conda and locally generated binaries. Perhaps a flag to ```artiq_flash``` could indicate which directory contains the build results. https://github.com/m-labs/artiq/issues/868#issuecomment-351831006
<GitHub177> [artiq] jbqubit commented on issue #870: I set "M switches" on PCB "HS1" to 1234 -> 0111. I can now flash the board using artiq_flash -t sayma and see on ttyUSB2 MiSoC BIOS messages. Thanks! ... https://github.com/m-labs/artiq/issues/870#issuecomment-351831260
<GitHub136> [artiq] jbqubit closed issue #870: Sayma: no debug info on flterm https://github.com/m-labs/artiq/issues/870
<GitHub60> [artiq] jbqubit commented on issue #872: Also, ... https://github.com/m-labs/artiq/issues/872#issuecomment-351831917
<GitHub90> [artiq] jordens commented on issue #872: That would not work. https://github.com/m-labs/artiq/issues/872#issuecomment-351832064
<GitHub140> [artiq] jordens commented on issue #872: From the symptoms this is the same as the 1.8V supply dying and the same as the FTDI chip locking up when bein accessed (or openocd ctrl-C-ed) when Sayma is not powered. We already have issues for those. ... https://github.com/m-labs/artiq/issues/872#issuecomment-351832606
<GitHub80> [artiq] jordens closed issue #872: Sayma_AMC artiq_flash :: Unknown flash device (ID 0x00000000) https://github.com/m-labs/artiq/issues/872
<GitHub31> [artiq] jbqubit commented on issue #872: @jordens don't summarily close Issues without discussion. ... https://github.com/m-labs/artiq/issues/872#issuecomment-351835272
ChanServ has quit [*.net *.split]
ChanServ has joined #m-labs
ChanServ has quit [*.net *.split]
ChanServ has joined #m-labs
<GitHub178> [artiq] gkasprow commented on issue #873: @jbqubit does this happen on single board or all boards?... https://github.com/m-labs/artiq/issues/873#issuecomment-351861119
<GitHub4> [artiq] jbqubit commented on issue #873: The following is reproducible.... ... https://github.com/m-labs/artiq/issues/873#issuecomment-351868814
<GitHub192> [artiq] gkasprow commented on issue #873: @jbqubit this is correct behaviour. DRT line causes MMC reset. Please disable flow control. Or unsolder pin 3 of T23. I can add a DIP switch that enables USB firmware update... https://github.com/m-labs/artiq/issues/873#issuecomment-351870640
<GitHub174> [artiq] gkasprow commented on issue #873: @jbqubit this is correct behaviour. Serial port DTR line causes MMC reset. Please disable flow control. Or unsolder pin 3 of T23. I can add a DIP switch that enables USB firmware update... https://github.com/m-labs/artiq/issues/873#issuecomment-351870640
<GitHub29> [artiq] gkasprow commented on issue #873: You can also short pins 1 and 2 of T24. https://github.com/m-labs/artiq/issues/873#issuecomment-351870848