This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TCI6630K2L: DFE Configuration for non-LTE application in RFSDK

Part Number: TCI6630K2L

Hello,

So I have been able to get the RFSDK up and running with LTE packets moving my data in and out throught the DFE. My next challenge now is getting our own custom packet sizing to work instead of LTE packets. I have noticed there are 4k configurations included with the RFSDK but I previously had my design working with the LTE60 Demo1 configuration which uses the lower speed JESD lan (4.9 GHz) it appears like the 4k configurations for the dfe only say they support the higher speed lane rate. Would I be able to use the same tgtcfg file from the LTE60 configuration with the 4k Demo1 config in order to get the lower lane rate as that rate is required by our design? Does the DFE tgtcfg file have anything to do with what size of data packets are being transmitted?

Thanks so much,

Ken Witham

  • Hello,
    The IQN is responsible for the packet size. The basis for this is the 5 or 10ms frame. There are frame timers in the IQN used for
    Triggering DMA, DSP activities. The number of IQ samples within a packet needs to be modulo 4 for the DFE Baseband IQ rate.
    The DFE baseband bus is 128 bits wide.

    The Serdes rate and number of JESD204 lanes is related to the DFE number of streams and IQ rate.
    The Baseband rate and number of antenna carriers or channels is the connection between the IQN and DFE.

    The different number of channels or streams, or different IQ rates for channels or streams means that you need a different TGTCFG configuration.

    There are no examples of custom frame periods in the RFSDK, the pktDMA needs to have enough resources for the number of channels at the IQ rates, to push the data from IQN to DSP, or DSP to IQN.

    Regards,
    Joe Quintal
  • Hello,

    Thanks for the response. So I am using the same baseband rate and frame size as of right now. I am using the build of Playback with the 4k custom symbol size as a base. I can get that code running perfectly and continuously but as soon as I increase the custom symbol size in the iqn2config to my custom size (4608 which is divisible by the BB rate of 92.16 MHz) and increase the PKTDMA packets to match size the IQN2 stops returning the packets to the free queue once transmitted. the program will fill the packets with data and submit them to the IQN2. IQN2 will pass that data to DFE perfectly. The IQN2 does not recycle the pacekts back to the free queue until the next frame. 

    Example: If I have 4 packets in the free queue at the begining of a frame, I can pop, fill, and push to the IQN2 at a 1 symbol rate until I have popped 4 packets off the free queue. The packets data does get transmitted but does not get returned to the free queue until the next frame strobe. Only 4 packets get transmitted then the IQN2 is sitting at transmitting 0 for the rest of the frame.

    Thanks

    Ken Witham

  • Hello,
    I have forwarded your request to an application engineer that knows about IQN.
    Regards,
    Joe Quintal
  • Hello,

    The IQN engineer has sent me this information.

    I think though it is likely the problem is an issue either with descriptor initialization or one of the pktDMAs is not configured correctly.

    Note: custom IQN packet sizes are not supported through TI support engineering.  There are 2 third party provides

    Azcom Ltd - Italy, Comm Agility Ltd. - England that provide further IQN customization.

    The 122.88Msps Complex Design 2, 1 carrier with DFE bypass is the fastest sample rate.  The packet size, should not limit your application other than latency.

    DFE doesn't know about PktDMA, it outputs the 4 Baseband IQ (or inputs 4 Baseband IQ) at the DFEclock / (BB IQ sample rate / 4).  The strobe 0, and this timer

    are used to transfer the data to DFE to/from IQN.

    Sorry for not having a direct answer,

    Regards

    Joe Quintal

  • Ok, I was able to figure it out!

    For those who come after: 

    Using PLAYBACK program included in RFSDK source code. Modified IQN2 config to include my custom packet size. Changed AT2 events to trigger packet transfer at the correct rate. Modified EDMA3 to transfer my packet size and at my rate. Changed interrupt function to work with my rate. Was able to build and get consistent TX and RX of my signals.

    Thanks,

    Ken