sb0 changed the topic of #m-labs to: https://m-labs.hk :: Logs http://irclog.whitequark.org/m-labs :: Due to spam bots, only registered users can talk. See: https://freenode.net/kb/answer/registration
<cr1901_modern> whitequark: http://www.sunburst-design.com/papers/CummingsSNUG2003Boston_Resets.pdf Page 20, in huge bold lol
<whitequark> I mean, duh
<whitequark> any asynchronous input must be synchronized
<whitequark> this is kind of obvious
<cr1901_modern> I suppose... just found it amusing how it was typeset
<cr1901_modern> in bold, in caps. Like if you miss this it's your fault
futarisIRCcloud has joined #m-labs
<GitHub-m-labs> [artiq] dhslichter commented on issue #1142: But can one wrap the physical layer specifications for each in some sensible way, and just make a DDS state machine that will be suitably track a simplified set of parameters (frequency with 32-bit FTW only, amplitude scale factor) and enable those to be overridden by injection? AFAICT the only thing one would want to do with injection would be to set frequency or a
<GitHub-m-labs> [artiq] dhslichter commented on issue #1142: But can one wrap the physical layer specifications for each in some sensible way, and just make a DDS state machine that will suitably track a simplified set of parameters (frequency with 32-bit FTW only, amplitude scale factor) and enable those to be overridden by injection? AFAICT the only thing one would want to do with injection would be to set frequency or ampl
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
wolfspraul has joined #m-labs
rohitksingh has joined #m-labs
X-Scale has quit [Read error: Connection reset by peer]
_whitelogger has joined #m-labs
<mithro> Any idea why the clear signal is not working in simulation here?
<whitequark> is clear driven from somewhere else?
<whitequark> in that case the simulator silently discards `yield x.eq
rohitksingh has quit [Ping timeout: 250 seconds]
rohitksingh has joined #m-labs
X-Scale has joined #m-labs
rohitksingh has quit [Ping timeout: 272 seconds]
rohitksingh has joined #m-labs
rohitksingh has quit [Ping timeout: 246 seconds]
rohitksingh has joined #m-labs
rohitksingh has quit [Ping timeout: 246 seconds]
rohitksingh has joined #m-labs
<GitHub-m-labs> [artiq] bradbqc commented on issue #1064: @marmeladapk Yes, except the flash failed, citing "Error: Cannot enable write to flash. Status=0x00000000." I'll try erasing and re-flashing and report back https://github.com/m-labs/artiq/issues/1064#issuecomment-442889179
<GitHub-m-labs> [artiq] jbqubit opened issue #1200: NXP firmware update via artiq_flash https://github.com/m-labs/artiq/issues/1200
<GitHub-m-labs> [artiq] bradbqc commented on issue #1064: I've discovered that part (if not all) of the reason I'm unable to flash is that the mmc is restarting every minute (pretty much exactly 60s, as far as I can tell) for some reason. I noticed a very brief dip in the current sayma was drawing and so I looked at the mmc serial output. It is repeatedly printing ... https://github.com/m-labs/artiq/issues/1064#issuecommen
m4ssi has quit [Remote host closed the connection]
cr1901_modern has quit [Ping timeout: 250 seconds]
<GitHub-m-labs> [artiq] gkasprow commented on issue #1064: @bradbqc do you use one or two power units at the time ?... https://github.com/m-labs/artiq/issues/1064#issuecomment-442963491
rohitksingh has quit [Ping timeout: 246 seconds]
hozer has quit [Ping timeout: 244 seconds]
<GitHub-m-labs> [artiq] sbourdeauducq commented on issue #1064: @bradbqc @gkasprow MMC and µTCA bugs are a different issue. https://github.com/m-labs/artiq/issues/1064#issuecomment-442996747
<GitHub-m-labs> [artiq] sbourdeauducq commented on issue #1064: @bradbqc @gkasprow MMC and µTCA bugs are a different issue.... https://github.com/m-labs/artiq/issues/1064#issuecomment-442996747
marmelada has joined #m-labs
<marmelada> sb0: brad is already using external power supply, reboots happen on bench otp
<marmelada> *top
<marmelada> so MTCA trash has nothing to do here this time
dlrobertson has quit [Quit: WeeChat 2.3]
cr1901_modern has joined #m-labs
_whitelogger has joined #m-labs
dlrobertson has joined #m-labs
<kbeckmann> I'm trying to use a PLL on ice40/glasgow with migen to output a clock on a pin and getting some annoying errors. I'm doing the following: https://gist.github.com/kbeckmann/03131ebdab6ca4235f114432c2640f29 Am I doing something obviously wrong?
<whitequark> kbeckmann: the PLL on UP5K is weird
<kbeckmann> oh
<whitequark> first, if you use it, you lose one of the pins
<whitequark> one of the IO pins becomes either an input-only or output-only, I don't recall which it is exactly
<kbeckmann> ok, i guess in my case that's fine since i have quite a few free and only want to output the raw clock on a pin.
<kbeckmann> uhh raw pll clock i mean of course.
<whitequark> why do you want to use a PLL to generate a 24 MHz clock?
<whitequark> actually nevermind, stupid question
<kbeckmann> reviving a broken ice40 devkit, oscillator broke and i just wanted to try it out
<kbeckmann> i can solve it in a thousand other ways but this is more fun :D
<whitequark> I have no idea what that nextpnr message means
<whitequark> try asking nextpnr people
<whitequark> daveshah on ##openfpga?
<kbeckmann> alright, will do that. have you used plls on the up5k through migen successfully otherwise?
<whitequark> yes
<whitequark> but only on the SYNC pin
<kbeckmann> oh right! will take a look at that.
marmelada has quit [Ping timeout: 256 seconds]
<GitHub-m-labs> [artiq] cjbe opened issue #1201: Gateware build error when instantiating multiple SUServo https://github.com/m-labs/artiq/issues/1201
<GitHub-m-labs> [artiq] cjbe opened issue #1202: Gateware build fails if there are no moninj probes https://github.com/m-labs/artiq/issues/1202