完善资料让更多小伙伴认识你,还能领取20积分哦, 立即完善>
这是一个如何使用Digilent的Adept和工具来编写这个devkit,专门针对Windows用户。
在影响13.3时遇到了一些问题,所以我一直在寻找一种更直接的方法来设计开发板。 看看Digilent的工具,Adept系统,Adept实用程序,sfutil.exe >>>:Adept >>>:SFUtilHowever,Adept系统和Adept实用程序都无法检测到板,原因是jtscdvclist.txtIt中缺少设备声明 可以添加所需的设备ID。首先,从Digilent工具运行djtgcfg.exe init -d obp。 devkit必须连接,结果应该是这样的:初始化扫描链...找到设备ID:XXXXXXXX ...在jtscdvclist.txt中搜索XC6SLX $,在DEVICES部分添加:9 0FFFFFFFh,所以它看起来像 即:设备{9 XXXXXXXXh 0FFFFFFFh 16 04002093h 0FFFFFFFh ... 注意设备ID后面的“h”。 文件jtscdvclist.txt将在“drive: program files common files digilent data”下找到。保存jtscdvclist.txt。 现在,Adept以及Adept工具将识别devkit。为了使它更舒适,可以使用.bat文件,它允许拖放.bit文件。用于编程FPGA: ************************************************** ******************************************** @EHO OFFC: Xilinx batchprg djtgcfg.exe enumC: Xilinx batchprg djtgcfg.exe init -d obpC: Xilinx batchprg djtgcfg.exe prog -d obp -i“0”-f%1 @ IF ERRORLEVEL 1 GOTO FEHLER @ GOTO END:FEHLER @ ECHO ############## @ ECHO#! 费勒! #@ ECHO ############## @暂停:结束 ************************************************** ******************************************** 还有一个用于编程FPGA的SPI闪存: ************************************************** ******************************************** 致电C: Xilinx 13.3 ISE_DS settings32.batcd .echo off :: AVNET“原样”提供本设计,代码或信息::仅用于开发XILINX :: DEVICES的程序和解决方案。 通过提供本设计,代码或信息::作为本功能,应用程序::标准的一次可能实现,AVNET不作任何陈述,表示此::执行不受任何侵权索赔的影响,::并且您对此负有任何责任 获得您可能需要的任何权利::为了您的实施。 AVNET明确拒绝对以下内容提供任何::保证,包括但不限于任何保证或::表示此实施不受侵权,侵权,适销性和适用性的默示保证:: 具体目的:::(c)版权所有2011 AVNET,Inc。::保留所有权利。@ echo ######################## ################################################## @echo#此文件使用iMPACT创建PROM文件,然后使用Digilent,Inc。提供的sfutil实用程序擦除和编程#@ echo#it。N25Q128#@ echo #Flash是mcs文件的目标PROM。 板载Digilent#@ echo#Atmel全速USB-JTAG在安富利上将mcs编程为Flash#@ echo#Spartan-6 LX9 MicroBoard#@ echo ############### ################################################## ######### :: set bitstream = uart_ctrlset bitstream =%~n1set spiPartName = N25Q128set cmd_file = config_s6lx9.cmd :: erase size by 65KB(65536)sector,standard LX9 bitstream take 6 sector :: 6 * 65536 = 393216set erase_size = 393216 @ echo setMode -pff>%cmd_file%@echo setPreference -pref StartupClock:Auto_Correction >>%cmd_file%@ echo setSubmode -pffspi >>%cmd_file%@ echo addDesign -version 0 -name“0”>> %cmd_file%@ echo addDeviceChain -index 0 >>%cmd_file%@ echo addDevice -spi%spiPartName%-p 1 -file%bitstream%.bit >>%cmd_file%@ echo generate -format mcs -generic -spi -fillvalue FF -output%bitstream%。mcs >>%cmd_file%@ echo quit >>%cmd_file%impact -batch%cmd_file%erase%cmd_file%C: Xilinx batchprg sfutil -d obp -cr -m N25Q128 -e -l %erase_size%-tC: Xilinx batchprg sfutil -d obp -cr -m N25Q 128 -NE -fi -w%bitstream%。mcs -t @ IF ERRORLEVEL 1 GOTO FEHLER @ GOTO END:FEHLER @ ECHO ############## @ECHO#! 费勒! #@ ECHO ############## @暂停:结束***************************** ************************************************** *************** 请注意AVNET的版权。 路径(在我的示例中为C: Xilinx batchprg )必须调整为您自己的配置。 将.bat文件添加到右键鼠标键的上下文菜单中可进一步简化编程。 以上来自于谷歌翻译 以下为原文 This is a howto targeted to use Digilent's Adept and tools for programming this devkit, intended to windows users. Got some issues with impact 13.3, so I was looking for a straighter way to get the devboard programmed. Had a look on Digilent's tools, Adept system, Adept utilities, sfutil.exe >>>: Adept >>>: SFUtil However, neither Adept system nor Adept utilities are able to detect the board, reason is the missing device declaration within jtscdvclist.txt It is possible to add the required device ID. First, run djtgcfg.exe init -d obp from the Digilent tools. The devkit has to be connected, result should be like that: Initializing scan chain... Found Device ID: XXXXXXXX ... Search in jtscdvclist.txt for XC6SLX$, in the section DEVICES add: 9 DEVICES{ 9 XXXXXXXXh 0FFFFFFFh 16 04002093h 0FFFFFFFh ... Notice the "h" after the device id. The file jtscdvclist.txt is to find under "drive:program filescommon filesdigilentdata". Save jtscdvclist.txt. Now Adept, as well as the Adept tools will recognice the devkit. To make it more comfortable, one can use .bat files, which allow drag and drop of .bit files. One for programming the FPGA: ********************************************************************************************** @EHO OFF C:Xilinxbatchprgdjtgcfg.exe enum C:Xilinxbatchprgdjtgcfg.exe init -d obp C:Xilinxbatchprgdjtgcfg.exe prog -d obp -i "0" -f %1 @IF ERRORLEVEL 1 GOTO FEHLER @GOTO END :FEHLER @ECHO ############## @ECHO # ! Fehler ! # @ECHO ############## @PAUSE :END ********************************************************************************************** And one for programming the FPGA's SPI-flash: ********************************************************************************************** call C:Xilinx13.3ISE_DSsettings32.bat cd . echo off :: AVNET IS PROVIDING THIS DESIGN, CODE, OR INFORMATION "AS IS" :: SOLELY FOR USE IN DEVELOPING PROGRAMS AND SOLUTIONS FOR XILINX :: DEVICES. BY PROVIDING THIS DESIGN, CODE, OR INFORMATION :: AS ONE POSSIBLE IMPLEMENTATION OF THIS FEATURE, APPLICATION :: OR STANDARD, AVNET IS MAKING NO REPRESENTATION THAT THIS :: IMPLEMENTATION IS FREE FROM ANY CLAIMS OF INFRINGEMENT, :: AND YOU ARE RESPONSIBLE FOR OBTAINING ANY RIGHTS YOU MAY REQUIRE :: FOR YOUR IMPLEMENTATION. AVNET EXPRESSLY DISCLAIMS ANY :: WARRANTY WHATSOEVER WITH RESPECT TO THE ADEQUACY OF THE :: IMPLEMENTATION, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OR :: REPRESENTATIONS THAT THIS IMPLEMENTATION IS FREE FROM CLAIMS OF :: INFRINGEMENT, IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS :: FOR A PARTICULAR PURPOSE. :: :: (c) Copyright 2011 AVNET, Inc. :: All rights reserved. @echo ########################################################################## @echo # This file uses iMPACT to create a PROM file and then erase and program # @echo # it using the sfutil utility provided by Digilent, Inc. The N25Q128 # @echo # Flash is the target PROM for the mcs file. The on-board Digilent # @echo # Atmel Full Speed USB-JTAG programs the mcs to Flash on the Avnet # @echo # Spartan-6 LX9 MicroBoard # @echo ########################################################################## :: set bitstream=uart_ctrl set bitstream=%~n1 set spiPartName=N25Q128 set cmd_file=config_s6lx9.cmd :: erase size by 65KB (65536) sector, standard LX9 bitstream takes 6 sectors :: 6 * 65536 = 393216 set erase_size=393216 @echo setMode -pff > %cmd_file% @echo setPreference -pref StartupClock:Auto_Correction >> %cmd_file% @echo setSubmode -pffspi >> %cmd_file% @echo addDesign -version 0 -name "0" >> %cmd_file% @echo addDeviceChain -index 0 >> %cmd_file% @echo addDevice -spi %spiPartName% -p 1 -file %bitstream%.bit >> %cmd_file% @echo generate -format mcs -generic -spi -fillvalue FF -output %bitstream%.mcs >> %cmd_file% @echo quit >> %cmd_file% impact -batch %cmd_file% erase %cmd_file% C:Xilinxbatchprgsfutil -d obp -cr -m N25Q128 -e -l %erase_size% -t C:Xilinxbatchprgsfutil -d obp -cr -m N25Q128 -NE -fi -w %bitstream%.mcs -t @IF ERRORLEVEL 1 GOTO FEHLER @GOTO END :FEHLER @ECHO ############## @ECHO # ! Fehler ! # @ECHO ############## @PAUSE :END ********************************************************************************************** Please notice AVNET's copyright. The paths (in my example C:Xilinxbatchprg) have to be adjusted to your own configuration. Adding the .bat files to the context menue for the right mouse key further simplifies programming. |
|
相关推荐
5个回答
|
|
topstat,
感谢您解释如何让Adept与该板一起工作。 我将添加一个关于sfutil性能的额外评论 - 我们发现通过sfutil编程flash比使用iMPACT快得多,即使使用Platform Cable USB-II或Digilent HS1也是如此。 这就是原因。 在MicroBoard上托管Digilent USB-JTAG固件的Atmel ATMEGA16U2控制器也可以直接连接到Micron N25Q SPI闪存。 由于sfutil利用这些直接的spi连接,因此没有JTAG开销,编程速度更快。 由于ATMEGA16U2仅具有全速USB连接,因此通过JTAG和iMPACT执行间接SPI编程非常缓慢。 但是,通过消除JTAG开销,通过sfutil的全速Atmel选项实际上比使用iMPACT的高速USB电缆更快。 另一个注意事项是,设计人员能够将Atmel设计从MicroBoard复制到他们自己的项目中,包括Digilent固件的许可,这将为您提供独立的直接SPI编程功能(以及全速USB-JTAG功能)。 板。 如果您对此感兴趣,请给我发消息或联系您的Avnet FAE了解更多详情。 布赖恩 以上来自于谷歌翻译 以下为原文 topstat, Thanks for your explanation on how to get Adept to work with this board. I'll add one additional comment regarding the performance of sfutil -- we've found programming flash through sfutil to be much faster than using iMPACT, even when using Platform Cable USB-II or Digilent HS1. Here's why. The Atmel ATMEGA16U2 controller that hosts the Digilent USB-JTAG firmware on the MicroBoard also has direct spi connections to the Micron N25Q SPI Flash. Since sfutil utilizes these direct spi connections, there is no JTAG overhead, and the programming goes much faster. Since the ATMEGA16U2 only has a full-speed USB connection, performing indirect SPI programming via JTAG and iMPACT is painfully slow. However, by eliminating JTAG overhead, the full-speed Atmel option via sfutil is actually faster than the high-speed USB cables using iMPACT. The other note is that designers are able to copy the Atmel design from the MicroBoard into their own project, including licensing of the Digilent firmware, which would give you sfutil Direct SPI Programming capability (and full-speed USB-JTAG capability) on your own board. If you're interested in doing that, send me a message or contact your Avnet FAE for more details. Bryan |
|
|
|
布莱恩,
这也是我对开发板的经验,sfutil更快,我很高兴分享我的发现的另一个原因。 感谢第二次通知,这是一个很好的信息。 路德维希 以上来自于谷歌翻译 以下为原文 Bryan, it was also my experience with the devboard that sfutil is much faster, another reason I was happy to share my findings. Thanks for the second notice, that's good info. Ludwig |
|
|
|
嗨布莱恩,
我只是收到了我的s6microboard,并注意到了主板上的ATmega16U2功能。 我对ATmega16U2的固件设计感兴趣,对我自己的项目/板。 我怎样才能获得Atmel设计的副本。 感谢致敬。 Sim CK 以上来自于谷歌翻译 以下为原文 Hi Bryan, I have just received my s6microboard and noted on the ATmega16U2 function on the board. I am interested in the firmware design in the ATmega16U2 for my own project/board. How can I get a copy of the Atmel design. Thanks and Regards. Sim CK |
|
|
|
嗨,
我认为这也可能让你感兴趣,因为显然你也遇到了针对Impact的Digilent插件的问题。 我找到了解决Impact问题的解决方案。 我的Spartan6-LX9主板现在得到了Impact的认可。 看这里的帖子: http://forums.xilinx.com/t5/Installation-and-Licensing/Ubuntu-11-10-and-impact-chipscope-etc/td-p/188486 干杯 托比亚斯 以上来自于谷歌翻译 以下为原文 Hi, I thought this might also interest you since apparently you also ran into problem with the Digilent plugin for Impact. I have found a solution that resolves the issue with Impact. My Spartan6-LX9 Board now gets recognized by Impact immeadiatly. See the post here: http://forums.xilinx.com/t5/Installation-and-Licensing/Ubuntu-11-10-and-impact-chipscope-etc/td-p/188486 Cheers Tobias |
|
|
|
Windows 7用户的答案是什么?
我从哪里得到驱动器。 刚拿到电路板,但系统看不到司机。 以上来自于谷歌翻译 以下为原文 What is the answer for a windows 7 user. Where do i get the drive. just got the board but no driver seen by my system. |
|
|
|
只有小组成员才能发言,加入小组>>
2420 浏览 7 评论
2823 浏览 4 评论
Spartan 3-AN时钟和VHDL让ISE合成时出现错误该怎么办?
2294 浏览 9 评论
3374 浏览 0 评论
如何在RTL或xilinx spartan fpga的约束文件中插入1.56ns延迟缓冲区?
2461 浏览 15 评论
有输入,但是LVDS_25的FPGA内部接收不到数据,为什么?
1171浏览 1评论
请问vc707的电源线是如何连接的,我这边可能出现了缺失元件的情况导致无法供电
585浏览 1评论
求一块XILINX开发板KC705,VC707,KC105和KCU1500
451浏览 1评论
2005浏览 0评论
729浏览 0评论
小黑屋| 手机版| Archiver| 电子发烧友 ( 湘ICP备2023018690号 )
GMT+8, 2024-12-23 15:06 , Processed in 1.501980 second(s), Total 87, Slave 70 queries .
Powered by 电子发烧友网
© 2015 bbs.elecfans.com
关注我们的微信
下载发烧友APP
电子发烧友观察
版权所有 © 湖南华秋数字科技有限公司
电子发烧友 (电路图) 湘公网安备 43011202000918 号 电信与信息服务业务经营许可证:合字B2-20210191 工商网监 湘ICP备2023018690号