Lofty changed the topic of #prjmistral to: Project Mistral: Yosys (and hopefully nextpnr) on Cyclone FPGAs - https://github.com/ZirconiumX/mistral - logs: https://freenode.irclog.whitequark.org/prjmistral
lethalbit has quit [*.net *.split]
lethalbit has joined #prjmistral
<gatecat> OK, I have a basic routing graph in nextpnr now - https://github.com/gatecat/nextpnr/tree/cyclonev and https://github.com/gatecat/mistral/tree/nextpnr
<gatecat> probably it for today, tomorrow I am going to look at the bel stuff (which is currently in an inbetween state), but a review of the current wire and pip stuff as well as the mistral changes would be appreciated
<gatecat> Sarayan:/Lofty: (sorry, forgot to poke you about earlier update) - one more question about routing; some IO seem to route through the memory controller (I see things like `HMC.025.000:IOINTDQDIN.65 GPIO.089.004.2:DATAIN.0` in the route output sometimes on Quartus bitstreams). Is there any data in mistral that maps a pin to IOINTDQDIN.65 (I guess this is HMC DQ65), for example?
<gatecat> the pin in question seems to be AH16, of the 5CSEBA6U23I7 device
<Sarayan> not yet, and I don't have the data yet either
<Sarayan> I have some idea of how I could get to it, but I'm not entirely sure
<gatecat> I guess a bruteforce script could just try every pin and see what happens
<Sarayan> Sure, but that's a lot of them. Probably way easier to extract them from the quartus routing table :-)
<gatecat> mmm
<Sarayan> more reliable too
<gatecat> it'd definitely be useful to have this kind of "routing but not bitstream-related" info in mistral in a consistent way (similar to the clock mux sources)
<Sarayan> yes
<Sarayan> I most definitely want to put it in
<Sarayan> HMCPHY_RE_IOINTDQDIN.25.00.00.0065 - VIOB.61.00.00.0010
<Sarayan> HMCPHY_RE_DDIOPHYDQDIN.25.00.00.0065 - HMCPHY_RE_IOINTDQDIN.25.00.00.0065 MEM_PHY_INPUT_DDIOPHYDQDIN.25.00.01.0065
<Sarayan> IO_RE_CDATA1IN.64.00.51.0000 - HMCPHY_RE_DDIOPHYDQDIN.25.00.00.0065
<Sarayan> yep, the link is in there
<gatecat> great!
<Sarayan> I'll have to extract them, probably make it a pnode-pnode link
<gatecat> sure, that makes sense
<Sarayan> yeah, think so too
mithro has quit [Ping timeout: 245 seconds]
mithro has joined #prjmistral
mithro has quit [Excess Flood]
mithro has joined #prjmistral
emilazy has quit [Ping timeout: 250 seconds]
emilazy has joined #prjmistral