Before examining the different key design areas relating to the PowerPC kernel implementation it’s worth taking a look at the overall system. The purpose of the kernel is to support a GSM radio platform capable of supporting two carriers of GSM, GPRS or EDGE. At the heart of the digital part of the radio is a PowerPC based communications processor (PowerQUICC 2). The other main digital components on the radio are illustrated in the diagram below and include digital signal processors (DSP), an ASIC, PCI bridge and memory.

The PowerPC based processor on the board is responsible for radio application software associated with initialization and control of the radio transceiver. This includes responsibility for configuring, monitoring and communicating with the DSP block. A number of software processes run on the processor to take care of the radio subsystem (needed for channel configuration, handover, power control etc.) a data link service provider for controlling a HDLC link off board and other maintenance applications for TTY debug and alarm monitoring.
The real time response of the platform comes from the timing demands of GSM. The PowerPC based kernel must provide real time response to multiple interrupt sources, including DSP interrupts at a frequency of 577 microseconds, GSM frame interrupts, sourced from the ASIC every 4.615 milliseconds, GSM Superframe interrupts every 6.12 seconds, HDLC interrupts and TTY interrupts.
With the above processing and interrupt handling requirements it’s clear that a real time operating system is needed. So why persist in porting or developing an in-house solution instead of going with an off the shelf option such as Linux or VxWorks? That’s a question I hope to tackle in the next article. Stay tuned….
PowerPC Kernel Implementation for GSM Radio Platform - Previous Posts
Recent Comments