Changes between Version 16 and Version 17 of ALOE
- Timestamp:
- 07/02/10 21:27:21 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ALOE
v16 v17 1 1 = ALOE Project = 2 2 3 Th is folder contains documentation and downloading instructions for the ALOE framework. To quickly go to download and user guides go to [wiki:ALOEImplementations ALOE Implementations].3 The ALOE project develops an SDR framework with cognitive resource management capabilities. 4 4 5 [wiki:ConceptandMotivation ALOE Concept and Motivation.] The ALOE concept tries to address the main issues related with the Software Radio technology: partial or total reconfiguration; execution in a heterogeneous hardware platform; strong real-time constraints; easy development and integration; portability; …5 [wiki:ConceptandMotivation ALOE Concept and Layers] 6 6 7 [wiki:PhalArchitecture ALOE Framework Architecture]. The ALOE architecture, its organization, based on a modular approach, and the ALOE associated functionalities tries to provide high levels of flexibility at low cost.7 [wiki:PhalArchitecture ALOE Architecture] 8 8 9 [wiki:ResourceManagement Computing Resource Management] . The Computing Resource Management framework constitutes the basis, from the infrastructure point of view, of the cognitive management approaches and mechanisms.9 [wiki:ResourceManagement Computing Resource Management] 10 10 11 11 [[BR]] 12 == Download ALOE Implementations==12 == Download ALOE == 13 13 14 14 ALOE is being written in plain C and VHDL for programmable and non-programmable devices respectively. Although their implementation is completely different, its functionality as middleware remains. The ALOE-C and ALOE-VHDL implements a reduced set of functions and services but its modular architecture allows and easy extension. … … 44 44 [wiki:MoreFPGA More Info] 45 45 46 [[BR]] 46 47 47 == = Developing Waveforms for ALOE ===48 == Developing Waveforms for ALOE == 48 49 49 50 Writing waveforms for ALOE is independent of the platform where it will be executed however, we recommend to perform the debugging and first phases of the development on a Linux platform as it is much more comfortable. Once you are sure that it works and it does what is supposed to, you can just re-build it for the DSP platform (linking with the HW API for DSP) and it should just 'work';