Forum Discussion

yzhan286's avatar
yzhan286
Icon for New Contributor rankNew Contributor
6 years ago

三速以太网IP核接收路径的用户侧少了一个字节

我在使用intel三速以太网IP核时，按照用户手册编写了MAC的配置模块，UDP发送模块和UDP接收模块，目前的发送模块已经测试成功，但是接收模块出现了问题，就是接收模块在对MAC的用户侧(ff_rx_data)数据解析时不成功，为了分析原因，用quartus II中的SignalTap抓取SignalTap抓取ff_rx_data信号，发现数据包的头部少了一个字节，导致了后面所有的数据错位。 ...
Deshi_Intel's avatar
Deshi_Intel
Icon for Regular Contributor rankRegular Contributor
6 years ago

Hi,

Thanks. I understand your problem statement now.

  • You are sending broadcast address FF:FF:FF FF:FF:FF
  • But Signal_Tap only captured FF:FF:FF FF:FF, looks like last 2 bytes of FF is missing

Couple debug suggestion

  1. Align packet headers to 32-bit boundary is enabled
  2. Align packet headers to 32-bit boundary is disabled
  3. Have you enabled TSE IP statistic counter option and read on register (Dword Offset 0x18 – 0x38) to check on potential error ?
  4. Did you also monitor TSE IP "status LED signals" to check for potential error ?
  5. Do you observed TSE RX FIFO underflow or overflow issue ?
  6. Do you still see similar issue when sending unicast address instead of broadcast address ?
  7. Do you still see similar issue when sending TCP/IP instead of UDP packet ?
  8. Lastly, would you be able to perform TSE IP internal loopback testing to isolate external factor issue ?
  • ff_tx -> TSE MAC -> ff_rx

Thanks.

Regards,

dlim

  • yzhan286's avatar
    yzhan286
    Icon for New Contributor rankNew Contributor
    6 years ago

    您好！

    再次感谢您的回复，我在您给的建议下做了如下的测试：

    1.使用了本地回环模式即TX->TSE MAC->RX，这个现象依然存在，FIFO端口用的32bit

    2.在FIFO宽度设置为8bit的模式下使用本地回环，依然还有这种现象。

    3.没有发单播数据报和TCP/IP报，因为我的调试软件在没有知道TSE MAC的MAC地址时不能发送单播报文。

    4.FIFO用32bit，不采用​Align packet headers to 32-bit boundary ，也有这种现象。

    我把我的工程发给您一下。

    软件版本是Quartus II13.0 SP1(64bit)​

    再次非常感谢​