getting back Xilinx ISE commands

  • Thread starter Amontec Team, Laurent Gau
  • Start date
A

Amontec Team, Laurent Gau

Guest
Hi all,

I am using Webpack ISE to do PAR for Coolrunner.

How to get back all command line from VHDL and UCF parser to JEDEC
generation (parser, synthesis and par works)

The goal is to do a generic project (using webpack IDE interface) and to
get back all ISE command line, and to re-run the ISE command line for an
other VHDL file with minor changes. All the work would be via script for
generating about 50 news configs of our Chameleon POD.

Are there any command log files?

Thanks for all advices,
Regards,
Laurent Gauch

------------ And now a word from our sponsor ---------------------
For a secure high performance FTP using SSL/TLS encryption
upgrade to SurgeFTP
---- See http://netwinsite.com/sponsor/sponsor_surgeftp.htm ----
 
Amontec Team, Laurent Gauch wrote:
Hi all,
I am using Webpack ISE to do PAR for Coolrunner.
How to get back all command line from VHDL and UCF parser to JEDEC
generation (parser, synthesis and par works)
The goal is to do a generic project (using webpack IDE interface) and to
get back all ISE command line, and to re-run the ISE command line for an
other VHDL file with minor changes. All the work would be via script for
generating about 50 news configs of our Chameleon POD.
Have a look at the chapter about "xflow" in the ISE Documentation.
Click to expand...
That's the command-line-tool to do the complete flow from synthesis to
bitfile generation (I assume you can generate JEDEC-files as well). The
options for each of the steps are set in *.opt-files, that reside in
$XILINX/epld/data. You can copy those and modify the local copies, and
run "xflow" with these instead of the globally available ones.

"xflow" is really not that complicated, and is great for using inside
scripts, so that should be what you need.

--
Sean Durkin
Fraunhofer Institute for Integrated Circuits (IIS)
Am Wolfsmantel 33, 91058 Erlangen, Germany
http://www.iis.fraunhofer.de

mailto:23@iis.42.de
([23 , 42] <=> [durkinsn , fraunhofer])
 
Sean Durkin wrote:
Amontec Team, Laurent Gauch wrote:

Hi all,
I am using Webpack ISE to do PAR for Coolrunner.
How to get back all command line from VHDL and UCF parser to JEDEC
generation (parser, synthesis and par works)
The goal is to do a generic project (using webpack IDE interface) and
to get back all ISE command line, and to re-run the ISE command line
for an other VHDL file with minor changes. All the work would be via
script for generating about 50 news configs of our Chameleon POD.

Have a look at the chapter about "xflow" in the ISE Documentation.
That's the command-line-tool to do the complete flow from synthesis to
bitfile generation (I assume you can generate JEDEC-files as well). The
options for each of the steps are set in *.opt-files, that reside in
$XILINX/epld/data. You can copy those and modify the local copies, and
run "xflow" with these instead of the globally available ones.

"xflow" is really not that complicated, and is great for using inside
scripts, so that should be what you need.

Sean,
Click to expand...

I will try the xflow way.
many thanks
Laurent
 
Hi,

I need to know where I have to include my .ucf file in XFLOW!

Laurent

Sean Durkin wrote:

Amontec Team, Laurent Gauch wrote:

Hi all,
I am using Webpack ISE to do PAR for Coolrunner.
How to get back all command line from VHDL and UCF parser to JEDEC
generation (parser, synthesis and par works)
The goal is to do a generic project (using webpack IDE interface) and
to get back all ISE command line, and to re-run the ISE command line
for an other VHDL file with minor changes. All the work would be via
script for generating about 50 news configs of our Chameleon POD.

Have a look at the chapter about "xflow" in the ISE Documentation.
That's the command-line-tool to do the complete flow from synthesis to
bitfile generation (I assume you can generate JEDEC-files as well). The
options for each of the steps are set in *.opt-files, that reside in
$XILINX/epld/data. You can copy those and modify the local copies, and
run "xflow" with these instead of the globally available ones.

"xflow" is really not that complicated, and is great for using inside
scripts, so that should be what you need.
Click to expand...
------------ And now a word from our sponsor ------------------
For a quality usenet news server, try DNEWS, easy to install,
fast, efficient and reliable. For home servers or carrier class
installations with millions of users it will allow you to grow!
---- See http://netwinsite.com/sponsor/sponsor_dnews.htm ----
 
Amontec Team, Laurent Gauch wrote:

Hi,
I need to know where I have to include my .ucf file in XFLOW!
As long as it has the same name as the rest of the design XFLOW should
Click to expand...
find it automatically. E.g., if you have a "top.vhd", or a "top.ngc",
then XFLOW should find a "top.ucf" on it's own, if it resides in the
current directory. Otherwise you can change it in the *.opt-file for the
"implement" stage (fast_runtime.opt, for example, or whatever you use).

--
Sean Durkin
Fraunhofer Institute for Integrated Circuits (IIS)
Am Wolfsmantel 33, 91058 Erlangen, Germany
http://www.iis.fraunhofer.de

mailto:23@iis.42.de
([23 , 42] <=> [durkinsn , fraunhofer])
 
I found. There are '-uc' parameter for the

Amontec Team, Laurent Gauch wrote:

Hi,

I need to know where I have to include my .ucf file in XFLOW!

Laurent

Sean Durkin wrote:

Amontec Team, Laurent Gauch wrote:

Hi all,
I am using Webpack ISE to do PAR for Coolrunner.
How to get back all command line from VHDL and UCF parser to JEDEC
generation (parser, synthesis and par works)
The goal is to do a generic project (using webpack IDE interface) and
to get back all ISE command line, and to re-run the ISE command line
for an other VHDL file with minor changes. All the work would be via
script for generating about 50 news configs of our Chameleon POD.


Have a look at the chapter about "xflow" in the ISE Documentation.
That's the command-line-tool to do the complete flow from synthesis to
bitfile generation (I assume you can generate JEDEC-files as well).
The options for each of the steps are set in *.opt-files, that reside
in $XILINX/epld/data. You can copy those and modify the local copies,
and run "xflow" with these instead of the globally available ones.

"xflow" is really not that complicated, and is great for using inside
scripts, so that should be what you need.


------------ And now a word from our sponsor ------------------
For a quality usenet news server, try DNEWS, easy to install,
fast, efficient and reliable. For home servers or carrier class
installations with millions of users it will allow you to grow!
---- See http://netwinsite.com/sponsor/sponsor_dnews.htm ----
Click to expand...
------------ And now a word from our sponsor ------------------
For a quality usenet news server, try DNEWS, easy to install,
fast, efficient and reliable. For home servers or carrier class
installations with millions of users it will allow you to grow!
---- See http://netwinsite.com/sponsor/sponsor_dnews.htm ----
 
Amontec Team, Laurent Gauch wrote:
Sean Durkin wrote:

Amontec Team, Laurent Gauch wrote:

Hi all,
I am using Webpack ISE to do PAR for Coolrunner.
How to get back all command line from VHDL and UCF parser to JEDEC
generation (parser, synthesis and par works)
The goal is to do a generic project (using webpack IDE interface) and
to get back all ISE command line, and to re-run the ISE command line
for an other VHDL file with minor changes. All the work would be via
script for generating about 50 news configs of our Chameleon POD.


Have a look at the chapter about "xflow" in the ISE Documentation.
That's the command-line-tool to do the complete flow from synthesis to
bitfile generation (I assume you can generate JEDEC-files as well).
The options for each of the steps are set in *.opt-files, that reside
in $XILINX/epld/data. You can copy those and modify the local copies,
and run "xflow" with these instead of the globally available ones.

"xflow" is really not that complicated, and is great for using inside
scripts, so that should be what you need.

Sean,

I will try the xflow way.
many thanks
Laurent
Click to expand...
For verilog and FPGA the log file is <top_level_name>.cmd_log just run
the flow once and copy it to a *.bat file

from the command line it pretty easy to guess what files you need to
look at to set options etc. and they are quite easy to read and modify

-Lasse
 
All are working fine.
I am now able to pass from VHDL source files to SVF output files only
using script ! We have now a Chameleon POD self programmable from VHDL
source. (Just need to intall the Free webpack) :)

A very nice solution.

Laurent
www.amontec.com

Sean Durkin wrote:
Amontec Team, Laurent Gauch wrote:

Hi,
I need to know where I have to include my .ucf file in XFLOW!

As long as it has the same name as the rest of the design XFLOW should
find it automatically. E.g., if you have a "top.vhd", or a "top.ngc",
then XFLOW should find a "top.ucf" on it's own, if it resides in the
current directory. Otherwise you can change it in the *.opt-file for the
"implement" stage (fast_runtime.opt, for example, or whatever you use).
Click to expand...
 
You must log in or register to reply here.

Welcome to EDABoard.com

Sponsor

Back
Top