##################################################################### # # PRODUCTS # This README file covers the following products: # Software Development Kit (SDK) for the OTX Hardware Win32 and Win64 Driver (DRV SDK); # Software Development Kit (SDK) for the OTX Hardware Linux Driver (DRV SDK); # Software Development Kit (SDK) for C55x Digital Signal Processors (DSP55 SDK); # OTX Windows WDM Driver for Windows XP, Windows 2003 Server, Windows Vista, # Windows 2008 Server and Windows 7 # OTX Linux Driver; # # PRODUCT NUMBERS # SAA-1006-1 (DRV SDK for Win32, Win64) # SAA-1008-1 (DRV SDK for Linux) # SAA-1012-1 (DSP SDK for C55x) # SDA-1012-1 (OTX WDM Driver) # SDA-1014-1 (OTX Linux Driver) # # PRODUCT REVISION # See the topmost history entry below # # COMPILER # Microsoft Visual Studio 2010 (Host) # Linux (Host) # TI Code Composer Studio 2.2 Code Generation Tools (DSP) # # SEE ALSO # For more information, please refer to the following Odin documents: # Programmer's Guide for OTX Hardware API (1412-1-SAA-1006-1) # Programmer's Guide for OTX DSP C55x SDK (1412-1-SAA-1012-1) # Installation Guide for OTX PCI Adapters (1512-1-HCA-1001-1) # Technical Description for Thor-8-PCI-Plus, Thor-8-PCIe (1111-1-HAA-1049-1) # Technical Description for Thor-2-PCI-Plus, Thor-2-PCIe (1111-1-HAA-1048-1) # Technical Description for Gimle-16-PCI-Plus, Gimle-16-PCIe (1111-1-HAA-1050-1) # Technical Description for Vidar-55x4-ASM # Technical Description for Thor-2(4)-ExpressCard (1111-1-HAA-1076-1) # # CONTACT INFORMATION # Odin TeleSystems Inc. # 800 East Campbell Road, Suite 334 # Richardson, Texas 75081-1873 # U.S.A. # Tel: +1-972-664-0100 # Fax: +1-972-664-0855 # Email: Support@OdinTS.com # URL: http://www.OdinTS.com # # Copyright (C) Odin TeleSystems Inc., 2011-2012 # ##################################################################### Technical Support: ================= Email: Support@OdinTS.com Fax : +1-972-664-0855 Phone: +1-972-664-0100 (M-F 9 a.m. - 5 p.m. CST (GMT-6)) Note: Starting from OTX Driver version 3.0.1.0, the following products are no longer supported: Arni-16-PCI Arni-6x6-PCI series Sleipnir-1-PCI Thor-2[8]-PCI Thor-2-PCMCIA, Thor-2-PCMCIA-Plus[EX,PRO,CST] Vidar-5x16-PCI Vidar-5x4-ASM, Vidar-5x4-ASM-EX[PRO,CST] Driver and SDK (Version 2.48.1.0) for products above can be found at our web site. DrvSdk Distribution Directory structure: (Demos are re-named by their functions from version 3.0.1.0, for comparison, the old names (if changed) are in parentheses) =============================================================================== Demos Host Demo programs (source and executable) using the OTX Hardware API. Separate subdirectories for each board supported by the OTX Hardware API. Burst (Burst Device - Direct Memory Access): BurstBasic (T8pBurstBasic): Demonstrates an efficient way of transferring data to and from the board using the OTX_DEVICE_BURST device. This demo loops data internally on the card, and sends and verifies a gamma pattern. GimleBurstEx: Demonstrates an efficient way of transferring data to the board using the OTX_DEVICE_BURST device. ThorBurstEx (T8pBurstEx): Demonstrates an efficient way of transferring data to and from the board using the OTX_DEVICE_BURST device. This demo can send and receive a file on one timeslot or all timeslots. Connection (Li Cross Connection, H.100 Connection): GimleGroomer: Demonstrating how to create an E1/T1 grooming application using a number of Gimle-16-PCI-Plus boards connected to a number of Thor boards (Thor-2[4,8]-PCI-Plus) over the H.100 bus. LiCrossConnect (ThorLiCrossConnection): Demonstrating the use of the timeslot crossconnect feature between two Line Interfaces on OTX T1/E1 Thor boards. Dsp55Sdk (DSP SDK demos for the C55x DSPs): Dsp55Demo1: User Application using the DSP55 SDK Demo program Dsp55Demo1.out. Demonstrates use of the DSP SDK IO Control interface by changing the blink frequency of the LEDs connected to each DSP. Dsp55Demo2: User Application using the DSP55 SDK Demo program Dsp55Demo2.out. Demonstrates how to connect to Pipes in a DSP55 SDK application. Each DSP is connected a Codec handset. The DSP application loops the Handset microphone samples to the handset speaker. It also performs a gain (volume) adjustment of the samples before they are sent to the handset speaker. The gain can be changed with keystrokes. Hdlc (Dsp-Hosted HDLC and T1E1-Hosted HDLC): DspHostedHdlc (T2p5x4Hdlc): Send/Receive HDLC frames on 4 different timeslots (4 per DSP/Li) using logical HDLC devices in two of the DSPs. GimleT1E1HostedHdlc (GimleDemo): Receive HDLC frames using a local HDLC device in the Line Interface. T1E1HostedHdlc (ThorDemo): Send/Receive HDLC frames using either a logical HDLC device in the Line Interface. Signaling (T1/E1 Line Signalings, Line Detection): E1ABCDbit (T2pE1ABCDBit): Configures a board in E1 mode and demonstrate the use of the ABCD bit access functions. LineAutoDetect (T8pLineAutoDetect): Demonstrates a method for automatically detect the optimum settings for the E1/T1 device by a trial-and-error method. LineMon (T8pLineMon): Demonstrates how the board can be configured to monitor a T1/E1 span. T1DlBit (T2pT1DlBit): Configures a Thor-2-PCI board in T1 mode and demonstrate the use of the DL-bit access functions. T1RobBit (T2pT1RobBit): Configures a Thor-2-PCI board in T1 mode and demonstrate the use of the bit-rob access functions. SS7 (SS7 functionalities): DspHostedSs7 (T2p5x4SS7): The demo send MSUs between two T1/E1 ports on the card using the following sequence: Li0 sends MSUs to Li1 Li1 acknowledges the MSU Li1 sends MSUs to Li0 Li0 acknowledges the MSU Tone (Telecommunication Tones): DualTone (T2p5x4DualTone): Sine wave telephony tones is generated and the tone is detected by dual tone detector using logical devices in the DSPs. GimleDtmf: Demonstrating the use the DTMF Detector / MF Detector devices, DTMF / MF digits are detected. MfR2Tone (T2p5x4MfR2): Generate and detect MF R2 tones MultiToneDetect (TppMultiToneDetect): Various tones detections. SingleTone (T2p5x4SingleTone): Sine wave telephony tones is generated and the tone is detected by single tone detector using logical devices in the DSPs. ThorDtmf (TppDtmf): Demonstrating the use the DTMF Detector, DTMF Dialer / MF Detector, MF Dialer devices. VariousTones (T2p5x4): Send and Detect DTMF tones using logical devices in the DSPs. Utils (Utilities and Tools): EnumOtxDevices: Demo Application which enumerates all installed OTX boards, and the devices (physical and logical) which they host. It also prints the serial number and build of each board. ThorAccess: Demonstrates how to access an OTX card even if another application has opened a handle to it. It also demonstrates the use of direct register reads and writes to the board, TimeStamp: Demonstrating the use of timestamps provided by the OTX Driver. Windows (Windows-based demo): OtxBurstStats: This is a standalone utility application that can be run in parallel with any OTX board that uses OTX_DEVICE_BURST devices. It provides statistics of the activity performed by the OTX_DEVICE_BURST device. Dll OTX Hardware API dynamic lib compiled with Visual C++ 6.0 (32-bit mode). Doc OTX Driver API documents (Windows HLP and HTML formats) Dsp OTX DSP C54x SDK (for writing custom DSP applications for OTX boards) C54x DspDemo1: Simple DSP Application for demonstrating how to write custom DSP applications using the DSP SDK. This application allows the user to control the blink frequency of the heart-beat LED. Use together with the Host Demo Application Demos\DspSdk\Pci\DspDemo1 DspDemo2: More advanced demo of a user written DSP application. This demo application connects two highways to a handset and controls volume gain. The gain can be set through a host application. Use togther with the Host Demo Application Demos\DspSdk\Pci\DspDemo2 Inc OTX Hardware API Header files Lib OTX Hardware API static lib compiled with Visual C++ 6.0 (32-bit mode). How to Build the Demos for Win32 Drv SDK? ============================================= To build the Demo applications for the Win32 Drv SDK open the "DrvSdkDemos.dsw" Workspace in Microsoft Visual C++ 6.0. The "DrvSdkDemos.dsw" file is located in the "Demos" directory. Each Demo program has its project file (*.dsp) located in the W32 subdirectory of the corresponding demo source directory. For more information on each demo, please refer to the header comment in the beginning of each source file. How to Build the Demos for Linux Drv SDK? ============================================= To build the Demo applications for the Linux Drv SDK run GNU make in the "Demos" directory. The GNUmakefile is this directory will recurse GNUmakefile files in each demo directory. For more information on each demo, please refer to the header comment in the beginning of each source file. What is new in release, 3.5.1.0 ================================ Linux 64-bit driver is released, tested on Ubuntu-11.04-desktop and CentOS 6.0. See BuildDrv64.txt in driver package for how to build driver. Windows releases including OtxDrv.sys with both 32-bit and 64-bit operating system. What is new in release, 3.4.1.0 ================================ Windows releases including OtxDrv.sys and OtxDrvUsb.sys. -- Occasional BSOD on Thor-8M-USB is fixed. -- Data overrun possibility is reduced by increased buffer size for Thor-8M-USB. -- Solution file DrvSdkDemos.sln for SDK is added. What is new in release, 3.3.1.0 ================================ Windows releases including OtxDrv.sys and OtxDrvUsb.sys with both 32-bit and 64-bit system. What is new in release, 3.2.1.0 ================================ Internal release: Linux 32-bit (CentOS 6.0). What is new in release, 3.1.1.0 ================================ Thor-8M-USB support is added (A separate driver release OtxDrvUsb.sys). Micorsoft Visual Studio 2010 is used for SDK. Windows 32-bit release only. What is new in release, 3.0.1.0 ================================ Thor-8-PCIe support is added. Demos directory structure and demo names are changed. Windows release only.