01:50 <jevinskie[m]> Cool, I got Display() to work in FSMs

05:05 <jevinskie[m]> DisplayEnter() only displays once when the state is entered, next up is emulating $monitor. Should be cake thanks to python :P

05:53 <_florent_> jevinskie[m]: nice!

10:13 <rah> _florent_: my understanding of FuseSoC is that its focus on resuse of existing cores is in order to facilitate the creation of your own SoC, which is to say that the purposes of FuseSoC and LiteX seem to be the same, not different

10:13 <rah> the clue's in the name

10:16 <rah> "Its main purpose is to increase reuse of IP (Intellectual Property) cores and be an aid for creating, building and simulating SoC solutions." -- https://fusesoc.readthedocs.io/en/stable/user/introduction.html

10:16 <tpb> Title: Why FuseSoC? — FuseSoC 1.12.0 documentation (at fusesoc.readthedocs.io)

19:24 <_franck_> rah: FuseSoC doesn't handle the interconnection by itself. You can configure which cores you need in your design and which tool you want to use for synthesis/simulation, FuseSoC will fetch all the cores and dependancies and build your design.

19:24 <_franck_> I see it like a super build tool

19:25 <_franck_> (well, I didn't use it for years so I may be wrong...)

23:16 <jevinskie[m]> Here is that emulation of $monitor: https://gist.github.com/jevinskie/fc4fc7b36d9eade490816576b235fe6e