Populate all parts

[dnltz]

These changes allow to easily generate all part information during a full db run.

closes #1476

[mithro]

Looks like there is some issue with directories on Kintex / Zynq?

[dnltz]

zynq was my fault. The kintex is because of a non-existing entry in KINTEX_PARTS= (Makefile). Removed the kintex70t from there.
Pushed the changes and also added the information about the kintex and zynq family. Let me know if I should drop these two patches again.

[mithro]

@dnltz - I sent you an invite to collaborate on the SymbiFlow project and PrjXRay repo. If you access then hopefully Kokoro will run automatically on your pull requests without needing another person to force the run.

[litghost]

Review in

[litghost]

Build failure:

make[1]: Leaving directory '/tmpfs/src/github/symbiflow-prjxray-presubmit-db-artix7/fuzzers'
source settings/artix7_50t.sh && if [ -e env/bin/activate ]; then . env/bin/activate; fi; source utils/environment.python.sh; ./utils/roi_all.py
Traceback (most recent call last):
  File "./utils/roi_all.py", line 46, in <module>
    main()
  File "./utils/roi_all.py", line 32, in main
    devices = util.get_devices(args.db_root).keys()
NameError: name 'args' is not defined

[dnltz]

Yeah, we have a failure :)
I would suggest to ignore

----------------------------------------
 Database Diff
----------------------------------------
diff has 167767 lines which is too large to display!

----------------------------------------
 Generating pretty diff output
----------------------------------------
diff has 167767 lines which is too large for HTML output!
----------------------------------------
+ make db-check-artix7

because this PR has a lot of changes and normal PRs should not have such a mount of changed lines.

Will take a look into the Artix und Zynq issues now.

[litghost]

So the artix7 failure arose from:

diff --git a/artix7/segbits_bram_l.origin_info.db b/artix7/segbits_bram_l.origin_info.db
index a1c00af..a959ca5 100644
--- a/artix7/segbits_bram_l.origin_info.db
+++ b/artix7/segbits_bram_l.origin_info.db
@@ -208,7 +208,7 @@ BRAM_L.ZALMOST_FULL_OFFSET[9] origin:028-fifo-config 27_13
 BRAM_L.ZALMOST_FULL_OFFSET[10] origin:028-fifo-config 27_12
 BRAM_L.ZALMOST_FULL_OFFSET[11] origin:028-fifo-config 27_11
 BRAM_L.ZALMOST_FULL_OFFSET[12] origin:028-fifo-config 27_08
-BRAM_L.RAMB18_Y0.DOA_REG origin:025-bram-config 27_69
+BRAM_L.RAMB18_Y0.DOA_REG origin:025-bram-config 00_278 27_69
 BRAM_L.RAMB18_Y0.DOB_REG origin:025-bram-config 27_72
 BRAM_L.RAMB18_Y0.FIFO_MODE origin:029-bram-fifo-config 27_150
 BRAM_L.RAMB18_Y0.IN_USE origin:029-bram-fifo-config 27_100 27_99

Nothing you did should've caused that change, but it might just be bad luck. Something to try is change https://github.com/SymbiFlow/prjxray/blob/c202abb8a1a89837c9246163f3288a2c1505aedb/fuzzers/025-bram-config/Makefile#L10 N ?= 15 to N ?= 20. That will increase the sample count, and hopefully decouple the bad bit.

[dnltz]

@litghost - Increasing N to 20 did not help. Should I just open an issue?

[litghost]

@litghost - Increasing N to 20 did not help. Should I just open an issue?

Ya, sure.

[litghost]

@litghost - Increasing N to 20 did not help. Should I just open an issue?

Another option to just add a bit blacklist for this bit.

[litghost]

See https://github.com/SymbiFlow/prjxray/blob/a0dbca4da800d4748dcd3833dbd34b467d866b90/fuzzers/025-bram-config/generate.py#L169-L171

[litghost]

So the bad solution is:

-BRAM_L.RAMB18_Y0.DOA_REG 27_69
+BRAM_L.RAMB18_Y0.DOA_REG 00_278 27_69

A quick search on https://github.com/SymbiFlow/prjxray-db/blob/master/artix7/segbits_bram_l.db shows that no bits are in frame 0, so we probably could just add a frame 0 exclusion, e.g.:

 def bitfilter(frame, bit): 
     # rw_width_tags() aliasing interconnect on large widths 
     return frame not in (0, 20, 21) 

GitHub

SymbiFlow/prjxray-db

Project X-Ray Database: XC7 Series. Contribute to SymbiFlow/prjxray-db development by creating an account on GitHub.

[dnltz]

Ah thanks for that hint :)
I added your suggestion. Let's see what happens...

[dnltz]

@litghost - Checks were successful today.

[litghost]

@litghost - Checks were successful today.

Great work. New prjxray-db should be updated tommorow or early next week.