01:24 <_whitenotifier> [YoWASP/yosys] whitequark pushed 1 commit to develop [+0/-0/±1] https://github.com/YoWASP/yosys/compare/6ee47a979025...db99accf94a3

01:24 <_whitenotifier> [YoWASP/yosys] whitequark db99acc - Update dependencies.

03:17 <Stevetronics> Hi all, extremely dumb question: What's the correct way to use the Connectors object associated with a platform (in my case, a TinyFPGA BX) to get a handle to a GPIO pin? I just want to spit a signal out so I can see it with my scope, but I'm struggling to find the right way to traverse the Connectors object to get what I need. I was able to hack

03:17 <Stevetronics> my way around it by creating a Resource tied to the pin I need with a Subsignal, but that doesn't feel like the right approach. I haven't been able to find where the Connector class is defined in amaranth or amaranth-boards so I'm not quite sure what the best approach is just from running dir(connector) on the object in the TinyFPGABXPlatform

03:19 <tpw_rules> each elaborate method gets a platform object, and you call request on it with the name of a connector

03:19 <tpw_rules> iirc

03:19 <tpw_rules> or the name of a resource

03:19 <tpw_rules> i don't recall off the top of my head what a Connector object is?

03:21 <tpw_rules> i think resources contain signals, which get pointed at a connector

03:21 <tpw_rules> https://github.com/amaranth-lang/amaranth/blob/4d83e131035af749b4aa604e4ea7d32a7abf9307/tests/test_build_res.py#L172

03:21 <Stevetronics> That's what I am trying to figure out - it feels like I should be able to do `platform.request("gpio", 15)` to get the 15th element in the GPIO connector, which in this case points at pad D9

03:22 <Stevetronics> Oh, that's a very helpful link - thank you!

03:23 <Stevetronics> So it seems like the correct approach is to create a resource with the pin(s) I want, and add it to the platform before I build it

03:24 <Stevetronics> Via something like `p15 = [Resource("Pin15", 0, Subsignal("p15", PinsN("D9", dir="o"), Attrs(IO_STANDARD="SB_LVCMOS33")))]`

03:25 <tpw_rules> yes i think so

03:25 <tpw_rules> or instead of pins you can use connectors which have pins

03:26 <Stevetronics> Ah, gotcha - Add the connector in the same way, then access its pins by connector.mapping['pin_number']

03:26 <Stevetronics> Thanks!

03:27 <tpw_rules> no, do you see the conn= attribute on line 175?

03:27 <tpw_rules> instead of a Pins referring to "physical" name like D9

03:27 <tpw_rules> they can refer to a pin number or name on a connector

03:27 <tpw_rules> which has physical pins

03:28 <tpw_rules> whether the extra indirection is useful, i leave up to you

03:28 <Stevetronics> Yep, I see it. Thanks - bonehead reading mistake.

03:29 <Stevetronics> Super helpful - thanks, tpw.

10:34 <vup> yeah you cannot request the pins pointed to by a Connector directly, you need to add a Resource that uses them