07:06 <d1b2> <dusk> (tangent) fascinating, I think it's a FX2LP clone http://corebai.com/en/usb-kongzhiqi/CBM9002A-56SCG.html

07:07 <d1b2> <OmniTechnoMancer> I think the \ is for escaping the [] on the end, but not sure

08:34 <d1b2> <josuah_dem> That is probably the worst line of logic analyzer I can think of (after GPIO), but still infinitely better than nothing at all. 🙂

15:19 <d1b2> <VA3TEC-Mikek-14362> OK I figured out more, For one thing the add Resource list for the DE10-nano (and Deca) Have both. The resource string that I am adding you have to start the count @ 2, not 0, amaranth just does not like it.. GPIO_pins = [ Resource("gpio", 0, #Subsignal("leds", Pins("V12 E8 W12 D11 D8 AH13 AF7 AH14", dir="o", conn=("gpio",0))), #Subsignal("gpio0", Pins("2", dir="o", conn=("gpio",1))),

15:19 <d1b2> Subsignal("gpio8", Pins("2 3 4 5 6 7 8 9", dir="o", conn=("gpio",1))), #Attrs(IO_TYPE="LVCMOS33"))#, DRIVE="4")) Attrs(io_standard="3.3 V"))#, DRIVE="4")) ]

15:21 <d1b2> <VA3TEC-Mikek-14362> This is the error message I get. File "/home/mikek/Documents/Cyclone5_SOC/DECA_Board/amaranth/amaranth/amaranth/build/dsl.py", line 46, in map_names raise NameError("Resource {!r} refers to nonexistent connector pin {}" NameError: Resource (subsignal gpio8 (pins o gpio_1:0 gpio_1:1 gpio_1:2 gpio_1:3 gpio_1:4 gpio_1:5 gpio_1:6 gpio_1:7 gpio_1:8 gpio_1:9)) refers to nonexistent connector pin gpio_1:0

15:22 <d1b2> <VA3TEC-Mikek-14362> Again, If I start with 0 for the resource. Subsignal("gpio8", Pins("0 1 2 3 4 5 6 7 8 9", dir="o", conn=("gpio",1))),

17:58 <d1b2> <OmniTechnoMancer> Which platform are you using again?

18:06 <d1b2> <OmniTechnoMancer> Oh, yea the pin numbers start at 1 not 0 for Connectors

19:00 <d1b2> <VA3TEC-Mikek-14362> Terasic Deca Board, Or the Terasic DE10_nano.

19:01 <d1b2> <VA3TEC-Mikek-14362> https://www.terasic.com.tw/cgi-bin/page/archive.pl?Language=English&CategoryNo=&No=944&PartNo=2

19:02 <d1b2> <VA3TEC-Mikek-14362> https://www.terasic.com.tw/cgi-bin/page/archive.pl?Language=English&CategoryNo=167&No=1046

20:16 <d1b2> <Nate> probably something related to the platform file I wrote for the crosslink-nx eval board (see PR https://github.com/amaranth-lang/amaranth/pull/759), but it seems nextpnr-nexus isn't picking up my clock constraint (seems amaranth has it right, as an explicit call to add_clock_constraint() complains about it already existing). Nothing in the pdc file

20:33 <d1b2> <VA3TEC-Mikek-14362> OK, I got it ALL to WORK!!! Wow Amaranth is not that completed for Quartus,

20:38 <d1b2> <VA3TEC-Mikek-14362> Yes!!!! FINALLY!!! got it to work!! 😁👍

20:38 <d1b2> <VA3TEC-Mikek-14362> https://cdn.discordapp.com/attachments/726185180599156796/1101970858584576000/20230429_163730.mp4