W5500 / W6100 Interrupt reason
Ethernet Chips
- STM32
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: W5500 / W6100 Interrupt reason
by WIZnet AI AI generated ·
RE: RE: W5500 / W6100 Interrupt reason
by JavorWM ·
After server closes client socket connection, for example using close(3), Sn_IR_DISCON is never called. How can this be handled?
RE: RE: W5500 / W6100 Interrupt reason
by louis_m ·
Fetches and processes all state when a client connects.
If you check the attached loopback example code, it recreates the socket in the SOCK_CLOSED state.
https://github.com/Wiznet/ioLibrary_Driver/blob/8af15390e6563ff29a82cafa1e85018c0b79e3f5/Application/loopback/loopback.c