add changes from db-workspace-for-kintex

kintex7/README.md

@@ -0,0 +1,43 @@
+# workspace for prjxray DB for kintex7
+
+A workspace for @hansfbaier's prjxray DB / kintex7.
+
+## ChangeLog
+
+
+[Dez 01]
+
+* Use latest database from the CI run of the prjxray upstream merge,
+  except changes from this issue:
+  https://github.com/f4pga/prjxray/issues/2061
+
+* add XC7K160T files from upstream prjxray db
+
+[Mar 28]
+
+* Add xc7k325tffg676-1 from the old database.
+
+* Remove a (suspicious) conflicting bit
+
+```
+prjxray.fasm_assembler.FasmInconsistentBits: FASM line "INT_R_X95Y132.IMUX34.SL1END1" wanted to set bit (4206489, 65, 21) but was cleared by FASM line "RIOB18_X95Y131.IOB_Y0.SSTL135.DRIVE.I_FIXED"
+```
+-> Drop !25_85 from RIOB18.IOB_Y0.SSTL135.DRIVE.I_FIXED.
+
+* Add the missing lines to segbits_rioi.db/segbits_rioi_tbyteterm.db from @hansfbaier's 20220326 DB.
+
+* Add a fake ppips_rioi_tbyteterm.db which is created from ppips_rioi3_tbyteterm.db.
+
+* Fill the empty "bits" of LIOI3_X0Y9 with the content of "bits" of LIOB33_X0Y9.
+
+[Mar 29]
+
+* Remove an another (suspicious) conflicting bit
+
+```
+prjxray.fasm_assembler.FasmInconsistentBits: FASM line "INT_R_X95Y101.IMUX34.SE2END1" wanted to clear bit (4206488, 2, 21) but was set by FASM line "RIOB18_X95Y101.IOB_Y1.SSTL135.DRIVE.I_FIXED"
+```
+-> Drop 24_21 from RIOB18.IOB_Y1.SSTL135.DRIVE.I_FIXED.
+
+* Add "RIOI_O0.RIOI_OLOGIC[01]_OQ always" to ppips_rioi.db/ppips_rioi_tbytesrc.db. Looks lioi3 counterparts have them.
+

kintex7/element_counts.csv

@@ -1,9 +1,9 @@
 type,count
-nodes,2663055
+nodes,6124690
 package_pins,676
-pips,29424910
-site_pins,740913
-site_pips,1505860
-sites,20251
-tiles,24453
-wires,8339126
+pips,67256102
+site_pins,1761297
+site_pips,3704892
+sites,46697
+tiles,49590
+wires,18471828

kintex7/mapping/devices.yaml

@@ -1,3 +1,11 @@
 # device to fabric mapping
 "xc7k70t":
   fabric: "xc7k70t"
+"xc7k160t":
+  fabric: "xc7k160t"
+"xc7k325t":
+  fabric: "xc7k325t"
+"xc7k420t":
+  fabric: "xc7k480t"
+"xc7k480t":
+  fabric: "xc7k480t"