In order to help with this, where are the data sources they are derived from?
datasheets, scripts, parts of vivado?

When Vivado opens a design, it has both the part, the device and package. Here is a small TCL example:

link_design -part xc7a35tcpg236-1
set design [get_design]
set part [get_parts [get_property PART $design]]
set package [get_property PACKAGE $part]
set device [get_property DEVICE $part]

From the device you can find all of the packages for that device:

get_parts -filter "DEVICE == xc7a35t"

You can also just get all parts that Vivado supports, but you'd want to filter by family:

get_parts -filter "FAMILY == artix7"

@litghost Where do we get the fabric from? I could not find a tcl property which relates to that.

@hansfbaier - Did you start working on this issue?

@dnltz No, after playing the tcl commands for a while I figured out that I still lack quite a bit of knowledge. I now try start smaller and add two FPGAs to enhance my understanding of how everything works

@litghost , @dnltz Yesterday I was trying to add a new part (from 2am to 6pm), and now I understand why this ticket exists. 32GB RAM do not seem to be enough for create_node_tree in 071-dump_all and it froze my system (even without swap space). I will try and do a proof of concept for 071-dump_all to use sqlite3 instead of json. Using that I could totally deduplicate (eg normalize) the data, so that everything is stored exactly once. sqlite seems to do well on large data sets: https://stackoverflow.com/questions/1033309/sqlite-for-large-data-sets

@dnltz When do you have time to work on it?

@hansfbaier - I started yesterday to set up the project. Not sure if you got further. I neither want to do the same work twice nor "steal" you the PR. Do you want to finish or should I try?

@dnltz Please go ahead. I still have a very steep learning curve ahead of me, and currently it looks like I first want to learn the ins and outs of litex and get more familiar with the details of FPGAs.
I looked a bit into what it would take to switch to a sqlite3 based data store.
I think it would be a great fit, because the data is very relational (mappings are relations),
if you think that is a good idea.

Actually it is very easy to use sqlite3 from vivado:

$ sudo apt install libsqlite3-tcl
$ ln -s /usr/lib/tcltk/sqlite3  ~/.Xilinx/Vivado/2017.2/XilinxTclStore/tclapp/sqlite3

as soon as the symlink into the local tcl store is in place, it is possible to use sqlite3 from the vivado tcl shell.
I also learned that it is possible for multiple parallel processes to write into the same sqlite3 database file,
so it looks like it would be feasible to run the fuzzers in parallel and have them write into the same database.

@litghost Where do we get the fabric from? I could not find a tcl property which relates to that.

So as a first pass you can treat device as equivalent to fabric, as that is generally true. Some exceptions exist, specifically we know that the xc7a50 and xc7a35 fabrics appear to be identical, and we alias the a50 fabric data onto the a35 devices.

One thing we could do is simply output all of the artix7 devices and then compare the outputs to verify that several devices are actually the same fabric. Does that make sense?

@dnltz Great work! I could not have done that with my current knowledge. Good that I got out of the way :)