) provide a configuration
eeprom for the LAN7800 chip. The factory setting for this chip were taken from the Microchip Lan7800
evaluation board with two modifications. 1. The assigned MAC address for the carrier board has been
added to the eeprom. 2. The default led functions have been enabled but are only useful for debugging
purposes when the cover is removed from the case. While it is possible for the end-user to reprogram this
eeprom, Curtiss Wright does not provide support for this action.
Product shipped before December 26th 2019 did not include the LAN7800 eeprom. The LAN7800
does not work well without a MAC address assigned at initialization. The result is that early units
require configuration in "/etc/network/interfaces" which gives a MAC address to the LAN chip early
enough to allow proper function.
If you modify the /etc/network/interfaces file ensure that a Line is included in the definitions for eth1 (the
LAN7800 port) defining the MAC address. Your MAC address can be found in the
/etc/C312/version.yml file.
Example:
iface eth1 inet static
hwaddress AA:BB:CC:DD:EE:FF
address 192.168.1.55
network 192.168.1.0
netmask 255.255.255.0
gateway 192.168.1.1
When there is a configuration in the interfaces file, Network Manager will ignore the /dev/eth1 port. There
is no other supported configuration for the early release boards. However there is a possible customer
self-support option to improve the eth1 configuration on early board revisions.
This self support fix requires programming the LAN7800 internal One-Time-programmable eprom using
ethtool. You must modify an appropriate image for the LAN7800 OTP with the correct MAC address
for the specific board. Because it is a OTP device there is some risk to this process. Programming an
incorrect image may render the eth1 port unusable. Double check your work at every step. The
eeprom image from the LAN7800 evaluation board from Microchip is known to configure the LAN7800
in an acceptable base configuration but was not used as a factory image for OTP programming
because Curtiss Wright has too little experience with it to recommend it as a final configuration image
for use in the OTP eprom. Curtiss Wright does not currently provide programming information to do
this task.
To Next Page
Loading...
