Spectra OE Webcast July 2010
•Transferir como PPT, PDF•
1 gostou•626 visualizações
The document discusses Spectra Operating Environment (OE), an SCA compliant radio development environment. It provides an overview of SCA OE requirements including supporting an Application Environment Profile, CORBA middleware, and SCA Core Framework. It outlines the benefits of using a commercial off-the-shelf (COTS) OE like Spectra OE over custom development. Spectra OE is highlighted as a standards-based, high performance, portable COTS solution for SCA application deployment across processor types.
![Agenda ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Semelhante a Spectra OE Webcast July 2010
Semelhante a Spectra OE Webcast July 2010 (20)
Mais de ADLINK Technology IoT
Mais de ADLINK Technology IoT (20)
Último
Último (20)
Spectra OE Webcast July 2010
- 1. Spectra Operating Environment (OE) – Setting a New Standard For High Performance SCA Compliant Radio Development July 2010 – Andrew Foster, Spectra OE Product Manager
- 3. The SCA Operating Environment
- 8. The Business Case for COTS OE
- 11. Spectra OE
- 16. Bringing Architectural Consistency to SCA SDR The first standards based, high performance, low footprint, fully interoperable COTS SCA middleware solution that can be deployed across multiple processor types, including GPP, DSP and FPGA environments DSP GPP e*ORB C & C++ FPGA e*ORB C ICO SCA (GIOP) Everywhere Extensible Transport Framework Waveform Component Waveform Component Waveform Component GPP DSP FPGA
- 32. Spectra SDR/SCA Tools and Middleware Spectra OE: e*ORB Spectra OE: Core Framework SCA Infrastructure SCA Infrastructure Radio Application (waveform) Radio Application (waveform) Host Development Tools Target Radio Platform RTOS GPP/DSP BSP ASP Spectra OE: ICO FPGA End-to-End: Model, Generate, Validate, Deploy Generate Spectra CX: Model-Based Development Tool Eclipse Workbench UML 2 Windows / Linux / Unix
Notas do Editor
- The DomainManager component provides control, configuration and a system-wide view of the SDR domain. The DM implements the Application and Application Factory Interfaces The DeviceManager component is used to manage Device and Service components. It controls the lifecycle of the Device and Service components described in the Device Configuration Descriptor (DCD) file. The FileSystemService is an implementation of a CORBA file system that is compliant with the Core Framework (CF) specification. Particularly, the FileSytemService implements the CF::FileSystem interface. The FileSystemService can be started as a stand-alone service, like a Naming Service, or be launched by a DeviceManager component. A Naming Service’s NameComponent structure is made up of an id-and-kind pair. The “id” element of each NameComponent is a string value that uniquely identifies a NameComponent. The “kind” element of each NameComponent shall be “” (null string). The OE shall provide an implementation of the CORBA Event Service. The Event Service shall implement the PushConsumer and PushSupplier interfaces of the CosEventComm module as described in OMG Event Service Specification [8] using the IDL found in that specification. The CosEventComm CORBA Module is used by consumers for receiving events and by producers for generating events. A component (e.g., Resource, DomainManager, etc.) that consumes events shall implement the CosEventComm PushConsumer interface. A component (e.g., Resource, Device, DomainManager, etc.) that produces events shall implement the CosEventComm PushSupplier interface and use the CosEventComm PushConsumer interface for generating the events. The CORBA Event Service has the capability to create event channels. An event channel allows multiple suppliers to communicate with multiple consumers asynchronously. An event channel is both a consumer and a producer of events. For example, event channels may be standard CORBA objects and communicate with those channels is accomplished using standard CORBA requests. The OE shall provide two standard event channels: Incoming Domain Management and Outgoing Domain Management. The An SCA compliant implementation may include a log service. If a log service is implemented, the log service shall conform to the OMG Lightweight Log Service Specification A log producer is a CF component (e.g., DomainManager, Application, ApplicationFactory, DeviceManager, Device) or an application’s CORBA capable component (e.g., Resource, ResourceFactory) that produces log records using the Lightweight Log Service CosLwLog::LogProducer interface. Log records are of type CosLwLog::ProducerLogRecord. Example Executable that can be used for starting the components provide in the product tutorials Boot loader - used to activate the correct DomainManager or DeviceManager implementation that is described by the domain profile The oeadmin utility provides the capability to easily install, create, start, stop, release and uninstall applications. Oeadmin also has an option to view DomainManager-registered components
- Safe and Secure Multicore Study Proposal © 2009 Wind River Systems, Inc. – Proprietary and Confidential