We've progressed with this. Added back wifi after a few warnings from my mentor about increased latency. Anyway, does not seem to have been much of an impact.
Finally got the N2+ connected to a MEsa 7i76e!
Ping times are very good
Code:
Ping:
odroid@odroidn2:~$ ping 10.10.10.1
PING 10.10.10.1 (10.10.10.1) 56(84) bytes of data.
64 bytes from 10.10.10.1: icmp_seq=1 ttl=64 time=0.075 ms
64 bytes from 10.10.10.1: icmp_seq=2 ttl=64 time=0.081 ms
64 bytes from 10.10.10.1: icmp_seq=3 ttl=64 time=0.081 ms
--- 10.10.10.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2032ms
rtt min/avg/max/mdev = 0.075/0.079/0.081/0.003 ms
Its possible this can be improved as Armbian is using a generic NIC driver but its not a high priority.
I got a couple of latency errors and smart serial overuns with QTplasmac
But when I investigated with htop which shows cpu utilisation by core, these are only happening when one core on the CPU sometimes briefly hits 100 CPU utilisation on startup.
These errors do not happen with axis.
This confirms my belief I've had for a while that the modern GUIS are adding additional load on the CPU which exacerbates latency in modern kernels. So all in all, this is a useable board as long as you don't browse internet when cutting a part.
