Ubicom IP2022 Wireless Network Processor

an article added by: Daniel R. at 12062007



In: Categories » » Ethernet » Ubicom IP2022 Wireless Network Processor

  

Ubicom IP2022 Wireless Network Processor. In addition to products that provide a complete generic system for networking, a variety of modules and chips are available to handle specific tasks. Some products can interface to just about any CPU. If you have an existing product or a CPU that you want to use, one of these modules may provide a way to add networking capability. This section describes a selection of products. Lantronix Device Server At a glance: enables any device with an asynchronous serial port to communicate over a network. Typical use: any device or system that communicates over a serial port and requires network access. Ethernet support: 10BASE-T, 100BASE-TX Source: Lantronix, Inc. (www.lantronix.com)

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 connector. 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 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 Typical use: Basic monitoring and control tasks. Source: Netmedia (.wwwnetmedia.com) Hardware. The main purpose of Netmedia’s SitePlayer(Network article 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 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 Definition 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 provided 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.

legal notice

Our website is not responsible for the information contained by this article. Web-articles is a free articles resource.
Suggestion: If you need fresh, daily updated content for your website, feel free to use our service. Click here for more information.

Useful tools and features

Ubicom IP2022 Wireless Network Processor  
If you like this article (tutorial), please link to it from your web page using the information above.

related articles

1. The MCF5282 supports a subset of the Motorola 68000
Ethernet support: 10BASE-T The MCF5282 supports a subset of the Motorola 68000. Typical use: Applications that use Java and require speed. Source: Systronix (www.systronix.com). Hardware. The TINI isn’t the only option for Java programmers. Systronix’s JStik board (Network article 3-8) contains aJ-100 microcontroller from aJile Systems Inc. The aJ-100’s native execution of Java bytecodes results in very fast performance. The chip is base...

2. EDTP Electronics Packet Whacker
EDTP Electronics Packet Whacker At a glance: An Ethernet interface on a circuit board with headers for connecting 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 (Network article 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 si...

3. NE2000 Compatibility
NE2000 Compatibility A term you’re likely to hear in reference to program code for network controllers is NE2000-compatible. The NE2000 was an early and popular PC network interface card from Novell. The card contained National Semiconductor’s DP8390 controller. Software for systems that use the ’8390 or a compatible chip has come to be known as NE2000-compatible code. A major feature of the ’8390 is its set of internal registers. By reading and writing to the registers, a CPU can c...

4. Using the Internet Protocol in Local and Internet Communications
The protocols in the IEEE 802.3 Ethernet standard enable the computers in a local network to exchange messages with each other. In practice, most Ethernet networks also use Internet protocols such as TCP or UDP and IP. These provide defined and well-supported methods for accomplishing common tasks such as flow control and flexible addressing and routing of messages. Messages that travel on the Internet must use IP. And because TCP and UDP are designed to work along with IP, local communications that use TCP or UDP also use...

5. There are several options for obtaining an Internet connection
Technologies for Connecting There are several options for obtaining an Internet connection. A long-popular way for home users to connect to the Internet is via dial-up connections on phone lines. For higher speeds, alternatives are a Digital Subscriber Line (DSL), an Integrated Services Digital Network (ISDN) line, or a cable modem. Satellite connections are also possible. Table 4-1 compares the capabilities of the different methods. Not every connection type is available in all locations. Depending on ...

6. Every computer that communicates over the Internet must have an IP address
Static and Dynamic IP Addresses Every computer that communicates over the Internet must have an IP address, which the computer typically receives from its ISP. The IP address may be static or dynamic. A static IP address stays the same until someone explicitly changes it, while a dynamic IP address can change on every boot up or network connect (though the address typically changes only occasionally). An embedded system may store a static IP address in non-volatile memory, either within an application...

7. Obtaining and Using a Domain Name
Obtaining and Using a Domain Name After you obtain Internet access, connect your embedded system to the Internet, and configure your firewall to enable the embedded system to communicate, the system is ready to send and receive messages on the Internet. Applications running on other computers on the Internet can access the embedded system by specifying its public IP address. For example, to view a server’s home page, in the Address text box of a Web browser, you enter http:// followed by the server&rsquo...

8. Inside the Internet Protocol
The Internet Protocol (IP) helps data find its way to its destination even if the data must travel through other networks, including the many and varied networks that make up the Internet. Although it’s called the Internet Protocol, local networks can use IP as well. Many communications in local networks use IP because they use its companion protocols, TCP and UDP. This section introduces IP, including how computers obtain IP addresses, the format of IP datagrams, how IP and the domain name system help in getti...

9. A computer that uses the Internet Protocol must have an IP address
IP Addresses A computer that uses the Internet Protocol must have an IP address. A network administrator may manually assign an IP address to each computer or the network may have a way of assigning addresses automatically to computers that connect to the network. An IPv4 address is 32 bits. As explained earlier in this networking tutorial, the conventional way to express an IP address is in dotted-quad format, such as 192.168.111.1. Assigning Addresses Each IP datagram includes t...

10. With classless addressing the network address and IP prefix
Classless Addressing With classless addressing, the network address and IP prefix are often expressed in the form: xxx.xxx.xxx.xxx/n where xxx.xxx.xxx.xxx is the lowest IP address in the network and n is the number of bits in the network-address portion of the IP address. For example, with a network address and IP prefix of 192.0.2.0/24, the network address is 192.0.2 (three bytes, or 24 bits), and the final eight bits in the IP address are the host address. In routing datagrams for addresses that us...