Software Development Kits

Currently Viewing:

The PCIe Switches and Bridges Technology Software Development Kit, or SDK, is a highly customized software package containing powerful tools to help customers get to market faster when designing with PCI Express and PCI devices. The SDK application offers an easy to use enhanced user interface that includes a variety of new and useful tools that can help in the following ways:

  • Used in conjunction with the RDK board, it helps users get familiar with PCIe Switches and Bridges devices
  • Allows users to configure the devices to their specific needs
  • Demonstrates all major features with the help of sample command line and GUI applications
  • Helps in de-bugging & performance analysis on a live system
  • Provides a framework for users to develop their own software tools and applications

This SDK is an integral part of the Rapid Development Kit (RDK) which includes both hardware and software. These are some of its main features:

  • Support for all PCI & PCIe (PEX) products
  • All Windows flavors XP and later, and Linux Kernel 2.6 / 3.x
  • 64-bit OS environments are supported
  • Kernel level Service & End-point drivers with source code
  • User level API Library with source code
  • Important command line applications with source code
  • Separate GUI Applications for PCI & PCIe
  • SDK User's Manual & Release Notes
  • Support for Non-PEX devices

Download SDK

Note: SDK 7.24 is recommended for all users. If you are upgrading from 6.50 or older versions, a new CDA license file will be required for v7.24. Please talk to an Avago representative to get the new license file.

This package contains the complete SDK in a Windows self-extracting executable, support documents for Windows and Linux, and all SDK Manuals.
This package contains only the Linux portion of the SDK. This is the latest package available and may be newer than the package included in the SDK. Please refer to the Linux Release Notes for installation.
This is the same PEX device Editor GUI that is currently available on Windows which has been ported to Java to run on Linux. Please refer to the Readme for installation instructions.


CDA requirement for using the PEX Device Editor (PDE) GUI application with PCIe switch devices


When the PEX Device Editor (PDE) GUI application is first launched, it will ask for a license file. This license file can be obtained from your local Avago sales representative. Based on the level of your company CDA access, a license will be provided to the appropriate switch devices. If no license is entered, the PDE application will still launch but will only provide support for bridge devices (9000, 6000, 8111, 8112, 8114, and 8311) and PLX legacy chips. Linux support is identical between SDK versions. Only customers using PEX switch devices under Windows will benefit from using the CDA version of the PDE.

Users with CDA access for PEX switches will be able to use all the high-end features of the PDE GUI mentioned above. Non CDA users will only be able to use the PDE GUI for the PCIe bridge devices.

Note: Installing this SDK along with older SDK versions is not supported. The original installation must be fully removed via Add/Remove Programs (or vice versa). Not fully removing before installing may cause the new install to malfunction.


Additional Software


PlxCm for DOS is a DOS version of the PlxCm command-line application that is included in the Windows and Linux versions of the SDK. PlxCm is a powerful tool that provides complete support for PEX Switches and Bridges and PCI9000 Bridges, and limited support for other PCIe/PCI devices. Within the application, type the command "help" or "?" to display a list of commands or syntax for any command.
PlxEep for DOS is a command-line only based utility useful for reading or writing EEPROMs connected to PEX chips via a binary file. This is often used in a production environment to easily program the EEPROM of one or more devices in DOS to minimize boot-up time. PlxEep executes in a pure DOS environment or Win 95/98 DOS prompt. Please execute "PlxEep /?" for usage details.