Below I will explain how it fails, and why. And I have found some very interesting things…įirst of all, here’s the picture of “faulty” session. Then I started to dig into the communication. No, I was unable to find anything material. I was digging into my chip’s driver for a while, hoping to find issue in the code. Other computers on the same network segment work, do not hang or abort their TCP sessions. However it is not a point that something has failed and WIZnet has no relation to it. My guess is that something has changed on the route from server to WIZnet chip, causing such behavior. In arbitrary time during communication, playback process stops, activity TX/RX LEDs turn off, and application hangs. The process was completely operable for a long time, but about 1.5 months ago, something has changed. But the issue makes TCP session completely inoperable, socket and process hangs.īackground: the task application is performing download of about 6 Megabytes of data (to be precise - plays PCM data through DAC). It would be not a very big deal if there would be small drop in performance.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |