Forum Discussion

Altera_Forum's avatar
Altera_Forum
Icon for Honored Contributor rankHonored Contributor
20 years ago

Version Control of Quartus Project...

I have looked over altera's suggestions for archiving projects (http://www.altera.com/literature/hb/qts/qts_qii54017.pdf), but they appear to have left out some important cases, namely, components created with the MegaWizard, and SOPC custom components.

It turns out, for the MegaWizard components, all you need to do is save the .vhd file it created.

SOPC custom components are not that easy. In my project directory, SOPC Builder seems to have created a folder for each custom component. In those folders, there are two files, and an 'hdl' folder (which is empty in my case). The two files are named the same in each folder: "cb_generator.pl" and "class.ptf."

Without the folder, SOPC complains that the component is not instantiated.

So, is there any easy way to keep these files in version control just using rcs (http://www.gnu.org/software/rcs/rcs.html)? Having the same name (class.ptf) and being in their own folder makes the solution unclear. How are other people keeping their SOPC system in version control?

Thanks,

Brian

PS: Other than this problem, I think I have a pretty good handle on keeping the whole project in version control using RCS--except for our encrypted 3rd party IP--which isn't too much of a problem since it never changes.

3 Replies

  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor

    I do not know the specifics of RCS, I use subversion, which does not have problems with adding or removing directories.

    There are two options:

    - Archive "cb_generator.pl" and "class.ptf" files and if you have any HDL than the "hdl" directory too inside the "component_name" directory inside your projects dir. This way the project is self contained.

    - You may create a separate project for SOPC components, where there are only component directories with those .pl and .ptf files. Than add this project dir to the SOPC builder list of directories containing components. This way all your SOPC components will be stored at a single place, but you may have problems archiving projects.

    Inside SOPC -> File -> SOPC Builder Setup ... -> Component/Kit Library Search Path

    Put the absolute path to the dir with your components into the box.

    IzI
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor

    Thanks for the advice Izi. It works like a charm now!

    --- Quote Start ---

    originally posted by iztok.jeras@Nov 8 2006, 04:21 AM

    - you may create a separate project for sopc components, where there are only component directories with those .pl and .ptf files. than add this project dir to the sopc builder list of directories containing components. this way all your sopc components will be stored at a single place, but you may have problems archiving projects.

    inside sopc -> file -> sopc builder setup ... -> component/kit library search path

    put the absolute path to the dir with your components into the box.

    <div align='right'><{post_snapback}> (index.php?act=findpost&pid=19286)

    --- quote end ---

    --- Quote End ---

  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor

    Be aware of files created by the wizzard if you have f.e. FIR components. that are part of a sopc component (somewhere deep down the instatiation tree...)

    We curently gave up to store the FIR files inside an SOPC componente folder due to the reason that quartus will not find some *.hex files that must be located at the same folder where the *.qpf and *.ptf files are.

    Especially these FIR wizzard created components cannot be located where you normaly place you sopc components for all project (search path) as the wizzard does some modification of some project files during generation and a different quartus project will not get these new informations.

    Even a simply copy of such a sopc folder including all files (100% all files!) to a new qartus project will not work until you run the wizzard there again. and ... remember the *.hex files for FIR. Quartus will not find them if they are not located as i mentioned above. even including them to the files dialog of your project will not help. we have verified that serveral times and the only realy working solution is to make FIR designs flat inside the same folder as qpf and ptf. otherwise sometimes some files are not included and you start searching why your fir is not working anymore.... and to find these green warnings under serval thausand sopc warnings ... nice job :-)

    so the only solution for storing such complex projects is a zip file for us.

    no cvs (subversion, vss, ... ) realy helped here.

    Regards

    Michael