<_whitenotifier-a>
[nmigen] hansfbaier commented on issue #620: Feature request: Integrate logic analyzer into the language Signal(trace=True) - https://git.io/JRkFx
emeb_mac has quit [Quit: Leaving.]
<lkcl>
vup: thx, that looks great - dead simple, too.
<lkcl>
sorry, took a while to reply
<lkcl>
we need a (basic, brain-dead, combinatorial-only) nmigen-to-c translator
<lkcl>
vup: that's superb, works really well.
<lkcl>
pysim actually compiles to python code, first? moo? cool!
<lkcl>
i want one! :)
<Degi>
How can I put strings etc. into a VCD file to show in GTKWave? (for example LTSSM state or 8b10b data)
<vup>
Degi: you can pass either a function that takes an integer and returns a string or a python Enum to the `decoder` argument of the `Signal` constructor
<Degi>
Uhh neat
<Degi>
Can the function know the width of the signal somehow?
<vup>
no
<vup>
but if you have a usecase for that, that seems like reasonable feature request you could file an issue about
<Degi>
Hm, in my case the width variable is declared a bit above and I can just use it, in this case I have a variable width decoded 8b10b stream, which is a Signal(9 * ratio) and then the decoder automatically adjusts depending on ratio
<Degi>
Can I assign the decoder variable after creating a signal or does it need to be in the constructor?
<vup>
yeah, I mean I can see a few uses cases for it, mostly for formatting numbers as binary or hex literals, where it would be nice to have a consistent length, or maybe for decoding a fixed / floating point format automatically depending on the width
<vup>
Degi: it will probably work if you assign it after creating the `Signal`, but then only for functions, not `Enum`s, those are treated specially in the constructor
<Degi>
Hm yes for functions
bvernoux has joined #nmigen
emeb has joined #nmigen
nak has quit [Read error: Connection reset by peer]