Role of gapy, list of peripherals and capabilities of gvsoc
Hi, thank so much for taking the time to respond.

Quote:- We have moved to "bender" for the most part instead of IPApprox recently.. that is correct. However the build scripts should execute this automatically
- The IPs will be downloaded form git recursively. You can see the list in Bender.yml
Some of these will also start loading additional repos (i.e. pulp_soc...)

Still, what is gapy? And, even better, what do the "python generators" do, where are they?

Quote:- GVSoC as you mention is a simulator so that the entire SoC can be emulated without running RTL simulations. It will accept different configurations, but there are some 'tested and known' configurations. However, there is no 'real' difference between a configuration with/without (say) SPI.. if you do not use the SPI, you do not use it.. it does not contain, area/power contributions for these additional components.

Right, makes sense - what does a software binary care if I access its part or not ("its part" being the piece of code that simulates the execution of SPI-related instructions). Still, what are the "tested and known" configurations - is there a list? 

Thanks, again!

Messages In This Thread
RE: Role of gapy, list of peripherals and capabilities of gvsoc - by nanoluka - 11-24-2022, 09:40 AM

Forum Jump:

Users browsing this thread: 1 Guest(s)