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 has joined #m-labs
<sb0> cr1901_modern, it should not be legal. it's a bug.
sb0 has quit [Client Quit]
mumptai_ has joined #m-labs
mumptai has quit [Ping timeout: 265 seconds]
sb0 has joined #m-labs
<cr1901_modern> sb0 (clearly I need to sleep): I created that contrived example after noticing that you allow BUILD_LIST opcodes in tracer,get_var_name.
<cr1901_modern> Idk why you allow BUILD_LIST at all, but I'm sure if you look at the disassembly of that stupid contrived edge case I made you'll immediately see why it succeeds.
<GitHub186> [artiq] sbourdeauducq commented on issue #854: @gkasprow Just looking at a different way of fixing things, in case the routing to non-clock-capable pins is causing excessive problems. Can the PHY be set up in a non-standard way to **receive** both the TX and the RX clock that would be generated by the FPGA, in either "RGMII" (1Gbps 125MHz DDR) or "MII" (100Mbps 25MHz SDR) modes? https://github.com/m-labs/artiq/i
<GitHub183> [artiq] sbourdeauducq commented on issue #854: @gkasprow Just looking at a different way of fixing things, in case the routing to non-clock-capable pins is causing excessive problems. Can the PHY be set up in a non-standard way to **receive** both the TX and the RX clocks that would be generated by the FPGA, in either "RGMII" (1Gbps 125MHz DDR) or "MII" (100Mbps 25MHz SDR) modes? https://github.com/m-labs/artiq/
<sb0> cr1901_modern, iirc BUILD_LIST is allowed somewhere else, not in that function that is used for CSRs, and that's for things like self.x = [Signal() for _ in range(y)]
rohitksingh_work has joined #m-labs
sb0 has quit [Ping timeout: 256 seconds]
<rohitksingh_work> sb0: ping
early has quit [Quit: Leaving]
early has joined #m-labs
<rohitksingh_work> sb0: Could you please check that the documentation correctly captures the requirements or not: https://github.com/rohitk-singh/mor1kx/wiki
<rohitksingh_work> sb0: i have added few commits which should work in theory, but are not tested yet https://github.com/rohitk-singh/mor1kx/commits/master
<rohitksingh_work> sb0: wishbone slave interface is most likely broken, which I'll fix. Block RAM to CPU interface should be fine.
<rohitksingh_work> sb0: If the structure of the modifications is fine, I'll go ahead and fix the wishbone interface (which currently is broken most likely) and add tests for testing the modifications
<rohitksingh_work> sb0: Currently the TCM memory is using mor1kx's own simple dual port ram module (https://github.com/rohitk-singh/mor1kx/blob/master/rtl/verilog/mor1kx_simple_dpram_sclk.v) which I'll replace with either true dual port ram module (https://github.com/rohitk-singh/mor1kx/blob/master/rtl/verilog/mor1kx_simple_dpram_sclk.v) or directly infer my own in the tcm verilog module
<rohitksingh_work> oops, the second link should have been -> https://github.com/rohitk-singh/mor1kx/blob/master/rtl/verilog/mor1kx_true_dpram_sclk.v
<rohitksingh_work> sb0: Apologies in advance if you find anything horrible (beginner). I would very much like to receive as many constructive criticisms, reviews and suggestions as possible.
ysionneau has quit [Quit: leaving]
Fallenou has joined #m-labs
Fallenou is now known as ysionneau
rohitksingh_work has quit [Read error: Connection reset by peer]
<cr1901_modern> sb0: I have an idea to refactor the code that's semantically equivalent to the current get_var_name code and will fix the bug. I'll code it this morning and you can critique it when you have the chance.
<cr1901_modern> This refactor will also make Python 3.6 support trivial
<cr1901_modern> (that will fix the bug in https://hastebin.com/kifiwuwoze.py)
mumptai_ has quit [Quit: Verlassend]
rohitksingh has joined #m-labs
sb0 has joined #m-labs
<rohitksingh> sb0: saw your comments from initial review! thanks! I'll fix those as well as other issues (like true dual port ram etc). And we are going to use same clock for Wishbone slave interface as for mor1kx core or different asynchronous clocks?
<rohitksingh> I'm just hoping the structure of the modifications is as envisaged by you
sb0 has quit [Remote host closed the connection]
sb0 has joined #m-labs
<sb0> _florent_, any update? if you're stuck on the serwb bug please make some progress on drtio
<sb0> rohitksingh, same clock
<sb0> rjo, which is the most mature dds? 9910 or 9912? I'd like to ship that one to SYSU to avoid cumulating delays
<sb0> (if possible)
<cr1901_modern> sb0: Bug is more complicated than I thought... you'd expect the following code to work (i.e. name from MySpecialCSRStatus to be inferred), correct? https://hastebin.com/uporeripam.py
<cr1901_modern> B/c this also doesn't work, and from the limited print() debugging I can do (I _hope_ pdb lets me run arbitrary python), get_obj_var_name isn't finding the correct frame
<cr1901_modern> to inspect when given code like this
<sb0> cr1901_modern, uh, no that code is quite broken
<cr1901_modern> how so?
<sb0> you're calling the constructor of MySpecialCSRStatus on MySpecialModule, which is not a derived class
<sb0> also expect __init__ to return a value, which it doesn't
<sb0> self.dummy is None.
<whitequark> sb0: we need to increase the amount of ethernet rx buffers
<sb0> whitequark, yeah go ahead
<cr1901_modern> sb0: You might not want to re-look at my previous example then
<sb0> though I'm surprised lwip seemed to work quite well
<whitequark> sb0: oh everything works fine
<whitequark> the reassembler does the job perfectly
<whitequark> it's just that I don't think we should have packets dropped at all
rohitksingh has quit [Read error: Connection reset by peer]
<cr1901_modern> (Example in the issue I opened has been modified. I can still produce the issue.)
<GitHub0> [artiq] whitequark pushed 1 new commit to master: https://github.com/m-labs/artiq/commit/701308474fa0e024deacb62a992da5b13e2bfb6a
<GitHub0> artiq/master 7013084 whitequark: runtime: update smoltcp.
<GitHub76> [artiq] sbourdeauducq pushed 1 new commit to release-3: https://github.com/m-labs/artiq/commit/231bf77b43f2aef5eb8f7830ebbf490970bb55fd
<GitHub76> artiq/release-3 231bf77 whitequark: runtime: update smoltcp.
<whitequark> sb0: that's probably not enough, I have more fixes upcoming
<whitequark> but this will have enough *diagnostics* to see why issues happen
rohitksingh has joined #m-labs
rohitksingh has quit [Read error: Connection reset by peer]
rohitksingh has joined #m-labs
rohitksingh has quit [Read error: Connection reset by peer]
<bb-m-labs> build #959 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/959
rohitksingh has joined #m-labs
rohitksingh has quit [Read error: Connection reset by peer]
<bb-m-labs> build #631 of artiq-win64-test is complete: Warnings [warnings python_coverage] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/631 blamelist: whitequark <whitequark@whitequark.org>
<bb-m-labs> build #1843 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1843
rohitksingh has joined #m-labs
rohitksingh has quit [Read error: Connection reset by peer]
<bb-m-labs> build #960 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/960
<cr1901_modern> sb0: https://github.com/m-labs/migen/pull/97 3.6 support will pretty much immediately follow from this
<bb-m-labs> build #632 of artiq-win64-test is complete: Warnings [warnings python_coverage] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/632 blamelist: whitequark <whitequark@whitequark.org>
<bb-m-labs> build #1844 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1844
<GitHub105> [smoltcp] jonaskeller opened issue #96: FPGA closes TCP connection on RPC, terminating the experiment https://github.com/m-labs/smoltcp/issues/96
<GitHub135> [smoltcp] whitequark closed issue #96: FPGA closes TCP connection on RPC, terminating the experiment https://github.com/m-labs/smoltcp/issues/96
<GitHub9> [smoltcp] whitequark commented on issue #96: Please file ARTIQ issues against the ARTIQ repository. https://github.com/m-labs/smoltcp/issues/96#issuecomment-352842901
<GitHub3> [artiq] whitequark opened issue #876: FPGA closes TCP connection on RPC, terminating the experiment https://github.com/m-labs/artiq/issues/876
<GitHub153> [smoltcp] jonaskeller commented on issue #96: Sorry - will do that next time. https://github.com/m-labs/smoltcp/issues/96#issuecomment-352844334
<GitHub54> [artiq] whitequark commented on issue #876: I believe that this bug is already fixed in the artiq-3 branch (see commit m-labs/smoltcp@42c93b99c0ff26b1bbed4e1ba882b2b20a54759f). https://github.com/m-labs/artiq/issues/876#issuecomment-352852306
<GitHub145> [artiq] whitequark closed issue #876: FPGA closes TCP connection on RPC, terminating the experiment https://github.com/m-labs/artiq/issues/876
<GitHub81> [artiq] whitequark commented on issue #876: cc @jonaskeller https://github.com/m-labs/artiq/issues/876#issuecomment-352852410
jkeller has joined #m-labs
<jkeller> bb-m-labs: force build --props=package=artiq-kc705-nist_qc2 artiq-board
<bb-m-labs> build forced [ETA 13m12s]
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #961 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/961
jkeller has quit [Quit: Page closed]
jkeller has joined #m-labs
<jkeller> bb-m-labs: force build --props=package=artiq-kc705-nist_qc2 --branch=release-3 artiq-board
<bb-m-labs> build forced [ETA 14m14s]
<bb-m-labs> I'll give a shout when the build finishes
jkeller has quit [Quit: Page closed]
<bb-m-labs> build #962 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/962
mumptai has joined #m-labs