USB Host Ethernet Driver

Windows 10 'Dos Box' cmd line from : ping 192.168.0.23 -n 1000 -l 465

Only saw it as first noted above today. All instances are always : MISCOMPARE at offset 22
Code:
Reply from 192.168.0.23: bytes=465 time=1ms TTL=64
Reply from 192.168.0.23: bytes=465 time=1ms TTL=64
Reply from 192.168.0.23: bytes=465 - MISCOMPARE at offset 22 - time=1ms TTL=64
Reply from 192.168.0.23: bytes=465 time=1ms TTL=64
Reply from 192.168.0.23: bytes=465 time<1ms TTL=64
 
Offset 22 seems to be the TTL number, not sure why that says its wrong.
 
Last edited:
Offset 22 seems to be the TTL number, not sure why that says its wrong.

Odd, it doesn't show what was received - and it hasn't ever shown on the 1465 long ping - but after using that here and before it suddenly is seeing that bad byte coming back?
 
I use Wireshark to view what’s received at the same time, and on Wireshark I went to byte 22 and it shows as the TTL value so maybe that can help diagnose the issue? I know on the MacOS terminal if ping receives something it doesn’t expect, it shows the original message and what was received, I’ve only had this happen once in the beginning because the code was wrong, but I fixed it. Now I only either drop a frame or receive it, I myself haven’t had any issues with any not matching up since the one time my code was wrong.
 
Found MS SysInternals tool PsPing here : https://docs.microsoft.com/en-us/sysinternals/downloads/psping

Does a FAST ping for 10 seconds here and completed 7,127 with I loss, and then 9680.

Two sets below - one had another ping running and was slow and this came out SerMon:
Message Recieve Error
Message Recieve Error

Code:
T:\T_Downloads\PSTools>psping -n 10s -q -i 0 192.168.0.23

PsPing v2.10 - PsPing - ping, latency, bandwidth measurement utility
Copyright (C) 2012-2016 Mark Russinovich
Sysinternals - www.sysinternals.com

Pinging 192.168.0.23 with 32 bytes of data:
10 seconds (1 warmup pings) connecting test: 100%

Ping statistics for 192.168.0.23:
  Sent = 7127, Received = 7126, Lost = 1 (0% loss),
  Minimum = 0.40ms, Maximum = 10.29ms, Average = 1.01ms

T:\T_Downloads\PSTools>psping -n 10s -q -i 0 192.168.0.23

PsPing v2.10 - PsPing - ping, latency, bandwidth measurement utility
Copyright (C) 2012-2016 Mark Russinovich
Sysinternals - www.sysinternals.com

Pinging 192.168.0.23 with 32 bytes of data:
10 seconds (1 warmup pings) connecting test: 100%

Ping statistics for 192.168.0.23:
  Sent = 9680, Received = 9680, Lost = 0 (0% loss),
  Minimum = 0.32ms, Maximum = 10.18ms, Average = 0.99ms

Here is a histogram of 10,000 pings:
Code:
T:\T_Downloads\PSTools>psping -n 10000 -h 20 -q -i 0 192.168.0.23

PsPing v2.10 - PsPing - ping, latency, bandwidth measurement utility
Copyright (C) 2012-2016 Mark Russinovich
Sysinternals - www.sysinternals.com

Pinging 192.168.0.23 with 32 bytes of data:
10001 iterations (warmup 1) ping test: 100%

Ping statistics for 192.168.0.23:
  Sent = 10000, Received = 10000, Lost = 0 (0% loss),
  Minimum = 0.35ms, Maximum = 11.19ms, Average = 1.00ms

Latency Count
0.35    1944
0.92    7907
1.49    52
2.06    17
2.63    23
3.20    8
3.77    7
4.34    6
4.91    11
5.48    5
6.05    5
6.62    7
7.19    2
7.76    2
8.34    0
8.91    3
9.48    0
10.05   0
10.62   0
11.19   1
 
I’m not sure what’s causing the message receive errors, I looked at one before and it was basically empty, a lot of zeros where there should’ve been data. So rather than lock up because it’s all zeros it just does nothing and prints the error to the serial monitor.
 
I trusted that as a tool to grab from MSFT - I don't seem to be able to control buffer size. Wasn't sure if it would - and if it would show error data.

Doing that FAST PING and then fBench {100*10@32767} caused some issues and long strings of the 'Message Receive Error'

where fBench had one bad group - and had to close?:
Code:
2.608	3,276,700	10,051.169
[B]0.403	589,806	11,695.460[/B]
2.611	3,276,700	10,040.443

But PsPing gave - two LONG lost packets and 9998 FAST ones:
Ping statistics for 192.168.0.23:
Sent = 10000, Received = 9998, Lost = 2 (0% loss),
Minimum = 0.40ms, Maximum = 5.79ms, Average = 1.10ms

Latency Count
0.40 9998
259.29 0
518.17 0
777.06 0
1035.95 0
1294.84 0
1553.72 0
1812.61 0
2071.50 0
2330.39 0
2589.27 0
2848.16 0
3107.05 0
3365.94 0
3624.82 0
3883.71 0
4142.60 0
4401.49 0
4660.37 1
4919.26 1
 
I wonder if there’s a way to see how full the buffer of the ASIX ram is, I’ll look into it and see if maybe that correlates with bad messages being received.
 
Running PING 465 and the large transfers I created this - then stopped wireshark capture and found this entry that seems applicable to : Reply from 192.168.0.23: bytes=465 - MISCOMPARE at offset 22 - time<1ms TTL=64

Code:
7769	22.676066	192.168.0.22	192.168.0.23	ICMP	507	Echo (ping) request  id=0x0002, seq=60941/3566, ttl=128 (no response found!)

Not sure if this shows right info usably?

wsk9_30.jpg

The same happened 12 pings before and couting up 12 pairs in wireshark log for messages that size I see the same thing

This goes out::
Code:
0000   00 50 b6 e2 25 ab 18 66 da 36 cc fd 08 00 45 00   .P..%..f.6....E.
0010   01 ed 8e aa 00 00 80 01 00 00 c0 a8 00 16 c0 a8   ................
0020   00 17 08 00 76 bf 00 02 ee 0d 61 62 63 64 65 66   ....v.....abcdef
0030   67 68 69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76   ghijklmnopqrstuv
0040   77 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f   wabcdefghijklmno
0050   70 71 72 73 74 75 76 77 61 62 63 64 65 66 67 68   pqrstuvwabcdefgh
0060   69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76 77 61   ijklmnopqrstuvwa
0070   62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70 71   bcdefghijklmnopq
0080   72 73 74 75 76 77 61 62 63 64 65 66 67 68 69 6a   rstuvwabcdefghij
0090   6b 6c 6d 6e 6f 70 71 72 73 74 75 76 77 61 62 63   klmnopqrstuvwabc
00a0   64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70 71 72 73   defghijklmnopqrs
00b0   74 75 76 77 61 62 63 64 65 66 67 68 69 6a 6b 6c   tuvwabcdefghijkl
00c0   6d 6e 6f 70 71 72 73 74 75 76 77 61 62 63 64 65   mnopqrstuvwabcde
00d0   66 67 68 69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75   fghijklmnopqrstu
00e0   76 77 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e   vwabcdefghijklmn
00f0   6f 70 71 72 73 74 75 76 77 61 62 63 64 65 66 67   opqrstuvwabcdefg
0100   68 69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76 77   hijklmnopqrstuvw
0110   61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70   abcdefghijklmnop
0120   71 72 73 74 75 76 77 61 62 63 64 65 66 67 68 69   qrstuvwabcdefghi
0130   6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76 77 61 62   jklmnopqrstuvwab
0140   63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70 71 72   cdefghijklmnopqr
0150   73 74 75 76 77 61 62 63 64 65 66 67 68 69 6a 6b   stuvwabcdefghijk
0160   6c 6d 6e 6f 70 71 72 73 74 75 76 77 61 62 63 64   lmnopqrstuvwabcd
0170   65 66 67 68 69 6a 6b 6c 6d 6e 6f 70 71 72 73 74   efghijklmnopqrst
0180   75 76 77 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d   uvwabcdefghijklm
0190   6e 6f 70 71 72 73 74 75 76 77 61 62 63 64 65 66   nopqrstuvwabcdef
01a0   67 68 69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76   ghijklmnopqrstuv
01b0   77 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f   wabcdefghijklmno
01c0   70 71 72 73 74 75 76 77 61 62 63 64 65 66 67 68   pqrstuvwabcdefgh
01d0   69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76 77 61   ijklmnopqrstuvwa
01e0   62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70 71   bcdefghijklmnopq
01f0   72 73 74 75 76 77 61 62 63 64 65                  rstuvwabcde

And this is received - that header repeat is not right?::
Code:
0000   [COLOR="#FF0000"]18 66 da 36 cc fd 00 50 b6 e2 25 ab 08 00 45 00[/COLOR]   [B].f.6...P..%...E.[/B]
0010   01 ed 32 cf 00 00 40 01 c4 c3 c0 a8 00 17 c0 a8   ..2...@.........
0020   00 16 00 00 3a 41 00 02 ee 0d 61 62 63 64 65 66   ....:A....abcdef
0030   67 68 69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76   ghijklmnopqrstuv
0040   70 71 72 73 74 75 76 77 61 62 63 64 65 66 67 68   pqrstuvwabcdefgh
0050   69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76 77 61   ijklmnopqrstuvwa
0060   62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70 71   bcdefghijklmnopq
0070   72 73 74 75 76 77 61 62 63 64 65 64 fb 01 04 f6   rstuvwabcded....
0080   [COLOR="#FF0000"]18 66 da 36 cc fd 00 50 b6 e2 25 ab 08 00 45 00[/COLOR]   [B].f.6...P..%...E.[/B]
0090   01 ed 32 cf 00 00 40 01 c4 c3 c0 a8 00 17 c0 a8   ..2...@.........
00a0   00 16 00 00 7e bf 00 02 ee 0d 61 62 63 64 65 66   ....~.....abcdef
00b0   67 68 69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76   ghijklmnopqrstuv
00c0   77 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f   wabcdefghijklmno
00d0   70 71 72 73 74 75 76 77 61 62 63 64 65 66 67 68   pqrstuvwabcdefgh
00e0   69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76 77 61   ijklmnopqrstuvwa
00f0   62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70 71   bcdefghijklmnopq
0100   72 73 74 75 76 77 61 62 63 64 65 66 67 68 69 6a   rstuvwabcdefghij
0110   6b 6c 6d 6e 6f 70 71 72 73 74 75 76 77 61 62 63   klmnopqrstuvwabc
0120   64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70 71 72 73   defghijklmnopqrs
0130   74 75 76 77 61 62 63 64 65 66 67 68 69 6a 6b 6c   tuvwabcdefghijkl
0140   6d 6e 6f 70 71 72 73 74 75 76 77 61 62 63 64 65   mnopqrstuvwabcde
0150   66 67 68 69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75   fghijklmnopqrstu
0160   76 77 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e   vwabcdefghijklmn
0170   6f 70 71 72 73 74 75 76 77 61 62 63 64 65 66 67   opqrstuvwabcdefg
0180   68 69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76 77   hijklmnopqrstuvw
0190   61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70   abcdefghijklmnop
01a0   71 72 73 74 75 76 77 61 62 63 64 65 66 67 68 69   qrstuvwabcdefghi
01b0   6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76 77 61 62   jklmnopqrstuvwab
01c0   63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70 71 72   cdefghijklmnopqr
01d0   73 74 75 76 77 61 62 63 64 65 66 67 68 69 6a 6b   stuvwabcdefghijk
01e0   6c 6d 6e 6f 70 71 72 73 74 75 76 77 61 62 63 64   lmnopqrstuvwabcd
01f0   65 66 67 68 69 6a 6b 6c 6d 6e 6f                  efghijklmno
 
I can see the ttl doesn't match, which would be offset 22 if that is what it was complaining about.
 
Looks like halfway through that message it starts from the beginning of the buffer again. I'm working on a fix for the receive errors so it can get the rest of the messages that are in there instead of discarding them all, it may fix that?
 
Alright I changed the error case so it looks for a new header in the error message and uses it if it finds one so not all the messages are lost now.
 
First was this before WS_capt
>> Reply from 192.168.0.23: bytes=465 - MISCOMPARE at offset 22 - time<1ms TTL=64

Then this - but I hit my finger too soon on stop :(
>> Reply from 192.168.0.23: bytes=465 - MISCOMPARE at offset 82 - time<1ms TTL=64

22 looks the same - will wait for an #88 or other again ...

Here is another #22 OUT>>
Code:
0000   00 50 b6 e2 25 ab 18 66 da 36 cc fd 08 00 45 00   .P..%..f.6....E.
0010   01 ed 44 91 00 00 80 01 00 00 c0 a8 00 16 c0 a8   ..D.............
0020   00 17 08 00 75 a9 00 02 ef 23 61 62 63 64 65 66   ....u....#abcdef
0030   67 68 69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76   ghijklmnopqrstuv
0040   77 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f   wabcdefghijklmno
0050   70 71 72 73 74 75 76 77 61 62 63 64 65 66 67 68   pqrstuvwabcdefgh
0060   69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76 77 61   ijklmnopqrstuvwa
0070   62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70 71   bcdefghijklmnopq
0080   72 73 74 75 76 77 61 62 63 64 65 66 67 68 69 6a   rstuvwabcdefghij
0090   6b 6c 6d 6e 6f 70 71 72 73 74 75 76 77 61 62 63   klmnopqrstuvwabc
00a0   64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70 71 72 73   defghijklmnopqrs
00b0   74 75 76 77 61 62 63 64 65 66 67 68 69 6a 6b 6c   tuvwabcdefghijkl
00c0   6d 6e 6f 70 71 72 73 74 75 76 77 61 62 63 64 65   mnopqrstuvwabcde
00d0   66 67 68 69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75   fghijklmnopqrstu
00e0   76 77 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e   vwabcdefghijklmn
00f0   6f 70 71 72 73 74 75 76 77 61 62 63 64 65 66 67   opqrstuvwabcdefg
0100   68 69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76 77   hijklmnopqrstuvw
0110   61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70   abcdefghijklmnop
0120   71 72 73 74 75 76 77 61 62 63 64 65 66 67 68 69   qrstuvwabcdefghi
0130   6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76 77 61 62   jklmnopqrstuvwab
0140   63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70 71 72   cdefghijklmnopqr
0150   73 74 75 76 77 61 62 63 64 65 66 67 68 69 6a 6b   stuvwabcdefghijk
0160   6c 6d 6e 6f 70 71 72 73 74 75 76 77 61 62 63 64   lmnopqrstuvwabcd
0170   65 66 67 68 69 6a 6b 6c 6d 6e 6f 70 71 72 73 74   efghijklmnopqrst
0180   75 76 77 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d   uvwabcdefghijklm
0190   6e 6f 70 71 72 73 74 75 76 77 61 62 63 64 65 66   nopqrstuvwabcdef
01a0   67 68 69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76   ghijklmnopqrstuv
01b0   77 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f   wabcdefghijklmno
01c0   70 71 72 73 74 75 76 77 61 62 63 64 65 66 67 68   pqrstuvwabcdefgh
01d0   69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76 77 61   ijklmnopqrstuvwa
01e0   62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70 71   bcdefghijklmnopq
01f0   72 73 74 75 76 77 61 62 63 64 65                  rstuvwabcde

And failed IN - looks similar::
Code:
0000   18 66 da 36 cc fd 00 50 b6 e2 25 ab 08 00 45 00   .f.6...P..%...E.
0010   01 ed 88 a6 00 00 40 01 6e ec c0 a8 00 17 c0 a8   ......@.n.......
0020   00 16 00 00 4f 3f 00 02 ef 23 61 62 63 64 65 66   ....O?...#abcdef
0030   67 68 69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76   ghijklmnopqrstuv
0040   63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70 71 72   cdefghijklmnopqr
0050   73 74 75 76 77 61 62 63 64 65 66 67 68 69 6a 6b   stuvwabcdefghijk
0060   6c 6d 6e 6f 70 71 72 73 74 75 76 77 61 62 63 64   lmnopqrstuvwabcd
0070   65 66 67 68 69 6a 6b 6c 6d 6e 6f 70 fb 01 04 f6   efghijklmnop....
0080   18 66 da 36 cc fd 00 50 b6 e2 25 ab 08 00 45 00   .f.6...P..%...E.
0090   01 ed 88 a6 00 00 40 01 6e ec c0 a8 00 17 c0 a8   ......@.n.......
00a0   00 16 00 00 7d a9 00 02 ef 23 61 62 63 64 65 66   ....}....#abcdef
00b0   67 68 69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76   ghijklmnopqrstuv
00c0   77 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f   wabcdefghijklmno
00d0   70 71 72 73 74 75 76 77 61 62 63 64 65 66 67 68   pqrstuvwabcdefgh
00e0   69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76 77 61   ijklmnopqrstuvwa
00f0   62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70 71   bcdefghijklmnopq
0100   72 73 74 75 76 77 61 62 63 64 65 66 67 68 69 6a   rstuvwabcdefghij
0110   6b 6c 6d 6e 6f 70 71 72 73 74 75 76 77 61 62 63   klmnopqrstuvwabc
0120   64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70 71 72 73   defghijklmnopqrs
0130   74 75 76 77 61 62 63 64 65 66 67 68 69 6a 6b 6c   tuvwabcdefghijkl
0140   6d 6e 6f 70 71 72 73 74 75 76 77 61 62 63 64 65   mnopqrstuvwabcde
0150   66 67 68 69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75   fghijklmnopqrstu
0160   76 77 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e   vwabcdefghijklmn
0170   6f 70 71 72 73 74 75 76 77 61 62 63 64 65 66 67   opqrstuvwabcdefg
0180   68 69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76 77   hijklmnopqrstuvw
0190   61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70   abcdefghijklmnop
01a0   71 72 73 74 75 76 77 61 62 63 64 65 66 67 68 69   qrstuvwabcdefghi
01b0   6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76 77 61 62   jklmnopqrstuvwab
01c0   63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70 71 72   cdefghijklmnopqr
01d0   73 74 75 76 77 61 62 63 64 65 66 67 68 69 6a 6b   stuvwabcdefghijk
01e0   6c 6d 6e 6f 70 71 72 73 74 75 76 77 61 62 63 64   lmnopqrstuvwabcd
01f0   65 66 67 68 69 6a 6b 6c 6d 6e 6f                  efghijklmno
 
I only saw update for FNET-master after last change?

Fail report of :: Reply from 192.168.0.23: bytes=465 - MISCOMPARE at offset 82 - time<1ms TTL=64

Is just the other end of the prior fail for #22.

Out ping: 19609 50.442781 192.168.0.22 192.168.0.23 ICMP 507 Echo (ping) request id=0x0002, seq=61461/5616, ttl=128 (no response found!)
Code:
0000   00 50 b6 e2 25 ab 18 66 da 36 cc fd 08 00 45 00   .P..%..f.6....E.
0010   01 ed 44 6a 00 00 80 01 00 00 c0 a8 00 16 c0 a8   ..Dj............
0020   00 17 08 00 74 b7 00 02 f0 15 61 62 63 64 65 66   ....t.....abcdef
0030   67 68 69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76   ghijklmnopqrstuv
0040   77 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f   wabcdefghijklmno
0050   70 71 72 73 74 75 76 77 61 62 63 64 65 66 67 68   pqrstuvwabcdefgh
0060   69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76 77 61   ijklmnopqrstuvwa
0070   62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70 71   bcdefghijklmnopq
0080   72 73 74 75 76 77 61 62 63 64 65 66 67 68 69 6a   rstuvwabcdefghij
0090   6b 6c 6d 6e 6f 70 71 72 73 74 75 76 77 61 62 63   klmnopqrstuvwabc
00a0   64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70 71 72 73   defghijklmnopqrs
00b0   74 75 76 77 61 62 63 64 65 66 67 68 69 6a 6b 6c   tuvwabcdefghijkl
00c0   6d 6e 6f 70 71 72 73 74 75 76 77 61 62 63 64 65   mnopqrstuvwabcde
00d0   66 67 68 69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75   fghijklmnopqrstu
00e0   76 77 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e   vwabcdefghijklmn
00f0   6f 70 71 72 73 74 75 76 77 61 62 63 64 65 66 67   opqrstuvwabcdefg
0100   68 69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76 77   hijklmnopqrstuvw
0110   61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70   abcdefghijklmnop
0120   71 72 73 74 75 76 77 61 62 63 64 65 66 67 68 69   qrstuvwabcdefghi
0130   6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76 77 61 62   jklmnopqrstuvwab
0140   63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70 71 72   cdefghijklmnopqr
0150   73 74 75 76 77 61 62 63 64 65 66 67 68 69 6a 6b   stuvwabcdefghijk
0160   6c 6d 6e 6f 70 71 72 73 74 75 76 77 61 62 63 64   lmnopqrstuvwabcd
0170   65 66 67 68 69 6a 6b 6c 6d 6e 6f 70 71 72 73 74   efghijklmnopqrst
0180   75 76 77 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d   uvwabcdefghijklm
0190   6e 6f 70 71 72 73 74 75 76 77 61 62 63 64 65 66   nopqrstuvwabcdef
01a0   67 68 69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76   ghijklmnopqrstuv
01b0   77 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f   wabcdefghijklmno
01c0   70 71 72 73 74 75 76 77 61 62 63 64 65 66 67 68   pqrstuvwabcdefgh
01d0   69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76 77 61   ijklmnopqrstuvwa
01e0   62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70 71   bcdefghijklmnopq
01f0   72 73 74 75 76 77 61 62 63 64 65                  rstuvwabcde

And other unmatched :: 19610 50.443599 192.168.0.23 192.168.0.22 ICMP 507 Echo (ping) reply id=0x0002, seq=61461/5616, ttl=64
Code:
0000   18 66 da 36 cc fd 00 50 b6 e2 25 ab 08 00 45 00   .f.6...P..%...E.
0010   01 ed bd a6 00 00 40 01 39 ec c0 a8 00 17 c0 a8   ......@.9.......
0020   00 16 00 00 4c 62 00 02 f0 15 61 62 63 64 65 66   ....Lb....abcdef
0030   67 68 69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76   ghijklmnopqrstuv
0040   77 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f   wabcdefghijklmno
0050   70 71 72 73 74 75 76 77 61 62 63 64 65 66 67 68   pqrstuvwabcdefgh
0060   69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76 77 61   ijklmnopqrstuvwa
0070   62 63 64 65 66 67 68 69 6a 6b 6c 6d fb 01 04 f6   bcdefghijklm....
0080   18 66 da 36 cc fd 00 50 b6 e2 25 ab 08 00 45 00   .f.6...P..%...E.
0090   01 ed bd a6 00 00 40 01 39 ec c0 a8 00 17 c0 a8   ......@.9.......
00a0   00 16 00 00 7c b7 00 02 f0 15 61 62 63 64 65 66   ....|.....abcdef
00b0   67 68 69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76   ghijklmnopqrstuv
00c0   77 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f   wabcdefghijklmno
00d0   70 71 72 73 74 75 76 77 61 62 63 64 65 66 67 68   pqrstuvwabcdefgh
00e0   69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76 77 61   ijklmnopqrstuvwa
00f0   62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70 71   bcdefghijklmnopq
0100   72 73 74 75 76 77 61 62 63 64 65 66 67 68 69 6a   rstuvwabcdefghij
0110   6b 6c 6d 6e 6f 70 71 72 73 74 75 76 77 61 62 63   klmnopqrstuvwabc
0120   64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70 71 72 73   defghijklmnopqrs
0130   74 75 76 77 61 62 63 64 65 66 67 68 69 6a 6b 6c   tuvwabcdefghijkl
0140   6d 6e 6f 70 71 72 73 74 75 76 77 61 62 63 64 65   mnopqrstuvwabcde
0150   66 67 68 69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75   fghijklmnopqrstu
0160   76 77 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e   vwabcdefghijklmn
0170   6f 70 71 72 73 74 75 76 77 61 62 63 64 65 66 67   opqrstuvwabcdefg
0180   68 69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76 77   hijklmnopqrstuvw
0190   61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70   abcdefghijklmnop
01a0   71 72 73 74 75 76 77 61 62 63 64 65 66 67 68 69   qrstuvwabcdefghi
01b0   6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76 77 61 62   jklmnopqrstuvwab
01c0   63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70 71 72   cdefghijklmnopqr
01d0   73 74 75 76 77 61 62 63 64 65 66 67 68 69 6a 6b   stuvwabcdefghijk
01e0   6c 6d 6e 6f 70 71 72 73 74 75 76 77 61 62 63 64   lmnopqrstuvwabcd
01f0   65 66 67 68 69 6a 6b 6c 6d 6e 6f                  efghijklmno

SerMon has this added text:
Code:
Benchmark results:
Megabytes: 3.275800
Seconds: 2.7480
Bytes/Sec: 1192066.9578
KBytes/Sec: 1192.0670
KBits/Sec: 9536.5357

[B]Message Recieve Error, searching for next header
Error: No new header found[/B]
Benchmark results:
Megabytes: 3.275800
Seconds: 2.7660
Bytes/Sec: 1184309.4722
KBytes/Sec: 1184.3095
KBits/Sec: 9474.4758

[B]Message Recieve Error, searching for next header
Error: No new header found
Message Recieve Error, searching for next header
Error: No new header found[/B]
Benchmark results:
Megabytes: 3.275800
Seconds: 2.7000
Bytes/Sec: 1213259.2593
KBytes/Sec: 1213.2593
KBits/Sec: 9706.0741
 
Note before said some PING sizes acted odd? Maybe 465 is triggering one of those? It happens with regularity when doing the fBench. Size 32758 now instead of 32768 - but it showed initially with smaller sizes IIRC.
 
Yeah the added text is to let you know if there was any extra information in the error packet that gets flagged. For some reason some messages get padded with extra 0’s so it throws the length off which wouldn’t be a problem if there weren’t multiple messages in some usb packets. So the error loops through the extra zeros to see if there is another message header or not and proceeds to process the message if it’s found.
 
As far as 465 bytes causing an error, I know that is the first ping size that was being split into multiple usb packets when I had the buffer set to 512 bytes originally, but now the buffer is bigger so it shouldn’t be getting split apart. Even if it did get split apart it should be reconstructed properly.
 
That is odd that I found a combo that is hitting errors with regularity. Let me know if there is anything else I can get from Wireshark logging to give info.

Just looked and the USB/LAN is "Hi-Speed Full 10/100 Mbps Ethernet " - is it connecting in 10 or 100 I wonder. Seeing speeds of 9-11 Mbps is either maxing out 10 or barely touching 100 Mbps?
 
That’s a good point about connection speed, I’ll make a function to print that when it connects to to a network and find out.
 
Scratch that, it is operating at 100BASE-T so there is a bottleneck somewhere.
 
Last edited:
So interesting results...
Code:
10:48:56.546 -> Benchmark results:
10:48:56.546 -> Megabytes: 0.32767
10:48:56.546 -> Seconds: 0.0060
10:48:56.546 -> Bytes/Sec: 5461166.5000
10:48:56.546 -> KBytes/Sec: 5461.1665
10:48:56.546 -> KBits/Sec: 43689.3320
 
@vjmuzik - T4 sitting IDLE here - and spitting these out. About 40 times - thought I saw them so cleared SerMon and left it last night
Code:
Message Recieve Error, searching for next header
Error: No new header found
Message Recieve Error, searching for next header
Error: No new header found
Message Recieve Error, searching for next header
Error: No new header found
...

Of course Wireshark shows tons of local net traffic - queries from Router etc - so likely just something not understood.? Turned on WS_capture with filter 'ip.src == 192.168.0.23 || ip.dst == 192.168.0.23' to see if there is a net event. Seems another occurred while typing this and setting up WS. Of course the LAN switch might direct that traffic to the T4's port without desktop seeing it? I see another of those in SerMon and nothing on WireShark capture.

Good it is setting up for 100BASE-T - my switch light does show 'Yellow' suggesting 100 - but wasn't sure it has a color for 10Mbps. Shows room for speed increase.

The "10:48:56.546 -> KBits/Sec: 43689.3320" above looks good - but wondering if it is just an anomoly with time calc across the multipart message? Not yet seen T4 system here not over 14Mbps?
 
Yeah the value seems inconsistent at best, I’ve hit around the same number a couple of times but it’s definitely an anomaly. Most of my tests come back ranging from 5-10Mbit/sec so it’s still an improvement over a w5500, but not quite as much as I was hoping for.
 
Back
Top