Closed cr1901 closed 5 years ago
That's already handled by doing something like:
vga = [
("vga_out", 0,
Subsignal("hsync", PinsN("led_0:3", dir="o")),
Subsignal("vsync", PinsN("led_0:4", dir="o")),
Subsignal("r", Pins("dio_0:1 dio_0:2 dio_0:3", dir="o")),
Subsignal("g", Pins("dio_0:4 dio_0:5 dio_0:6", dir="o")),
Subsignal("b", Pins("dio_0:7 clkio_0:1", dir="o")),
Attrs(IOSTANDARD="LVCMOS33", SLEW="FAST")
)
]
Occasionally, it is possible a user will want to add their custom
Resource
to their boardsConnector
s that matches the following conditions:Subsignal
of their shiny newResource
has multiplePins
that should be associated with it.Pins
of thisSubsignal
will be spread out across multipleConnector
s.omigen
already handles this case by hardcoding the connector to use into thePins
string, as per this example on theb
Subsignal
.What should the equivalent
nmigen
behavior be?My Proposal