ISE 14.7怎么从tcl脚本更改.bit文件名

我不确定你可以将它作为bitgen命令的一个选项 - 从Project Navigator中似乎没有一个选项可以控制它。
但是，您可以使用Tcl命令“文件重命名”完成bitgen后重命名文件
Avrum



以下为原文

I'm not sure you can do it as an option to the bitgen command - from the Project Navigator there doesn't appear to be an option to control this.
 
However, you can always rename the file after bitgen is done using the Tcl command "file rename "
 
Avrum

@mvalvoNo没有办法像vivado一样使用bitgen重命名比特流。
通过defalut ISE获取您的顶级模块名称并使用[top_module_name.bit]生成.bit文件
-Pratham ------------------------------------------------
----------------------------------------------请注意 - 请
如果提供的信息有用，请将答案标记为“接受为解决方案”。给予您认为有用并回复导向的帖子。感谢K-
--------------------------------------------------
-----------------------



以下为原文

@mvalvo No there is no way like vivado to rename bitstream using bitgen.
 
By defalut ISE takes your top module name and generate .bit file with [top_module_name.bit]
-Pratham

----------------------------------------------------------------------------------------------
Kindly note- Please mark the Answer as "Accept as solution" if information provided is helpful.

Give Kudos to a post which you think is helpful and reply oriented.
----------------------------------------------------------------------------------------------

嗨@mvalvo
bitgen [options] infile [.ncd] [outfile] [pcf_file.pcf]
Outfile是位文件的名称。
有关详细信息，请参阅http://www.xilinx.com/support/documentation/sw_manuals/xilinx14_7/devref.pdf的第223页。
谢谢，维杰-----------------------------------------------
---------------------------------------------请将帖子标记为
一个答案“接受为解决方案”，以防它有助于解决您的查询。如果一个帖子引导到解决方案，请给予赞誉。



以下为原文

Hi @mvalvo
 
bitgen [options] infile[.ncd] [outfile] [pcf_file.pcf]
 
Outfile is the name of the bit file.
 
Refer to page 223 of http://www.xilinx.com/support/documentation/sw_manuals/xilinx14_7/devref.pdf for details.
Thanks,Vijay
--------------------------------------------------------------------------------------------
Please mark the post as an answer "Accept as solution" in case it helped resolve your query.
Give kudos in case a post in case it guided to the solution.

@vijayak，
原始问题询问如何从.tcl脚本更改它。
在ISE中，Tcl脚本通过Project Navigator，因此bitgen命令的所有选项必须通过Project Navigator设置窗口提供的字段。
对于bitgen，没有提供用于指定outfile名称的选项。
通常，可以使用“其他选项”字段来指定没有提供机制的内容，但是您在此处放置的额外选项将放在[options]字段中，并假设与位置无关。
[outfile]字段取决于位置，因此只有在项目导航器具有指定选项时才能更改。
因此，虽然您的建议对于直接或在.bat / .sh / .csh脚本中运行bitgen的人来说是正确的，但它不适用于使用.tcl脚本的人（通过Project Navigator）。
Avrum



以下为原文

@vijayak,
 
The original question asked how to change it from the .tcl script. In ISE the Tcl script goes through the Project Navigator, and hence all the options to the bitgen command must come through the fields provided by the Project Navigator settings window.
 
For bitgen there is no option provided for specifying the name of the outfile. Normally, one would use the "Other options" field for specifying something for which there is not provided mechanism, but the extra options you put here would be putin the [options] field, and are assumed to be position independent. The [outfile] field is position dependent, and hence would only be able to be changed if the project navigator had a specified option for it.
 
So while your suggestion is correct for someone running bitgen directly or in a .bat/.sh/.csh script, it doesn't apply to someone using a .tcl script (through the Project Navigator).
 
Avrum

谢谢你的回复。
除了在这种情况下使用tcl脚本之外，你可以建议一个更好的方法：
对于我的设计，我需要生成许多不同的（.bit）和（.mcs）文件;
像50或更多。
我在最高级别使用泛型来区分每个构建。
有人可以指导如何自动化以下过程：
1.修改顶级泛型
2.建设项目
3.将（.bit）文件输出到特定名称/位置
4.将（.mcs）文件生成到特定名称/位置
谢谢。



以下为原文

thanks for the responses.  
Maybe you can suggeset a better way other than using the tcl script for this situation:
For my design, I need to generate many different (.bit) and (.mcs) files; like 50 or more.  I have generics at the top level that differentiate each build.  Can someone guide on how to automate the process of:
1.  modifying the top level generics
2.  building the project
3.  output the (.bit) file to a specific name/place
4.  generating the (.mcs) file to a specific name/place
 
thanks.

好吧，你有两个选择 - 你可以在Tcl中编写脚本，也可以在.bat / .sh / .csh中编写脚本。
所有这些都是脚本语言，因此他们可以访问正常的流控制概念，如循环，条件和变量等......绝对可以做你想要的，但你需要学习脚本语言。
如果这些构建中的每一个都使用影响设计实现的泛型（即，在RTL代码中使用泛型），那么您实际上处理的是50种不同的设计。
理想情况下，您可以在自己的目录中构建每个目录，其中每个目录都是完整的构建（最多为.bit和.mcs文件），使用一组不同的泛型。
这可以在所有脚本语言中完成。
Projet  - > Write Tcl脚本生成的Tcl脚本可用作起点。
将50个变体中的每一个包含在for循环中。
对于每个目录，使用依赖于变量的名称创建一个新目录（使用Tcl'file mkdir'命令）;
即my_proj_run0，my_proj_run1，my_proj_run2 ...然后cd到该目录。
在循环中，Tcl脚本已经知道如何制作项目，并设置过程属性。
在启动综合之前，您可以适当地设置泛型的值 - 这可以使用项目属性在Tcl中完成。
运行完成后，正常生成位文件。
这将把它放在项目目录中。
如果要移动或重命名它，请使用Tcl命令执行此操作。
然后关闭你的项目，'cd'回到上层指令并完成循环 - 这将迭代你所有的变化。
如果您选择放弃ProjectNavigator Tcl脚本，则可以在.bat / .sh / .csh中执行此操作。
你仍然会使用循环并创建目录，但是你会直接调用xst，ngdbuild，map，par，trce和bitgen进程，每个进程都有自己的（复杂的）命令行。
定制设计的泛型将放在xst的命令行中。
顺便说一下，在Tcl中你有两个选择 - 你可以在Project Navigator中做到这一点，或者你可以在PlanAhead中做到这一点。
虽然两者都使用Tcl，但PlanAhead的脚本功能更清晰，可能更强大，更像Vivado而不是ProjectNavigator。
如果你必须学习一个，那么它可能是PlanAhead。
更好的是，如果设计是7系列设计，你应该转移到Vivado ......
Avrum



以下为原文

Well, you have two choices - you either script it in Tcl or you script it in .bat/.sh/.csh.
 
All of these are scripting languages and hence they have access to the normal flow control concepts like for loops and conditions and variables, etc... It is definitely possible to do what you want, but you need to learn the scripting language.
 
If each of these builds uses generics that affects the implementation of the design (i.e. the generics are used in your RTL code), then you are really dealing with 50 different designs. Ideally you would build each one in its own directory, where each directory is a complete build (up to the .bit and .mcs file) using a different set of generics. This can be done in all scripting languages.
 
The Tcl script generated by the Projet -> Write Tcl script can be used as a starting point. Wrap that in a for loop for each of your 50 variants. For each one, create a new directory (using the Tcl 'file mkdir' command) using a name that is dependent on the variant; i.e. my_proj_run0, my_proj_run1, my_proj_run2... and then cd to that directory. Within the loop the Tcl script already knows how to make the project, and set the process properties. Before launching synthesis, you would then set the value of the generics appropriately - this can be done in Tcl using project properties.
 
Once the run is complete, generate the bit file normally. This will put it in the project directory. If you want to move or rename it, use the Tcl command to do so. Then close your project, 'cd' back to the upper diretory and complete the loop - this will then iterate through all your variations.
 
If you choose to abandon the ProjectNavigator Tcl scripts, you can do this all in .bat/.sh/.csh. You would still use a loop and create directories, but then you would invoke the processes xst, ngdbuild, map, par, trce and bitgen directly, each with their own (complex) command lines. The generics that customize your design would be put on the command line for xst.
 
By the way, in Tcl you have two choices - you can do this in Project Navigator, or you can do it in PlanAhead. While both use Tcl the scripting capabilities of PlanAhead are a little cleaner, probably a bit more powerful and much more like Vivado than ProjectNavigator. If you have to learn one, it might make sense for it to be PlanAhead.
 
Better yet, if the design is a 7 series design, you should move to Vivado...
 
Avrum

HI mvalvo
现在大约3年前你发布了你的问题。
你找到了解决方案吗？
我尝试做同样的事情，我有一个ISE14.7 FPGA设计，并希望得到不同的位文件依赖于通用参数。
问候



以下为原文

HI mvalvo
 
Now it's about 3 years ago you posted your issue.
Did you find any solution?
I try to do the same thing, I have a ISE14.7 FPGA design and want to get different bit files in dependency of a generic parameter.
 
Regards