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.
side by side
lines around each change
Show the changes in full context
White space changes
Jun 18, 2010, 4:22:53 PM (
== R3 Overview ==
With R3, we have included a dedicated control plane with RMAP processor which will handle all register map
related accesses. In future releases, we may replace the RMAP processor with a real 32-bit soft processor such
as Xilinx Microblaze, or equivalent processors.
The register maps associated with the control plane handle all Board related controls e.g. RF SPI, general purpose
IOs, LEDs and so forth. Whereas, data plane centric register maps are maintained within the Tx and Rx Application modules.
Within the APP module, we have an option of having a top level RMAP, and/or an application specific RMAP. Usually, the top
level RMAP is shared among multiple applications, whereas application specific RMAPs are only designed for a particular application.
__Figure 1 - R3 architecture overview__
R3 architecture consists of following modules :
* '''Ethernet Port''' - Ethernet framing function, [[BR]]
* Rx - receives ethernet frames from Host. Performs CRC checking, and forwards error free payload to packet processor.
* Tx - transmits ethernet frames to Host. Generates Ethernet header and CRC, IP payload is provided by packet processor. [[BR]]
* '''Packet Processor''' - IP layer processing[[BR]]
* Packet classification - RMAP, Data, and other (such as ARP and DHCP packets)
* UDP is used for board level communication e.g. RMAP and Data packets
* '''APP''' - User specific application [[BR]]
* '''RF Port''' - DAC/ADC interfacing [[BR]]
* '''Control Plane''' - RMAP and RF control [[BR]]
* '''Timing Control''' - system wide clock control using clock enables [[BR]]
From Host, we can control the hardware (RMAP read/write operations) by sending RMAP ethernet frame messages. The packet classifier classifies and forwards packets according to its
* RMAP packets -> RMAP Processor
* Data packets -> Tx Buffer for APP processing
* Other packets -> TCP/IP stack
For RMAP read operations, read data must be forwarded back to Host. This is accomplished by following operations : [[BR]]
1. RMAP Processor forwards read data to Rx Memory Controller. Note : shared access to Rx buffer with dataflow.[[BR]]
2. Generate IP and Ethernet frame for transmission back to host. Some control header information are added in the payload section for Host RMAP read synchronization.[[BR]][[BR]]
Part of ORBIT