Wiznet W5300 data stuck in TX buffer
Ethernet Chips
No replies yet. Be the first to reply.
Join the discussion.
Ethernet Chips
No replies yet. Be the first to reply.
Join the discussion.
Share projects and connect with makers.
Joined before the site update? first.
New to WIZnet Makers?
We sent a verification link to your address. Open it to activate your account, then log in.
Accounts from this email provider are reviewed by an administrator after verification. Approval usually takes one business day.
Already have an account?
Enter your email address. If it belongs to an account, we'll send a link to set a new password. Members who joined before the site update use this to set their password.
If an account uses that address, we sent a link to set a new password. The link works once and expires in 30 minutes.
Know your password?
Need an account?
RE: Wiznet W5300 data stuck in TX buffer
by Eugeny ·
Wireshark output of the session would help to see what is going on the network - in both cases.
RE: Wiznet W5300 data stuck in TX buffer
by Aleksandr N ·
Thanks for quick response! Here the WS output sessions. I checked both cases again, fixed some errors and find out, that data get stuck in TX buffer when WR time is less than 4 FPGA tacts (160 ns).
I send 32 bit counter data to PC. Device IP is 192.168.0.2, port is 5000, packet size is 512 bytes. If WR time is less than 4 tact, almost all data are sended correctly except last 12-13 KBytes. When WR time increases to 4 tact, all data are sended correctly.
PS: Files with “.pcapng” aren’t allowed to upload, so I add “.pdf” after their name.
wr_time_120_ns.pcapng.pdf (1,5 МБ)
wr_time_160_ns.pcapng.pdf (1,5 МБ)
RE: RE: Wiznet W5300 data stuck in TX buffer
by Eugeny ·
I do not see anything wrong in the wireshark logs, looks like W5300 just does not send the data. Your application thinks that data is sent, judging by looking at the activity on port 5001.
RE: Wiznet W5300 data stuck in TX buffer
by Aleksandr N ·
Sorry for slow response, I managed to go back to that job only now.