W7500P Ethernet/UDP Transmit Delay
MCU & Boards
No replies yet. Be the first to reply.
Join the discussion.
MCU & Boards
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: W7500P Ethernet/UDP Transmit Delay
by joaopaulob ·
I have some issues like that. Any solutions let me know.
RE: W7500P Ethernet/UDP Transmit Delay
by arthurbe ·
not sure if this is your case but you can try to define the DHAR register in the TOE
then use Sn_CR_SEND_MAC instead Sn_CR_SEND
in sendto library call
RE: W7500P Ethernet/UDP Transmit Delay
by kralcllib ·
Wiznet sent me updated W7500x_miim.c and .h files that fix the issue. Not sure exactly why, but the previous code used a hard PHY address and the PHY was not being initialized. The new code somehow extracts the PHY address from the PHY and allows initialization.
RE: RE: W7500P Ethernet/UDP Transmit Delay
by joaopaulob ·
Hi,
Could you share the code?
Thanks
RE: W7500P Ethernet/UDP Transmit Delay
by kralcllib ·
The code is at:
RE: RE: W7500P Ethernet/UDP Transmit Delay
by joaopaulob ·
Hi,
The last commit is a year ago. I’ve been using this code.
Is this code solved your problem?
REgards
RE: W7500P Ethernet/UDP Transmit Delay
by kralcllib ·
It did solve my problem. But, there is a hardware fix for a related problem. It had something to do with the network not working at 100Mbps. The new W7500P revision was released in early August, 2017. If your chip is older than this, you should investigate this fix.