Posted by Grommish on Jan 05, 2021; 6:28pm
URL: https://itus.accessinnov.com/FIRMWARE-Itus-Shield-v2-tp2014p2168.html

Interesting development and I'm not sure how/where to attribute this (I'm still testing).

I was having issues loading an image and the system would not pickup a DHCP address on eth0.  We've seen this issue in the past and were never able to track it down.  After blowing the Shield up to the point I am having to TFTP a rescue image, I noticed I have any issues with the network port IN THE FIRMWARE..  Eh, this is new?

I've tracked it down to the following: If the Shield is booted with a cable plugged into Eth1, the ports will never work.  If you unplug the Eth1 cable (Eth0/Eth2 seem fine) it boots fine. It's either a CABLE issue or a FIRMWARE issue.  I'm testing the cable as soon as I can, but I wonder if anyone wants to try and confirm this on their device?  Simply put, cold-boot with a cable not plugged into Eth1, make sure it works..  Plug eth1 in, reboot..  If this works as a bug, eth0 will NOT have an IP address.  If so, unplug, reboot and see if the IP on eth0  comes back up.

Just as a FYI if you get issues with picking up a DHCP address, try that :)