<TJ[m]>
Hi, I'm trying to write a super simple wiring.Component and a platform wrapper so I can actually assign it an LED (trying to understand the process before doing this for other modules). How can I connect a signature member (i.e. a wiring.Component In/Out member) to the pin of a platform request? It seems like a m.d.sync/m.d.comb assignment isn't correct and wiring.connect doesn't like that my wrapper is missing a signature. I'm not
<TJ[m]>
sure how to provide a dummy one if that is the solution. Here's what I'm working with https://github.com/TJ9867/NandBug-Software/blob/master/bitstreams/modules/blinker.py#L40-L41. The big idea is I would apply this to other modules in this project so I can write testbenches and debug. Kind of new to all of this so if I'm doing something dumb or there's an easier way I'd definitely like to know. Thank you for the awesome project.
Raito_Bezarius has quit [Ping timeout: 272 seconds]
Raito_Bezarius has joined #amaranth-lang
greghashtag9468[ has joined #amaranth-lang
<greghashtag9468[>
The ordering is important. In this statement you are assigining a value created by your module to your blink_led output.
<greghashtag9468[>
This should work: `m.d.comb += blink_led.o.eq(blinker.led_sig)`
<greghashtag9468[>
I might be wrong, but using wiring.connect to connect to top level i/o ports would require wrapping the port with a signature to define In/Out?
<whitequark[cis]>
platform.request returns an interface object
Psentee has quit [Quit: Off]
Psentee has joined #amaranth-lang
jorolf[m] has joined #amaranth-lang
<jorolf[m]>
I think the link on https://amaranth-lang.org for the latest release needs to be updated? It still points to 5.3
<jorolf[m]>
* points to 0.5.3
<whitequark[cis]>
ah yeah
<whitequark[cis]>
the docs are the same anyway, aside from changelog