...
Let's test the TCP/IP stack on the i.MX RT1050RT10XX.
From the development host validate that the i.MX RT1050 target is visible using ping:
| Code Block |
|---|
$ ping -c 5 192.168.1.86 PING 192.168.1.86 (192.168.1.86) 56(84) bytes of data. 64 bytes from 192.168.1.86: icmp_seq=1 ttl=64 time=20.7 ms 64 bytes from 192.168.1.86: icmp_seq=2 ttl=64 time=5.72 ms 64 bytes from 192.168.1.86: icmp_seq=3 ttl=64 time=5.84 ms 64 bytes from 192.168.1.86: icmp_seq=4 ttl=64 time=5.72 ms 64 bytes from 192.168.1.86: icmp_seq=5 ttl=64 time=6.30 ms --- 192.168.1.86 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4005ms rtt min/avg/max/mdev = 5.715/8.851/20.692/5.924 ms |
ping the development host from the i.MX RT1050target:
| Code Block |
|---|
/ # ping -c 5 192.168.1.89 PING 192.168.1.89 (192.168.1.89): 56 data bytes 64 bytes from 192.168.1.89: seq=0 ttl=64 time=4.916 ms 64 bytes from 192.168.1.89: seq=1 ttl=64 time=5.071 ms 64 bytes from 192.168.1.89: seq=2 ttl=64 time=5.286 ms 64 bytes from 192.168.1.89: seq=3 ttl=64 time=5.226 ms 64 bytes from 192.168.1.89: seq=4 ttl=64 time=5.595 ms --- 192.168.1.89 ping statistics --- 5 packets transmitted, 5 packets received, 0% packet loss round-trip min/avg/max = 4.916/5.218/5.595 ms |
...