05:26 <sf-slack> <kgugala> @risto.pejasinovic can you write a name of such pin (and corresponding IOPAD?)

11:52 <sf-slack> <risto.pejasinovic> @kgugala Looks like I was wrong. Probably something to do with optimizations in Vivado first time. I disabled it now. EMIO indeed goes into fabric directly. Here are paths: GPIO_O: https://imgur.com/v0PlhU7 GPIO_I: https://imgur.com/ijzvnNh AXI: https://imgur.com/7aevbSr

11:52 <tpb> Title: Imgur: The magic of the Internet (at imgur.com)

12:02 <sf-slack> <risto.pejasinovic> What is the goal of fuzzer to find for every pin in this situation? Address of first Tile it encounters on path in fabric? In this case I get Tile: INT_L_X0Y73

12:14 <sf-slack> <acomodi> @risto.pejasinovic I would say that one of the fuzzer's goal is to find the pip <--> PS7_pin correlation on all the INT_L_X0YY tiles

13:32 <duck2> mithro: sorry, wasn't here. i read the python script, but didn't understand how to populate the pip edges. i guess i should go through prjxray_routing_import first.