Conversation
|
I think we will have to get a v0.2 board to Joel to make this a real thing. Possibly have both v0.1 or v0.2 board definitions. Given v0.1 boards are so few, the main definition can be the v0.2 one. |
|
Agreed, once we have some v0.2 boards we can decide how to support them. I wanted to submit this definition so we didn't have people duplicating the work of describing the pin layouts. |
An iCE40UP5K FPGA in a Feather compatible form factor. https://github.com/joshajohnson/iCE40-feather
|
|
||
| *LEDResources(pins="47", invert=True, attrs=Attrs(IO_STANDARD="SB_LVCMOS")), | ||
| # Semantic aliases | ||
| Resource("led_r", 0, PinsN("47", dir="o"), Attrs(IO_STANDARD="SB_LVCMOS")), |
There was a problem hiding this comment.
What's going on with the LEDs here? If there's one RGB LED then there should be just an RGB LED resource.
| Resource("button_sw1", 0, Pins("9", dir="i", conn=("wing", 0)), Attrs(IO_TYPE="LVCMOS33")), | ||
| Resource("button_sw2", 0, Pins("10", dir="i", conn=("wing", 0)), Attrs(IO_TYPE="LVCMOS33")), | ||
| Resource("button_sw3", 0, Pins("12", dir="i", conn=("wing", 0)), Attrs(IO_TYPE="LVCMOS33")), | ||
| Resource("button_sw4", 0, Pins("11", dir="i", conn=("wing", 0)), Attrs(IO_TYPE="LVCMOS33")), |
There was a problem hiding this comment.
"Semantic alias" generally means that there is some semantics beyond the numeric index, e.g. button_up would be one.
| ] | ||
| led_wing = [ | ||
| # Buttons present on the "led wing" attachment | ||
| *ButtonResources(pins={0: "9", 1: "10", 2: "12", 3: "11"}, invert=True, attrs=Attrs(IO_STANDARD="SB_LVCMOS")), |
There was a problem hiding this comment.
This is resource is missing the connector specification.
|
Thanks for the review @whitequark. I have learnt a bit more about nmigen and fixed a bunch of things; I'll rework the patch and try again. |

An iCE40UP5K FPGA in a Feather compatible form factor.
https://github.com/joshajohnson/iCE40-feather