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
antgreen has joined #m-labs
<ccube> what is the recommended way to write data into a CSRStorage from my design? Do I have to set write_from_dev and then call my_storage.dat_w.eq(data)?
<ccube> i tried to call my_storage.storage.eq(data), but then synthesis fails :/
<sb0> create your CSRStorage with write_from_dev=True
<sb0> and use we and dat_w
<sb0> if your CSRStorage is read-only from the bus, you should use CSRStatus instead
<ccube> sb0, thx. so as long as i keep 'we' = 1, the bus is not able to read?
<sb0> it is able to read, but this isn't the most efficient solution
sj_mackenzie has joined #m-labs
rofl__ has joined #m-labs
sh[4]rm4 has quit [Ping timeout: 265 seconds]
<ccube> whats the best way to implement a sleep function? is there a non-busy wait?
<sb0> if you are using libbase it's bare metal, so there's no concept of non-busy wait
<ccube> kk
<ccube> then whats the best concept of busy wait?
<ccube> counting a volatile?
<ccube> shouldnt there be a timer in misoc which i can use?
<sb0> there is one, look at the bios boot timeout for example
sj_mackenzie has quit [Ping timeout: 264 seconds]
FabM has joined #m-labs
fengling has joined #m-labs
bentley` has joined #m-labs
<ccube> nice, thx sb0
<ccube> is there any way to speed up synthesis with Xilinx ISE? Something like less optimization stuff for quicker debugging?
<sb0> no
<sb0> but you can use verilator simulations of the whole soc now
<ccube> cool
<GitHub173> [artiq] sbourdeauducq pushed 1 new commit to master: http://git.io/veBmC
<GitHub173> artiq/master 45bb9d8 Sebastien Bourdeauducq: runtime: support RPC and log on AMP
travis-ci has joined #m-labs
<travis-ci> m-labs/artiq#96 (master - 45bb9d8 : Sebastien Bourdeauducq): The build passed.
travis-ci has left #m-labs [#m-labs]
<sb0> whitequark, essentially, you could replace their fancy single-photon source with a $5 CW laser pointer off dealextreme, the photon counters with regular photodiodes, and the photon detection probabilities with the intensity measured by the photodiodes. after you apply their postselection tricks, you can show their "entanglement" between the classical beams ...
fengling has quit [Ping timeout: 264 seconds]
fengling has joined #m-labs
<whitequark> ah I see
fengling has quit [Quit: WeeChat 1.0]
<ccube> ERROR:Place:375 - The design does not fit in device. :(
kugg has quit [*.net *.split]
early has quit [*.net *.split]
kmehall_ has quit [*.net *.split]
mog has quit [*.net *.split]
ysionneau has quit [*.net *.split]
tommylommykins has quit [*.net *.split]
FabM has quit [*.net *.split]
rofl__ has quit [*.net *.split]
kyak has quit [*.net *.split]
jaeckel has quit [*.net *.split]
mumptai_ has quit [*.net *.split]
aeris has quit [*.net *.split]
bentley` has quit [*.net *.split]
FabM has joined #m-labs
rofl__ has joined #m-labs
kyak has joined #m-labs
jaeckel has joined #m-labs
mumptai_ has joined #m-labs
aeris has joined #m-labs
early has joined #m-labs
tommylommykins has joined #m-labs
kmehall_ has joined #m-labs
mog has joined #m-labs
ysionneau has joined #m-labs
kugg has joined #m-labs
bentley` has joined #m-labs
early has quit [*.net *.split]
early has joined #m-labs
<sb0> ccube, lm32 or or1k?
<ccube> lm32
<sb0> and what else are you trying to fit in there?
<ccube> code, Ive written by myself
<sb0> you can also switch to the smaller sdram controller
<sb0> minicon
<sb0> gee! all unittests pass on AMP
<ccube> internet dropped, maybe missed some messages sb0 . anyway, deleted some code. seems to fit in now. but still 20 min waiting :(
<GitHub6> [artiq] sbourdeauducq pushed 1 new commit to master: http://git.io/veRIO
<GitHub6> artiq/master 5538ad5 Sebastien Bourdeauducq: runtime: support RPC exceptions on AMP
<sb0> ccube, look at the log http://irclog.whitequark.org/m-labs
<ccube> oh, so you missed my messages haha
<ccube> just said, that probably my code is not being very efficient
<ccube> synthesis taking hours...
travis-ci has joined #m-labs
<travis-ci> m-labs/artiq#97 (master - 5538ad5 : Sebastien Bourdeauducq): The build passed.
travis-ci has left #m-labs [#m-labs]
<sb0> rjo, what exactly is that dds_clock on C:15 that you added?
<sb0> should we use that on ppro as well?
<GitHub76> [misoc] sbourdeauducq pushed 2 new commits to master: http://git.io/veRDy
<GitHub76> misoc/master 176b924 Sebastien Bourdeauducq: soc: use new ModuleTransformer API
<GitHub76> misoc/master 8b41ab3 Sebastien Bourdeauducq: make: add target in build names
<rjo> that's the same signal you put on xtrig on ppro. the rtio/dds clock input
<sb0> rjo, sure, but if it's not xtrig, what is it?
<sb0> it is routed on the qc_dac adapter?
<sb0> pmt2?
<GitHub153> [artiq] sbourdeauducq pushed 3 new commits to master: http://git.io/veRd7
<GitHub153> artiq/master 1ed60e0 Sebastien Bourdeauducq: gateware/amp: use new ModuleTransformer API
<GitHub153> artiq/master 7e591bb Sebastien Bourdeauducq: targets: use _Peripherals/UP/AMP class names, share QC1 IO defs
<GitHub153> artiq/master c8039e9 Sebastien Bourdeauducq: doc: update Papilio Pro info
<sb0> kept xtrig on ppro. it won't meet timing with C:15/pmt2...
<sb0> pipistrello amp doesn't meet timing either
<sb0> (one reason I liked the monsterboard is fighting timing on slowtan6 is a pita)
travis-ci has joined #m-labs
<travis-ci> m-labs/artiq#98 (master - c8039e9 : Sebastien Bourdeauducq): The build has errored.
travis-ci has left #m-labs [#m-labs]
FabM has quit [Quit: ChatZilla 0.9.91.1 [Firefox 36.0.4/20150320202338]]
<rjo> that BTN2/PMT2/dds_clock pin is a global clock input on pipistrello. that's why i went for it and it is wired up on the adapter board.
<rjo> is fighting timing on k7 easier?
<rjo> wbtc?
<rjo> sb0: ppro up with xtrig does not meet timing either anymore afaict.
<ysionneau> ah, webtalk, the spying Xilinx program
<ysionneau> we could just put some dummy wbtc binary in PATH that does nothing, it's safe to ignore webtalk
<ysionneau> (in Readme)
<ysionneau> strange that we only get to hear about wbtc from now on
<ysionneau> maybe the tool only tries to send reports to Xilinx if timing fails to meet constraints
rofl__ has quit [Ping timeout: 265 seconds]
sh4rm4 has joined #m-labs
<rjo> lets leave it. it fails because of the bitstream rename.