sb0 has quit [Read error: Connection reset by peer]
FabM has quit [Ping timeout: 246 seconds]
sb0 has joined #m-labs
FabM has joined #m-labs
sb0 has quit [Quit: Leaving]
aeris_ has quit [Ping timeout: 244 seconds]
aeris_ has joined #m-labs
aeris_ has quit [Ping timeout: 256 seconds]
aeris_ has joined #m-labs
aeris_ has quit [Ping timeout: 246 seconds]
aeris_ has joined #m-labs
aeris_ has quit [Ping timeout: 256 seconds]
<GitHub184>
[misoc] enjoy-digital pushed 1 new commit to master: http://git.io/hwfv
<GitHub184>
misoc/master 9107710 Florent Kermarrec: litexxx cores: use default baudrate of 115200 for all tests
FabM has quit [Quit: ChatZilla 0.9.91.1 [Firefox 36.0.1/20150305021524]]
aeris_ has joined #m-labs
<GitHub29>
[artiq] sbourdeauducq pushed 1 new commit to master: http://git.io/hwQb
<GitHub29>
artiq/master 200e20f Sebastien Bourdeauducq: worker: close devices immediately after run and before analyze
aeris_ has quit [Ping timeout: 256 seconds]
aeris_ has joined #m-labs
aeris_ has quit [Ping timeout: 245 seconds]
aeris_ has joined #m-labs
aeris_ has quit [Ping timeout: 246 seconds]
aeris_ has joined #m-labs
fengling has quit [Quit: WeeChat 1.0]
mog has left #m-labs ["Leaving"]
mog has joined #m-labs
_florent_ has joined #m-labs
_florent_ has quit [Quit: Leaving]
aeris has quit [Quit: en a pas]
SturmFlut has joined #m-labs
SturmFlut has quit [Read error: Connection reset by peer]
aeris has joined #m-labs
aeris has quit [Quit: en a pas]
aeris has joined #m-labs
aeris has quit [Client Quit]
aeris has joined #m-labs
aeris has quit [Client Quit]
aeris has joined #m-labs
aeris has quit [Client Quit]
aeris has joined #m-labs
_florent_ has joined #m-labs
<_florent_>
stb0: (if you read the logs) I've created an instrumented SoC with litescope to try to debug kc705 runtime
kyak has quit [Ping timeout: 264 seconds]
<_florent_>
I can trigger litescope when runtime start running (or during runtime execution since I'm write the software write to a specific register to trigger analyzer)
<_florent_>
I'm can observe all the signals we want
<_florent_>
I'm going to investigate on that tomorrow, but if you have some ideas on interesting signals to visualize, please share :)
_florent_ has quit [Quit: Leaving]
kyak has joined #m-labs
kyak has joined #m-labs
<ysionneau>
whitequark: I heard you're joining us (M-Labs) to work on ARTIQ? :)
<whitequark>
yea
<whitequark>
already did, in fact
<ysionneau>
yes that's what sb0 told me (we had lunch today)
<ysionneau>
welcome ! :)
kyak has quit []
sb0 has joined #m-labs
kyak has joined #m-labs
<rjo>
whitequark: welcome!
<rjo>
_florent_: are you using ethernet or the uart for piping the litescope data?
_florent_ has joined #m-labs
<_florent_>
rjo: in this case it uses UART since runtime is loaded with netboot
<_florent_>
sb0: do you remember what toolchain you used last time you tested runtime sucessfully on kc705, ISE or Vivado?
<rjo>
_florent_: ah. so your liteeth stack is single-master? either used/claimed by litescope or byt the bios/runtime?