PicoBlaze在ISE 14.7中复制文件出错该怎么办？

@pkiangGreat！
请关闭此帖子
-Pratham ------------------------------------------------
----------------------------------------------请注意 - 请
如果提供的信息有用，请将答案标记为“接受为解决方案”。给予您认为有用并回复导向的帖子。感谢K-
--------------------------------------------------
-----------------------
在原帖中查看解决方案



以下为原文

@pkiang Great! Please close this thread
-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.
----------------------------------------------------------------------------------------------View solution in original post

喜
您正在尝试编译哪个项目？
是否可以使用最新版本的picoblaze代码？
--hs
--------------------------------------------------
--------------------------------------------请注意 - 请注明
如果提供的信息有用，请回答“接受为解决方案”。给予您认为有用并回复导向的帖子。感谢K--
--------------------------------------------------
---------------------



以下为原文

hi,
 
which project are you trying to compile? 
 
would that be possible to use the latest version of the picoblaze code?
 
--hs
----------------------------------------------------------------------------------------------
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.
----------------------------------------------------------------------------------------------

你的意思是在ISE 14.7中使用KCPSM6代替KCPSM3吗？



以下为原文

Do you mean use KCPSM6 instead of KCPSM3 in ISE 14.7?

@ pkiangNo，KCPSM6适用于6和7系列。我看到你正在使用Virtex II的文件。
请下载spartan3的文件并使用它。
文件可以从这里下载
http://www.xilinx.com/ipcenter/processor_central/picoblaze/member/
-Pratham ------------------------------------------------
----------------------------------------------请注意 - 请
如果提供的信息有用，请将答案标记为“接受为解决方案”。给予您认为有用并回复导向的帖子。感谢K-
--------------------------------------------------
-----------------------



以下为原文

@pkiang No,KCPSM6 is for 6 and 7 series. I see you are using files for Virtex II. Please download files for spartan3 and use it.
 
files can be downloaded from here
 
http://www.xilinx.com/ipcenter/processor_central/picoblaze/member/
-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.
----------------------------------------------------------------------------------------------

@pkiangDid有帮助吗？
你能下载文件并使用它们吗？
-Pratham ------------------------------------------------
----------------------------------------------请注意 - 请
如果提供的信息有用，请将答案标记为“接受为解决方案”。给予您认为有用并回复导向的帖子。感谢K-
--------------------------------------------------
-----------------------



以下为原文

@pkiang Did that help? are you able to download files and use them?
-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.
----------------------------------------------------------------------------------------------

我查看了链接http://www.xilinx.com/ipcenter/processor_central/picoblaze/member/，并下载了PicoBlaze下的Spartan-3，Virtex-4，VirtexII Pro FPGA的zip文件。
解压缩下载后，发现文件正是我目前正在使用的文件。



以下为原文

I checked the link http://www.xilinx.com/ipcenter/processor_central/picoblaze/member/ and downloaded the zip file under PicoBlaze for Spartan-3, Virtex-4, VirtexII Pro FPGAs.
After unzipping the downloaded, it was found that the files are exactly what I am currently using.

'PicoBlaze for Spartan-3，Virtex-4，Virtex-II和Virtex-II Pro FPGA的封装已于10年前发布，在此期间ISE工具已发生变化，不再支持Virtex-II器件。
实际上，JTAG Loader工具是使用程序ROM模板中的BSCAN_VIRTEX2原语来描述的，但该原语在针对Spartan-3设备时是兼容的。
现在已经删除了对Virtex-II的支持，这些工具无法定位该原语，因此您可以看到您所遇到的问题。
有两种解决方案。
1）在程序ROM文件中简单地将“BSCAN_VIRTEX2”替换为“BSCAN_SPARTAN3”。
这些原语在所有其他方面都是相同的（因此它们总是兼容的）所以只需更改名称即可。
更好的是，您在'ROM_form'模板文件中进行文本替换，因此每次运行KCPSM3汇编器时，它将生成包含Spartan原语的文件，您不需要每次都进行手动编辑。
2）停止使用带有JTAG Loader功能的程序ROM。
您需要使用普通的'ROM_form'模板再次组装程序，该模板仅定义BRAM（即没有附加逻辑或'BSCAN_VIRTEX2'原语）并调整设计以反映没有JTAG Loader的内存没有'
proc_reset'输出。
JTAG Loader是一种在开发过程中快速更改程序的好方法，但是现在重新实现Spartan-3设计并不需要很长时间，因此使用它不像10年前那样引人注目。
仅供参考 -  PicoBlaze论坛已存档，不再对新帖开放。
但是，您（和其他人）仍然可以读取可能找到答案的先前线程。
https://forums.xilinx.com/t5/PicoBlaze-Archived/bd-p/PicoBlaze
Ken Chapman英国Xilinx主要工程师



以下为原文

The 'PicoBlaze for Spartan-3, Virtex-4, Virtex-II and Virtex-II Pro FPGAs' package was released 10 years ago during which time the ISE tools have changed and no longer support the Virtex-II devices. As it happens, the JTAG Loader facility was described using the BSCAN_VIRTEX2 primitive in the template for the program ROM but that primitive was compatible when targeting a Spartan-3 device. Now that support for Virtex-II has been removed, the tools can't locate that primitive so you see the problem that you do.
 
There are two solutions.
 
1) Simply replace 'BSCAN_VIRTEX2' with 'BSCAN_SPARTAN3' in the program ROM file. These primitives are the same in all other respects (hence they were always compatible) so just change the name. Better still, you make that text replacement in the 'ROM_form' template file so that each time the KCPSM3 assembler is run it will generate a file containing the Spartan primitive and you won't need to do a manual edit every time.
 
2) Stop using the program ROM with the JTAG Loader facility. You'll need to assemble your program again using the normal 'ROM_form' template that only defines a BRAM (i.e. no additional logic or the 'BSCAN_VIRTEX2' primitive) and adjust the design to reflect that the memory without JTAG Loader doesn't have the 'proc_reset' output. JTAG Loader is a nice way to quickly change programs during development but these days it doesn't take long to re-implement a Spartan-3 design so it's not quite as compelling to use it as it was 10 years ago.
 
FYI - The PicoBlaze forum has been archived and is no longer open to new posts. However, you (and others) can still read previous threads where answers may be found.
 
https://forums.xilinx.com/t5/PicoBlaze-Archived/bd-p/PicoBlaze
 
 
   
 
 
Ken Chapman
Principal Engineer, Xilinx UK

我尝试了第一个解决方案。
已编辑ROM_form.vhd并重新运行KCPSM3汇编程序。
问题解决了。
谢谢肯！



以下为原文

I tried the first solution. The ROM_form.vhd has been edited and rerun the KCPSM3 assembler. The problem was solved. Thanks to Ken!

@pkiangGreat！
请关闭此帖子
-Pratham ------------------------------------------------
----------------------------------------------请注意 - 请
如果提供的信息有用，请将答案标记为“接受为解决方案”。给予您认为有用并回复导向的帖子。感谢K-
--------------------------------------------------
-----------------------



以下为原文

@pkiang Great! Please close this thread
-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.
----------------------------------------------------------------------------------------------