The primary power for the ARMweb is 3.3V provided from a linear regulator. The input power for the PCB may be 5V regulated supply or a 6-9V unregulated supply, with a current rating of 250 mA or more. The connector is a standard 2.5mm barrel connector with the + positive side of the supply in the center. A good choice for this power is this 5V regulated supply from SparkFun .
You should see a green LED connect light on the lower left side of the Ethernet cable indicate a connection was made. Also your hub normally has a similar type of connection indicator. There should also be some traffic indicated on the right side as the ARMweb looks for a DHCP.
If you don't see the LEDs lit, check your power connections (you should see at least 6V of the + side marked on C1 with an unregulated supply or 5V with a regulated supply, and 3.3V as marked in the prototype area).
For the mbed LPC1768 power can be supplied from the USB port. The picture above shows the Ethernet connection using a breakout board from Cool Components (unfortunately no longer in production). The Ethernet connection can also be made with a MAGJACK breakout board or mbed Application board from SparkFun.
We recommend that you have at least one USB connection to debug BASIC programs as well as network issues. This can be our USB dongle (specific ARMweb version when ordering separately) or some other TTL serial connection. Details on making the USB connection here.
Below is the picture you should see. Depending on which version of firmware and which USB dongle you may see an EINT1 interrupt message. EINT1 was being used for network debug in earlier firmware versions. You should disable that by choosing ARMweb control under the Options. After that you should see the ARMweb "Searching for DHCP" and if there is one it will report the DHCP IP address and the IP address assigned by the DHCP (MyIP)
Again, if you don't see the LEDs or this display, check your power connections (you should see at least 6V of the + side marked on C23, and 3.3V as marked in the prototype area), check your com connections (details in Troubleshooting section ).
The ARMweb will configure itself with an IP address assigned by a DHCP server. IP addresses are the way networks organize themselves. If there is no DHCP server found, the ARMweb can provide limited DHCP services in a Diagnostic mode, assuming a single connection on Ethernet with a PC using either a hub or cross-over cable (see the Diagnostic section below).
Assuming a DHCP server is available and you are running on a Windows machine, you can use the Windows NetBIOS Name Service. In which case you can find the ARMweb initially with http://armweb. Note that some administrators disable NetBIOS name service .
Finding the card using the DHCP server
On most home networks your DHCP will be your internet connection, and its address will share the first 3 bytes with the IP address of your PC. And the final byte being 1. The IP address of your PC is available from the control panel or by typing IPCONFIG at a DOS command line. Common values for the DHCP server are 192.168.1.1 or 192.168.0.1 as in the example below.
You can navigate to the DHCP server using that IP address from a browser as below.
Most DHCP servers will list client machines which have been assigned an IP address. This 2wire server indicates it on the details view of the home network, and details for the device
Another example is the display from a Dlink Firewall that is also providing DHCP services.
So in this case the ARMweb can be found at http://192.168.0.2
Now that you have the IP address of the ARMweb
You can go onto configuration settings, or writing simple programs using the web interface (the web interface is only meant for simple programs, to do more extensive programs will require a USB connection and BASICtools.
But for this web interface navigate using a browser to http://w.x.y.z where w.x.y.z is the IP address of the ARMweb
DHCP assignment vs. fixed IP addressing
We routinely allow the DHCP server to assign an initial address, but will use a fixed IP address in the final setup. One reason to assign a fixed IP, is to make sure that the IP address assigned never changes, for instance following a power outage. Details on setting a fixed IP address.