close Warning: Can't synchronize with repository "(default)" (/common/SVN/crkit does not appear to be a Subversion repository.). Look in the Trac log for more information.

Changes between Initial Version and Version 1 of crkit/Software/Firmware/Framework


Ignore:
Timestamp:
Jun 15, 2010, 7:06:21 PM (12 years ago)
Author:
khanhle
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • crkit/Software/Firmware/Framework

    v1 v1  
     1== CR Kit Framework ==
     2
     3[[TOC]]
     4
     5=== Introduction ===
     6The CR Kitframework is a VHDL-based set of building blocks interconnected into a complete radio system, which makes the process of building a custom radio application quick and easy. The framework is Ethernet command based: it takes in data and control commands. Data commands are used to send user application data, whereas control commands are used to set certain parameters of the user application, e.g. changing the operating mode or configuring the ADCs, DACs and the RF cards.
     7
     8[[Image(ocrp_arch.jpg, 800px)]]
     9
     10As seen in the Figure, the framework consist of three types of building blocks apart from the application:[[BR]]
     11a) basic blocks that are part of the OCRP firmware library and are essential for running any application on this platform - Ethernet interfaces, SPI, DAC and ADC interfaces,[[BR]]
     12b) framework specific blocks that are connecting other blocks and facilitating command based structure - System controller, Command generator, Memory controller, and [[BR]]
     13c) Xilinx blocks that are providing standard DSP and hardware functions - FIFOs and buffers. The most important blocks of the framework are:
     14 * System controller – it is used to route commands among various blocks in the framework.
     15 * Command generator – processes the Ethernet packets and generates commands that can be understood by the system controller
     16 * Memory Controllers – these blocks manage space in the Tx and Rx buffers and give out necessary information like the buffer being full or empty, or the next address location to write data, etc.
     17The framework thus reduces user effort by assembling all the essential parts of the system and allowing user to concentrate on the application. Any application must conform to the interface given by OCRP.
     18
     19[[Image(app_arch.jpg, 500px)]]
     20
     21OCRP provides a control block and a register map to support the application. The Application RMAP is optional. The user may opt out this option and only use the User Specific RMAP instead. The user may or may not use these blocks, i.e., the user application may contain its own control logic and its own register map (optional).User specific logic/functions are contained in the User Application module.
     22
     23=== Architectures ===
     24Up to this point, we have described the framework in general terms. We will henceforth proceed with more detailed technical descriptions of the framework architectures and specifications. The framework architecture had been through many iterative evolutions as described below. 
     25
     26 * [wiki:Internal/SDR/Firmware/Framework/R1_arch R1] - Initial release
     27 * [wiki:Internal/SDR/Firmware/Framework/R2_arch R2] - includes Receiver datapath, and spectrum sensing capability   
     28 * [wiki:Internal/SDR/Firmware/Framework/R3a_arch R3] - First complete radio system, including support of WDR
     29 * [wiki:Internal/SDR/Firmware/Framework/R3_arch (R3)] - Old R3 architecture
     30 
     31
     32[wiki:Internal/SDR Return \]