lekernel changed the topic of #m-labs to: Mixxeo, Migen, MiSoC & other M-Labs projects :: fka #milkymist :: Logs http://irclog.whitequark.org/m-labs
fengling has joined #m-labs
<sb0> maybe the solution to this annoying simulation bug is just ditch Verilog for simulation
<sb0> figuring out verilog tricks that get that mess to work sounds as complicated as just interpreting the logic directly
<sb0> plus, there will be no more VPI module to install (unless people want to co-simulate verilog code)
xiangfu has joined #m-labs
<sb0> rjo, http://www.thorlabs.com/thorProduct.cfm?partNumber=TCH002 << is this thing more than a USB hub from the PC point of view?
<rjo> sb0: just an expensive one.
<sb0> so no driver needed then
<rjo> no. who mentioned that tch002?
<GitHub151> [artiq] sbourdeauducq pushed 1 new commit to master: http://git.io/fhOvlA
<GitHub151> artiq/master 8d305e3 Sebastien Bourdeauducq: doc: some precisions about controllers
<sb0> it's in the original project spec
<sb0> "We require Controllers to be made [...] for the following additional hardware [...] Thorlabs TDC001 servo motor controllers, TPZ001 piezo controllers, ***and TCH002 hubs***"
<rjo> ack. trivially done then ;)
<rjo> sb0: and the others are just a more or less asynchronous single-shot devices like those labbricks.
<sb0> there's also the NI PXI-6733
<sb0> are you still using those, or switching to PDQ?
<rjo> sb0: some experiments use them.
<rjo> sb0: and it would be nice if the API for the PXI-6733 and PDQ2 would be very similar. But I did not have that in mind when I wrote the PDQ2 driver/api.
<rjo> sb0: i personally would push the 6733 to the bottom of the list.
<sb0> ok. speaking of pdq, I still have some questions: https://ssl.serverraum.org/lists-archive/artiq/2014-October/000150.html
<rjo> ah. forgot. sorry.
<rjo> anything else i promised and did not deliver (apart from getting more people deeply involved ;)?
<sb0> well, it seems that workshop was mostly successful :)
<sb0> and no, not that I remember. thanks :)
fengling has quit [Ping timeout: 245 seconds]
xiangfu has quit [Ping timeout: 256 seconds]
<rjo> sb0: i replied to your mail. let me know if i missed the point.
xiangfu has joined #m-labs
<rjo> sb0: ah. the talk slides and your comments on them. i'll try to do that tomorrow...
sj_mackenzie has joined #m-labs
xiangfu_ has joined #m-labs
xiangfu has quit [Ping timeout: 244 seconds]
fengling has joined #m-labs
xiangfu_ has quit [Read error: Connection reset by peer]
xiangfu has joined #m-labs
fengling has quit [Quit: WeeChat 1.0]
fengling has joined #m-labs
<sb0> rjo, about those slides, I dropped JSON because serializing numpy arrays was a mess
<sb0> and writing a numpy-aware serializer in python is easy, https://github.com/m-labs/artiq/blob/master/artiq/management/pyon.py
<zyp> especially when you don't need to deal with untrusted input
<rjo> sb0: i agree. this is why i tend to gravitate towards yaml which does support that.
<rjo> sb0: but pyon is also just fine.
<rjo> sb0: yaml may also be a bit too flexible for the embedded side of things.
<zyp> please don't believe that simply removing builtins will make it safe, ref: nparray.__globals__['__builtins__'].open('foo.txt', 'w').write('foo')
<sb0> zyp, this is not meant to be used over the open internet, but between trusted machines on a LAN
<zyp> fair enough, it's just a reminder :)
<zyp> the dangerous part is that it's seemingly secure, so somebody might decide to use it for untrusted input
xiangfu has quit [Ping timeout: 244 seconds]
<sb0> that's pretty much the case for most software ;)
<sb0> but yes, I see you point
<sb0> *your
xiangfu has joined #m-labs
<rjo> a funny sidestory to that: we have a so-called "research network" now (not "research on networks" but a "network for research equipment") because people definitely want to connect their 1990 oscilloscope with Windows NT 3.whatever to the network. virtually no rules enforced on that network. a honeypot. the story goes that some of the more powerful oscilloscopes were hijacked and used as warez/etc distribution bots. i am just waiting for some virus to run amok i
<zyp> haha
xiangfu_ has joined #m-labs
xiangfu has quit [Ping timeout: 258 seconds]
xiangfu_ has quit [Remote host closed the connection]
xiangfu has joined #m-labs
<sb0> ysionneau, can you save your simulator-breaking code somewhere?
<sb0> might want to use it as a test case for the bugfix
xiangfu_ has joined #m-labs
xiangfu has quit [Ping timeout: 255 seconds]
<GitHub105> [artiq] sbourdeauducq pushed 1 new commit to master: http://git.io/mrt3bQ
<GitHub105> artiq/master 4cae553 Sebastien Bourdeauducq: pc_rpc: server identification support
mumptai has joined #m-labs
<sj_mackenzie> sb0: github.com/upstandinghackers/hammer
xiangfu_ has quit [Ping timeout: 272 seconds]
fengling_ has joined #m-labs
fengling has quit [Ping timeout: 260 seconds]
fengling_ is now known as fengling
nengel has quit [Ping timeout: 260 seconds]
<ysionneau> 08:06 < sb0> ysionneau, can you save your simulator-breaking code somewhere? < sure!
<sb0> ysionneau, did the artiq tutorial go smoothly on your board/pc?
<ysionneau> yes, I don't remember any issue, except that I needed to re-run a few times experiments, but maybe I had another terminal with the serial port open (flterm), not sure
<ysionneau> sb0 how can I convert a 'Proxy' (from simulation context) into an integer?
<sb0> and was everything clear?
nengel has joined #m-labs
<sb0> ysionneau, the selfp proxy?
<ysionneau> some selfp.a signal
<ysionneau> so that I can do selfp.b[selfp.a]
<sb0> if selfp.a is a signal, then the getattr of selfp for "a" should return an integer
<ysionneau> ok maybe I misunderstood the error then
<ysionneau> ok I worked around the issue
<ysionneau> I could just use self.a instead of selfp.a
<ysionneau> since a was a constant value
_florent_ has joined #m-labs
<ysionneau> 10:09 < sb0> and was everything clear? < I think if it was not clear I would have added some text to my patch, so except the python3.3 issue and the sudo -E PATH=$PATH stuff I think it was OK
<sb0> ah yes, selfp doesn't work for anything else than a signal
<ysionneau> but I can try again
<sb0> in fact I should probably remove selfp, even though it gives some syntactic sugar in simple use cases, it causes obscure errors in others
fengling has quit [Ping timeout: 245 seconds]
<ysionneau> ah ok, I was doing selfp.dfi.phases[selfp.sdrphy.phy_settings.rdphase]
<ysionneau> 10:09 < sb0> and was everything clear? < I can try again all the install procedure from scratch, I have setup a 'fresh' VM snapshot for that kind of stuff, so that I can easily try 'from scratch' stuff
<ysionneau> I just have the toolchain already compiled
fengling has joined #m-labs
mumptai has quit [Ping timeout: 272 seconds]
<sb0> ysionneau, your video: https://www.youtube.com/watch?v=AfEPbw4nREo
<sb0> from orconf
<ysionneau> ah thanks!
<ysionneau> maybe it will be hard to see since it's all console demo
<ysionneau> ok the focus is wrong on the slides :(
<sb0> ysionneau, I was asking more about using it, not installing it
<sb0> creating the pulses etc.
fengling has quit [Quit: WeeChat 1.0]
<ysionneau> I just went through the installing part so far, and then tried running a few pre-written experiments and had the issues I told you about, then I switched on the spiflash
<ysionneau> -on+to
MY123 has joined #m-labs
Gurty has quit [Excess Flood]
Gurty has joined #m-labs
sj_mackenzie has quit [Remote host closed the connection]
xiangfu has joined #m-labs
xiangfu has quit [Ping timeout: 244 seconds]
_florent_ has quit [Read error: Connection reset by peer]
nengel has quit [Ping timeout: 250 seconds]
nengel has joined #m-labs
nengel has quit [Ping timeout: 256 seconds]
nengel has joined #m-labs
xiangfu has joined #m-labs
xiangfu has quit [Ping timeout: 244 seconds]
_florent_ has joined #m-labs
xiangfu has joined #m-labs
xiangfu has quit [Ping timeout: 264 seconds]
xiangfu has joined #m-labs
xiangfu has quit [Ping timeout: 240 seconds]
xiangfu has joined #m-labs
xiangfu has quit [Remote host closed the connection]
sb0 has quit [Ping timeout: 255 seconds]
sb0 has joined #m-labs
mumptai has joined #m-labs
mumptai has quit [Quit: Verlassend]
MY123 has quit [Quit: Connection closed for inactivity]
_florent_ has quit [Quit: Leaving]