You are not logged in.
We're using OFDM_ReferenceDesign_v04
After we've run: sysgen2opb('ofdm_txrx_mimo') and WARP OPB Export tool, the following extra ports are generated:
PORT smwoaddr_pktbufferber = "", DIR = I, VEC = [0:9]
PORT smwoaddr_rxmodulation = "", DIR = I, VEC = [0:4]
PORT smwoaddr_txmodulation = "", DIR = I, VEC = [0:4]
PORT smwodatai_pktbufferber = "", DIR = I, VEC = [0:31]
PORT smwodatai_rxmodulation = "", DIR = I, VEC = [0:31]
PORT smwodatai_txmodulation = "", DIR = I, VEC = [0:31]
PORT smwowe_pktbufferber = "", DIR = I
PORT smwowe_rxmodulation = "", DIR = I
PORT smwowe_txmodulation = "", DIR = I
These ports are not available on your v04 reference design ofdm_txrx_mimo peripheral.
1) Why did they appear?
2) How did you generate the ofdm_txrx_mimo peripheral on v04 reference design?
3) Is it safe to connect the inputs to ground? Are those buffers required in the normal setup, or are used only for debug?
4) How did you intend to use these interfaces?
Offline
You have to use sysgen2opb's shared memory extension when converting the OFDM model. Call sysgen2opb('ofdm_txrx_mimo', 'smon') (more details here).
The gateways you're seeing are hooks for sysgen2opb to recognize the shared memory blocks in the PHY. These blocks are used for configuring the Tx/Rx modulation schemes and storing a packet payload for BER comparison. When you use the 'smon' option, sysgen2opb replaces these gateways with logic which maps the corresponding dual-port RAM into the OPB address space.
Offline
I've called sysgen2opb('ofdm_txrx_mimo', 'smon') as you've adviced and the SM is mapped in the OPB address space.
Thanks.
Offline