完善资料让更多小伙伴认识你,还能领取20积分哦, 立即完善>
扫一扫,分享给好友
早上好,
我们有一个基于aSpartan 3A设计的产品,带有几个支持CTS / RTS的UART。 UART基于Ken Chapman为Spartan 3设计的UART,但针对CTS / RTS支持进行了修改。 我们无法访问修改UART的人员。 我们现在正在将我们的设计迁移到Spartan 6,我们需要在设计中维护这些UART。对于Spartan 6实现,我在KCPSM6包中找到了Ken Chapman的UART,我正在考虑修改它们以获得RTS / CTS支持,但是我 我遇到了一些麻烦。 UART_TX6的FIFO与UART集成在一起,当在Spartan 3A中时,FIFO在外面。 对于CTS支持,我需要控制FIFO输出到UART_TX,我不知道如何做,因为Spartan 6 UART中的集成(一切似乎都是使用LUT6实例编写的)。 UART_RX6中的RTS支持也可能存在问题。 你能就这件事给我一些建议吗? 最好的祝福, 幸运 以上来自于谷歌翻译 以下为原文 Good morning, we have a product based on a Spartan 3A design with several UARTs that have CTS/RTS support. The UARTs are based in the UARTs designed by Ken Chapman for Spartan 3, but modified for CTS/RTS support. We have no access to the person that modified the UARTs. We are migrating now our design to Spartan 6 and we need to maintain those UARTs in the design. For Spartan 6 implementation, I have found Ken Chapman's UARTs in the KCPSM6 package and I was thinking of modifying them for RTS/CTS support, but I am having some trouble. The FIFO of the UART_TX6 is integrated with the UART, when in Spartan 3A the FIFO was outside. For CTS support I need to control the FIFO output to the UART_TX, and I don't know how to do it, because of the integration in the Spartan 6 UARTs (everything seems to be written using LUT6 instances). The RTS support in the UART_RX6 could also be problematic. Could you give me some advice on this matter, please? Best regards, Lucky |
|
相关推荐
4个回答
|
|
我在Spartan 6项目中简单地将Spartan3A UART与CTS / RTS支持集成在一起。
这些LUT是LUT4,我之前谈到的属性是那些LUT4的属性。 我不知道为什么现在在Spartan 6项目中给出了这个INIT属性的错误。 Spartan 3项目中没有任何错误。 以上来自于谷歌翻译 以下为原文 I have simply integrated Spartan3A UARTs with CTS/RTS support in the Spartan 6 project. These LUTs are LUT4, and the attributes I talked about before are the attributes from those LUT4s. I don't know why now is giving an error with this INIT attributes in the Spartan 6 project. There wasn't any error in the Spartan 3 project. |
|
|
|
通过Spartan 3A和Spartan 6的库指南,3A和6的LUT4之间的唯一区别在于它是3A中的原语和6中的“宏”.INIT矢量应该以相似的方式映射
两种情况。 你能发布你得到的确切错误吗? 还有一个想法。 当您定位Spartan6时,您将运行更新的XST合成前端。 这也称为“新解析器”。 您不能在不返回ISE 11.x的情况下为Spartan6使用较旧的解析器,但您可以在Spartan 3A项目上尝试新的解析器,以查看是否出现类似错误。 这可能指向工具问题而不是设备架构的问题。 要在3A项目上运行新解析器,请在“其他XST命令行选项”中设置此解析器 -use_new_parser是的 - Gabor 以上来自于谷歌翻译 以下为原文 Looking through the library guides for Spartan 3A and Spartan 6, the only difference between LUT4 for the 3A and the 6 is that it is a primitive in the 3A and a "macro" in the 6. The INIT vector is supposed to map similarly in both cases. Can you post the exact errors you get? One more thought. When you target Spartan6, you will be running a newer front-end to XST synthesis. This is also known as the "new parser." You can't use the older parser for Spartan6 without going back to ISE 11.x, but you can try the new parser on a Spartan 3A project to see if you get a similar error. That could point to a tool issue rather than a problem with the device architecture. To run the new parser on the 3A project, set this in the "Other XST Command Line Options" -use_new_parser yes -- Gabor |
|
|
|
通过Spartan 3A和Spartan 6的库指南,3A和6的LUT4之间的唯一区别在于它是3A中的原语和6中的“宏”.INIT矢量应该以相似的方式映射
两种情况。 你能发布你得到的确切错误吗? 当我离开时激活kcpsm3.vhd文件中的下一行: 第237行:属性INIT:string; 第238行:t_state_lut的属性INIT:label为“1”; 第239行:int_pulse_lut的属性INIT:label为“0080”; 我收到以下错误: 错误:Xst:3154 - “C: src R750 02_Development 02_Firmware 03_Top src qrs_detector src kcpsm3.vhd”。 第290行。无法在块实例上设置值为“1”的属性“INIT”。 通过VHDL泛型或Verilog参数在块定义中已使用值“0”定义此属性。 通过覆盖默认的VHDL泛型或Verilog参数来应用所需的值。 不允许使用属性。 错误:Xst:3154 - “C: src R750 02_Development 02_Firmware 03_Top src qrs_detector src kcpsm3.vhd”。 第333行。无法在块实例上设置值为“0080”的属性“INIT”。 通过VHDL泛型或Verilog参数在块定义中已使用值“0000”定义此属性。 通过覆盖默认的VHDL泛型或Verilog参数来应用所需的值。 不允许使用属性。 还有一个想法。 当您定位Spartan6时,您将运行更新的XST合成前端。 这也称为“新解析器”。 您不能在不返回ISE 11.x的情况下为Spartan6使用较旧的解析器,但您可以在Spartan 3A项目上尝试新的解析器,以查看是否出现类似错误。 这可能指向工具问题而不是设备架构的问题。 要在3A项目上运行新解析器,请在“其他XST命令行选项”中设置此解析器 问题可能是,正如你所指出的那样,新的解析器是不同的。 我在Spartan3A项目中尝试了新的解析器,但由于乘法/除法运算中的大小不匹配,我得到了一些错误,我需要更正它们才能测试我是否在kcpsm3.vhd文件中得到相同的错误。我会在这里发布 最近有更多结果。 以上来自于谷歌翻译 以下为原文 Looking through the library guides for Spartan 3A and Spartan 6, the only difference between LUT4 for the 3A and the 6 is that it is a primitive in the 3A and a "macro" in the 6. The INIT vector is supposed to map similarly in both cases. Can you post the exact errors you get? When I leave activated the next lines in the kcpsm3.vhd file: Line 237: attribute INIT : string; Line 238: attribute INIT of t_state_lut : label is "1"; Line 239: attribute INIT of int_pulse_lut : label is "0080"; I get the following errors: ERROR:Xst:3154 - "C:srcR750 2_Development 2_Firmware 3_Topsrcqrs_detectorsrckcpsm3.vhd". Line 290. Unable to set attribute "INIT" with value "1" on instance ERROR:Xst:3154 - "C:srcR750 2_Development 2_Firmware 3_Topsrcqrs_detectorsrckcpsm3.vhd". Line 333. Unable to set attribute "INIT" with value "0080" on instance One more thought. When you target Spartan6, you will be running a newer front-end to XST synthesis. This is also known as the "new parser." You can't use the older parser for Spartan6 without going back to ISE 11.x, but you can try the new parser on a Spartan 3A project to see if you get a similar error. That could point to a tool issue rather than a problem with the device architecture. To run the new parser on the 3A project, set this in the "Other XST Command Line Options" The problem could be, as you point out, the new parser being different. I have tried the new parser in the Spartan3A project but I get some errors due to size mismatch in multiplication/division operations, I need to correct them before I can test if I get the same errors with the kcpsm3.vhd file. I will post here more results lately. |
|
|
|
错误消息意味着宏已经为INIT定义了通用,并且您只需要在实例化LUT时将新值作为通用映射传递。
这显然与处理基元的方式不同。 我不认为这实际上是一个“新的解析器”问题,但由于宏的实现方式是具有VHDL泛型的实体。 - Gabor 以上来自于谷歌翻译 以下为原文 The error message implies that the macro already has a generic defined for INIT and you just need to pass the new value as a generic map when you instantiate the LUT. This is apparently different from the way you handle a primitive. I don't think this is really a "new parser" issue, but due to the way the macro is implemented as an entity with generics for VHDL. -- Gabor |
|
|
|
只有小组成员才能发言,加入小组>>
2360 浏览 7 评论
2779 浏览 4 评论
Spartan 3-AN时钟和VHDL让ISE合成时出现错误该怎么办?
2247 浏览 9 评论
3324 浏览 0 评论
如何在RTL或xilinx spartan fpga的约束文件中插入1.56ns延迟缓冲区?
2411 浏览 15 评论
有输入,但是LVDS_25的FPGA内部接收不到数据,为什么?
725浏览 1评论
请问vc707的电源线是如何连接的,我这边可能出现了缺失元件的情况导致无法供电
520浏览 1评论
求一块XILINX开发板KC705,VC707,KC105和KCU1500
330浏览 1评论
734浏览 0评论
1933浏览 0评论
小黑屋| 手机版| Archiver| 电子发烧友 ( 湘ICP备2023018690号 )
GMT+8, 2024-11-5 12:16 , Processed in 1.266838 second(s), Total 83, Slave 66 queries .
Powered by 电子发烧友网
© 2015 bbs.elecfans.com
关注我们的微信
下载发烧友APP
电子发烧友观察
版权所有 © 湖南华秋数字科技有限公司
电子发烧友 (电路图) 湘公网安备 43011202000918 号 电信与信息服务业务经营许可证:合字B2-20210191 工商网监 湘ICP备2023018690号