Architecture file hierarchy

[bgeorge]

Hello,

I would like to deploy the pulp-platform in an Artix fpga but I don't know what files to include in the design and simulation, as well.
Are there any tree file which explains how the files are connected on RTL and Simulation level so that know which is the top level ?

[meggiman]

Hi @bgeorge,

Which project do you want to deploy on the Artix? Pulpissimo? In any case, you can and should use Bender to generate the required file list for the FPGA deployment. Bender has a dedicated vivado target to generate the tcl file for the project and e.g. the pulpissimo fpga port makes use of this feature. If it is about understanding the code structure I could share some auto-generated file dependency graphs if you tell me the project of interest.
Best,
Manuel

[bgeorge]

Hi @bgeorge,

Which project do you want to deploy on the Artix? Pulpissimo? In any case, you can and should use Bender to generate the required file list for the FPGA deployment. Bender has a dedicated vivado target to generate the tcl file for the project and e.g. the pulpissimo fpga port makes use of this feature. If it is about understanding the code structure I could share some auto-generated file dependency graphs if you tell me the project of interest.
Best,
Manuel

Hi Manuel,

Thank you very much for your fast reply, I want to deploy the PULP SoC with the 8-cores Cluster.
I tried to deploy it using the make file but the new vivado doesn't support the zcu102.
I would be grateful if you could share the graphs.

Best Regards,
George

[meggiman]

I suggest you go through the Bender documentation in the README of this repository (https://github.com/pulp-platform/bender) to learn about how to use bender to assemble the f-lists. The makefiles internally just call Bender with certain flags. Regarding the file hierarchy, here are the three auto-generated files.

• file_dependencies.pdf shows a directed graph containing each RTL source files as a node with edges between the nodes file a requires file b (due to module instantiation, include, pkg usage etc.)
  
• hierarchy.pdf shows the Module instantiation hierarchy as tree graph. Each node (module instance) contains the instance name, module name and evaluated parameter values.
  
• hierarchy.json contains the machine readable module instantiation hierarchy in JSON format including the full relative path of the RTL files corresponding to the modules.
  

https://iis-nextcloud.ee.ethz.ch/s/Eow8Je7jFJxoxJa

Best,
Manuel

[bgeorge]

I suggest you go through the Bender documentation in the README of this repository (https://github.com/pulp-platform/bender) to learn about how to use bender to assemble the f-lists. The makefiles internally just call Bender with certain flags. Regarding the file hierarchy, here are the three auto-generated files.

• file_dependencies.pdf shows a directed graph containing each RTL source files as a node with edges between the nodes file a requires file b (due to module instantiation, include, pkg usage etc.)
  
• hierarchy.pdf shows the Module instantiation hierarchy as tree graph. Each node (module instance) contains the instance name, module name and evaluated parameter values.
  
• hierarchy.json contains the machine readable module instantiation hierarchy in JSON format including the full relative path of the RTL files corresponding to the modules.
  

https://iis-nextcloud.ee.ethz.ch/s/Eow8Je7jFJxoxJa

Best,
Manuel

Thank you very much Manuel for your assistance.