|
vxWorks I2C and SCC 10Mbps device drivers for Freescale PowerQUICC 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 PowerQUICC 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++ high-speed serial HDLC message router to socket-based TCP client in vxWorks environment. 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/Windows Services |
|
Services Oriented Architecture (SOA) 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++. |
|
ISDN protocol software stack ported to operating systems such as ThreadX, vxWorks and Nucleus |
|
Similar 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 was ported to commercial operating systems such as ThreadX, vxWorks, Nucleus and Windows. |
|
|
|
|
|
|
Page 2 of 4 |