完善资料让更多小伙伴认识你,还能领取20积分哦, 立即完善>
亲爱的社区,
我很难添加Xilinx的以太网IP核(核心类型:三模式以太网MAC;版本:4.6)。 除了受到这个核心所需的大量投入和产出的打击之外,我还面临以下基本问题: 我的Spartan 3AN的UCF文件只知道四个TXD和RXD网络: NET“E_TXD”LOC =“F8”| IOSTANDARD = LVCMOS33 | DRIVE = 8 | SLEW = FAST; NET“E_TXD”LOC =“E7”| IOSTANDARD = LVCMOS33 | DRIVE = 8 | SLEW = FAST; NET“E_TXD”LOC =“E6”| IOSTANDARD = LVCMOS33 | DRIVE = 8 | SLEW = FAST; NET“E_TXD”LOC =“F7”| IOSTANDARD = LVCMOS33 | DRIVE = 8 | SLEW = FAST; NET“E_TX_EN”LOC =“D8”| IOSTANDARD = LVCMOS33 | DRIVE = 8 | SLEW =快; 但核心需要八根线。 我从生成的实例化代码中得出结论: .emacphytxd(emacphytxd),//输出[7:0] emacphytxd 有没有办法在我的Spartan 3AN上使用这个IP块? 怎么样? 谢谢 以上来自于谷歌翻译 以下为原文 Dear community, I am stuck with adding an ethernet IP core from Xilinx (Core Type: Tri Mode Ethernet MAC; Version: 4.6). Apart from being struck by the sheer amount of inputs and outputs which are required by this core, I face the following fundamental problem: my Spartan 3AN's UCF file knows only four TXD and RXD nets: NET "E_TXD<0>" LOC = "F8" | IOSTANDARD = LVCMOS33 | DRIVE = 8 | SLEW = FAST ; NET "E_TXD<1>" LOC = "E7" | IOSTANDARD = LVCMOS33 | DRIVE = 8 | SLEW = FAST ; NET "E_TXD<2>" LOC = "E6" | IOSTANDARD = LVCMOS33 | DRIVE = 8 | SLEW = FAST ; NET "E_TXD<3>" LOC = "F7" | IOSTANDARD = LVCMOS33 | DRIVE = 8 | SLEW = FAST ; NET "E_TX_EN" LOC = "D8" | IOSTANDARD = LVCMOS33 | DRIVE = 8 | SLEW = FAST ; But the core requires eight wires. I conclude this from the generated instantiation code: .emacphytxd(emacphytxd), // output [7 : 0] emacphytxd Is there a way to use this IP block with my Spartan 3AN? How? Thanks |
|
相关推荐
8个回答
|
|
所以,我从RGMII切换到GMII
我认为这是倒退的。 你想要4根电线的RGMII。 “R”代表减少引脚数。 - Gabor 在原帖中查看解决方案 以上来自于谷歌翻译 以下为原文 So, I switched from RGMII to GMII I think that's backwards. You want RGMII for 4 wires. The "R" stands for Reduced pin count. -- GaborView solution in original post |
|
|
|
您需要生成内核以使用实际位于主板上的PHY接口。
如果你 每个方向只有4根线,我认为它是RGMII。 根据您对8条数据线的描述, 我假设你已经为GMII生成了核心。 - Gabor 以上来自于谷歌翻译 以下为原文 You need to generate the core to use the PHY interface that's actually on your board. If you only have 4 wires each way, I assume it's RGMII. From your description of 8 data wires, I assume you have generated the core for GMII. -- Gabor |
|
|
|
感谢你的指针,它有助于知道在哪里看...所以,我从RGMII切换到GMII,它仍然需要8线([7:0])。
但是当我将PHY接口设置为“MII”时,它似乎只需要四条线路用于TXD和rXD。 以上来自于谷歌翻译 以下为原文 Thanks for your pointer, it helped to know where to have a look at ... So, I switched from RGMII to GMII and it still requires 8 wires ( [7:0]). But when I set the PHY interface to "MII", it requires only four wires for TXD and rXD, it seems. |
|
|
|
所以,我从RGMII切换到GMII
我认为这是倒退的。 你想要4根电线的RGMII。 “R”代表减少引脚数。 - Gabor 以上来自于谷歌翻译 以下为原文 So, I switched from RGMII to GMII I think that's backwards. You want RGMII for 4 wires. The "R" stands for Reduced pin count. -- Gabor |
|
|
|
在我的核心生成器中,它显示了RGMII的八条线,请参阅附带的屏幕截图。
与 另一件好事......对于任何人发现这一点......当你使用生成的核心时,ISE会在当前项目中放入文件“ipcore_dir”,核心并在其中包含一个文件夹“example_design”,其中包含用法示例。 我真的更喜欢ISE提到这个...... 以上来自于谷歌翻译 以下为原文 In my core generator, it says eight wires for RGMII, see attached screenshots. vs. One other nice thing ... for whomever finds this ... when you use a generated core, ISE puts into a file "ipcore_dir" in the current project, the core and in there a folder "example_design", which contains usage examples. I would really prefer ISE to mention this ... |
|
|
|
这似乎是核心生成器图形中的一个错误,应该修复。
如果您希望Xilinx注意到,您应该为此打开一个Webcase。 此外,当您使用Project - > New Source ...为设计添加核心时,ipcore_dir就是 默认目录,但您可以在第一个屏幕中更改此目录。 我一般都会保留我的项目 层次结构,使“project”目录是“main”目录中的一个级别。 所以,如果我的 项目名称是FooBar,我有一个目录FooBar,下面有一个目录FooBar / synth ISE项目所在的地方。 源代码将在FooBar / source,UCF文件中 FooBar /约束,FooBar /核心下的Coregen IP等。这样做多一点 在添加文件时工作,但有助于将包含工作的目录分开 来自ISE生成的中间文件和目录的大量内容。 - Gabor 以上来自于谷歌翻译 以下为原文 It would seem that this is a bug in the graphics of the core generator that should be fixed. You should probably open a webcase for this if you want Xilinx to take notice. Also, when you add a core to a design using Project --> New Source..., ipcore_dir is the default directory, but you can change this in the first screen. I generally keep my project hierarchy such that the "project" directory is one level from the "main" directory. So if my project name was FooBar, I'd have a directory FooBar and under that a directory FooBar/synth where the ISE project lives. Source code would be under FooBar/source, UCF file in FooBar/constraints, Coregen IP under FooBar/cores, etc. This makes a little more work when adding files, but helps to keep the directories containing your work separate from the scads of ISE-generated intermediate files and directories. -- Gabor |
|
|
|
说实话,我认为这不是ISE中唯一的错误。
...例如......当我处于“模拟”模式并且正在编辑UUT而不是测试台时,我仍然可以触发“运行模拟”任务。 由于UUT没有测试脚本,因此无意义。 虽然UUT与测试用例正确关联,但ISE模拟UUT而不是测试脚本。 信不信由你,花了两个小时才弄清楚为什么我的模拟有时成功,有时我的CLK信号都是Z.嗯。 现在我明白了。 以上来自于谷歌翻译 以下为原文 to be honest, I think that's not the only bug in ISE. ... for example ... when I am in "Simulation" mode and am editing the UUT and not the test bench, I can still trigger the task "run simulation". Which spits out nonsense as the UUT doesn't have a test script. Although the UUT is correctly associated with a test case, ISE simulates the UUT and not the test script. Believe it or not, it took me two hours to figure out why my simulation succeeded sometimes and at other times my CLK signals were all Z. Well. Now I know. |
|
|
|
是的,那个人也是我。
问题是如果双击UUT中的UUT 层次结构窗格编辑它,它还选择该文件进行模拟。 我已经习惯了 现在,在我开始模拟之前检查突出显示的内容。 无论如何,有很多错误,这些论坛不适合报告 如果你想让控制软件的人对它做些什么的话。 - Gabor 以上来自于谷歌翻译 以下为原文 Yeah, that one's bit me too. The problem is that if you double-click the UUT in the hierarchy paneto edit it, it also selects that file for simulation. I've gotten used to checking what's highlighted before I start simulations, now. In any case, there are lots of bugs and these forums are not the proper place to report them if you want the people who control the software to do something about it. -- Gabor |
|
|
|
只有小组成员才能发言,加入小组>>
2416 浏览 7 评论
2821 浏览 4 评论
Spartan 3-AN时钟和VHDL让ISE合成时出现错误该怎么办?
2292 浏览 9 评论
3372 浏览 0 评论
如何在RTL或xilinx spartan fpga的约束文件中插入1.56ns延迟缓冲区?
2458 浏览 15 评论
有输入,但是LVDS_25的FPGA内部接收不到数据,为什么?
1121浏览 1评论
请问vc707的电源线是如何连接的,我这边可能出现了缺失元件的情况导致无法供电
581浏览 1评论
求一块XILINX开发板KC705,VC707,KC105和KCU1500
447浏览 1评论
2002浏览 0评论
725浏览 0评论
小黑屋| 手机版| Archiver| 电子发烧友 ( 湘ICP备2023018690号 )
GMT+8, 2024-12-21 20:27 , Processed in 1.432265 second(s), Total 91, Slave 74 queries .
Powered by 电子发烧友网
© 2015 bbs.elecfans.com
关注我们的微信
下载发烧友APP
电子发烧友观察
版权所有 © 湖南华秋数字科技有限公司
电子发烧友 (电路图) 湘公网安备 43011202000918 号 电信与信息服务业务经营许可证:合字B2-20210191 工商网监 湘ICP备2023018690号