Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with RFDC device tree generator parameter names #287

Open
litghost opened this issue Feb 1, 2024 · 1 comment
Open

Issue with RFDC device tree generator parameter names #287

litghost opened this issue Feb 1, 2024 · 1 comment

Comments

@litghost
Copy link

litghost commented Feb 1, 2024

Configuration

Vivado/PetaLinux/device-tree-xlnx at 2023.2 on Ubuntu 20.04

Expected behavior

Device tree writer correctly outputs NCOFreq parameters into device tree param-list.

Actual behavior

Device tree writer outputs NCOFreq as "0.0" to device tree param-list.

Issue

Between 2022.2 and 2023.2 the device tree writer for the RFDC driver added the NCOFreq parameter (see commit). However that commit reads from a parameter named C_DAC_NCO_FREQ00 (and C_DAC_NCO_FREQ01, etc). However Vivado appears to believe this parameter is named C_DAC_NCO_Freq00 (and C_DAC_NCO_Freq01, etc).

When the device tree generator is run on a design that contains an usp_rf_data_converter block, the device tree writer complains about not finding the relevant configuration:

WARNING: [Common 17-673] Cannot get value of property 'CONFIG.C_DAC_NCO_FREQ00' because this property is not valid in conjunction with other property setting on this object.

When checking the output device tree param-list, the output has all the NCO frequencies at 0.0 instead of the correct value.

As an experiment, I changed rfdc.tcl to use C_DAC_NCO_Freq00 instead of C_DAC_NCO_FREQ00, and this appears to resolve this issue. I suspect rfdc.tcl needs to updated to use the names used in Vivado?

@conallogriofaamd
Copy link
Contributor

Hi,

Thank you for your comment, we will include this fix in the upcoming release.

Thanks & Best Regards,
Conall.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants