1. Home
  2. Field-Programmable Gate Arrays
  3. Re: Quartus and source control (continued)

Re: Quartus and source control (continued)

I'm starting a new thread on this since Google locked me out from replying.

Regarding conflicts using CVS, use SVN and tag certain files as requiring checkout. (I forget the procedure but it uses the property name you attach. You need to run a script on a regular basis that does this because it's done on a pre file basis.

Regarding which source control system. Any one should work (but I hate CVS). SVN is pretty nice.

Regarding which files should be archived (as source). I would not sweat it too much (e.g. files that get copied from library etc.) It's not the end of the world if they get versioned.

Ragarding binary: Just check them in as binary. SVN handles binary much better than svn and the database is amazingly small.

I'm still working myself on what makes sense for users. I have the CAD folks that use solid works working very nicely on SVN. If also saved their butts in short order.

I'm trying to understand where FPGA pin mappings are stored as the users claim they are in the db directory and other folks on the previous thread said never to version the db directory.

Reply to
mswlogo
Loading thread data ...

I put pin mappings in the RTL source file. You can assign I/O type there as well.

I like to keep all technology/implimentation dependant stuff in one spot. The very top level usually works well.

Reply to
ghelbig

The pin mappings are stored in the *.qsf file. Each revision for the project has its own qsf file. You should not be storing anything from the db directory in the source code control system.

H> I'm starting a new thread on this since Google locked me out from

Reply to
Subroto Datta

The *nice* thing about Quartus is that you only need to store *2* text files for the project, aside from your source - namely the .QPF and .QSF files.

Everything else is generated output from Quartus!

Works really well with SVN.

Nice Regards,

--
Mark McDougall, Engineer
Virtual Logic Pty Ltd, 
21-25 King St, Rockdale, 2216
Ph: +612-9599-3255 Fax: +612-9599-3266
Reply to
Mark McDougall

If you have more than one device in the JTAG chain also store the .cdf. And for the SOPC builder all information is in the .ptf. So you end up with a maximum of 4 files and they are all plain text. Very convenient.

Martin

Reply to
Martin Schoeberl

I only store ONE file for Quartus, a tcl script to compile the design. It includes all the pin assignments, global assignments to generate SVF files etc.

A typical build from a fresh checkout will look like:

cvs co designname cd designname/impl/ep1c6t144c8 quartus_sh -t compile.tcl

Petter

--
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?
Reply to
Petter Gustad

Ah yes, indeed! However, we'll strategically overlook mentioning NIOS IDE projects and the !@#*@&^#%$% workspace... ;)

Regards,

--
Mark McDougall, Engineer
Virtual Logic Pty Ltd, 
21-25 King St, Rockdale, 2216
Ph: +612-9599-3255 Fax: +612-9599-3266
Reply to
Mark McDougall

Now there's someone who doesn't like documenting build instructions! ;)

Regards,

--
Mark McDougall, Engineer
Virtual Logic Pty Ltd, 
21-25 King St, Rockdale, 2216
Ph: +612-9599-3255 Fax: +612-9599-3266
Reply to
Mark McDougall

Although the Nios IDE is Eclipse under its makeup, and Eclipse supports Subversion very well via the Subclipse plugin:

formatting link
- has anyone tried installing this?

Reply to
toby

As for NIOS I've made a makefile to build everything from the ptf file. In the NIOS case compile.tcl, mysystem.ptf and makefile are the only files checked in besides hdl and c source files.

The makefile is probably not portable across different versions of the sopc builder. There are lots of variables which have to be set (SOPC_PERL, sopc_kit_nios, etc.)

Petter

--
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?
Reply to
Petter Gustad

Mark McDougall kirjoitti:

I save these project files into repository.

.cdtbuild .cdtproject .project application.stf

My problem is related to Linked Resources, since I use variables to define location of some common files. And value of Linked Resources is hidden in user !@#*@&^#%$% workspace.

Antti

Reply to
antti.tyrvainen

If only Xilinx made life that simple :(

I'm not what you'd call a fan of the .ise file.. Project Navigator regularly corrupts it (usually after it's destroyed the backup copy), and the tools that interface to it are.. weak. pjcli can't even recreate a full project because it doesn't understand how to add a constraint file to it!

And let's not get into the tool's obsession with absolute pathnames which make having 'beta' versions of your design very frustrating :(

(but on the plus side I have a makefile which replicates the build functionality I need.. still working on generating simulation)

--
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
Reply to
Daniel O'Connor

ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.