W5100 Status Register Sn_SR unspecific value has been responsed
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: W5100 Status Register Sn_SR unspecific value has been responsed
by Eugeny ·
Hello Kazuhito-san, it is more important what happens after you see this code.
My guess is that it is one of the codes in the list while socket is being closed.
[quote]0x18 SOCK_FIN_WAIT
0x1A SOCK_CLOSING
0X1B SOCK_TIME_WAIT
0X1D SOCK_LAST_ACK
It is shown in the process of connection termination. If the
termination is normally processed or Timeout interrupt is
asserted, it will be automatically changed to SOCK_CLOSED.[/quote]
Wait for some time, and you should see SOCK_CLOSED (0x00) in this register. However if 0x1E happens to be for “quite some time”, then something is going wrong. In general your question is very related to what I asked in [url]Connection termination process problem!]. I decided NOT to use interrupts, but status codes instead.
So far it works this way.
RE: W5100 Status Register Sn_SR unspecific value has been responsed
by ogawakazuhito ·
Hello Eugeny-san
Very Thanksful for your kindness.
Your advice is very important and nice.
In the end, I have a solution for my problem by retrying reading repeatedly status register untill getting SOCK_CLOSED code(0x00).
As I mention about these in detail that
1)When W5100 is disconnecting TCP and closing socket by itself, these close procedure is performing very smoothly with a little time.
2)When the Server application is disconnecting TCP voluntarily, the disconnecting and closing procedure in W5100 is tough to complete
and is having over very long time such as about 2 ro 3 minutes, and more I am getting this undesirable code 0x1E.
3)W5100 is having some unfavorable actions such as having a long time response for reflecting its status to status register
when W5100 is exposed in noisy environments such as Relay Noise. W5100 is very poor in terms of noise tolerance compared to another IC.
Happy christmas for you
RE: W5100 Status Register Sn_SR unspecific value has been responsed
by Eugeny ·
和人さん、[url][SOLVED] W5100 Sn_CR_DISCON Time]ページを見て下さい。Server modeで、DISCONの終わることが待たないかも知れません。和人さんもよいお年をおめでとうございます!