##################################################################### # # 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 C54x Digital Signal Processors (DSP SDK); # Software Development Kit (SDK) for C55x Digital Signal Processors (DSP55 SDK); # Software Development Kit (SDK) for Alvis boards; # OTX Windows WDM Driver for Windows 98, Windows 2000, Windows XP, # Windows 2003 Server, Windows Vista, Windows 2008 Server and Windows 7 # OTX Windows NT4 Driver; # OTX Linux Driver; # OTX Pocket PC 2002 Driver; # Hugin Windows WDM Driver; # Hugin Linux Driver; # Alvis MontaVista Linux Driver; # # PRODUCT NUMBERS # SAA-1006-1 (DRV SDK for Win32, Win64) # SAA-1008-1 (DRV SDK for Linux) # SAA-1007-1 (DSP SDK for C54x) # SAA-1012-1 (DSP SDK for C55x) # SAA-1016-1 (Alvis SDK for MontaVista Linux) # SDA-1012-1 (OTX WDM Driver) # SDA-1013-1 (OTX NT4 Driver) # SDA-1014-1 (OTX Linux Driver) # SDA-1015-1 (OTX Pocket PC 2002 Driver) # SDA-1018-1 (Hugin WDM Driver) # SDA-1019-1 (Alvis MontaVista Linux Driver) # # PRODUCT REVISION # See the topmost history entry below # # COMPILER # Microsoft Visual C++ 6.0 (Host) # Linux (Host) # MontaVista Linux (Alvis Targets) # 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 C54x SDK (1412-1-SAA-1007-1) # Programmer's Guide for OTX DSP C55x SDK (1412-1-SAA-1012-1) # Programmer's Guide for Alvis DMP SDK (1412-1-HCA-1022-1) # Installation Guide for OTX PCI Adapters (1512-1-HCA-1001-1) # Installation Guide for OTX PCMCIA Adapters (1512-1-HCA-1003-1) # Technical Description for Arni-PCI (1111-1-HAA-1008-1) # Technical Description for Thor-2-PCI (1111-1-HAA-1022-1) # Technical Description for Thor-2-PCMCIA (1111-1-HAA-1012-1) # Technical Description for Thor-8-PCI (1111-1-HAA-1019-1) # Technical Description for Vidar-5x16-PCI (1111-1-HAA-1020-1) # Technical Description for Vidar-5x4-ASM (1111-1-HAA-1009-1) # Technical Description for Thor-8-PCI-Plus (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 Arni-6x6-PCI-Plus (1111-1-HAA-1064-1) # Technical Description for Hugin-2-PC104 (1111-1-HAA-1069-1) # Technical Description for Alvis-ASM (1111-1-HCA-1018-1) # Technical Description for Alvis-PCIe (1111-1-HCA-1021-1) # Technical Description for Alvis-CSI (1111-1-HCA-1020-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., 2010-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)) Distribution Directory structure: ================================= 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 Lib OTX Hardware API static lib compiled with Visual C++ 6.0 (32-bit mode). Dll OTX Hardware API dynamic lib compiled with Visual C++ 6.0 (32-bit mode). Inc OTX Hardware API Header files Demos Host Demo programs (source and executable) using the OTX Hardware API. Separate subdirectories for each board supported by the OTX Hardware API. Generic 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. Alvis AlvisDmp: Host based application that controls and Alvis-ASM or Alvis-DMPs on an Alvis-PCIe board. AlvisCsi Alvis4CsiBasicDemo: Simple application that opens the some of the simple devices on an Alvis-4-CSI or Alvis-4M-CSI like the temperature sensor device. AlvisBurst: An application that exercises the burst device on an Alvis-4-CSI or Alvis-4M-CSI. Arni32Pci A16: Demo Application for Arni-16-PCI board (Arni base NIC without the Arni-16-Ext extension module) Configures 2 POTS line interfaces and allows the user to go off-hook and dial numbers. A16Vd5x4: Demo for Arni-16-PCI equipped with Vidar-5x4-ASM Daughter board. User can make calls and connect hansets to create speech connection. Arni6x6Pci Arni6x6Demo: Demo for Arni-6x6-PCI-Plus. It demonstrates the use of the features the OTXCST2 SPM which is the DSP program targeted for this board. This demo show features of the OTXCST2 SPM such as the Pots Li device, the DTMF dialer device, the DTMF detector device, the Call Progress Tone detector device, and the VoiceMixer device. This demo also shows how to record voice data using the Burst device of this board. A66Slic2: Demo for Arni-6x6-PCI-Plus. It demonstrates the use of the FXS devices on this board. This demo also shows how to record voice data using the Burst device of this board. A66FxoFxs: Demo for Arni-6x6-PCI-Plus. It demonstrates the use of the FXS and FXO devices on this board. It also demonstrates the normal highway connections needed to connect these devices. A66EchoCancel: Demo for Arni-6x6-PCI-Plus. It demonstrates the use of the Echo Cancel device provided by the FXO device on this board. It shows how the reference/prompt signal being played using the Burst device can be removed/cancelled by the Echo Cancel device, so that only the callers receive signal is recoded. A66BurstEx Simple demo which show how to use the Burst device on an Arni-6x6-PCI-Plus board. DspSdk (DSP SDK demos for the C54x DSPs) DspDemo1: User Application using the DSP SDK Demo program DspDemo1.out. Demonstrates use of the DSP SDK IO Control interface by changing the blink frequency of the LEDs connected to each DSP. DspDemo2: User Application using the DSP SDK Demo program DspDemo2.out. Demonstrates how to connect to Pipes in a DSP 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. 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. Gimle16Pci GimleBurstEx: Demonstrates an efficient way of transferring data to the board using the OTX_DEVICE_BURST device. GimleDemo: Receive HDLC frames using a local HDLC device in the Line Interface. 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-PCI-Plus, Thor-4-PCI-Plus, Thor-8-PCI-Plus) over the H.100 bus. Thor2ExpressCard TecMultiToneDetect: Detects Single Tone, Multi Tone and Silence on multiple timeslots. TecSs7: Sends and receives MSUs and FISUs. Thor4ExpressCard T4ecDemo: Based on Thor2Pci\ThorDemo. Sends and receives HDLC frames using the HDLC device in the T1/E1 device. T4ecTone: Based on Thor2Pci\T2p5x4. Sends and receives DTMF and MF tones. TecRecPlay: Sends and receives raw data files (one per Li) using the burst device. Thor2Pci (many of these applications work for the Thor and Thor-Plus boards as well) ThorDemo: Send/Receive HDLC frames using either a logical HDLC device in the Line Interface. 2T2p: 2 Thor-2-PCI boards connected via the H.100 bus. A handset connection is made over the H.100 highways. T2p5x16Hdlc: Thor-2-PCI connected to with a Vidar-5x16-PCI board. Send/Receive HDLC frames on 4 different timeslots (4 per DSP/Li) using logical HDLC devices in two of the DSPs on Vidar-5x16-PCI. T2p5x4: Thor-2-PCI equipped with a Vidar-5x4-ASM. Send/Receive HDLC frames using a logical HDLC device in the Line Interface. Send and Detect DTMF tones using logical devices in the DSPs on the Vidar-5x4-ASM. T2p5x4DualTone: Thor-2-PCI equipped with a Vidar-5x4-ASM. Sine wave telephony tones is generated and the tone is detected by dual tone detector using logical devices in the DSPs on the Vidar-5x4-ASM. T2p5x4Fsk: Thor-2-PCI equipped with a Vidar-5x4-ASM. Demonstrate the use of Raw Data Sender, Silence Detector and FSK Detector logical devices in the DSPs on the Vidar-5x4-ASM. T2p5x4Hdlc: Thor-2-PCI equipped with a Vidar-5x4-ASM. Send/Receive HDLC frames on 4 different timeslots (4 per DSP/Li) using logical HDLC devices in two of the DSPs on Vidar-5x4-ASM. T2p5x4MfR2: Thor Plus series equipped with a Vidar-5x4-ASM-PRO. Generate and detect MF R2 tones T2p5x4Ss7: Thor-2-PCI-Plus / Thor-4-PCI-Plus / Thor-8-PCI-Plus equipped with a Vidar-5x4-ASM, or the Thor-2-PCMCIA series boards. 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 T2p5x4Recorder: Thor-2-PCI equipped with a Vidar-5x4-ASM. Demonstrates the use of the Raw Data Sender and Raw Data Receiver Logical device by using these device to Record and Playback voice file to and from the Codec. T2p5x4SingleTone: Thor-2-PCI equipped with a Vidar-5x4-ASM. Sine wave telephony tones is generated and the tone is detected by single tone detector using logical devices in the DSPs on the Vidar-5x4-ASM. T2pE1ABCDBit: Configures a Thor-2-PCI board in E1 mode and demonstrate the use of the ABCD bit access functions. T2pE1Sbits: Configures a Thor-2-PCI board in E1 mode and demonstrate the use of the Sa and Si bit access functions. T2pT1DlBit: Configures a Thor-2-PCI board in T1 mode and demonstrate the use of the DL-bit access functions. T2pT1RobBit: Configures a Thor-2-PCI board in T1 mode and demonstrate the use of the bit-rob access functions. T2pT1TR08DLAccess: Configures a Thor-2-PCI board in T1 mode and demonstrate the use of the T1 SLC96/TR-08 9-State signalling states. Thor2Pcmcia (most of these applications work for Thor-2-PCI and Thor-8-PCI as well) T2mDemo: Send/Receive HDLC frames using either a logical HDLC device in the Line Interface, or in the DSP module. Send and detect DTMF tones. T2mRawData: Demonstrates the use of the Raw Data Sender and Raw Data Receiver. Sends a text file (or any file not containing a 0xFF character) over a 64kbit/s raw data pipe. T2mRawDataSync: Demonstrates sending two raw data files (one from each Line Interface) in a synchronized fashion (i.e. the first byte of each file is transmitted in the same T1/E1 multiframe. T2mSamples: Demonstrates the use of OTX Driver with the Thor-2-PCMCIA-EX and Thor-2-PCMCIA-PRO boards. Vidar5x16Pci Vd5x16: The demo application loads the standard Otx Signal Processing Module 1 (OtxSpm1) DSP Application Pack to all DSPs and configures a selectable DSP to send sweeping sine wave to the handset connected to Codec#0. 2xVd5x16: 2 Vidar-5x16-PCI boards connected via the H.100 CT bus. A handset connection is made over the H.100 highways. Thor8Pci 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. 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. T8pLineMon: Demonstrates how the Thor-8-PCI-Plus board can be configured to monitor a T1/E1 span. T8pLineAutoDetect: Demonstrates a method for automatically detect the optimum settings for the E1/T1 device by a trial-and-error method. T8pSs7: This program is written for the Thor-8-PCI-Plus + Vidar-55x4-ASM board combination. It configures multiple SS7 channels per span. Utils 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, Windows 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. 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. How to Build the Demos for WinCE Drv SDK? ============================================= To build the Demo applications for the WinCE Drv SDK open the "DrvSdkDemos.vcw" Workspace in Microsoft Embedded Visual C 3.0. The "DrvSdkDemos.vcw" file is located in the "Demos" directory. Each Demo program has its project file (*.vcp) located in the WinCE 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 Alvis Linux Drv SDK? =============================================== See file AlvisSdkReadme.txt. What is new in release, 2.48.1.0 ================================ Windows (XP, 2003 Server, Vista, 2008 Server and 7) 64-bit driver is digitally signed. What is new in release, 2.47.1.0 ================================ Added support for Gimle-16-PCIe-Basic-32 and Gimle-16-PCIe-Basic-64. For Linux Enterprise Kernal 2.6.18 release, dynamic library instead of static library is used for demos. What is new in release, 2.46.1.0 ================================ Support of FPGA aggregation on Alvis-4-CSI Rev. 2.0. A bug fix on Raw Data Receiver with OTX_DSP_SPM_OTXSPM2 on DSP C5510. A bug (for example DTMF can't always be detected) is fixed with OTX_DSP_SPM_OTXSPM2EX on DSP C5410A and C5416. What is new in release, 2.45.1.0 ================================ Some fixes for the build 3.0 of Alvis-CSI and Alvis-PBX. Alvis Linux SDK release only. What is new in release, 2.44.1.0 ================================ 48 kbps pipe is supported. A fix on clock source for Alvis-2-CSI and Alvis-2-PBX. What is new in release, 2.43.1.0 ================================ Added support for Temux Device to driver Added Gimle-PCIe and Alvis-PCIe to Windows 64-bit driver INF file Release of Windows 64 and 32 bit drivers, files built using WDK 7600.16385.1 Support of Windows 2003 Server 64-bit What is new in release, 2.42.1.0 ================================ Improved Burst Device performance: Removed memory copy in burst send and receive. Pass a pointer to the user memory. Fixed a bug on burst device which caused duplicated frame IDs when computer is busy. In linux, there are error messages when the driver module is removed, this is fixed. DSP module SPM2 is supported on Alvis-ASM. What is new in release, 2.41.1.0 ================================ A bug fix on pipe disconnection on Thor-8-PCI-Plus Rev.2. Some pipe connections cross CT bus can't make connections on the right H.100 highway, timeslot, this is fixed. What is new in release, 2.40.1.0 ================================ Thor-8-PCI-Plus Version 1.0 Build 2.0 firmware updated to use update burst interface was added to release. Firmware update version 6 TH8PPLUS: 098A support for 4mSec hardware burst buffer, and updated burst interface available with this driver release. Modified demo T2p5x4Hdlc and T2mRawData to include types OTX_DEVICE_THOR_4_PCI_PLUS and OTX_DEVICE_THOR_8_PCI_PLUS for ASM DSP BSP initialization. The initialization of the DSP BSP is performed after the clock source has been setup. These two demos did not perform the initialization function. Need to call initialize BSP using OTX API call OtxDrvDbgDump(g_hPhysDevs.hDsp[nDsp], 1). OTX message log error "Interrupt received from DSP but DSP BSP initialization has not finished" is reported. Driver release: 2.6-cc3 - Linux Enterprise 2.6 Kernel ES 4 (2.6.9-34.EL) 2.6-cc4 - Linux Enterprise 2.6 Kernel ES 5 (2.6.18-128.el5) Windows 32bit OS What is new in release, 2.39.1.0 ================================ Linux release only Driver supports Thor-8-PCI-Plus burst interface version 1.0 and 2.0. Burst interface was added with firmware update number 4 available for Thor-8-PCI-Plus Version 2.0 Build 2.0/1.0. Corrected error in the thor-8-pci-plus object that was introduced in release 2.38.1.0 Added event bypass option to T8pBurstEx demo. Increased burst buffer size 2x for T8PP and T4PP What is new in release, 2.38.1.0 ================================ The Raw Data receiver device hosted by the T1E1 device needed a bit-reversal per byte. This has been corrected. Thor-8-PCI-Plus Version 2.0 Build 2.0/1.0 firmware modified to use update burst interface. Modified Linux driver to process DPC task as part of the on interrupt. This has shown to reduce CPU usage. Correct 5.x Linux driver reload issue with plus cards that has been reported on some units. What is new in release, 2.37.1.0 ================================ Build directory created for Linux: 2.4-cc3-EL - Linux Enterprise 2.4 Kernel ES 3 (2.4.21-32.EL) 2.6-cc3-EL - Linux Enterprise 2.6 Kernel ES 4 (2.6.9-11.EL) Hugin release What is new in release, 2.36.1.0 ================================ Added Alvis ASM demo applications to the Linux and Windows SDK distribution see Demo/Alvis in the SDK. Added support for Alvis-CSI version 1.2. What is new in release, 2.35.1.0 ================================ Added support for Alvis_PCIe to driver. Added support for Linux CentOs 5.2. Windows 32bit Linux release Kernel : 2.6.18-92.1.18.el5 Kernel : 2.6.9-42.EL What is new in release, 2.34.1.0 ================================ Added support for 56k HDLC channels when hosted by the E1T1 device. Linux Alvis SDK release only. What is new in release, 2.33.1.0 ================================ Added support for OtxHdlcSS7SetFilter() function when the HDLC receiver is hosted by the T1E1 device. Linux Alvis SDK release only. What is new in release, 2.32.1.0 ================================ Linux support on RHEL/CentOS 5.1. First Linux Alvis SDK that supports Alvis-4-CSI and Alvis-4M-CSI. What is new in release, 2.31.1.0 ================================ Corrected H100 timing issue T8PP version 2.0 Initial release of Alvis SDK. What is new in release, 2.30.1.0 ================================ Added a new demo program called GimleGroomer which 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-PCI-Plus, Thor-4-PCI-Plus, Thor-8-PCI-Plus) over the H.100 bus. Added two demo programs for Thor-4-ExpressCard. T4ecDemo is based on Thor2Pci\ThorDemo, but is specific for the Thor-4-ExpressCard. T4ecTone is based on Thor2Pci\T2p5x4, but is specific for the Thor-4-ExpressCard. These two demos are located in the Demos\Thor4ExpressCard directory. What is new in release, 2.29.1.0 ================================ Release of Windows 64 bit driver, files built using Visual Studio 2005 IDE Added windows Driver SDK 64 Added OTX_SYS_ADDR type to support 32 and 64 bit address variables Visual Studio 6 IDE support available in Windows Driver SDK 32 What is new in release, 2.28.1.0 ================================ Added the Thor2ExpressCard/TecRecPlay demo which sends and receives "raw" data (all timeslots) from each Li using the burst device. Add attribute OTX_ATTR_HDLC_RECEIVER_SS7_SIGNAL_LSSU_FISU_COUNT to allow user to enable and disable the LSSU/FISU count events. Set the default value of the attribute to OTX_FALSE (disabled). The application will need to enable the event when it is needed. The Layer 1 E1/T1 status was not reported properly by the OtxT1E1GetLayer1StatusEx() function under certain conditions. This problem has now been corrected. This change affects all OTX T1/E1 boards. What is new in release, 2.27.1.0 ================================ Added event logging to the WDM driver code: These log events can be displayed using the Windows "Event Viewer". Event type "Information" is used to log a successful operation of the driver usually during system initialization when no application code is active. Event type "warning" are used to log event that are found at user execution level which are already reported to the application level but may not be necessarily significant. Event type "error" indicates a significant error was detected by the code running at either the user or system execution level. These errors are an indication of a loss of data or loss of functionality. The burst device for Thor-8-PCI-Plus version 2.0 is unreliable in this version. This problem will be corrected in the next version. What is new in release, 2.26.1.0 ================================ Added the OTX_ATTR_USERAPP_SUB_DEV_TYPE attribute for the OTX_LDEVICE_USER_APPLICATION logical device. This attribute can be set to use sub-devices types of the OTX_LDEVICE_USER_APPLICATION logical device (see OtxType.h). The DTMF detection failed during T4EC evaluation. Modified 55x DSP software load DTMF detection pause threshold. The 55x DSP and 54x are now using the same pause threshold level. What is new in release, 2.25.1.0 ================================ The T1E1 device could on occasion miss an interrupt. This could cause the HDLC controller hosted by this device to stop functioning properly. This issue has now been corrected, and now the T1E1 device handles all interrupts properly. What is new in release, 2.24.1.0 ================================ Fixed a bug on PCMCIA card, this bug causes system to crash. What is new in release, 2.23.1.0 ================================ Added Thor-4-ExpressCard 1.0 support. Added OTX_CLOCK_SOURCE_EXTERNAL clock source. Added OTX_ATTR_BRD_MONITOR_ONLY to support board configured as monitors, like the Thor-4-ExpressCard which defaults to monitor mode. Transmit pins are not active by default the application must enable transmit. Added OTX_ATTR_T1E1_LINE_FREQUENCY to capture the current line frequency. Only available on the Thor-4-ExpressCard. What is new in release, 2.22.1.0 ================================ When using OTX_DSP_SPM_OTXSPM2EX_INTMEM and OTX_DSP_SPM_OTXSPM2EX on a C5510 DSP it was not possible to receive HDLC frames longer than 47 bytes. This problem has now been corrected. The driver package is now distributed as an MSI file. What is new in release, 2.21.1.0 ================================ Added support for FALC transparent mode using OTX_T1_FF_UNFRAMED and OTX_E1_FF_UNFRAMED frame format. While in this mode the FALC does not perform automatic framing and all data bits in the data stream are accessable to the application for receive and transmit. What is new in release, 2.20.1.0 ================================ The non-null-check of the last parameter of the OtxDrvGetAttributeValue() function was removed. This check was added in the 2.19.1.0 version of the driver, but it was removed to be backwards compatible with older drivers. Support for Thor-2-ExpressCard 1.0 was added. What is new in release, 2.19.1.0 ================================ Added HDLC send timestamp option to the DSP device. The following events were added to support the timestamp OTX_HDLC_SENDER_EC_FRAME_COUNT_ZERO and OTX_HDLC_SENDER_EC_FRAME_SENT. Add MTP2 FISU/LSSU processing option to DSP device. Added bLsbReceivedFirst option to OtxRawDataReceiverInit. The previous version did not support this option. Note use of this option requires the DSP to perform additional data processing. Care should be taken if DSP is already heavily loaded. Updated NDIS driver to support burst device. Updated Linux build to support CentOs release 4.4 Kernel 2.6.9-42. Added support for the Thor-2-ExpressCard. See new Thor2ExpressCard demos: TecMultiToneDetect, and TecSs7, and the the new SPMs for this card (OTX_DSP_SPM_OTXSPM2_INTMEM, OTX_DSP_SPM_OTXSPM2EX_INTMEM, and OTX_DSP_SPM_OTXHDLC_INTMEM). Improved error string handling by providing a more detailed error string for each specific return code. To use the new error string handling, supply zero as the first parameter to OtxDrvResultCode2String(). The demo applications are now linked with the OtxHwDll.lib to conserve file space for the distribution package. OtxHwDll.dll must be in the DLL path to execute the demos. What is new in release, 2.18.1.0 ================================ Error that occurred during driver load in the WDM driver, was not properly reported to the Plug-n-Play engine. This was now corrected. The ASM frame sync adjustment made in 2.17.1.0 was rolled back, and instead firmware package #5 was released for Gimle-16-PCI-Plus. Added section Example Application Structure to available application note documents. Modified FwUpd utility to support Linux OS. Added support to HUGIN for firmware release 1143. What is new in release, 2.17.1.0 ================================ Thor-8-PCI-Plus firmware release #5 (TH8PPLUS: 0988) added an additional non-critical interrupt enable signal to FPGA firmware. Support was added to driver to enable this signal. This firmare release increassed the hardware buffer from 2mSec to 4mSec. The ASM data highways did not align properly for the 5510 implementation of OTXSPM2 for the Gimle-16-PCI-Plus board. This was corrected. Internal release. Not for public use. What is new in release, 2.16.1.0 ================================ Added support 56kbps HDLC channels in SPM2 for 5510 DSPs. Improved the handling of critical interrupts for OTX Plus cards. Release for WDM driver only. What is new in release, 2.15.1.0 ================================ Added support for GIMLEDM firmware 1024 (Firmware package #4). Firmware package #4 replaces Firmware package #2 (GIMLEDM 1022) and Firmware package #3 (GIMLEDM 1023). Release for WDM driver only. What is new in release, 2.14.1.0 ================================ Added support for GIMLEDM firmware 1023 (Firmware package #3). Added support for SMP for the PCMCIA cards. Release for WDM driver only. What is new in release, 2.13.1.0 ================================ Corrected a problem in the OTXCST2 SPM for the Arni-PCI-Plus boards which could potentially cause the DSP program to halt. Multiple OTX PCI Plus cards did not share interrupts correctly. This problem was corrected in this release. Added support for OTX PCMCIA cards on Linux kernel 2.6.x Release for WDM driver only. What is new in release, 2.12.1.0 ================================ The RawDataSender device now support the A-law and U-law data formats. Please see the T2mRawData demo program for a example of this feature. Corrected NT4 build for Burst data capture. Added support to ARNI demos for the card variants. Release for WDM, NDIS, and Linux UP and SMP drivers Build directory created for Linux: 2.4-cc3 - Linux Fedora 2.4 Kernel (2.4.22-1.2115.nptl) 2.4-cc3-EL - Linux Enterprise 2.4 Kernel ES 3 (2.4.21-32.EL) 2.6-cc3-EL - Linux Enterprise 2.6 Kernel ES 4 (2.6.9-11.EL) What is new in release, 2.11.1.0 ================================ Modified Arni6x6Demo to support the signed 16 bit linear data format. Modified CST DSP code u-law and A-law conversion to use the upper 14 bits of the the DSP 16 bit word used to process data within the DSP. This will preserve the MSB of the data processed by the DSP. Release for WDM, NDIS, and Linux UP and SMP drivers Build directory created for Linux: 2.4-cc3 - Linux Fedora 2.4 Kernel (2.4.22-1.2115.nptl) 2.4-cc3-EL - Linux Enterprise 2.4 Kernel ES 3 (2.4.21-32.EL) 2.6-cc3-EL - Linux Enterprise 2.6 Kernel ES 4 (2.6.9-11.EL) What is new in release, 2.10.1.0 ================================ Added support for Hugin-2-PC104 Rev. 1.1 with Conformal Coat Hugin release What is new in release, 2.9.1.0 ================================ Added support for Thor-1-PCI-Plus Release for WDM only What is new in release, 2.8.1.0 ================================ Corrected ARNI board critical interrupt processing. Modified CST DSP API to include input and out gain adjustments in the voice mixer device. Release for WDM, NDIS, and Linux UP and SMP drivers Build directory created for Linux: 2.4-cc3 - Linux Fedora 2.4 Kernel (2.4.22-1.2115.nptl) 2.4-cc3-EL - Linux Enterprise 2.4 Kernel ES 3 (2.4.21-32.EL) 2.6-cc3-EL - Linux Enterprise 2.6 Kernel ES 4 (2.6.9-11.EL) What is new in release, 2.7.1.0 ================================ Correct bug found in Linux ES 4.x release that was not correctly accessing 8 bit register. Kernel version 2.6.9-5.EL Hugin release. What is new in release, 2.6.0.3 ================================ Modified Linux ES 4.x builds to use software interrupt (Softirqs). Kernel version 2.6.9-5.EL Hugin release. The attribute OTX_ATTR_T1E1_RX_INPUT_THRESHOLD did not set the correct treshold for the Thor-8-PCI-Plus and Gimle-16-PCI-Plus boards. This was corrected. A call to OtxT1E1SetMonitorMode() with a FALSE value without a prior call to the same function with a TRUE value could change the receive input threshold to an unexpected value. This was corrected. The E1/T1 driver code for the Thor-8-PCI-Plus and Gimle-16-PCI-Plus boards was modified to achieve optimum receiver sensitivity in E1 longhaul mode (ReceiveEqualizer=OTX_TRUE). What is new in release, 2.6.0.2 ================================ Corrected a problem related to Offhook/Onhook for the Slic devices on Arni-6x6-PCI-Plus. Added support for Gimle-16-PCI-Plus firmware package #2 (GIMLEDM 1022), which uses 4ms receives (as opposed to the the 2ms buffers in the original firmware version). The size of burst user mode buffers have been doubled for the Gimle-16-PCI-Plus board. The default values for nLosSensitivity and nLosRecovery in all of the E1/T1 demos were modified to fulfill the G.775 and Telcordia (Bellcore) standards. nLosSensitivity is now set to 10 (which results in LOS detection after 176 consecutive zeros. nLosRecovery is now set to 21 (which results in LOS recover after 22 ones in the LOS recovery period. What is new in release, 2.6.0.1 ================================ HUGIN driver Build directory created for Linux: 2.4-cc3 - Linux Fedora 2.4 Kernel (2.4.22-1.2115.nptl) 2.4-cc3-EL - Linux Enterprise 2.4 Kernel ES 3 (2.4.21-32.EL) 2.6-cc3-EL - Linux Enterprise 2.6 Kernel ES 4 (2.6.9-5.EL) Burst device: In some situations the burst device could get into a situation where he thinks that a DMA request is never finished. Consequently, this had the affect the burst device did not receive or send any data. This problem was introduced in the 2.4.0.1 driver release, but is corrected in this release. What is new in release, 2.6.0.0 ================================ Added support for Linux Enterprise ES 4.1 Build directory created for Linux: 2.4-cc3 - Linux Fedora 2.4 Kernel (2.4.22-1.2115.nptl) 2.4-cc3-EL - Linux Enterprise 2.4 Kernel ES 3 (2.4.21-32.EL) 2.6-cc3-EL - Linux Enterprise 2.6 Kernel ES 4 (2.6.9-11.EL) Burst device: The burst device could occasionally cause a BSOD during over/underrun conditions. This has now been corrected. Reduced the amount of stack used by the burst device. Kernel 2.6 provide a 4KByte stack, kernel 2.4 provided an 8KByte stack. ARNI: Updated DSP firmware to correct data slip. CPLD firmware update package #2 is needed to support the DSP modification. This is CPLD Build: A66DM: 1122. Loop current measurement accuracy improved with this release. What is new in release, 2.5.0.4 ================================ Added Linux enterprise ES3 build support (Kernel 2.4) to OtxDrv. Modified Llb and Exe GNUmakefile.def file to build the enterprise support files. What is new in release, 2.5.0.3 ================================ Added Linux build support for HUGIN. Added Linux enterprise ES3 build support (Kernel 2.4). What is new in release, 2.5.0.2 ================================ Modified Thor-8-PCI initialization. The critical and non-critical interrupts are masked durring initialization and are also mask when the card handle is closed. This will prevent any spurious interrupts durring the card initialization. WDM OtxDrv.sys release only. What is new in release, 2.5.0.1 ================================ Internal release. Added Hugin-2-PC104 support. The following demos are modified to work with Hugin: ThorDemo, Dsp55Demo1, Dsp55Demo2, T2p5x4Hdlc, T2mDemo, T8pBurstEx What is new in release, 2.4.0.1 ================================ Added additional counters to the OtxBurstStat utility. Support for Firmware Package #5 for Thor-8-PCI-Plus. This firmware package has doubled the sized DMA buffers, thus further reducing the risk of underruns and overruns on a busy PCI DMA system. Added A66FxoFxs demo to support the Arni 6x6 PCI Plus board (HAA-1064-1). What is new in release, 2.3.0.1 ================================ Removed DPRINTF in three files from debug version of the driver. What is new in release, 2.3.0.0 ================================ Added support for Arni 6x6 PCI Plus board (HAA-1064-1). Added double buffering to burst send and receive. Added additional support for 54x CST. WinCe projects were not part of this distribution. What is new in release, 2.2.1.0 ================================ Added a new SPM OtxSpm2Ex. This SPM supports the same logical devices as OtxSpm2. The added feature of OtxSpm2Ex is lower latency HDLC decoding/encoding (1ms in OtxSpm2Ex vs 12.75ms in OtxSpm2). OtxSpm2Ex also supports 16kpbs and 32kpbs subrates for HDLC devices (whereas OtxSpm2 only supports 64kpbs HDLC devices). OtxSpm2Ex and OtxSpm2 both have 12.75 ms bufferering for tone devices. Release of latest NDIS WAN driver with support files. Modified INF file to better support default configuration. Fixed bug that caused system lockup. What is new in release, 2.1.1.0 ================================ OtxHdlcSS7SendData() could under heavy load send incorrect frames. This has now been corrected. OTXSPM1, OTXSPM2, OTXHDLC, and OTXHDLCEX were effected by this correction. What is new in release, 2.0.1.0 ================================ Event driven triggers have been added to the Burst device, allowing applications the means to either use the current polling method or the new event driven method to send and/or receive data via Burst (DMA). With a application supplied trigger level (how much data is available to be read or how much space to be available to send - same as a Fifo level implementation), and waiting on those events, an application can now make better use of resources. For details and implementation examples, please reference the demo T8pBurstEx and the corresponding SDK documentation. What is new in release, 1.0-P151 ================================ Added Gimle-16-PCI demo program: Demos\Gimle16Pci\GimleDemo Corrected Gimle-16-PCI-Plus, Thor-2-PCI-Plus and Thor-8-PCI-Plus H.100 pipe connections. What is new in release, 1.0-P150 ================================ Corrected T1/E1 span voltage measurement for Thor-2-PCI-Plus. CT Bus connections are now allowed for Thor-2-PCI-Plus and Gimle-16-PCI-Plus. Fixed declarations of the SS7 structures OtxHdlcSS7FisuS, OtxHdlcSS7ShortLssuS, and OtxHdlcSS7LongLssuS. These are now true representations of what they are intended to map, and their size is now accurate: sizeof(OtxHdlcSS7FisuS) == OTX_HDLC_SS7_CB_FISU == 3 sizeof(OtxHdlcSS7ShortLssuS) == OTX_HDLC_SS7_CB_SHORT_LSSU == 4 sizeof(OtxHdlcSS7LongLssuS) == OTX_HDLC_SS7_CB_LONG_LSSU == 5 What is new in release, 1.0-P149 ================================ Change Burst device handling logic in overrun conditions. Changed Thor-8-PCI-Plus ISR to help when multiple boards are in the same machine. What is new in release, 1.0-P148 ================================ T1 transmit pulse mask was adjusted for Thor-8-PCI-Plus boards. Split clock mode is now allowed for Build 1.0 boards of Thor-2-PCMCIA-Plus. What is new in release, 1.0-P147 ================================ Added OtxBurstStats to base distribution. OtxBurstStats is a Windows MFC application that demonstrates the OTX SDK API usage under Windows. This utility retrieves the Burst Device statistics from the selected device and displays them in a Windows dialog box. Fixed a bug in demo T8pBurstEx where, when 'R' to save to file was selected, and the user was asked for a timeslot, or -1 for all, and the input was a specific timeslot, the wrong data was saved to the file. Now, when a specific timeslot was requested (0-127), the proper timeslot is saved. Added DTMF and HDLC support in the SPM2 module for the Vidar-55x4-ASM board. What is new in release, 1.0-P146 What is new in release, 1.0-P145 ================================ Internal release. Added MF support in the SPM2 module for the Vidar-55x4-ASM board. What is new in release, 1.0-P144 What is new in release, 1.0-P143 ================================ Fixed subtle SMP race condition in the event queue when receiving many events from the driver (for instance, when the line has not been configured correctly). Added support for WinCe .Net (PocketPC 2003) platform. Fixed race condition that could cause a BSOD when creating/opening/closing many logical devices when running multiple cards in the same maching. Fixed error in Ambassador highway speed calculation (applicable to any card that has an Ambassador). Added 56kpbs sub-channel support to OTXSPM1 and OTXSPM2. Fixed Otx5x4Hdlc demo to work in 56kpbs (command line option /5) and enabled use of OTXSPM1 and OTXSPM2 for 56kpbs. Fixed an internal WinCE Console I/O routine that affected the demos' ability to open files. WinCE MSI Installation now reinstalls through ActiveSync when Repair is selected, and removes what was installed therough ActiveSync when Remove is selected. Added OtxCeMon to base distribution. OtxCeMon is a PocketPc Win32 SDK GUI application that demonstrates the OTX SDK API on the PocketPc platform in its true environment. This applet samples data from both LIs and also allows setting a constant value to be transmitted on any timeslot(s), as well as other functionality. Added Frame Reference Data to Burst Device (see T8pBurstEx.c). What is new in release, 1.0-P142 ================================ Fixed OtxDrvResultCode2String (returned failure if the error code was one from OtxCommonResultCodesE). Added OtxT1E1GetLayer1StatusEx(), which can be used to query more specific details of the current T1/E1 line status. Added OTX_DSP_SPM_OTXHDLCEX SPM which can support HDLC pipes up to 31 timeslot wide (full E1 or T1). This SPM is supported on the Vidar-55x4-ASM and the Thor-2-PCMCIA-PRO boards. The define OTX_LOCAL_PIPE_TIMESLOTS_MAX has been set back to reflect the number of timeslots on a local PCM highway, which is 32. See OtxDef.h. Added attribute OTX_ATTR_T1E1_TX_IDLE_CHARACTER, which allows the value that is sent when idle to be changed or retrieved. Added OTX_ATTR_DSP_FRAME_COUNTER and OTX_ATTR_HDLC_RECEIVER_USE_FRAME_COUNT_AS_SEQUENCE attributes, which can be used to provide an accurate timestamp of received HDLC frames. Added support for Gimle-16-PCI-Plus. Added support for Firmware 3.0 of the Thor-2-PCMCIA-PRO and Thor-2-PCMCIA-EX (which relates to way interrupts are handled in the Pocket PC operating system). Added support to configure the line inteface devices for either J1 (ITU-T JG.704 + JG.706) or T1 (ITU-T G.704 + G.706) alarm handling and CRC6 generation/checking. Added new demos programs. These include: T8pLineMon T8pSs7 What is new in release, 1.0-P141 ================================ ******************************** *** IMPORTANT API SDK change *** ******************************** In order to facilitate the availability to applications written in programming languages other than C (such as Pascal (Delphi), Visual Basic, etc.), the API routines in OtxHwDll are now declared as _stdcall (using the OTX_API macro). The routines are now imported without the leading '_' (underscore), and, more importantly, changes who is responsible for cleaning up the calling parameter stack. Although the change affects the static library as well, a recompile and link will automatically adjust to the new calling syntax. ******************************** Changed function OtxBurstReceiveData() to OtxBurstReadData(). This more closely follows the OTX naming convention. Added OtxT1E1InsertSingleBitDefect() which can be used insert a single bit defect (error) into the transmitted T1/E1 data stream. Fixed condition where the HDLC Sender, that was not enabled, was called to send data; it would return successful, but the frame wasn't ever sent. The HDLC Sender must be enabled before sending data, and will now return an error if called to send data if it is not in a working state. Added a command line switch (/5) to the T2p5x4Hdlc.c demo program, that will configure the HDLC pipes in 56kpbs mode. Changed the character sent when idle to a more standard character. The Common NULL character for E1 is 0x7F, and the Common NULL character for T1 is 0x54. Previously, 0xFF was sent as the idle character. This change improves synchronization times. A change in the settings for multi-frame resynchronization improves F4/F12/F72 resynchronization attempts. On older products, when loss of multiframe synchronization has been detected, you may have to perform one or more calls to OtxT1E1ForceResynch() to try to force a resynchronization when running in T1 mode and using frame formats other than ESF. A new attribute, OTX_T1E1_EC_AUTO_FORCE_RESYNC, is available for use in older products that help workaround multi-frame synchronization problems. Please see the help documentation for details. This provides an automatic attempt to perform the resynchronization mentioned above. As of this release, HDLC subchannel and SPM2 on the 5510 DSP is not supported. Additionally, it is not yet supported on the new Plus products, such as Sleipnir. This will be implemented in a future revision. What is new in release, 1.0-P140 ================================ ******************************* *** CRITICAL API SDK change *** ******************************* The return codes from the API have been changed to included extended error information in what was previously designated the FACILITY field of the error code (which has been 0 up to this point). The FACILITY field no longer exists, however, this field has been replaced by source information that generated the error, which now permits the support team to better and more quickly determine causes of errors. It is now VERY IMPORTANT that any code that checks the return against a value use the OTX_RESULT_CODE() macro to properly format the return code (strip the extended information). An example is: result = OtxDrvConnectLib(); if (OTX_RESULT_CODE(result) != OTX_S_OK) { ... } Without using this macro, the result code may contain extended information, and the comparison would fail. Please see OtxErr.h for details, and the demo programs for examples. ******************************* *********************************** *** IMPORTANT Thor-8-PCI change *** *********************************** Applications written for the Thor-8-PCI and Thor-8-PCI-Plus cards must now open the physical device OTX_DEVICE_QUAD_T1E1 for each QuadFalc (2), and use that handle to host the line devices (such as OTX_DEVICE_LI_T1E1, etc.). This device must also be enabled before the line devices are enabled and disabled after the line devices are disabled, when applicable. Although most demos reflected this, it was not previously a requirement. Please reference the available demos (such as ThorDemo, etc.) for examples (search for OTX_DEVICE_QUAD_T1E1 and the associated handle variables). *********************************** Support for the new Thor-8-PCI-Plus card. The new Plus card has DMA capability, and can be utilized by using the new burst device. Please see the demos Thor8Pci\T8pBurst for an example of using the burst device to send/receive using the new, faster DMA highway. Additionally, please reference the product specifications on the Thor-8-PCI-Plus for further details. Additionally, an extended Burst option has been added that supports the direct buffer to DMA use. This set of API calls bypass the normal OTX schema, and allow the user application to handle the raw buffer directly. This option must be used in high input/output applications, otherwise the application will not be able to keep the buffer full, and will receive under/over run errors. Please see T8pBurstEx demo application for details. OTX_T1E1_EC_ES event is now reported after the error counters. Previous releases reported this event before the counters. You may now run multiple tone detectors in SPM2 in parallel as intended. T1/E1 attribute OTX_ATTR_T1E1_TR08_MODE is now properly initialized everytime the device is opened. Previously it was only initialized when the driver was loaded. Linux makefiles now create the symbolic link if it does not exist: /usr/src/linux-->/usr/src/$(OS_VER) Linux makefiles now create the module directory if it does not exist: /lib/modules/$(KERNEL_VER)/misc Support for SMP Linux has been fixed and enhanced. What is new in release, 1.0-P139 ================================ Support for the PocketPC 2002 platform. MSI installation packages for the OTX Driver and OTX Demo applications are included in the OTX for WinCE package. Currently we have tested on the iPaq 5xxx series handheld. To support this platform you will need to aquire a newer revision of the PCMCIA card. You may contact our sales and/or support departments for help and information. Support for new Thor PCMCIA cards: Thor-2-PCMCIA-CST, Thor-2-PCMCIA-EX and Thor-2-PCMCIA-PRO. The newer cards support more devices in the OTXSPM1 and OTXSPM2 DSP modules. For more details, please refer to the OtxDspD.h header file. Support for new Vidar ASM cards: Vidar-5x4-ASM-PRO, Vidar-5x4-ASM-EX, Vidar-5x4-ASM-CST. The newer cards support more devices in the OTXSPM1 and OTXSPM2 DSP modules. For more details, please refer to the OtxDspD.h header file. Added support for Linux Red Hat 8.0 and 9.0. Removed support for Linux Red Hat 6.x (2.2 kernel) The function OtxHdlcSS7SendData() can now accept the maximum SS7 payload length (272 bytes, excluding flags). Added pragma push support for __BORLANDC__ in the SDK headers to aid Borland compiler users to develop applications. Additionally, you must insure that the size of an enumeration is set to the size of an int (compiler switch). Fixed problem with TR-08 rob bit visibility. Fixed potential problem with driver aquiring a spinlock more than once. What is new in release, 1.0-P138 ================================ Linux directory tree has changed. Prior to this release, the directory tree was based on the kernel revision, defined as either 2.2 or 2.4. The Linux directory tree now includes an added specifier, the major version of the compiler (CC) used in the build. This is defined as cc#, where # is, at this time, either 2 or 3. The directory tree is as follows: i386/Release/2.2-cc2 Kernel 2.2.x, gnuc version 2.x used i386/Debug/2.2-cc2 i386/Release/2.4-cc2 Kernel 2.4.x, gnuc version 2.x used i386/Debug/2.4-cc2 i386/Release/2.4-cc3 Kernel 2.4.x, gnuc version 3.x used i386/Debug/2.4-cc3 For reference, the prior convention used was as follows: i386/Release/2.2 Kernel 2.2.x i386/Debug/2.2 i386/Release/2.4 Kernel 2.4.x i386/Debug/2.4 TestE1T1: Fixed problem where user keystroke wasn't processed when an initialization error occurred. OtxSS7SendData() is modified so that it can be used to send either an MSU followed by a repeated FISU, or a FISU followed by a repeated FISU. The T2p5x4Hdlc.c demo programs shows an example of how to use this functionality. Implemented driver support for the nInterFrameTimeFill parameter of the OtxHdlcSenderInit() function. Prior to this driver nInterFrameTimeFill was hardcoded to 2 (non-shared flags). Now shared flags are supported (nInterFrameTimeFill=1) as well as any of number of interframetimefill characters in the range of 0x0001 to 0xFFFF. The nInterFrameTimeFill parameter is supported in the following SPM modules: OTXHDLC, OTXSPM1, and OTXSPM2. Added DSP SDK support for the Vidar-55x4-ASM board. Please refer to the Sdk55Demo1.c and Sdk55Demo.2 demo programs. What is new in release, 1.0-P137 ================================ TT10180: Fix load problems on the Windows 98 and Windows NT4 platforms. (see 1.0-P136 release notes below). Updated, clarified and fix SDK API documentation. What is new in release, 1.0-P136 ================================ OtxT1E1SetLineTermination() did not set the proper termination for Li4, Li5, Li6, and Li7 for Thor-8-PCI of Build 4.0 and newer. This is now corrected. When using OtxDrvConnectPipe(), a connection mask is needed for pipes of a capacity < 64 kpbs. E.g. if a 56kpbs pipe is specified for an HDLC device, the timeslot mask for that pipe must be specified to 0xFE. The driver will now check the this requirement is fulfilled. Running frame format OTX_T1_FF_ESF and line coding OTX_T1_LC_AMI on Thor-8-PCI results in a different mapping of the timeslots on the internal highway. TS1 on the T1 span is mapped to TS31 on the internal highways, TS2 on the T1 span is mapped to TS0 on the internal highways, TS3 is mapped to TS1, etc. In this release the driver is modified to accept pipe connections to TS31, which would otherwise be an invalid connection. This mapping issued be be resolved in a future driver release. TT10180: An additional fix was applied to the driver for OtxDrvGetEventDataEx() (see 1.0-P135 release notes below). What is new in release, 1.0-P135 ================================ DTMF key '*' (941Hz/1209Hz) was not detected properly in the OTXSPM1 module. This is now corrected. The T2mDemo and T2p5x4 demo program were modified to include detection of all 16 possible DTMF tones (0-9, A-D, '*' and '#'). TT10180: Fix potential Windows exceptions when low memory conditions caused users application's memory to be paged out before the driver accessed it, resulting in a BSOD. Now, this memory is locked down in the driver before it is used. What is new in release, 1.0-P134 ================================ Error counters (Code violation, Framing Errors, E-bit/Errored Block, CRC) were inaccurate. This has now been corrected. Corrected a potential detection problem which could occur if multiple tone detectors were enabled for the same timeslot. The Single and Dual Tone Detector devices were enhanced. The attribute OTX_ATTR_SINGLE_TONE_DETECTOR_THRESHOLD_VARIANCE_ENERGY was added for the Single Tone Detector. The default threshold for all of the detectors were modified. The amplitude for the SineWave Generator device did not match the amplitude supplied (in dB) for its init function. This has now been corrected. Added Ring, Busy, and Dial tone detector functionality in the A16Vd5x4 demo program. Added support for Thor-1-PCI. What is new in release, 1.0-P133 ================================ Fixed mismatch dongle version in the driver for Thor-2-PCMCIA-Plus. The correct version should be "HMA-1079-2-1.0". Added support for Thor-2-PCI Build 11.0 and 12.0 (to support the new Vidar-55x4-ASM). Added support for Thor-8-PCI Build 5.0 and 6.0 (to support the new Vidar-55x4-ASM). What is new in release, 1.0-P132 ================================ It is now possible to send a constant DTMF tone using the OTX_LDEVICE_TONE_DTMF_DIALER device, but supplying nOnTime=0 in the call to the OtxToneDtmfDiallerInit() function. FISU filtering: A FISU is now considered changed only if the backwards sequence number changes. If only the forward sequence number changes the FISU is still considered unchanged, and remains filtered. The HDLC Receiver can now be reset (using OtxDrvReset()) to reset FISU/LSSU filtering function. Corrected OtxHdlcSS7SendData() so that it will properly send FISUs following the MSU. Support Alis Direct Register (8-bit) access by using OtxDrvReadReg8() and OtxDrvWriteReg8(). Added Linux Driver support for OTX (both PCI and PCMCIA) boards, Linux kernel is up to 2.4.18 What is new in release, 1.0-P131 ================================ Internal release. Added support for OTX_LDEVICE_TONE_FSK_DETECTOR devices in OTXSPM1. What is new in release, 1.0-P130 ================================ Internal release. Added support for OTX_LDEVICE_TONE_SILENCE_DETECTOR devices in OTXSPM1. What is new in release, 1.0-P129 ================================ Added OTX Driver support for Linux Kernel 2.4.x Added support for Single Tone Detector in the Spm2 Dsp module. The single tone detector can detect a tone. The frequencies to detect are supplied as a parameter to this function. This device can handle 6 frequencies (FreqA through FreqF). The detected tones can either be stored in the Event Queue and be extracted with the appropriate Read function, or they can be stored internally in which case only the most recently received digit can be retrieved with a call to function OtxToneSingleDetectorStatus Start detection by calling the function OtxDrvEnable and stop generation by calling the function OtxDrvDisable SingleTone Detector is initialized as follows: OTX_RESULT OtxToneSingleDetectorInit( IN OTX_HANDLE hDevice, // @parm Handle to the Logical device IN OtxDataFormatE eDataFormat, // @parm Data Format of the Monitored Data Stream IN OTX_UINT32 sqFreq[], // @parm An array of up to 6 frequencies to be detected. IN OTX_INT32 coFreq, // @parm Number of elements in

IN OTX_BOOL bStoreInQueue, // @parm If OTX_TRUE, generate events and store the received digits IN OTX_BOOL bReportPause, // @parm If OTX_TRUE the detector generates an event when a tone ends IN OTX_INT16 nMinDuration // @parm Minimum duration required to validate a digit ); Spm3 DSP module: Increased number of Dtmf/Val devices from 30 to 31. This module also contains 2 Hdlc/Rawdata devices. Added a demo program T2p5x4Spm3 which illustrates the features of OtxSpm3 Dsp module. Added support for COFF version 2 for DSP modules. What is new in release, 1.0-P128 ================================ Added support for generic Dual Tone Detector in the Spm2 Dsp module. The dual tone detector can detect a number tone pairs (two-frequency tones). The frequencies to detect are supplied as a parameter to this function. This device can handle 6 frequencies (FreqA through FreqF). The detected tones can either be stored in the Event Queue and be extracted with the appropriate Read function, or they can be stored internally in which case only the most recently received digit can be retrieved with a call to function OtxToneDualDetectorStatus Start detection by calling the function OtxDrvEnable and stop generation by calling the function OtxDrvDisable DualTone Detector is initialized as follows: OTX_RESULT OtxToneDualDetectorInit( IN OTX_HANDLE hDevice, // Handle to the Logical device IN OtxDataFormatE eDataFormat, // Data Format of the Monitored Data Stream IN OTX_UINT32 sqFreq[], // An array of up to 6 frequencies to be detected. IN OTX_INT32 coFreq, // Number of elements in

IN OTX_BOOL bStoreInQueue, // If OTX_TRUE, generate events and store the received digits IN OTX_BOOL bReportPause, // If OTX_TRUE the detector generates an event when a tone ends IN OTX_INT16 nMinDuration // Minimum duration required to validate a digit ); Demo feature of the DualTone Detector implementation can be found in the A16Vd5x4 program which uses an Arni Board with a 5x4 DSP daughter board. Added Spm3 DSP module. This DSP module comprises of the following devices: 30 Dtmf senders and receivers, 30 Constant Val generators and samplers, 2 Hdlc Senders and receivers 2 Rawdata senders and receivers Removed the channel mapping on the SLC96 TR08 signalling mode. This would make the device more flexible with all the shelves of SLC96 mode. What is new in release, 1.0-P126 ================================ Fixed a problem of HDLC sender. Support for HDLC frames of length > 255 octets. Fixed SLC96 TR08 mode which was not reading bits every 3ms. Added support for 56kbps. What is new in release, 1.0-P125 ================================ Updated firmware for Arni-16-PCI. A net was not driven to a proper level. This has now been corrected (A32AIC 1.0-P21). Added support for TurnstoneCe What is new in release, 1.0-P121 ================================ Added support for Thor-8-PCI Build 1.0-P2. Added TR08 decoding for the OTX_LDEVICE_T1_ROB_BIT_ACCESS device. This mode is enable by setting the new attribute OTX_ATTR_T1E1_TR08_MODE to OTX_TRUE for those hosting T1E1 device. For more information on this mode please refer to the OTX_ATTR_T1E1_TR08_MODE declaration in OtxT1E1D.h. What is new in release, 1.0-P120 ================================ Added support for Thor-2-PCI build 10. What is new in release, 1.0-P119 ================================ Internal release. Testing DSP loading on 700+ MHz PCs. Implemented an extended queue in the DSP code for the HDLC Sender device. The added queue makes the driver accept longer interrupt latencies. Added new attributes for the HDLC Sender which can be used to optimize the performance of the buffer handling of this device (for further details please refer to OtxHdlcD.h): OTX_ATTR_HDLC_SENDER_MAX_QUEUED_PACKETS OTX_ATTR_HDLC_SENDER_QUEUE_NOTIFY_LEVEL OTX_ATTR_HDLC_SENDER_QUEUE_MAX_PACKET_SIZE Added a new SPM called OtxHdlcE.out (based on the OtxHdlc.out SPM) which utilizes extended DSP memory (available on Vidar-5x4-ASM and Vidar-5x16-PCI) to increase the available heap space (dynamic memory used for the transmit and receive buffers within the DSP). Added new event codes for the Raw Data Receiver. The events codes are active when the Raw Data Receiver is configured to filter flags (for further details please refer to OtxRawD.h): OTX_RAWDATA_RECEIVER_EC_EXTRACTING_FLAGS OTX_RAWDATA_RECEIVER_EC_BUFFERING_DATA Changed memory allocation function in the Linux driver to vmalloc() (instead of kmalloc() which was used in earlier versions of the drivers but which is limited to 128k of total allocated memory for Intel platforms). Using vmalloc will allow the driver to allocate more memory for buffers (e.g. when setting OTX_ATTR_DEVICE_IRP_QUEUE_LIMIT and OTX_ATTR_RAWDATA_RECEIVER_FIFO_SIZE attributes). What is new in release, 1.0-P118 ================================ Internal release. Testing DSP loading on 700+ MHz PCs. The interrupts did not reach the driver when using the OTX Linux driver with the Thor-2-PCMCIA card. This has now been corrected. Implemented an extended queue for Notify Events sent from the DSP code to the host driver. The added queue makes the driver accept longer interrupt latencies. Added attributes OTX_ATTR_DSP_NOTIFICATION_EVENT_EXT_QUEUE_CURRENT_USAGE and OTX_ATTR_DSP_NOTIFICATION_EVENT_EXT_QUEUE_PEAK_USAGE which can be used to read utilization statistics from the extended event queue. What is new in release, 1.0-P117 ================================ The OTX_LDEVICE_DATA_RAW_RECEIVER device implemented in the OTXSPM1 DSP module would produce corrupt data (when used with any of the OTX_DATA_FORMAT_UINT16, OTX_DATA_FORMAT_COMPAND8_A_LAW, or OTX_DATA_FORMAT_COMPAND8_U_LAW data formats). This has now been corrected. Added attribute OTX_ATTR_BRD_PCMCIA_DONGLE0_AMP_ON and OTX_ATTR_BRD_PCMCIA_DONGLE1_AMP_ON (only applicable for the HMA-1079-2-1.1 dongle for the Thor-2-PCMCIA-Plus card) Added the OTX_ATTR_T1E1_RX_INPUT_THRESHOLD attribute which provides an easy way to modify the Receive Input Threshold of the T1E1 device. This attribute is further described in the OtxT1E1D.h header file. Added attributes OTX_ATTR_BRD_DEVICE_ID and OTX_ATTR_BRD_SUBSYSTEM_ID to access the product number and revision of the board. Please refer to OtxBrdD.h for further details. What is new in release, 1.0-P116 ================================ Internal release. Testing DSP loading on 700+ MHz PCs. What is new in release, 1.0-P115 ================================ Added support for the HMA-1079-2-1.0 dongle type for the Thor-2-PCMCIA-Plus card. (Plese see the OTX_ATTR_BRD_PCMCIA_DONGLE_TYPE attribute). The default dongle type for the Thor-2-PCMCIA-Plus card is now the HMA-1079-2-1.0 dongle. The OtxT1E1SetLineTermination() for Li#1 on the Thor-2-PCMCIA-Plus card would set the termination for Li#0. This has now been corrected. What is new in release, 1.0-P114 ================================ Added two new clock sources OTX_CLOCK_SOURCE_A_CLOCKS_ETCF and OTX_CLOCK_SOURCE_B_CLOCKS_ETCF (used as a parameter to the OtxBrdSetClocks() function). These clocks source will make board synchronize to an 8.192 MHz clock provided on C8A (or C8B respectively). The OTX_CLOCK_SOURCE_A_CLOCKS and OTX_CLOCK_SOURCE_A_CLOCKS clock sources have not changed. These two clock source will synchronize to a 4.096 MHz clock provided on C8A (or C8B respectively) as in earlier releases of the driver. Added a new clock mode OTX_CLOCK_MODE_H100_ETCF (used as a parameter to the OtxBrdSetClocks() function). If this mode is used with any of the bus driving clock sources (see OtxBrdClockSourceE), this mode will drive the C8A, C8B, FRAMEA and FRAMEB H.100 clocks in ETCF mode (noninverted 8.192 MHz). The OTX_CLOCK_MODE_H100 has not changed. If this mode is used with any of the bus driving clock sources (see ), this mode will drive the C8A, C8B, FRAMEA and FRAMEB H.100 clocks in MC-1 mode (inverted 4.096 MHz) as in earlier releases of the driver. Added support for Hermod-PCI (JTAG controller board). Multiple successive connections/disconnections of logical devices would exhaust the DSP heap in the OTXHDLC SPM. This has now been corrected. Added a new attribute OTX_ATTR_BRD_PNP_ID, which can be used to read the Plug-and-Play ID of the board (only applicable for the OTX WDM driver). Please refer to the Thor-2-PCMCIA\T2mDemo for an example of how to use this attribute. The 1.0-P100 version of the driver introduced a new problem in the Raw Data Receiver device. Every 16th octet was received with a constant value of 0 (for a 64kpbs pipe). This faulty behavior has now been corrected. Added two new attributes OTX_ATTR_RAWDATA_RECEIVER_GENERATE_DATA_EVENTS and OTX_ATTR_RAWDATA_SENDER_GENERATE_DATA_EVENTS, which can be used to prevent the driver from generating events when Raw Data is available/needed. By setting these attributes to OTX_FALSE some event handling process can be eliminated, thus increasing performance. The demo program Thor2Pcmcia\T2mRawData.c shows an example of how to use the OTX_ATTR_RAWDATA_RECEIVER_GENERATE_DATA_EVENTS event. What is new in release, 1.0-P113 ================================ OtxDrvReadReg8() and OtxDrvWriteReg8() are now implemented for the TSS device. What is new in release, 1.0-P112 ================================ Added support for multiple OTX PCMCIA cards in the Linux driver. What is new in release, 1.0-P111 ================================ Added support for the Thor-2-PCMCIA board in the Linux driver. The support is distributed in a separate package, otxdrv_csLinux.tar.gz. What is new in release, 1.0-P110 ================================ Internal release. Added split clock support for Thor-2-PCMCIA-Plus. The following clock modes were added: OTX_CLOCK_SOURCE_LOCAL_3: Split clock, both Lis synchronized to its respective T1E1 span OTX_CLOCK_SOURCE_LOCAL_4: Split clock, Li0 synchronized to its T1E1 span. Li1 internal. OTX_CLOCK_SOURCE_LOCAL_5: Split clock, Li1 synchronized to its T1E1 span. Li0 internal. What is new in release, 1.0-P109 ================================ Internal release. Testing DSP loading on 700+ MHz PCs. What is new in release, 1.0-P108 ================================ Corrupted timestamps could occur when OTX_ATTR_DRV_TIMESTAMP_FROM_1601 was set. This has now been corrected. Added support for setting the CT bus rate (2048, 4096, or 8192 kpbs). Please see the OTX_ATTR_TSS_CTBUS_RATE_STREAM_GROUP_x attributes in OtxBrdD.h. The demo application Thor2Pci\2T2p.c demonstrates the use of this new functionality. What is new in release, 1.0-P107 ================================ Added OTX_ATTR_RAWDATA_RECEIVER_FIFO_SIZE attribute which allows the application to modify the Fifo size allocated in the driver for the received raw data stream. The RawDataReceiver device now allocated a fifo size which depends on the capacity of the pipe which is connects to. For faster pipes a larger fifo is allocated. The demo application Thor2Pcmcia\T2mRawData.c demonstrates the use of this new functionality. What is new in release, 1.0-P106 ================================ Added OTX_ATTR_DTMF_DETECTOR_MIN_DURATION attribute. This attribute can be used to modify the minimum required duration of the tone before it is reported as a DTMF digit. The time is specified in milliseconds. The demo program Thor2Pcmcia\T2mDemo shows an example of how to use this attribute. The timeslots were skewed on the internal highways (in relation to the E1/T1 span) for the Thor-2-PCMCIA-Plus card. This has now been corrected. The thresholds for the secondary harmonics of the DTMF tones (in OtxSpm1) were incorrect. This problem has now been corrected. Inplemented the auto reset functionality for Thor-2-PCMCIA-Plus. Implemented the OTX_LDEVICE_TONE_MF_DETECTOR and OTX_LDEVICE_TONE_MF_DIALER devices in a new SPM (OtxSpm2). OtxSpm2 supports 8 devices of each type (please see a OdDspD.h). Please refer to the Thor2Pci\T2p5x4.c demo program for an example of how to use the new MF devices. Reduced driver code overhead when servicing DSP interrupts (which decreases the chances of overflowing the DSP notification event buffer). What is new in release, 1.0-P105 ================================ Minor corrections to the handling of the OTX_ATTR_T1E1_AUTOMATIC_RESET attribute. What is new in release, 1.0-P104 ================================ Added OTX_ATTR_DEVICE_IRP_QUEUE_LIMIT and OTX_ATTR_DEVICE_IRP_QUEUE_SIZE attributes. These attributes sets or gets the number of the IO Request Packets (IRP) that the driver can buffer for this device, which can be used to optimize the behaviour for devices like OTX_LDEVICE_HDLC_SENDER and OTX_LDEVICE_DATA_RAW_SENDER. The OTX_T1E1_EC_LOSR event was not always reported properly. This has now been corrected. The OTX_ATTR_T1E1_AUTOMATIC_RESET attribute now defaults to OTX_TRUE, i.e. the T1/E1 device will attempt to reset itself if an abnormal condition occurs (e.g. due to an ESD strike). What is new in release, 1.0-P103 ================================ If CRC6 generation/checking is selected in T1 mode (by setting bCRC6Enable to OTX_TRUE in the OtxT1ConfigOptionsS struct), the T1E1 device is now configured to check both the framing pattern and the CRC6 bits before synchronous state is reached. This change should eliminate the continuous "Errored Block Count" status message which could occur when the T1 span is connected to the T1E1 device. DTMF detector threshold parameters tuned to meet DTMF standards. Added OTX_ATTR_T1E1_SECONDS_INTERRUPT attribute which can be used a 1 second heartbeat watch dog from the T1E1 device. The call sequence OtxT1SetConfiguration()/OtxE1SetConfiguration() followed by OtxT1E1SetLiMode() can now be called to reconfigure the E1T1 device with different options. Loop settings are preserved through this call sequence. Added OTX_DSP_EC_NOTIFY_EVENT_FREQ_HIGH event code, which can be used to determine if the event frequency from the DSP is approaching the upper limit (fatal errors are imminent). Added OTX_ATTR_DSP_AUTO_DISABLE attribute which can be used to disable the "Auto Disable" feature of the DSP device. Added OTX_BRD_EC_AUTO_DISABLED event. If a fatal error (e.g. an infinite interrupt loop) would occur, the this event will be issued from the board device. Added OTX_BRD_EC_INTR_FREQ_TOO_HIGH event. This event will be issued for the board device if the interrupt frequency reaches critical levels. What is new in release, 1.0-P102 ================================ Added a new attribute OTX_ATTR_BRD_PCMCIA_DONGLE_TYPE which informs the driver of which dongle that is connected to a Thor-2-PCMCIA or Thor-2-PCMCIA-Plus board. The driver uses this information to customize the transmit pulse mask for the E1/T1 span (to be compliant with the G.703 and T1.102 standards). Interrupts from Li4 and Li12 on Arni-16-PCI did not reach the driver properly. This has now been corrected. Li devices on Arni-16-PCI are now reset when opened and closed (i.e. it returns to On-hook state). Added a new attribute OTX_ATTR_POTS_CFG_SET, which sets the Country Specific configuration set for the POTS line interface (e.g. DC characteristics, ringer impedance, filter coefficients, etc). Please see the Arni32Pci\A16Vd5x4 demo program for an example of how to use this attribute. What is new in release, 1.0-P101 ================================ Added support for the Thor-2-PCMCIA-Plus board. Internal release. What is new in release, 1.0-P100 ================================ The driver could BSOD if a board-to-board pipe connection was made without having the proper board serial number information entered in the registry (Win32 drivers only). This has now been corrected. Added a new physical device OTX_DEVICE_CT_BUS, which represents one H.100 interconnect cable. This device is hosted by the driver device and can be opened with OtxDrvOpenPhysicalDevice(). The driver can be informed of CT Bus board connections by calling OtxDrvConnectBoard(). This allows CT bus connections to work in the Linux driver. The Thor2Pci\2T2p.c demo program was modified to support multiple CT buses (/N switch). This demo program shows an example of how to use the new OTX_DEVICE_CT_BUS device. (Supplying board interconnect information via the registry in Win32 still works the same way as before.) The could crash if the OtxRawDataReadData(), OtxHdlcReadData() or OtxDspReadData() was called with a buffer which had been paged out by the operating system. This problem has now been corrected. Implemented the OTX_LDEVICE_DATA_RAW_RECEIVER and OTX_LDEVICE_DATA_RAW_SENDER device in the OtxSpm1 SPM. These devices now supports different OtxDataFormatE (in the OtxSpm1 implementation). OtxRawDataReceiverInit() and OtxRawDataSenderInit() now takes one additional parameter, eDataFormat. Sharing of interrupts between several OTX boards are now properly handled in the Win32 drivers. What is new in release, 1.0-P99 =============================== Added support for the External clock mode for Thor-2-PCI (harmonica connector Local clock 0 and Local clock 1). Added new attribute OTX_ATTR_LIB_TYPE_STATIC which can be used to determine if the OTX library is a static or dynamic linked library. Please see Thor2Pci\ThorDemo.c for an example of how to use this attribute. Added new attribute OTX_ATTR_LIB_FILE_NAME which can be used to query the file name of the OTX library linked with the application. Please see Thor2Pci\ThorDemo.c for an example of how to use this attribute. Added attribute to query the HDLC Receiver Fifo for current/max usage. Please see Thor2Pci\T2p5x4Hdlc.c for an example of how to use these attributes. ABCD bit (Bitrob) access in T1 mode did not work properly for the Thor-8-PCI. This has now been corrected. Added OTX_ATTR_T1E1_CHANNELIZED_ABCD_BIT_ACCESS attribute for the T1E1 device and OtxT1SetChannelizedRobBitData(), OtxT1GetChannelizedRobBitData(), OtxE1SetChannelizedABCDBit(), OtxE1GetChannelizedABCDBit() API functions. By setting this attribute for the T1E1 device you enable these new API functions which can set and get ABCD data per channel. When this new attribute is set to OTX_TRUE the OTX_T1E1_EC_BITROB_SIGNALING event will report ABCD bit changes per channel (instead of one event for A-bits, one for B-bits, etc). Please see the OtxT1E1D.h header file for further information on this new attribute. Please see the Thor2Pci\T2pT1RobBit.c Thor2Pci\T2pE1ABCDBit demo programs for examples of how to use this new feature. The OTX_LDEVICE_TONE_SINEWAVE_GENERATOR device is modified to support generation of up to 5 different sinewave components. Pleae note that the parameters to OtxToneSineWaveGeneratorInit() have changed. The tone parameters are now specified in terms of frequency (Hz) and attenuation (dB). Please see the Thor2Pci\T2p5x4.c demo program for an example of how to use these features. The OTX_RAWDATA_SENDER_EC_COMPLETED event used to contain 0xFFFF in the m_RequestId field of the OtxEventDataS. Now it contains the nTaskRef of the last transmitted packet (frame). Added support for the OTX_LDEVICE_DATA_CONVERTER device in the OtxHdlc SPM to facilitate cross-connections of timeslots (mainly target for the Thor-2-PCMCIA). Please see the DemoCrossConnect() function in Thor2Pcmcia\T2mDemo.c for an example of how to use the OTX_LDEVICE_DATA_CONVERTER as a cross-connect device. Calling OtxDrvGetAttributeType() for OTX_ATTR_T1E1_CHANNELIZED_ABCD_BIT_ACCESS would fail. This has now been corrected. Now the OTX_LDEVICE_E1_S_BIT_ACCESS device will generate an event OTX_T1E1_EC_SA_BITS_CHANGED when the Sa bits change. Please see the Thor2Pci\T2pE1Sbits.c demo program for an example of this feature. This feature can be turned off by setting the OTX_ATTR_T1E1_S_BIT_CHANGE_EVENTS attribute to OTX_FALSE. Added a new logical device, OTX_LDEVICE_T1_DL_BIT_ACCESS, which can be used to access the DL-bits in T1 mode. Please see the Thor2Pci\T2pT1DlBit.c demo program for an example of how to use this device. Added OTX_ATTR_PIPE_CT_BUS_CONNECTIONS_COUNT and OTX_ATTR_PIPE_CT_BUS_CONNECTIONS_DETAILS attributes to allow querying of the timeslot/highway usage for pipes which are connected over the H.100 bus. The demo program Thor2Pci\2T2p.c shows an example of how to use these attributes. Implemented OtxDrvGetEventDataEx() which fetches multiple events that occurred in the driver. This function has the same functionality as the OtxDrvGetEventData() function, except that this function is able to fetch multiple events from the driver in one call (and thus reduce overhead introduced by context-switching). Please see the Thor2Pci\ThorDemo.c demo program for an example of how to use this feature. What is new in release, 1.0-P98 =============================== The driver did not properly report a memory allocation error when a logical device was created (mostly apparent in the Linux driver). This has now been corrected. The Linux driver did not always allocate memory with the correct priority. This has now been corrected. Modified the transmit pulse mask slightly to make it comply with the G.703 standard. Implemented new setable attributes for the T1E1 device, OTX_ATTR_T1E1_TX_PULSE_MASK_SUB_PULSE_x, which allows customization of the transmit pulse mask. Please see the OtxT1E1AttributesE type in the OtxT1E1D.h header and the Thor2Pci\ThorDemo.c demo program for an example of how to use these attributes. Added OtxDrvOpenPhysicalDeviceEx(), which can be used to open a physical device if the handle is previously acquired by a call to OtxDrvEnumDevice(). Please see the Generic\EnumOtxDevices.c for an example of how to use this function. What is new in release, 1.0-P97 =============================== Internal release. Attempt to correct bug which could cause the NT4 driver to (blue screen) in a OtxRawDataReadData(), OtxHdlcReadData(), or OtxDspReadData() call. The timer used for the time-stamping of driver events is now re-synchronized with the system time every time the OTX_ATTR_DRV_TIMESTAMP_FROM_1601 attribute is set. What is new in release, 1.0-P96 =============================== The attribute OTX_ATTR_DSP_NOTIFICATION_EVENT_BUF_INCLUDE_TIMESTAMP is now changed to FALSE as default. I.e. there is not DSP supplied timestamp in the DSP->host event notification packets. Fixed a bug in the internal Test Bus Controller (TBC) which could potentially cause the driver to hang during the driver loading process (predominantly occurring for Thor-8-PCI boards). The maximum DTMF string length which the DTMF Dialler device can handle was increased to 32 digits. The low level IO access performance was improved for the Thor-2-PCMCIA board. The RawDataReceiver implementation in the OtxHdlc SPM was optimized to support 32x64kpbs pipes. What is new in release, 1.0-P95 =============================== Corrected a problem in the OTX driver which could cause the operating system to crash (especially noticeable in Linux and Win98). This scenario could be triggered by an HDLC Sender (hosted by the DSP) sending frequent long frames. What is new in release, 1.0-P94 =============================== The E1T1 event code OTX_T1E1_EC_AISR had the wrong value. It was corrected. The OTX_LDEVICE_T1_ROB_BIT_ACCESS now filters OTX_T1E1_EC_BITROB_SIGNALING events for timeslot which are defined as clear-channels. The OTX_LDEVICE_DATA_RAW_RECEIVER, OTX_LDEVICE_HDLC_RECEIVER, OTX_LDEVICE_USER_APPLICATION will now discard any data which is received during a full event queue condition. An new system IO code for the DSP SDK is defined. OTXDSP_SDK_IO_CLOSE, which is issued when OtxDrvClose() is called. It is now possible to close a logical device without having to first call OtxDrvDisconnectLogicalDevice(). Closing of the HDLC Sender and HDLC Receiver hosted by the E1T1 device will now correctly disconnect from its previously connected timeslot(s). Corrected a problem with the DSP handle of OTX_LDEVICE_USER_APPLICATION logical device, which was introduced in the 1.0-P92 version of the driver. What is new in release, 1.0-P93 =============================== Dynamic connection and disconnection of the OTX_LDEVICE_DATA_CONVERTER device now works as intended. Increased the device capacity for the OtxSpm1 module. OtxSpm1 now supports the following logical devices: 8 OTX_LDEVICE_HDLC_RECEIVER (all 8 can not be enabled at one time) 8 OTX_LDEVICE_HDLC_SENDER (all 8 can not be enabled at one time) 16 OTX_LDEVICE_TONE_DTMF_DETECTOR 16 OTX_LDEVICE_TONE_DTMF_DIALER 16 OTX_LDEVICE_TONE_EFFECTS_GENERATOR 16 OTX_LDEVICE_DATA_CONVERTER 16 OTX_LDEVICE_TONE_CONST_VAL_GENERATOR 16 OTX_LDEVICE_TONE_VAL_SAMPLER 16 OTX_LDEVICE_TONE_SINEWAVE_GENERATOR 16 OTX_LDEVICE_TONE_SILENCE_DETECTOR Added support for OTX_LDEVICE_TONE_VAL_SAMPLER in the OtxSpm1 DSP module. What is new in release, 1.0-P92 =============================== The implementation of the SS7 filtering functions have changed: OTX_HDLC_SS7_FILTER_FISU - Filters identical consecutive FISU frames (LI=0) OTX_HDLC_SS7_FILTER_SHORT_LSSU - Filters identical consecutive Short LSSU frames (LI=1) OTX_HDLC_SS7_FILTER_LONG_LSSU - Filters identical consecutive Long LSSU frames (LI=2) OTX_HDLC_SS7_FILTER_FISU_ALL - Filters all FISU frames (LI=0) OTX_HDLC_SS7_FILTER_SHORT_LSSU_ALL - Filters all Short LSSU frames (LI=1) OTX_HDLC_SS7_FILTER_LONG_LSSU_ALL - Filters all Short LSSU frames (LI=2) Plesae see the OtxHdlcSS7SetFilter() API call in the T2ptx5Hdlc.c demo program for an example of how to use the SS7 filtering functions. The demo program T2p5x4Hdlc has been modified to work with the Thor-8-PCI board (please see the /T8 command line switch). OtxHdlcSS7GetFilter() now works as intended. OtxHdlcSS7SendData(), OtxHdlcStartRepeatData(), and OtxHdlcStopRepeatData() were implemented. What is new in release, 1.0-P91 =============================== The OTX_ATTR_BRD_PCMCIA_SOCKET_NUMBER attribute should now work on any PCMCIA controller in Win98 (the WDM driver). Added Thor2Pci\T2pE1Sbits.c demo program. The DspSdk Demo programs (DspDemo1 and DspDemo2) programs were added to the Win32 and Linux Driver SDKs. What is new in release, 1.0-P90 =============================== Added the attribute OTX_ATTR_BRD_USER_STRING, which is a user supplied string stored persistently on the board. Corrected a problem which caused the HDLC Sender and the Raw Data Sender to send corrupt data for pipes with a capacity larger than 64 kbps. Improved performance for Hdlc Senders and Hdlc Receivers in the OtxHdlc DSP module. Now this module supports up to 20*64kpbs pipe capacity for the Hdlc Sender or 14*64kpbs pipe capacity for the Hdlc Receiver. Errored seconds (e.g. Slips and Code Violations) interrupts from the E1/T1 device are now ignored if LOS (Loss Of Signal) is active. Added new DSP attributes (see OtxDspD.h) which will allow a DSP SDK application to override the default HPI configuration (Event Notification Buffer and IO Control buffer). See DspIoctl.h and the DspDemo1 demo application for an example. Added a new attributes OTX_ATTR_LIB_REV_STR and OTX_ATTR_LIB_REV_NUM. These attributes can be used to read the revision of the library (without communicating with the driver). See ThorDemo.c for an example of how to use these attributes. Added a new boolean attribute OTX_ATTR_DRV_TIMESTAMP_FROM_1601, which can be used to change the base of the timestamp generated by the driver. If this attribute is set to OTX_FALSE, then the driver uses QueryPerformanceCounter() as the method of timestamping (NT and WDM drivers only). See the Thor2Pcmcia\T2mDemo.c demo application for an example of how to use this attribute. What is new in release, 1.0-P89 =============================== Corrected a problem in the Thor2Pci\T2p5x4Recorder.c demo program. The 'p' key will now start the DemoRawDataSender thread correctly. The filtering of SS7 LSSUs has changed. If filtering of LSSU is enabled (by calling the OtxHdlcSS7SetFilter() API function) repeated LSSU frames are filtered. As soon as the LSSU frame changes (compared to the previously received LSSU frame) it is delivered (unfiltered) to the API. Added the following attributes in OtxDspD.h: OTX_ATTR_DSP_NOTIFICATION_EVENT_BUF_CURRENT_USAGE OTX_ATTR_DSP_NOTIFICATION_EVENT_BUF_MAX_USAGE OTX_ATTR_DSP_NOTIFICATION_EVENT_BUF_SIZE OTX_ATTR_DSP_NOTIFICATION_EVENT_BUF_LOST_EVENTS These attributes can be used to query the status of the Notification Event Buffer in the DSP. The pragma for the struct packing is changed in the OtxHdlcD.h, OtxT1E1D.h, and DspIoctl.h files (to accommodate for multiple inclusions of API header files). What is new in release, 1.0-P88 =============================== OtxDspRunImage was not exported in the OtxHwDll.dll library. This has been corrected. Added support for the SystemSoft Card Wizard (NT4 driver with the Thor-2-PCMCIA card). Please note that the OtxDrv.reg file is updated in this release. Added new API functions OtxDspReadHpi() and OtxDspWriteHpi(). These functions are special-purpose functions, and should only be used by advanced DSP SDK users. What is new in release, 1.0-P87 =============================== Corrected a bug in the HDLC Sender device (hosted by the DSP) which could cause corrupt HDLC frames (for certain CRC octets). Added support for the Thor-2-PCMCIA card in the OTX NT4 driver. Please note that the OtxDrv.reg file is updated, and that NT4 only supports one card of the same type in the PCMCIA sockets. What is new in release, 1.0-P86 =============================== Implemented new T1E1 events (OTX_T1E1_EC_APIR, OTX_T1E1_EC_LOSR, OTX_T1E1_EC_LMFAR16, OTX_T1E1_EC_AISR) which are sent when a certain alarm goes inactive. Added attributes: OTX_ATTR_BRD_PCMCIA_SOCKET_NUMBER OTX_ATTR_BRD_PCI_DEVICE_NUMBER OTX_ATTR_BRD_PCI_FUNCTION_NUMBER Please see OtxBrdD.h and T2mDemo.c for an example of how to use these attributes. The WDM driver now has added support for surprise removal. Surprise removal is now safe as long as the OTX application is idle (i.e. it is not executing in kernel mode at the exact time of the board removal). What is new in release, 1.0-P85 =============================== The NT4 driver could conflict with other PCI boards having the deviceId as the OTX boards. This has now been corrected. OtxPotsOffHook() for the Arni-16-PCI board would fail on faster PCs. This has now been corrected. What is new in release, 1.0-P84 =============================== The timestamps in the driver events could wrap after some time on faster PCs. This has been corrected. OtxDspRunXXX() could hang the PC (or return with a timeout error code) on occasion. This has been corrected. What is new in release, 1.0-P83 =============================== Simplified the makefile for building the OTX Linux driver (OtxDrv.o). Please see the BuildDrv.txt file. Corrected a problem with H.100 connections for the Vidar-5x16-PCI board. What is new in release, 1.0-P82 =============================== Prevented the driver (WDM) from unloading if an application has opened any OTX devices. The OtxDrvReset() for a logical device will now flush (empty) the queue of any IO or data packets waiting to be transmitted to the DSP. The default Line Termination for the E1/T1 front end (after the driver loads) has been changed from OTX_T1E1_TERM_100_OHM to OTX_T1E1_TERM_HIGHZ. An application should call OtxT1E1SetLineTermination() to switch the board to the desired termination mode. OtxT1E1SetLineTermination() for Thor-8-PCI did not work properly. This has now been corrected. Corrected a problem related to the compilation of the Linux driver. The Linux driver is now distributed with a single makefile which makes the OTX Linux driver. Added a new API function OtxT1E1SetMonitorMode() which can be use to switch the E1T1 transceivers on Thor-8-PCI in to a -20dB monitor mode. Reverted back to host generated timestamps. The granularity (tick frequency) of the timestamps generated by the host is improved for the NT and WDM drivers. These host generated timestamps now have a tick frequency of around 1us. However, timestamps are still reported in the OTX standard 100ns tick steps. Added support for Thor-2-PCI Build 5. What is new in release, 1.0-P81 =============================== Logicaldevices hosted by the DSP device now use a timestamp of a higher accuracy. The timestamp clock (in each DSP) is running at 10MHz producing a time stamp "tick" of 100ns. A new API function OtxDspRestartProgram() was added. This function needs to be called if a DSP Debugger is attached (e.g. Code Composer). Please see the DSP SDK Demo program DspDemo1 for an example of how to use the OtxDspRestartProgram() function. Added two new IO codes for the DSP SDK (OTXDSP_SDK_IO_START_PROGRAM and OTXDSP_SDK_IO_INIT_TIMER). The revision of the driver is passed in the OTXDSP_SDK_IO_START_PROGRAM call. The handle of the pipe is now passed to the DSP in the DSP SDK OTXDSP_SDK_IO_CONNECT and OTXDSP_SDK_IO_DISCONNECT calls. Servicing of the serial ports in the DSP SDK is now called from the main idle loop instead of directly from the ISR (as before). Implemented OtxRawDataSenderFlush() which flushes (empties) the queue of raw data octets waiting to be transmitted (if any). Source code for the Linux driver is now supplied with the Linux Driver distribution which allows the driver to be compiled for any Linux kernel version. What is new in release, 1.0-P80 =============================== Added support for one-to-many connections over the H.100 bus. Added a more extensive check for the validity of a connection. OtxDrvConnectPipe() will now return an error code for invalid connections. In additions to the static linked OtxDrv.Lib, the Win32 driver SDK is now distributed with a dynamically linked library (OtxHwDll.dll and OtxHwDll.lib) as well. Please see the Dll directory in the distribution package. What is new in release, 1.0-P79 =============================== Added support for subchannel (8, 16, 32 kpbs) for the HDLC Sender/Receiver and the Raw Data Sender/Receiver devices. Please see Thor2Pcmcia\T2mDemo (with the /ph command line switch) and Thor2Pcmcia\T2mRawData (with the /n8, /n16 or, /n32 command line switch) for an example of how to use this added feature. Please note that the driver can only make 64kpbs through-connections in the Time-Space-switch. Therefore, all subchannels within the same timeslot (64kpbs) must be processed by the same DSP. The driver does yet check that this requirement is not violated. Corrected some problems in OtxDrvDisconnectPipe() and OtxDrvDisconnectLogicalDevice(). What is new in release, 1.0-P78 =============================== Corrected a bug related to the host-DSP IO communication which could cause corrupt IO packets over this interface. This bug was especially apparent on an multi-processor machine, but it could also occur (although less frequent) on a single processor. The symptom of this bug could be that DSP IO commands could be sent to the wrong device, or the DSP communication would stop functioning resulting in a return code indicating that a time has occurred. Increased IO performance to the DSPs located on Vidar-5x4-ASM hosted by a Thor-2-PCI board. Linux driver is now compiled for kernel 2.2.12 (instead of 2.2.5 for earlier drivers). What is new in release, 1.0-P77 =============================== Corrected a bug in OtxDspReadData() which caused the driver to crash (DspDemo1 and DspDemo2). The 1.0-P76 version of the driver did not work with the Thor-2-PCMCIA board. This has now been corrected. Implemented OTX_T1E1_LOCAL_LOOP (loop of the internal highway) in the E1T1 device. See OtxT1E1LoopE in OtxT1E1D.h. What is new in release, 1.0-P76 =============================== Improved the DTMF detector in the OtxSpm1 module to prevent it from detecting digits in white noise. It is now possible to start the driver while a DSP Emulator/Debugger is connected to the Hermod-2x20 debug module. Implemented OtxToneDtmfDetectorStatus(). What is new in release, 1.0-P75 =============================== Note: There will an API change in the release following this release. The names of the API header file names will change. Added a Visual C++ 6.0 workspace file called Demos\DskSdkDemos.dsw which includes all of the DrvSdkWin32 demos. Each project file automatically links the OtxDrv.lib library. New T1E1 option bAutoCrcBitInversion in OtxE1ConfigOptionsS and OtxT1ConfigOptionsS. If set to OTX_TRUE, all CRC bits of one outgoing sub-multiframe are inverted in case a CRC error is flagged for the previous received sub-multiframe. The parameters to OtxHdlcReadDataEx() have changed. Please see Thor2Pci\ThorDemo and Thor2Pci\T2p5x4Hdlc for an example of how to use the OtxHdlcReadDataEx() function. The demo program Thor2Pcmcia\T2mDemo now works for both Thor-2-PCMCIA and Thor-2-PCI/Vidar-5x4-ASM (see the /T command line switch). Added support for Thor-2-PCI boards of Build 3.0 and Build 4.0. Linux driver and SDK released. It is now possible to use OtxDrvConnectPipe() to connect a pipe from a device on one OTX board to a device on a different OTX board (via the H.100 bus). The demo program Thor2Pci\2T2p.cpp shows an example of how to use this feature. What is new in release, 1.0-P74 =============================== The OTX_RAWDATA_SENDER_EC_COMPLETED event (the m_nRequestId member of OtxEventDataS) now contains the last nTaskRef used in OtxRawDataSendData() function. Implemented support for multi-slot pipes in the OtxHdlc SPM. The demo program Thor2Pcmcia\T2mRawData now works for both Thor-2-PCMCIA and Thor-2-PCI/Vidar-5x4-ASM (see the /T command line switch). The /N switch to T2mRawData specifies the capacity of the Raw Data pipe. What is new in release, 1.0-P73 =============================== Earlier versions of driver could incorrectly report a timeout error in an API call to a DSP module. This has now been corrected. What is new in release, 1.0-P72 =============================== Implemented OtxDrvReset() for the T1E1 device. Corrected a firmware bug which could cause the E1T1 device to stop generating interrupts towards the host. Added new SPM module OtxDtTx (OTX_DSP_SPM_OTXDTTX) which supports up to 32 DTMF Senders. Fixed a bug in OtxSpm1 (OTX_DSP_SPM_OTXDTTX) which could cause the driver to time-out in blocking calls to the DSP code. What is new in release, 1.0-P71 =============================== The nTaskRef parameter of the OtxRawDataSendData() function is now returned in the m_nRequestId field of the EventDataS structure for the OTX_RAWDATA_SENDER_EC_BUF_DEPLETED event. The functions OtxHdlcReadData, OtxHdlcReadDataEx, OtxRawDataReadData, and OtxDspReadData can now also return OTX_E_BUFFER_TO_SMALL (in addition to OTX_S_OK and OTX_S_FALSE). Corrected a bug in the Raw Data Receiver which caused the driver to crash when OtxRawDataReadData() was called when the driver buffer contained a certain amount of data in it. What is new in release, 1.0-P70 =============================== Implemented a new API function OtxHdlcReadDataEx() which allows reading of multiple HDLC frames in one call to the driver. Please see ThorDemo and T2p5x4Hdlc demo applications for an example this added functionality. Added a parameter bEventForEveryFrame to the function OtxHdlcReceiverInit(). If this parameter is OTX_TRUE the HDLC device will generate an event for every received frame, if it isOTX_FALSE then the HDLC device will only generate an event when one or more frames have been received since the last call to OtxHdlcReadData() or OtxHdlcReadDataEx(). The internal buffer within the driver for the received HDLC frames has been increased from 8k to 24k. What is new in release, 1.0-P69 =============================== Implemented bit inversion for the HDLC Sender hosted by the DSP. Implemented OtxDspRunSpm() which loads a Standard Program Module (SPM) from an image stored in the library (no file access is needed). Most demo applications have been modified to use this new feature. DtmfDial() will now return OTX_DTMF_DIALER_RES_BUSY if the DTMF Dialer is currently busy dialing digits. What is new in release, 1.0-P68 =============================== Added support for reading the CPLD Build on the board. See T2p5x4Hdlc.c for an example. What is new in release, 1.0-P67 =============================== OtxDrvDisconnectLogicalDevice() now works properly for devices hosted by the DSP device. The driver will no longer force a resynchronization of Frame Alignment (E1T1 Device) after 5 Errored seconds. The application can still force a resynchronization by calling OtxT1E1ForceResynch() for E1T1 device at any time. What is new in release, 1.0-P66 =============================== The HDLC receiver hosted by the E1T1 device could go into an inactive state if it received HDLC frames while it was being initalized. This has now been corrected. The calling sequence for OtxBrdSetClocks() has changed. This function should be called at a very early stage in the application (right after board device has been opened). OtxBrdSetClocks() should be called before calling OtxT1E1SetLiMode(). See Thor2Pcmcia\T2mDemo.c for an example. Added clock source as a command line parameter to Thor2Pcmcia\T2mDemo.c. What is new in release, 1.0-P65 =============================== The driver now properly handles Thor-2-PCI boards of Build 2.0 when the board is running in INTERNAL clocking mode. It is now possible to run multiple (up to 8) Raw Data Senders simultaneously per DSP. Added a generic demo program called EnumOtxDevices which enumerates all installed OTX boards, and the devices (physical and logical) which they host. The OtxDrv.lib is now compiled with Visual C++ 6.0. What is new in release, 1.0-P64 =============================== Added new API function: OtxDrvGetCurrentTime() Enhanced the performance for the HDLC Sender/Receiver and Raw Data Sender/Receiver by eliminating an unnecessary byte-copy step. Added new API functions: OtxDspCreateProgramImage() and OtxDspRunImage(). See T2p5x4.cpp for an example of how to use these functions. These functions makes it possible to link the DSP program into an application without having to perform FILE IO to load the DSP program. What is new in release, 1.0-P63 =============================== The driver no longer crashes if a DSP User Application transfers larger data than 256 bytes. Added support for HPI Event Buffer Diagnostics in DspDemo1. There was a bug which could cause the DSP SDK HPI Event Buffer to become out of sync with the host. This has now been corrected. Added attributes for reading Board Build, and Driver Revision. See ThorDemo.cpp for an example. Added example of how to translate error codes to a more descriptive error message. See DspDemo1.cpp and DspDemo2.cpp for an example. Added support for super-pipes (> 64kbit/s) in the HDLC Sender/Receiver hosted by the E1T1 device. Pipe capacity must be in increments of 64kbit/s. What is new in release, 1.0-P62 =============================== Implemented OtxDrvSignalEvent. Changed OtxDrvEnumDeviceNo to OtxDrvEnumDevice since it's now returning a handle to the device instead of the number. With this handle the user can ask for the number as an attribute instead. Fixed so that event queues can return their user mode handles as attributes (event qeue handles are different from other device handles in user mode). What is new in release, 1.0-P61 =============================== Corrected a bug which caused the driver to fail when more than 3 OTX boards were installed in the same PC. Implemented Raw Data Sender and Raw Data Receiver (for 64kbit/s pipe). See new example program T2mRawData (which is written for the Thor-2-Pcmcia) and T2p5x4Recorder (which is written for the Thor-2-PCI/Vidar-5x4-ASM combination). The driver now works in Windows 2000 Beta 3. Enumerations of device (types and numbers) are now implemented. User mode applications can now set event events. Common results codes can now be translated to strings. What is new in release, 1.0-P60 =============================== Added support for E1 ABCD-bit access (see T2pE1ABCDBit.c demo program). Added support for T1 Bit-rob access (see T2pT1BitRob.c demo program). What is new in release, 1.0-P59 =============================== The firmware for Arni-32-PCI was updated. The demo program A16Vd5x4.cpp should now function properly. What is new in release, 1.0-P58 =============================== The OtxSpm1 module could falsely report OTX_DSP_EC_RX_OVERFLOW (which in turn caused the DSP to become Disabled. This has now been corrected. The HDLC Receiver in OtxSpm1 would incorrectly report a frame length of -1 for short frames (frames of length 1). This has now been corrected. OtxDrvGetState() is now implemented. The E1/T1 device will now report counts of Frame Errors, CRC Errors, Code Violations, and Slips if as part of the Errored Second Interrupt. After 5 Errored Seconds then the E1/T1 device will force a resynchronization to find a better framing candidate. DSP SDK Demo applications (DspDemo1 and DspDemo2) would fail when logical devices were created. This has now been corrected. The new DSP SDK works with the 3.10 version of the TI C-compiler. New DSP module OtxHdlc.out was added. This module contains HDLC Sender and HDLC Receiver Logical devices. It is used by the T2p5x4Hdlc and T2p5x16Hdlc demo programs. In the next release of the driver support for Raw Data Sender and Raw Data Receiver will be added to this module. What is new in release, 1.0-P57 =============================== Increased performance for the HDLC Receiver in the OtxSpm1 module. What is new in release, 1.0-P56 =============================== Increased performance by shortening the IO access time to the boards. What is new in release, 1.0-P55 =============================== Added new demo program T2p5x16Hdlc.c which demonstrates how to use a Vidar-5x16-PCI with a Thor-2-PCI board. Corrected a problem related to an interrupt deadlock situation for the Vidar-5x16-PCI board. Renamed OTX_CLOCK_MODE_SLAVE to OTX_CLOCK_MODE_LOCAL. Renamed OTX_CLOCK_MODE_MASTER to OTX_CLOCK_MODE_H100. OtxE1GetConfiguration and OtxT1GetConfiguration now returns the correct data. What is new in release, 1.0-P54 =============================== New driver firmware for Vidar-5x16-PCI. This new driver firmware corrects a problem of a lost Dsp Handle which could occur if the OtxSpm1 code was exercised with a high load of HDLC frames. The Vidar-5x4-ASM module has the same problem, and it needs a HW Firmware Update to correct the "Lost Handle" (update program will be available in the next release). What is new in release, 1.0-P53 =============================== The demo programs Vd5x16 and A16Vd5x4 failed when the Logical Devices were created. This has been corrected. What is new in release, 1.0-P52 =============================== Corrected a bug in OtxSpm1 which caused the driver to incorrectly read the Event Nofications from the OtxSpm1 module. The DSP SDK was updated as well with the same correction (OtxApi.c). The driver now runs on an SMP machine. What is new in release, 1.0-P51 =============================== Added support for Vidar-5x16-PCI and Arni-32-PCI The OtxSpm1 module can now handle multiple Logical Devices. Previously a bug prevented multiple data sinks (e.g. HDLC Receivers, DTMF detectors) from working properly. This has now been corrected. Added command line switch to run ThorDemo, T2p5x4 and T2mDemo in either E1 or T1 mode. Added command line switch to enable SS7 FISU filtering. Added new application T2p5x4Hdlc which demonstrates how to connect and use multiple HDLC Sender and HDLC Receiver devices hosted by the DSP (in OtxSpm1). Added support for SS7 FISU filtering in the HDLC Receiver hosted by the DSP. The physical device (e.g. the DSP) must be enabled before logical devices can be created. All of the demo applications using DSP-hosted devices have been modified so that the DSPs are enabled prior to creating the logical devices. DSP SDK Demo Programs now work with all OTX PCI boards with C54x DSP resources. DSP SDK is now separated to its own distiribution file. DSP SDK has its own Help files: OtxDspApi.hlp and OtxDspApi.html What is new in release, 1.0-P50 =============================== Added DSP SDK and two sample applications (DspDmo1 and DspDmo2). The sample applications are written for a Thor-2-PCI board equipped with a Vidar-5x4-ASM board. Added a demo application 2T2p which demonstrates how to connect 2 Thor-2-PCI over the H.100 bus. What is new in release, 1.0-P49 =============================== Implemented OtxDrvReadReg16(), OtxDrvWriteReg16(), OtxDrvReadReg8() and OtxDrvWriteReg8(), which can be used to directly read and write to registers within a physical device. Implemented OtxHdlcSS7SetFilter() for HDLC receivers hosted by the OTX_DEVICE_LI_T1E1 device. This enables filtering of FISUs, LSSUs, and/or MSUs. To use this feature define DEMO_SS7_FISU_FILTERING in ThorDemo.c. What is new in release, 1.0-P48 =============================== Pipes connected to the H.100 highways can now be connected by using the Time-Space Switch (TSS) as the host device. The board serial number can now be queried from the board (see Thordemo.c). What is new in release, 1.0-P47 =============================== The NT4 driver does no longer crash when the driver is stopped. Increased performance for the HDLC logical devices. Added additional demo program for Thor-2-PCI (T2p5x4.c). What is new in release, 1.0-P46 =============================== Implemented OtxDrvWaitForSingleEvent(). T2mDemo shows an example of how to use this function for the Thor-2-PCMCIA board. The OTX_LDEVICE_HDLC_RECEIVER logical device will now issue an event OTX_HDLC_RECEIVER_EC_BUFFER_OVERRUN if the host is too slow calling OtxHdlcReadData(). Logical devices hosted by the DSP were not freed correctly in OtxDrvReleaseLib(). This has now been corrected. The E1/T1 Line interfaces were not properly reset when the application started, causing the HDLC Receiver to fail on the second execution of the application. This has now been corrected. What is new in release, 1.0-P45 =============================== Added NT4 driver. What is new in release, 1.0-P44 =============================== The driver for previous release (1.0-P43) did not load properly for the Thor-2-PCI board. This has been corrected in this version. Added implementation for OtxBrdSetClocks(). ThorDemo shows an example of how to use this function for the Thor-2-PCI board. What is new in release, 1.0-P43 =============================== Calls to OtxHdlcSendData() are now buffered in the driver. This allows the application to send back-to-back HDLC frames. What is new in release, 1.0-P39 =============================== On occasion two HDLC frames could be concatenated, or could contain corrupt data. This has been corrected. What is new in release, 1.0-P38 =============================== Some event status codes have changed. Event status codes are now strictly associated with its device (either a physical or logical device). Added OtxT1E1SetLineTermination() as an API function. OtxBrdSetClocks() is now implemented for the Thor-2-PCMCIA board. The driver now supports hot-swapping of the Thor-2-PCMCIA board. Miscellanous internal driver code corrections, which are too numerous to list. Timestamps (provided by the host with a resolution of 1-50 milliseconds (depending on platform and configuration)) are now implemented. In future releases, logical devices implemented in the DSP will provide a more accurate timestamp resolution (125 microseconds). The driver now also supports the Thor-2-PCI board. What is new in release, 1.0-P37 =============================== N/A. What is new in release, 1.0-P36 =============================== For certain serial numbers of the Thor-2PCMCIA the driver will now ignore the CIS Revision. What is new in release, 1.0-P35 =============================== For certain serial numbers of the Thor-2PCMCIA the driver will now ignore the Firmware Build Revision, which should correct a problem when error code is received 0x80000000B when the board is opened. What is new in release, 1.0-P34 =============================== A debug version of the driver is now included What is new in release, 1.0-P33 =============================== This is the first beta release of the driver, and it has the following known limitations: Boards supported by this driver are: Thor-2-PCMCIA, Thor-2-PCI, and Arni-32-PCI. Hot-swap is not supported yet. I.e. the Thor-2-PCMCIA board can not be be removed and then inserted again when the PC is powered on. The application must supply a path for DSP Signal Processing Module to be loaded. This will be changed in future releases. The DSP Signal Processing Module "OtxSpm1" supports the following logical devices: OTX_LDEVICE_TONE_CONST_VAL_GENERATOR OTX_LDEVICE_TONE_EFFECTS_GENERATOR OTX_LDEVICE_TONE_SINEWAVE_GENERATOR OTX_LDEVICE_TONE_DTMF_GENERATOR OTX_LDEVICE_TONE_DTMF_DIALER OTX_LDEVICE_TONE_SILENCE_DETECTOR OTX_LDEVICE_TONE_DTMF_DETECTOR OTX_LDEVICE_DATA_CONVERTER OTX_LDEVICE_HDLC_SENDER OTX_LDEVICE_HDLC_RECEIVER