UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

cancel
Showing results for 
Search instead for 
Did you mean: 
Observer paulburnsuk
Observer
892 Views
Registered: ‎08-25-2016

ZCU111 RF Data Converter Eval design generates VDMA errors on large DDR captures

Hi,

I have a ZCU111 RFSoC Eval board, running the pre-built 2018.3 release of the "NON-MTSDesign_8x8" images from SD card. Everything seems to running OK when configured in BRAM mode, and when I switch to DDR mode I can increase the capture size to 2097152 samples without issue. But if I attempt larger capture sizes I see DMA errors appearing on the RFSoC console:

 xilinx-vdma b000a000.dma: Channel ffffffc87ad86418 has errors 10, cdr 15964680 tdr 15974400

This is using the default sample rate (3194.4 MHz) and ADC Tile 0 configured with the Mixer disabled (Real-mode). I've tried various decimation rates down to 8x - so the effective output rate is ~400MHz real-only. I'm capturing on only a single ADC channel (Tile 0 ADC01).

According to the documentation the design should support single channel ADC captures of up to 128MB @ 4096 MHz but I don't seem to be getting anywhere near that. See https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/57606309/ZCU111+RFSoC+RF+Data+Converter+Evaluation+Tool+Getting+Started+Guide#ZCU111RFSoCRFDataConverterEvaluationToolGettingStartedGuide-AppendixAPerformanceTable

Shorter captures (up to 2M samples) do seem to be robust and I can capture multiple complex channels and simultaneously output complex DAC waveforms without error. It's only when attempring long captures that I see this problem.

Any suggestions as to what I might be doing wrong?

 

Thanks,

 

Paul

11 Replies
Observer desaic
Observer
821 Views
Registered: ‎01-07-2019

Re: ZCU111 RF Data Converter Eval design generates VDMA errors on large DDR captures

I have encountered exactly the same problem! Do you have a solution? Otherwise let's hope and pray.

0 Kudos
Observer paulburnsuk
Observer
796 Views
Registered: ‎08-25-2016

Re: ZCU111 RF Data Converter Eval design generates VDMA errors on large DDR captures

I have a service request in. WIll update when I get a response.

 

Paul

761 Views
Registered: ‎09-27-2018

Re: ZCU111 RF Data Converter Eval design generates VDMA errors on large DDR captures

I'm also seeing this same issue with larger capture size.  We're suspecting the issue is related to the rftool application code, in data_interface.c,  ReadDataFromMemory_ddr.   From the 18.3 verison of this file . . . 

/* Trigger DMA */
ret = read((info.fd_adc[adc]), &adc_chaninfo,
(((adc_chaninfo.channel_size[0])) * sizeof(signed char)));

The &adc_chaninfo doesn't make sense to us.  Below is the same code from version 18.2.  There are many changes in data_interface.c between 18.2 and 18.3 so it's not suprising that this line is different, but we're wondering if the updates were made correctly to this line.

/* Trigger DMA */
ret = read((info.fd_adc[adc]), info.map_adc[adc],
((size + (512 * 1024)) * sizeof(signed char)));

Observer paulburnsuk
Observer
709 Views
Registered: ‎08-25-2016

Re: ZCU111 RF Data Converter Eval design generates VDMA errors on large DDR captures

Xilinx support have been able to re-create the problem and its been passed to the dev team to investigate...
Observer desaic
Observer
637 Views
Registered: ‎01-07-2019

Re: ZCU111 RF Data Converter Eval design generates VDMA errors on large DDR captures

Is there any update from Xilinx dev team?

Thanks!

0 Kudos
Highlighted
Observer paulburnsuk
Observer
620 Views
Registered: ‎08-25-2016

Re: ZCU111 RF Data Converter Eval design generates VDMA errors on large DDR captures

I got this update through while I was away last week:

"With higher sizes of DMA transfer, Recently the FIFO sizes of DAC and ADC data path are changed to 16k and 32k respectively. Sample size of 4194304 corresponds to 8388608 bytes. As FIFO size of ADC is 32k, to transfer 8388608 from ADC to memory we need ((8388608 ) / (32 *1024) = 256) ~256 descriptors.

As per AXDI DMA specifications maximum supported COALESCE count is 255 COALESCE , in this case we are getting a DMA done interrupt before all packets are transferred(as max number of descriptors(256) > max coalesce count(255)). As soon as interrupt is received driver is clearing all the descriptors(it is clearing both completed and pending descriptors --- which is the reason for issue), due to which descriptor buffer length is configured wrongly and henceyou are seeing error message.

So we are still working on a fix but by way of an update we have at least understood what is going on."

 

 

Observer desaic
Observer
607 Views
Registered: ‎01-07-2019

Re: ZCU111 RF Data Converter Eval design generates VDMA errors on large DDR captures

Thanks! That was quite involved.

0 Kudos
Observer desaic
Observer
364 Views
Registered: ‎01-07-2019

Re: ZCU111 RF Data Converter Eval design generates VDMA errors on large DDR captures

Hi Paul, 

Is there any new update from Xilinx dev team? Would you mind sharing the contact information of their dev team ?

 

Thanks!

0 Kudos
Observer paulburnsuk
Observer
348 Views
Registered: ‎08-25-2016

Re: ZCU111 RF Data Converter Eval design generates VDMA errors on large DDR captures

Last message I had through Xilinx support said the driver code had been modified and would be in the 2019.1 release. I suggest you open a service request if you think you need access to it sooner than that. I'm OK to wait now that I know the issue isn't memory bandwidth related.

 

Paul

Observer desaic
Observer
342 Views
Registered: ‎01-07-2019

Re: ZCU111 RF Data Converter Eval design generates VDMA errors on large DDR captures

Thanks for the heads up!

0 Kudos
Moderator
Moderator
320 Views
Registered: ‎08-08-2017

Re: ZCU111 RF Data Converter Eval design generates VDMA errors on large DDR captures

Hi @desaic 


Yes i have checked internally and this issue is resolved in 2019.1

-------------------------------------------------------------------------------------------------------------------------------
Reply if you have any queries, give kudos and accept as solution
-------------------------------------------------------------------------------------------------------------------------------