All Colibri Module comes with one compatible Ethernet interface(10/100Mbps). There is an option of adding a second Ethernet on Memory bus / USB / RMII. Adding another Ethernet port using external USB based Ethernet controller is simple to implement and will be compatible across the Colibri modules. Memory bus implementation of Ethernet is slightly more complex to implement and involve driver modification for Ethernet to work. The memory bus is also not available on all the modules. RMII feature is available only on Vybrid modules and is not compatible with the rest of the Colibri family.
Below is the list for Ethernet controller on Colibri PXAxx
Product Name Controller REGBASEKEY --------------------------------------------------------------- Colibri PXA270 Vx.x <-> DM9000 -> [HKLM\Comm\DM90001] Colibri PXA300 (XT) Vx.x <-> AX88796(B) -> [HKLM\Comm\AX887961] Colibri PXA310 Vx.x <-> AX88796(B) -> [HKLM\Comm\AX887961] Colibri PXA320 V1.x <-> AX88796(B) -> [HKLM\Comm\AX887961] Colibri PXA320 V2.x <-> AX88796C -> [HKLM\Comm\AX88796C1] Protea External NIC <-> AX88796(B) -> [HKLM\Comm\AX887962]
For more information go through this article.
The Colibri T20, Colibri T30 and Apalis T30 have built-in drivers for the USB attached Ethernet controller AX88772B.
Adding a 2nd Ethernet controller of the same type is as simple as adding a few registry keys:
[HKEY_LOCAL_MACHINE\Comm\AX88772B\Linkage] "Route"=multi_sz:"AX88772B1","AX88772B2" [HKEY_LOCAL_MACHINE\Comm\AX88772B2] "DisplayName"="ASIX AX88772B USB 2.0 Fast Ethernet Driver" "Group"="NDIS" "ImagePath"="AX88772B.dll" [HKEY_LOCAL_MACHINE\Comm\AX88772B2\Parms] "BusNumber"=dword:0 "BusType"=dword:1
Starting in Image V1.1Beta4, these settings are already included in the default registry.
2nd Ethernet controller can be connected over USB interface.
Colibri i.MX6 modules don't have built-in drivers for the USB attached Ethernet controller AX88772B, but user can install the driver from this cab installer for CE6 and WEC7 or WEC2013.
Colibri VF50 and Colibri VF61 have built-in RMII attached Ethernet controller.
2nd Ethernet controller can be connected over USB or RMII interface.
Colibri VFxx modules don't have built-in drivers for the USB attached Ethernet controller AX88772B, but user can install the driver from this cab installer for CE6 and WEC7 or WEC2013.
The Vybrid processor mounted on VF50 and VF61 modules provide a second Ethernet interface that could be enabled in Windows CE. The RMII interface is available on SO-DIMM pins as described in the product datasheet. Please use the link below to download the reference schematics and CAE data for RMII based Ethernet:
NOTE: This feature is not compatible with other modules in the Colibri family.
To enable the second Ethernet interface the following entries should be added to the device registry. After editing, save the registry and reboot the system to activate the settings.
[HKEY_LOCAL_MACHINE\Comm\1ENET] "DisplayName"="ENET Ethernet Driver" "Group"="NDIS" "ImagePath"="enet.dll" "Index"=dword:0 [HKEY_LOCAL_MACHINE\Comm\1ENET\Linkage] "Route"=multi_sz:"ENET1" [HKEY_LOCAL_MACHINE\Comm\ENET1] "DisplayName"="ENET Ethernet Driver" "Group"="NDIS" "ImagePath"="enet.dll" [HKEY_LOCAL_MACHINE\Comm\ENET1\Parms] "BusNumber"=dword:0 "BusType"=dword:0 ; DuplexMode: 0:AutoDetect; 1:HalfDuplex; 2:FullDuplex. "DuplexMode"=dword:0 [HKEY_LOCAL_MACHINE\Comm\ENET1\Parms\TcpIp] ; This should be MULTI_SZ "DefaultGateway"="" ; This should be SZ... If null it means use LAN, else WAN and Interface. "LLInterface"="" ; Use zero for broadcast address? (or 255.255.255.255) "UseZeroBroadcast"=dword:0 ; Thus should be MULTI_SZ, the IP address list "IpAddress"="0.0.0.0" ; This should be MULTI_SZ, the subnet masks for the above IP addresses "Subnetmask"="0.0.0.0" "EnableDHCP"=dword:1 [HKEY_LOCAL_MACHINE\Comm\TcpIp\Parms] ;Set to True to keep the device from entering idle mode if there's network adapter ;;"NoIdleIfAdapter"=dword:1 ;Set to True to keep the device from entering idle mode while communicating/loop back "NoIdleIfConnected"=dword:1 [HKEY_LOCAL_MACHINE\Comm\Tcpip\Linkage] ; This should be MULTI_SZ ; This is the list of llip drivers to load "Bind"=multi_sz:"ENET1","ENET2"
You can even follow the procedure mention below to directly import registry settings: