完善资料让更多小伙伴认识你,还能领取20积分哦, 立即完善>
我们有一个应用程序使用APIC32 MZ2048 EFH 144通过SPI通信到一个EnC424J600(我们没有足够的引脚使用PHY)。我正在尝试实现CyrOnETCP(开源版本)来进行硬件测试。正如本主题中提到的,PHYLNK比特是低的,正如预期的那样,阻止TCP/IP栈起作用。不幸的是,TeNE624J600数据表并不能很好地描述这个比特意味着“以太以太网链路已经建立了一个远程以太网合作伙伴”,也没有提到什么检查或做时,“没有链接存在”被指示。对于这个以太网芯片,似乎也没有APP注释(无论如何,搜索没有找到一个)。我目前的问题是:“以太远程以太网合作伙伴建立以太网链路”意味着什么?合适的以太网信号存在吗?PHY级别握手与“远程伙伴”设备?还有别的吗?此位是否仍然是由TeNC624J600安装和配置中的错误引起的?除了数据表之外,还有其他关于TENC624J600的信息吗?谢谢!
以上来自于百度翻译 以下为原文 We have an application using a PIC32MZ2048EFH 144 communicating over SPI to an ENC424J600 (we don't have enough pins to use a PHY). I am attempting to implement CycloneTCP (open source version) to do hardware testing. As mentioned in the subject, the PHYLNK bit is low, which, as expected, prevents the TCP/IP stack from functioning. Unfortunately, the ENC624J600 data sheet is not very descriptive regarding what this bit means beyond "Ethernet link has been established with a remote Ethernet partner," nor does it mention what to check or do when "no link present" is indicated. There also does not appear to be an app note for this Ethernet chip (search didn't find one, anyway). My current questions:
Thanks! |
|
相关推荐
2个回答
|
|
这段时间花了3个星期的时间才得到批准,我当时能够解决这个问题。我将发布结果,以防任何人遇到类似的问题。
以上来自于百度翻译 以下为原文 It took a while (3 weeks) for this post to be approved, and I was able to solve the problem in that time. I will post the results shortly in case anyone comes across this post with a similar issue. |
|
|
|
PyLnk的问题是在库实现中。因为我避免设置我正在设置的测试中断,所以我只需要在一些时间之后检查PHYLNK(我通过添加命令到调试接口),或者读取Enc424J600上的中断引脚。我们确实有PIN有线到一个引脚在我们的PIC32 MZ,但PIC引脚设置为输入,而不是改变通知。即便如此,监控PIC输入引脚使LIB工作足够好用于测试;数据包可以被更新,但是性能很低。因此,尽管我仍然没有对以上问题的答案,但我确实解决了如何解决这个问题。
以上来自于百度翻译 以下为原文 The problem with PHYLNK was in the library implementation. Because I was avoiding setting up the interrupts for the test I was setting up, I simply needed to check for PHYLNK after some more time (which I did by adding a command to our debug interface), or read the interrupt pin on the ENC424J600. We do have the pin wired to a pin on our PIC32MZ, but the PIC pin is setup as input only, not change notification. Even so, monitoring the PIC input pin got the lib working well enough for the test; packets can be exchaged, but performance is low. So, while I still don't have answers to my questions above, I did figure out how to get past this issue. |
|
|
|
只有小组成员才能发言,加入小组>>
5238 浏览 9 评论
2028 浏览 8 评论
1950 浏览 10 评论
请问是否能把一个ADC值转换成两个字节用来设置PWM占空比?
3204 浏览 3 评论
请问电源和晶体值之间有什么关系吗?PIC在正常条件下运行4MHz需要多少电压?
2253 浏览 5 评论
777浏览 1评论
666浏览 1评论
有偿咨询,关于MPLAB X IPE烧录PIC32MX所遇到的问题
595浏览 1评论
PIC Kit3出现目标设备ID(00000000)与预期的设备ID(02c20000)不匹配。是什么原因
676浏览 0评论
576浏览 0评论
小黑屋| 手机版| Archiver| 电子发烧友 ( 湘ICP备2023018690号 )
GMT+8, 2024-12-23 05:39 , Processed in 1.127447 second(s), Total 78, Slave 62 queries .
Powered by 电子发烧友网
© 2015 bbs.elecfans.com
关注我们的微信
下载发烧友APP
电子发烧友观察
版权所有 © 湖南华秋数字科技有限公司
电子发烧友 (电路图) 湘公网安备 43011202000918 号 电信与信息服务业务经营许可证:合字B2-20210191 工商网监 湘ICP备2023018690号