Sign in

username:

password:



Not a member?

Search Comp.Arch.FPGA



Search tips

fpga by Keywords

Altera | ASIC | CPLD | Cyclone | DCM | DDR | DSP | Ethernet | ISE | JTAG | Linux | LVDS | Microblaze | ML310 | Modelsim | NIOS | OPB | PCI | Quartus | RocketIO | SDRAM | Spartan | Spartan3 | SRAM | Stratix | Verilog | VHDL | Virtex | Virtex-4 | Virtex-II | Xilinx | XST


Ads

See Also

DSPEmbedded SystemsElectronics

Comp.Arch.FPGA | Multiple builds with different top-level generic

There are 3 messages in this thread.

You are currently looking at messages 0 to 3.

Multiple builds with different top-level generic - Neill Arnell - 2010-08-10 05:17:00

Hi,

I'm working on a Xilinx FPGA design (VHDL) that uses a top level 
generic, and need to build multiple versions of the FPGA where the 
generic is the only thing that changes.  The generic is used to select 
different modules to be used in the FPGA, the modules can't all fit in 
the FPGA together.

Currently there are 4 different settings for the generic, and for a 
release I need to build the FPGA with each of the different generic options.

What I am looking for is advice on how to set up a script/makefile to 
generate the builds in parallel, whilst ensuring that the results are 
all kept separate.  I'm using a Windows machine with a quad core processor.

Thanks in advance

Neill.



Re: Multiple builds with different top-level generic - Benjamin Krill - 2010-08-10 06:51:00

Hi Neill,

as you wrote, you need a script or Makefile which "generates" an xst
script file where options + generics are specified (-generics {a=3DBLA}).
Further the build script must call the needed build steps: xst,
ngdbuild, map, par, trce and bitgen. To do this for multiple builds,
just call your script with different parameters or so. Since you are
using windows, I would recommend the cygwin environment.=20

cheers
ben

On Tue, 2010-08-10 at 10:17 +0100, Neill Arnell wrote:=20
> Hi,
>=20
> I'm working on a Xilinx FPGA design (VHDL) that uses a top level=20
> generic, and need to build multiple versions of the FPGA where the=20
> generic is the only thing that changes.  The generic is used to select=
=20
> different modules to be used in the FPGA, the modules can't all fit in=
=20
> the FPGA together.
>=20
> Currently there are 4 different settings for the generic, and for a=20
> release I need to build the FPGA with each of the different generic optio=
ns.
>=20
> What I am looking for is advice on how to set up a script/makefile to=20
> generate the builds in parallel, whilst ensuring that the results are=20
> all kept separate.  I'm using a Windows machine with a quad core processo=
r.
>=20
> Thanks in advance
>=20
> Neill.


______________________________
Join the blogging team on FPGARelated.com and earn rewards! Details Here.

Re: Multiple builds with different top-level generic - KJ - 2010-08-10 09:01:00

On Aug 10, 5:17=A0am, Neill Arnell
<nei...@pipstechnology.co.uk> wrote:
> Hi,
>
> I'm working on a Xilinx FPGA design (VHDL) that uses a top level
> generic, and need to build multiple versions of the FPGA where the
> generic is the only thing that changes. =A0The generic is used to select
> different modules to be used in the FPGA, the modules can't all fit in
> the FPGA together.
>
> Currently there are 4 different settings for the generic, and for a
> release I need to build the FPGA with each of the different generic optio=
ns.
>
> What I am looking for is advice on how to set up a script/makefile to
> generate the builds in parallel, whilst ensuring that the results are
> all kept separate. =A0I'm using a Windows machine with a quad core proces=
sor.
>
> Thanks in advance
>
> Neill.

What I do is have a top level with no generics that defines values for
all of the constants that will be generics and then instantiate the
'more general' one that has the generics.  These can all be in the
same file if you want.  At the end of the day, you need to segregate
these builds for purposes of synthesis, archiving, analysis and
release.  You can spend your time futzing with build scripts and then
trying to keep it straight which build is which or spend it creating
code that avoids any build script fanciness...your choice.

KJ
______________________________
Join the blogging team on FPGARelated.com and earn rewards! Details Here.