Finally, a working g_ether module for the WIZ. This makes it much easier possible to use the WIZ for development.
You can now copy your compiled programs directly to the WIZ, run them and check their debug output.
1. Run the 'NetworkUp.gpe' script from the Launcher.
The NetworkUp.gpe script will configure the usb0 interface with '10.0.0.2/24'. I guess I didn't have to use a /24 but it is easier to type on the host side slightly.
2. Now on the host side, check 'dmesg', and then configure the host side of the interface so the two can speak (automating this step depends largely on host OS and is up to you):
usb 5-2: new full speed USB device using ohci_hcd and address 18
usb 5-2: not running at top speed. connect to a high speed hub
usb 5-2: new device found, idVendor=049f, idProduct=505a
usb 5-2: new device strings: Mfr=1, Product=2, SerialNumber=0
usb 5-2: Product: OpenWiz Ethernet
usb 5-2: Manufacturer: Linux 2.6.24/lf1000_udc
usb 5-2: configuration #1 chosen from 1 choice
usb 5-2: unsupported MDLM descriptors
usb0: register 'cdc_subset' at usb-0000:00:13.4-2, Linux Device, 76:63:3c:8b:35:72
# ifconfig usb0 inet 10.0.0.1 netmask 255.255.255.0
# ping 10.0.0.2
PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data.
64 bytes from 10.0.0.2: icmp_seq=1 ttl=64 time=4.69 ms
64 bytes from 10.0.0.2: icmp_seq=2 ttl=64 time=0.986 ms
64 bytes from 10.0.0.2: icmp_seq=3 ttl=64 time=0.959 ms
At this stage, the Wiz is attached to the host by networking. What network applications to build, install, or configure, and how to use them, is a howto for another day.
Note that again while the LF1000 device is in use, the Wiz cannot be used as a block device to mount the SDRAM or NAND devices. To remove the g_ether module and restore these functions while the Wiz is running, simply run the NetworkDown.gpe script included in the same directory. This will take the Wiz off network. You may also safely simply restart the Wiz.
You can now copy your compiled programs directly to the WIZ, run them and check their debug output.
1. Run the 'NetworkUp.gpe' script from the Launcher.
The NetworkUp.gpe script will configure the usb0 interface with '10.0.0.2/24'. I guess I didn't have to use a /24 but it is easier to type on the host side slightly.
2. Now on the host side, check 'dmesg', and then configure the host side of the interface so the two can speak (automating this step depends largely on host OS and is up to you):
usb 5-2: new full speed USB device using ohci_hcd and address 18
usb 5-2: not running at top speed. connect to a high speed hub
usb 5-2: new device found, idVendor=049f, idProduct=505a
usb 5-2: new device strings: Mfr=1, Product=2, SerialNumber=0
usb 5-2: Product: OpenWiz Ethernet
usb 5-2: Manufacturer: Linux 2.6.24/lf1000_udc
usb 5-2: configuration #1 chosen from 1 choice
usb 5-2: unsupported MDLM descriptors
usb0: register 'cdc_subset' at usb-0000:00:13.4-2, Linux Device, 76:63:3c:8b:35:72
# ifconfig usb0 inet 10.0.0.1 netmask 255.255.255.0
# ping 10.0.0.2
PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data.
64 bytes from 10.0.0.2: icmp_seq=1 ttl=64 time=4.69 ms
64 bytes from 10.0.0.2: icmp_seq=2 ttl=64 time=0.986 ms
64 bytes from 10.0.0.2: icmp_seq=3 ttl=64 time=0.959 ms
At this stage, the Wiz is attached to the host by networking. What network applications to build, install, or configure, and how to use them, is a howto for another day.
Note that again while the LF1000 device is in use, the Wiz cannot be used as a block device to mount the SDRAM or NAND devices. To remove the g_ether module and restore these functions while the Wiz is running, simply run the NetworkDown.gpe script included in the same directory. This will take the Wiz off network. You may also safely simply restart the Wiz.