Professional Documents
Culture Documents
Chapter 3
112
Hardware: Lantronix offers its Device Servers in a variety of packages,
including devices in enclosures, circuit boards and chips for incorporating
into other devices, and a server squeezed into a slightly extended RJ-45 connect
or.
Each server has a TTL-compatible asynchronous serial port for communicating
with an external device or system and an RJ-45 connector for
connecting to an Ethernet network. Firmware is stored in Flash ROM. The
CPU varies depending on the product. Two of the options are AMD s
AMD186ES and Lantronix s DSTni-LX, which contains a CPU, serial
ports, Ethernet controller, and RAM.
Software: The Device Servers contain firmware to support Ethernet and
Internet protocols, including UDP, TCP, IP, and HTTP. User firmware
manages communications between the serial port and the server. For programming,
the DSTni-LX Development kit includes a development board
and the Paradigm C++ Professional development toolkit. The USNET
TCP/IP software suite and a real-time operating system are also available
separately for use in your own hardware. USNET is compatible with Intel
80x86, Motorola 68K, and other microprocessors. Source code is included.
Ubicom IP2022 Wireless Network Processor
At a glance: A CPU optimized for networking with software-configurable
peripherals and wireless support.
Typical use: Web servers and wireless networking
Ethernet support: 10BASE--T
Source: Ubicom, Inc. (www.ubicom.com)
Hardware. Ubicom s IP2022 Wireless Network Processor is a CPU optimized
for networking functions. The chip contains two configurable Serializer/
Deserializer blocks. Using software modules provided by Ubicom, each
block can support Ethernet, USB, a General Purpose Serial Interface
(GPSI), a Serial Peripheral Interface (SPI), or a UART. The CPU uses a
120-Megahertz clock obtained from a 4.8-Megahertz crystal.
The Universal Device Networking Kit contains a development board, an
adapter for in-circuit programming, and software. The Advanced Wireless
Design Choices
113
Kit adds support for IEEE 802.11b wireless networking on a PC Card with
supporting firmware. The Phantom Server is a Web server module with an
IP2022 CPU, 512 kilobytes of Flash memory for storing Web pages, and
support for CGI and SSI.
Software. Project development uses Ubicom s integrated development environment
and GNUPro, a software development suite that includes a C
compiler. The suite is built around the open-source GNU standard and is
available from Red Hat (www.redhat.com). The IP2022 s Core Software
Development Kit includes support for Ethernet and Internet protocols.
Netmedia SitePlayer Ethernet Web Server
At a glance: a very inexpensive module that can serve Web pages and perform
UDP communications with a minimum of user programming.
Requires a serial link to a CPU to update Web page data and receive data
from clients.
Ethernet support: 10BASE-T
Figure 3-9: Ubicom s Universal Device Networking Kit contains the IP2022
Wireless Network Processor. (Photo courtesy of Ubicom, Inc.)
Chapter 3
114
Typical use: Basic monitoring and control tasks.
Source: Netmedia (www.netmedia.com)
Hardware. The main purpose of Netmedia s SitePlayer(Figure 3-10) is to
provide a very low-cost platform for serving Web pages, including pages
with dynamic content. For most projects, the SitePlayer communicates with
an external CPU over a serial link. The SitePlayer can place data received
from the CPU in its Web pages and can send data from a form or a hyperlink
on a Web page to the CPU. The CPU can also use the SitePlayer to
send and receive UDP datagrams over a network. In some very basic applications,
you can use the SitePlayer without a connection to a CPU, such as
applications where users click buttons on a Web page to toggle pins on the
SitePlayer s board.
The SitePlayer contains just two chips: a Philips 8051-compatible P89C51
microcontroller and a Realtek RTL8019AS Ethernet controller. Two 10-pin
headers provide access to the Ethernet interface, an asynchronous serial
Figure 3-10: Netmedia s SitePlayer and development board provide a Web
server with Ethernet and RS-232 interfaces.
Design Choices
115
interface, an output for indicating status of the Ethernet interface, a reset
input, and eight I/O pins.
The microcontroller s Flash memory stores the program code that runs the
SitePlayer and the Web pages the SitePlayer serves. The SitePlayer can store
up to 48 kilobytes of Web pages.
The SitePlayer s development board contains a SitePlayer module and headers
for monitoring or connecting to the SitePlayer s pins. Also included are
an RJ-45 connector for the Ethernet interface, an RS-232 interface and connector
for the asynchronous serial interface, a voltage regulator and
power-supply connector, an LED controlled by the LINK output, a Reset
button, and two additional LEDs and pushbuttons.
Software. A SitePlayer project requires a SitePlayer Definition file, which is
a text file that contains setup parameters and variable definitions in a
Siteplayer-specific format. The setup parameters include information such
as whether the SitePlayer should receive its IP address from a DHCP server
and if not, what IP address to assign to the SitePlayer. The definitions are for
variables that will contain dynamic content in the Web pages. The
SitePlayer s software manual explains the syntax to use in the Definition file.
The Web pages served by the SitePlayer are like any Web pages except that
they may contain pointers to objects that correspond to variables in the Definit
ion
file. A ^ before a name indicates a pointer. For example, ^flow is a
pointer to the variable flow. When the SitePlayer serves the Web page, it
substitutes the current value of the named variable for the pointer.
Netmedia s SiteLinker utility assembles a Definition file into a SitePlayer
Binary image and enables you to load the image and your Web pages into
the SitePlayer. A SitePlayer Interface File enables receiving information provid
ed
by a user viewing a SitePlayer Web page.
The firmware inside the SitePlayer manages communications over the
Ethernet and serial ports. The source code isn t available.
Chapter 3
116
EDTP Electronics Packet Whacker
At a glance: An Ethernet interface on a circuit board with headers for connectin
g
to a CPU.
Typical use: adding Ethernet to any microcontroller circuit.
Ethernet support: 10BASE-T
Source: EDTP Electronics (www.edtp.com)
Hardware. The Packet Whacker (Figure 3-11) from EDTP Electronics is an
Ethernet interface only. The circuit board contains a Realtek RTL8019AS
Ethernet controller, an RJ-45 connector, two headers that bring out the signals
required to communicate with the Ethernet controller, and related
components. You can use the Packet Whacker to add Ethernet to just about
any microcontroller. EDTP Electronics has similar boards with other Ethernet
controllers: the NICki has a Cirrus 8900A and the NICkita has an ASIX
88796L. The Whacked 8051 Development Board includes Packet Whacker
circuits and adds a Philips P89C668 8051-compatible microcontroller and
64 kilobytes of Flash memory.
Software. EDTP provides example Packet Whacker firmware for UDP and
TCP communications using a Microchip PIC16F877. The Whacked 8051
Figure 3-11: EDTP s PacketWhacker makes it easy to add an Ethernet interface
to an external CPU. (Photo courtesy of EDTP Electronics.)
Design Choices
117
Development Board includes C and Basic (BASCOM-51) code for UDP,
TCP, and other Internet protocols. The NICkita includes an e-book with
information about using the ASIX 88796L controller.
Serial-to-Ethernet Bridge
At a glance: enables RS-232 and RS-485 devices to communicate over networks
Ethernet support: 10BASE-T
Typical use: remote communications with devices with serial interfaces.
Sources: Z-World (www.zworld.com), Netburner (www.netburner.com), R.E.
Smith (www.rs485.com).
Hardware. Thousands of existing devices that don t support Ethernet have
an RS-232 or RS-485 serial interface. With a serial-to-Ethernet bridge, you
can communicate with these devices in an Ethernet network.
The bridge connects to the device s serial interface and to an Ethernet network.
Computers anywhere in the network can then exchange data with the
device. After being configured, the bridge transparently sends received serial
data on the network in TCP segments and sends data received in TCP segments
to the device s serial interface.
Two devices that connect to a network via bridges can communicate the
same as if they were connected directly by a serial interface. The bridge conver
ts
between interfaces as needed.
Serial-to-Ethernet bridges are available from a variety of sources. Z-World s
EM1500 Multipoint Serial-to-Ethernet Bridge supports four RS-232 ports
and one RS-485 port. The board s CPU is a Rabbit 3000. R.E. Smith s
ESPSX3 Serial Port Server has two RS-232 ports and one port that is configurable
as an RS-232 port or an isolated RS-485 port. The board contains a
Rabbit Semiconductor RCM2200 module. Netburner s SB72
Serial-to-Ethernet Device and Processor Board supports one RS-232 or
RS-485 interface. The board s CPU is a Motorola ColdFire 5272.
Software. A Serial-to-Ethernet Server typically comes with an application
that enables you to enter settings for your network and devices. Most also
Chapter 3
118
include a Web page that you can use for configuring when the device is on
the network.
After configuring, computers on the network can use TCP/IP applications
to communicate with the device.
In Depth:
Ethernet Controllers
An embedded system that supports Ethernet requires Ethernet controller
hardware to provide the Ethernet interface. Many Ethernet controller chips
are designed for use in desktop computers and include support for standard
PC buses and Plug-and-Play functions. Small embedded systems typically
don t need all of the capabilities of a PC s Ethernet controller. But because
they re available and familiar, a few of the older, simpler PC controllers have
found new life in embedded systems. More recently, controllers designed
specifically for use in embedded systems have become available.
This section introduces some of the more popular controllers for embedded
systems. If you buy a module with a controller on it, it s likely that it will use
one of the chips described below. A module containing an Ethernet controller
will probably include firmware support for communicating with the controller.
In many cases you can use the firmware without having to know
much about the controller s inner workings. Some vendors provide source
code so you can customize if needed, while others release only the executable
code.
Even if you don t need to program a controller directly, a basic understanding
of how the controller works is helpful in selecting hardware and troubleshooting
.
What the Hardware Does