Release Notes for Devicescape Universal Wireless Platform
|
Release
|
Date
|
Description
|
|
2.0
|
14 March 2005
|
Devicescape Universal Wireless Platform
|
The following topics are included in these release notes:
What's in the Box?
|
Item
|
Description
|
|
Devicescape Studio CD
|
CD containing the Devicescape Studio integrated development environment (IDE). (Install this first! See How to Install.)
|
|
Devicescape Universal Wireless Platform CD
|
CD(s) containing the Devicescape Universal Wireless Platform software for the Development Host system. Includes tools and cross-compilers specific to a target architecture (one CD per target). You will have one or more of these CDs, depending on how many target architectures you ordered. Each platform CD contains:
- Devicescape Linux Toolchain for your target architecture
- Reference Linux distribution and software development kit (SDK)
- RPMs and ipkgs (binaries)
- Source RPMS for all runtime packages
(Install only after installing the Devicescape Studio. See How to Install.)
|
|
Platform Release Notes
|
This document in "booklet" form.
|
What is the Devicescape Universal Wireless Platform?
Devicescape Universal Wireless Platform is a general purpose platform that provides a foundation for original equipment manufacturers (OEMs) and original design manufacturers (ODMs) to quickly and easily build wirelessly-enabled devices with value-added technologies to address specific markets and areas of expertise.
The platform is a Linux based, wireless development solution for building feature-rich, Wi-Fi certified wireless capable devices for wireless local area networks (WLANs). The platform is a foundation for development of embedded software that conforms to IEEE 802.11 standards. It provides for rapid deployment to target systems, testing, and debugging. Development of both client devices and access points is supported.
The platform includes a Linux kernel, key runtime embedded software such as the Devicescape wireless subsystem (a device-independent IEEE 802.11 software core), an Eclipse based integrated development environment (Devicescape Studio), and command-based development environment. Wireless-specific tools for the 802.11 subsystem, GNU toolchain, and build scripts and makefiles are integrated into the development environment. You can choose from baseline packages and add new functionality (configuration subsystems and interfaces), build, deploy to target systems, and test-all from within the platform.
The following table shows some of the typical WLAN datacom and CE applications that can be implemented with the Devicescape Universal Wireless Platform. This is by no means a comprehensive list; the consumer electronics market, in particular, is rapidly evolving and continues to generate new applications.
Table 1 Examples of Applications for Wireless Devices built on Devicescape Universal Wireless Platform
|
WLAN Datacom
Applications
|
CE Applications
|
- Enterprise and SMB access points (APs)
- Light APs
- Client bridges
- Wireless Ethernet bridges
- Wireless Gateways
- Voice-over-WLAN phones
- Print servers
|
Note: The CE market is particularly rich and dynamic in terms of creating new categories of WLAN-enabled products. The landscape is continually changing.
|
Supported Platforms
The Devicescape Universal Wireless Platform is designed to allow you to customize, build, and deploy embedded applications on wireless devices. All runtime packages are provided as binary RPMs and source SRPMs (which can be modified and rebuilt for the purpose of modifying or adding features, or porting to a different driver or chipset).
The platform (Devicescape Studio, C libraries, packages, toolchains for each target, and related utilities) is installed on a development host. A binary image (built on the platform with a cross-compiler) is loaded onto a target system. The target system is the wireless device which will run as an access point or client.
The development host is an Intel-based PC running a supported Linux distribution. Several target systems are supported. Development and target platforms are described in the following sections.
Development Host Platform
A "development host" is the computer on which you develop and build the wireless system before loading it onto the target system. The development host should be an Intel-based PC running a supported Linux distribution as detailed below.
System Requirements
The recommended system configuration for the development host is:
- Intel Pentium or compatible processor
- 512 MBytes RAM
- 2 GBytes available disk space
- Red Hat or Fedora Core 2 Linux install as described in the next section
Linux
Your development host should be set up as a Linux machine, with standard Linux tools and utilities available to the Devicescape Universal Wireless Platform. Supported versions of Linux are:
|
Vendor
|
Version
|
|
Red Hat
|
Red Hat Enterprise Linux WS v.3
|
|
Red Hat
|
Fedora Core 2
|
See http://www.redhat.com/ for more information on Linux.
Target System Platforms
A target system is the platform that will function as the wireless device. It is a combination of processor board and, if applicable, radio chipset. The low-level hardware drivers have been incorporated into these builds.
The Devicescape Universal Wireless Platform also runs on standard PC hardware: the Intel IA-32 (x86Pc) target. This configuration allows the PC to act as a wireless access point or client station. You can use this platform for development and testing. x86 PCs are more readily available than embedded boards (especially at the start of a project when embedded hardware may not be ready).
Radio Devices
|
Vendor
|
Model Numbers
|
Radio Modes
and Comments
|
|
Atheros
|
AR5213
|
Modes: a/b/g MAC/BB
|
|
Broadcom
|
BCM4306
|
Modes: b/g MAC/BB/Radio
Support via Devicescape monolithic driver interface
|
|
Broadcom
|
BCM4309
|
Modes: a/b/g MAC/BB/Radio
Support via Devicescape monolithic driver interface.
|
|
Broadcom
|
BCM4320
|
Modes: a/g MAC/BB/radio USB 2.0
Support via Devicescape monolithic driver. (Client Only)
|
|
Conexant
|
All SoftMAC architecture
|
Modes: b/g
Support via platform monolithic driver interface. (Client Only)
|
CPUs
|
Vendor
|
Model
Numbers
|
CPU Family and Comments
|
|
Intel
|
IXP425
|
XScale (ARM)
Includes all IXP42x.
|
|
Atheros
|
AR5312
|
a + a/g SoC
220 MHz MIPS
Atheros SoC (MIPS-based System-On-a-Chip)
|
|
AR2313
|
a or g SoC
180 MHz MIPS
Atheros SoC (MIPS-based System-On-a-Chip)
|
|
Broadcom
|
BCM4712
|
b/g SoC 200MHz MIPS
Broadcom SoC (MIPS-based System-on-a-Chip)
|
|
Intel
|
IA-32
|
Intel Pentium class CPUs
|
Boards
The following table shows the hardware platforms used by Devicescape for quality assurance testing. Many other platforms are supported. Please contact your Devicescape Sales Representative for a complete list.
|
Vendor
|
CPU Family
|
Board Model
|
|
ADI/Intel
|
IXP425
|
IXDPG425 (Monte Jade)
|
|
D-Link
|
AR2313
|
DWL-2210AP
|
|
Broadcom
|
BCM4712
|
BCM94712
|
|
Intel
|
Pentium
|
Standard PC
|
How to Register
For product registration and license keys, contact Devicescape at http://register.devicescape.com/.
Provide your Contact Information and MAC (Hardware) address of your development host on the support page and click the Submit button. You should receive a license file in about one business day.
Since the turn-around time for acquiring license keys is approximately one business day, we recommend that you apply for a license before installing the software so that you have an up-to-date license file at install time.
License configuration information is also displayed in the final dialog of the Devicescape Studio Install wizard. (See step 10 in Step 1. Install Devicescape Studio.)
How to Install
Follow these steps to install the Devicescape Studio and Devicescape Universal Wireless Platform on your development host.
Step 1. Install Devicescape Studio
Step 2. Install the Devicescape Universal Wireless Platform
Step 1. Install Devicescape Studio
The Devicescape Studio CD includes the Devicescape Studio IDE.
|
Notes
|
You must have root user permissions to execute the commands to install the IDE. In the examples below, we assume you will use "sudo" to get permissions per command.
|
To install the Devicescape Studio:
- Insert the CD into the CD-ROM drive on your development host. (If your system is not set up to automount the CD-ROM, please mount it manually.)
- Bring up a terminal command line shell in which to run the installation.
- Run the install script by type the following at the command line:
sudo /mnt/cdrom/install.sh
Some system messages are displayed to indicate unpacking/starting the installer:
After this, the installer wizard is displayed.
- Read the Introduction information and click Next.
- Read the License agreement, click accept, and click Next. (Or click "do not accept..." and exit the install.)
- Choose a location in which to install the Devicescape Studio. To accept the default location "
/opt/devicescape/studio/3.0", just click Next.
- Choose the components you want to install and click Next. We recommend installing all Applications and Documentation.
- Review the Pre-installation Summary showing components to install and target locations. If you want to change anything, click Previous to go back. If you are satisfied with these selections, click Next to start the installation.
The "Installing . . . " dialog is displayed during the install, with status messages and a progress bar.
- When the installation completes, a success message shows the results of the install. Click Next.
- License key information is shown on the final dialog of the Install wizard. If you do not have a license, select Request a license file to connect to the Devicescape Web site, or contact Devicescape directly. (See also How to Register). If you already have a license, skip to step 12 on page 20.
Provide your Contact Information and MAC (Hardware) address of your development host on the support page and click the Submit button. You should receive a license file in about one business day.
- The "Configure License" dialog will re-display with "Exit" radio button selected. Click Done to exit the installer wizard.
- When the installation is complete, enter the following on the command line to unmount the CD and eject it from the CD-ROM drive:
$ sudo umount /mnt/cdrom
$ eject
Step 2. Install the Devicescape Universal Wireless Platform
Each Devicescape Universal Wireless Platform CD contains the following components:
- Reference Linux distribution and software development kit (SDK)
- RPMs and ipkgs (binaries)
- Source RPMS for all runtime packages
|
Notes
|
- The Devicescape Studio must be installed first before installing the Devicescape Universal Wireless Platform software target-specific tools.
- Platform CDs include tools and cross-compilers specific to the target architecture for which you are building (one CD per target). You will have one or more of these CDs, depending on how many target architectures you ordered. If you are installing toolchains for more than one target architecture, the order of installation among these is not important. Just make sure you install the Devicescape Studio first, before installing any of the platform software.
- You must have root user permissions to execute the commands to install the platform. In the examples below, we assume you will use "sudo" to get permissions per command.
|
To install the platform:
- Insert the CD into the CD-ROM drive on your development host. (If your system is not set up to automount the CD-ROM, please mount it manually.)
- Bring up a terminal command line shell in which to run the installation.
- Run the install script by type the following at the command line:
sudo /mnt/cdrom/install.sh
Follow the prompts. Some key points are described here for the rest of the steps.
- Enter YES (or yes) if you agree with the terms of the license (or NO to stop the install).
- Select the components to install or update by entering the selection numbers separated by commas. For example:
1. uClibc Toolchain for target armv5b
running linux
2. Kernel for Devicescape arm-ixdpg425
3. Minimal RFS based on busybox and
uclibc
|
Note
|
The first two of these components are always board-specific. The choices shown above are meant to be an example. If you are installing for a different target, the first two selections will differ from those shown above.)
|
Normally you will install all three components, so enter '1,2,3' at the prompt.
|
Note
|
By default, the board architecture platforms will install as follows:
IXDPG425 (Monte Jade) will install in /opt/devicescape/linux/2.0/armv5b-bbdyn-uclibc/
X86PC will install in /opt/devicescape/linux/2.0/i686-bbdyn-uclibc/
DWL-2210AP (Atheros AR531x/AR231x) will install in /opt/devicescape/linux/2.0/mips-bbdyn-uclibc/
Broadcom BCM9471x will install in opt/devicescape/linux/2.0/mipsel-bbdyn-uclibc/
|
- The component list is then displayed again with asterisks next to the ones you chose. Verify or change your selections as instructed by the prompts (enter A or Accept to accept the current selections).
The script shows the default directories where components will be installed, and asks if you want to relocate any of these components.
- Enter N to accept the default directory locations for all components. (Or enter Y to choose different paths in which to install, and follow the prompts. When you are satisfied with the install locations, enter N to indicate you do not want to make any more modifications.)
Accepting the install locations launches the installer. Status messages are displayed in the command window during the install.
Here is an example:
Partition summary:
Partition: / Available: 28478504K
Required: 316543K
Do you want to relocate any of these
components? [y/N]:N
Installing uClibc Toolchain for target
armv5b running linux
Installing Kernel for Devicescape arm-
ixdpg425
Installing Minimal RFS based on busybox
and uclibc
Installing additional host tools...
Installing binary packages...
Installing source packages...
Installation complete
- When the installation is complete, enter the following on the command line to unmount the CD and eject it from the CD-ROM drive:
$ sudo umount /mnt/cdrom
$ eject
Where to Go Next
Documentation and Online Help
A complete set of documentation for the Devicescape Universal Wireless Platform is included on the Devicescape Studio CD. When you install the Devicescape Studio you have the option to install Documentation. Once installed, the Documentation is available on your development host both as Online Help from the Devicescape Studio Help menu (Eclipse-based IDE), and also as PDFs in the doc/ directory where you installed Devicescape Studio.
Devicescape also provides documentation for current releases of all products on its corporate Web site. To view Devicescape Universal Wireless Platform documentation on our Web site, please visit the online documentation site for this product directly through Devicescape customer support:
http://www.devicescape.com/support/
(Or through our public Product Documentation portal at http://www.devicescape.com/docs/)
To access documentation on the development host, you must have chosen the Documentation components at install time. The Linux Release Notes (architecture-specific getting started guides for the boards) are installed when with the Devicescape Universal Wireless Platform CDs. The rest of the documentation is installed from the Devicescape Studio CD. (See How to Install.)
- Devicescape Universal Wireless Platform Release Notes (An earlier version of this document; suggest using this printed version instead.)
/opt/devicescape/studio/3.0/doc/releasenotes_pfm.pdf
- Linux Release Notes - Prerequisite information for the boards; one per target architecture.
/opt/devicescape/linux/2.0/<arch>-bbdyn-uclibc/docs/release_notes.txt
Where <arch> is the name for the target architecture. For example, the release notes for an Atheros board is installed in: /opt/devicescape/linux/2.0/armv5b-bbdyn-uclibc/docs/release_notes.txt
- Board architecture specific Getting Started Guides - Setup, configuration, and boot information specific to targets; one per target architecture.
/opt/devicescape/linux/2.0/<arch>-bbdyn-uclibc/docs/getting_started.pdf
Where <arch> is the name for the target architecture. For example, the Getting Started Guide for an Atheros board is installed in: /opt/devicescape/linux/2.0/armv5b-bbdyn-uclibc/docs/getting_started.pdf
- Devicescape Developer Guide - Provides overview of development process overview, describes architectures of runtime systems. Includes example walk-throughs of building Reference Designs (AP, client, client bridge). Explains how to build packages (IDE and command line) and how to add new features or modify existing. Includes information on board porting.
/opt/devicescape/studio/3.0/doc/developer_guide.pdf
This document is also available from the Devicescape Studio Help menu:
Help > Help Menu > Devicescape Developer Guide
- Devicescape Package Guide - Describes runtime packages. Includes information on start/stop options, configuration, building, external APIs, debugging, and licensing.
/opt/devicescape/studio/3.0/doc/package_guide.pdf
This document is also available from the Devicescape Studio Help menu:
Help > Help Menu > Devicescape Package Guide
- Getting Started with Devicescape Studio - Setup and configuration details for Devicescape Studio.
/opt/devicescape/studio/3.0/doc/getting_started.pdf
- Devicescape Studio User Guide - Describes use of Devicescape Studio, which is an integrated development environment (IDE) for creating applications and other binaries for Linux systems (such as Devicescape Linux). Built as a plug-in to the Eclipse IDE, Studio offers a number of special features.
/opt/devicescape/studio/3.0/doc/user_guide_ds.pdf
This document is also available from the Devicescape Studio Help menu as "Devicescape Studio Features Guide":
Help > Help Menu > Devicescape Studio Features Guide
- Devicescape Studio Target Configurator Guide- Describes use of the optional Target Configurator, which is a plug-in to Devicescape Studio.
/opt/devicescape/studio/3.0/doc/user_guide_tc.pdf
This document is also available from Devicescape Studio Help menu as "Target Configurator Features Guide":
Help > Help Menu > Target Configurator Features Guide
- Release notes for components - In addition to these Platform release notes and board-specific Linux release notes (see above), text file release notes are provided specific to Studio components. For example, release notes for the Devicescape Studio can be found in the following file:
/opt/devicescape/studio/3.0/doc/release_notes_ds.txt
Last Minute Documentation Updates
Please note the following changes regarding directory locations, filenames, and procedures. These items will differ from how they were originally documented in the Online Help and PDFs that ship with the product. Use this information instead. (See also the customer support Web site at http://www.devicescape.com/support/ for up-to-date solutions.)
Location of Examples Directory
The location of the examples/ directory has changed. Examples are located in: /opt/devicescape/toolchains/<Architecture>/examples
The examples are installed when you install the Devicescape Universal Wireless Platform. (See Step 2. Install the Devicescape Universal Wireless Platform.) The version of the Devicescape Developer Guide included in the installed Documentation and Online Help gives a different (incorrect) location for the examples/ directory.
Clarification on <hostapd>.conf File
In the Devicescape Package Guide, the topic "hostapd package" describes configuration options for a file called "hostapd.conf". This is meant to serve as an example configuration file for the hostapd package. In practice, you might rename this file (<hostapd>.conf). When you create the root file system for an access point per the AP reference design (see Devicescape Developer Guide), example files are generated for /etc/hostapd (with a symbolic link to /config/etc/hostapd) directory. You can use these as reference configuration files. In most cases, the <hostapd>.conf file must be edited before bringing up the access point and you must specify which .conf file should be loaded when hostapd starts. That is, hostapd looks at this particular configuration file so that it knows which "<hostapd>.conf" to use.
# cat /etc/default/hostapd
# Settings for the hostapd init script
# Specify all the config files, one per radio that
# will be running in access point mode
CONFIG_FILES="/etc/hostapd/atheros_a.conf"
# Set the level of debug output desired
DEBUG_LEVEL=1
For multi-radio support, you can have two or more .conf files, separated by a space:
CONFIG_FILES="/etc/hostapd/atheros_a.conf /etc/hostapd/broadcom_g.conf"
For complete information, refer to "hostapd package" topic in the Devicescape Package Guide.
Clarification on Board Porting Hints for Atheros (Booting without a Bootloader)
In the Devicescape Developer Guide, information on board porting for Atheros AR531x/AR231x Boards includes a "Hints and Tips" topic on booting without a bootloader.
In order for this process to work, you must follow the steps given in that section (on CONFIG_BOOTLOADER and Flash Partitioning) and then also do the following with regard to Flash Partitioning:
- Update ZTEXTADDR in
arch/mips/boot/Makfile with the start address of the flash device from which you are booting.
- Adjust CONFIG_CMDLINE to include the root file system for the new device. (For example '
root=/dev/mtdblock2')
- Apply the following patch:
diff -u arch/mips/ar531x/ar531xprom.c
arch/mips/ar531x/ar531xprom.c
--- arch/mips/ar531x/ar531xprom.c
+++ arch/mips/ar531x/ar531xprom.c
@@ -34,10 +34,12 @@
int bank0AC, bank1AC;
int memsz_in_mb;
+#ifdef CONFIG_BOOTLOADER
for (i=0; i<argc; i++) {
strcat(arcs_cmdline, " ");
strcat(arcs_cmdline, argv[i]);
}
+#endif
mips_machgroup = MACH_GROUP_AR531X;
#ifdef CONFIG_APUNUSED
Package Guide Update: Broadcom Driver does not use channel_policy option
In the Devicescape Package Guide topic "broadcom-wl-drv package" > "Runtime Configuration", the table on "hostapd.conf Options Supported in the Broadcom Driver" incorrectly shows "channel_policy" as an option supported by the Broadcom driver. Only the "channel" setting is supported on this driver; not "channel_policy".
FAQs on Development Tasks
For information on key development tasks, refer to the platform document topics or Web sites referenced below.
|
Question
|
Where to Find Information
|
|
How do I get a target system ready for use?
|
See the release notes for the specific target board. Target-specific release notes are included on the Devicescape Universal Wireless Platform CD for each board/architecture.
|
|
How do I get an image loaded and running on a target system (TFTP, NFS, and so on)?
|
See the release notes for the specific target board. Target-specific release notes are included on the Devicescape Universal Wireless Platform CD for each board/architecture.
|
|
How do I build an image for a target specifying the binary packages?
|
See Devicescape Developer Guide.
|
|
Where can I find information on debugging?
|
See Devicescape Package Guide and the Target Configurator Guide.
|
|
How do I configure runtime packages?
|
See Devicescape Package Guide.
|
|
How do I start and stop packages (services) on the runtime target system?
|
See Devicescape Package Guide.
|
|
Where can I find a list of all runtime packages?
|
See the "Package Overview" in the Devicescape Package Guide.
|
|
Where can I find information on each package?
|
See topics on individual packages in the Devicescape Package Guide.
|
Extras
On the Devicescape Studio CD there is a directory containing some extra packages that might prove useful. These are not supported but we hope you find them useful. See the README file in the extras directory for more information about what is there and how to use it.
Where to Get Support
For support on Devicescape Universal Wireless Platform, contact Devicescape Customer Support or your Devicescape Sales representative.
|
Customer Support
|
Web site: http://www.devicescape.com/support/
Telephone Number: +1 (650) 829 2600 option 3
|
|
Sales
|
Telephone Number: +1 (650) 829 2600 option 2
|
