e2a technology logo  
 

e2a technology Experience

The following is a list of some of the projects and systems we've built, or assisted in building, along with details on technologies used. If technologies that you require are not listed, please contact us. It's likely that we've worked on a relevant project that may not be listed below.

    vxWorks and Linux VME device driver for Freescale Power PC MPC8270 microprocessor and Tundra Tsi148 VME bridge with application software

    This work required building the VME device driver into the vxWorks BSP and building a loadable Linux module (device driver). vxWorks 5.5 was used with the Tornado 2.1 development environment and the WindRiver supplied GNU toolchain. Linux 2.6 was used for the Linux driver development. This was a hard realtime application with messages transferred across the VME bus between two MPC8270 based adapters; one running vxWorks and the second Linux.

    vxWorks I2C and SCC 10Mbps device drivers for Freescale Power PC MPC8270 microprocessor, along with TCP/IP sockets-based message routing application software

    This work required some amount of BSP work that targeted vxWorks to a larger memory-based (128MB) MPC8270, along with driver work to control I2C devices (I2C bus switch, temperature, A/D converter, discrete I/O), with SCC driver work that provided TCP/IP sockets to a server that stored messages transmitted at 10Mbps. vxWorks 5.5 was used with the Tornado 2.1 development environment and the WindRiver supplied GNU toolchain. This was a hard realtime application with messages received at 10Mbps across all four SCCs (an aggregate of 40Mbps), and relayed to a server across TCP/IP sockets. Ilogix' Rhapsody Object Model Development tool was used for UML creation, and also the Rhapsody embedded software framework was used.

    Linux 2.4 Montevista 4-port Fibre Channel device driver and configuration application

    Each fibre channel runs at a rate of 1Gbps (that is one gigabit per second). A true challenge to support four interfaces with received messages stored on high-bandwidth SCSI disk drives. The realtime extensions to Linux provided by Montevista went a long way in helping achieve line rates, with Linux application software and fibre channel ASIC device drivers running on a 400Mhz Power PC MPC8260. All software was written in C with the Montevista provided GNU tool chain. BDI JTAG emulators were used for debugging.

    Message routing object oriented software designed in C++ routing high-speed serial HDLC messages to socket-based TCP client operating in a vxWorks environment. vxWorks BSP configuration done for network performance. Test harnesses done in C++, Perl and Python.

    Another hard realtime application with four SCC channels operating at 10Mbps, and messages slightly reformatted then relayed to a storage server. vxWorks TCP/IP stack was tuned for optimal performance, along with some device driver work for the SCC interfaces. The system was tested with C++, Perl and Python test scripts, depending on the test point. vxWorks 5.5 and Tornado were used.

    Client/Server software object oriented design in C#/C++ using .NET and XML technologies. Included .NET web service & remote object interface to C# message router that routes messages to/from C++ unmanaged specialized device drivers operating as Windows Services. UML w/design patterns; Rhapsody+Together 4.NET tools, SQL Server; developed in SEI CMMI Level 3 environment.

    Services Oriented Architecture that leveraged Microsoft's .NET environment with a collection of web services that provided device control. Two servers existed in the system: one housed the web services and a SQL database running under Windows Server 2003, and the second housed .NET device configuration GUIs and applications that controlled several dozen different types of radio and switching devices. The web services communicated with the device control applications using .NET remote objects. The web services and device configuration GUIs were developed in C#, and the device control applications in C++.

    Research project studying streaming XML Client-Server transmission in Java and the affects of compression and alternate XML encodings on realtime response and performance.

    Research supported an ARMY Small Business Administration proposal to provide a mechanism for reducing the amount of network bandwidth XML messages take on military networks.

    Portable SS#7 MTP1/2/3 protocol software architecture/development supporting a variety of processor architectures.

    Packaged telecommunications protocol software was the primary product of the predecessor of e2a technology, Link Technology. The SS#7 protocol software was developed in portable C, and was packaged in order to be re-targeted to different processor architectures and realtime operating systems. Protocol software is no longer a product of e2a technology.

    ISDN protocol software stack supporting operating systems such as Windows and various embedded operating systems (e.g. Nucleus, vxWorks, ThreadX).

    Simular to the SS#7 protocol software, ISDN protocol software was developed in portable C, and was packaged in order to be re-targeted to different processor architectures and realtime operating systems. A custom RTOS was also provided that could be ported to commercial operating systems such as Nucleus, vxWorks, ThreadX and Windows.

    Software architecture/development for an ISDN BRI/PRI/Switched Digital embedded PC adapter to support H.320 multimedia video teleconferencing desktop applications.

    We ported our ISDN protocol software to an Intel 80188 microprocessor based PC adapter that provided digital network connectivity for a videoconferencing hardward platform. The software supported Windows, and operated under our own custom RTOS on the 80188.

    Software architecture/development for LAPB, LAPD and SS#7 protocol support for a high-performance RISC processor

    We assisted a major semiconductor manufacturer by providing software support for a proprietary RISC processor for these link layer protocols: LAPB, LAPD and SS#7 MTP Level 2. All software was developed in C.

    Software architecture/development for an IBM PC/XT/AT ISDN BRI embedded PC Terminal Adapter, including LAPD/Q.931 software along with Windows device drivers

    Our predecessor, Link Technology, offered an ISDN Basic Rate PC adapter that supported data transfer and voice call processing on Windows personal computers. The ISDN software ran completely under Windows as the PC adapter was a shallow adapter; i.e. it had no on-board processor.

    Software architecture/development of a realtime embedded water sample collection system used for pollution monitoring

    In order to provide EPA compliance, a major chemical company contracted an engineering firm to build a water collection system that had programmable collection sizes and time frequencies. The hardware was based on an Intel 8032 microcontroller, and the software was written in C, and contained a custom cyclic scheduler.

    Software architecture/development for an Oracle-based database server under Open VMS on a VAX-Alpha cluster-based Message Switch with User Interface design

    This work was done to support a major telecommunications company's mail and fax message switch. The software was developed in C, along with SQL stored procedures that interfaced with an Oracle database engine.


© 2008 e2a technology, Inc. U.S.A. All rights reserved.
All logos and trademarks in this site are the property of their respective owners.

Home About Services Experience FAQ Contact