Changes between Version 3 and Version 4 of crkit/Software/Firmware/Framework/R3_arch

Timestamp:

Jun 15, 2010, 8:13:04 PM (14 years ago)

Author:

khanhle

Comment:

--

crkit/Software/Firmware/Framework/R3_arch

@@ -10 +10 @@
 
 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 data planes. 
-Within each dataplane, we have an option of having a dataplane top level register map, and/or an application specific
-register map. Usually, the top level register map are shared among multiple applications, whereas application 
-specific register maps are only designed for a particular application. 
+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__ 
@@ -19 +18 @@
 [[Image(r3_arch.jpg, 1200px)]]
 [[BR]][[BR]]
+
+R3 architecture consists of following modules : 
+
+'''Ethernet Port''' - Ethernet framing function, 
+'''Packet Processor''' -
+'''App''' -
+'''RF Port''' -
+'''Control Plane''' -
+'''Timing Control''' -
+
 From Host, we can control the hardware (RMAP read/write operations) by sending RMAP ethernet frame messages. The Tx Command Generator forwards RMAP specific frames to RMAP Processor, whereas data specific frames are routed to the Tx Memory Controller. The RMAP frames are then parsed by the RMAP processor, where a register map read/write operation can be initiated.