AR# 52887: 2012.2 Vivado IP Flows - Invalid parameter reported on IP core parameters with hexidecimal values after importing XCO file into Vivado
2012.2 Vivado IP Flows - Invalid parameter reported on IP core parameters with hexidecimal values after importing XCO file into Vivado
In CORE Generator XCO files, hexadecimal numbers are stored without the 0x prefix.
In Vivado XGUI, the hexadecimal values are prefixed with 0x.
When I import an IP core (XCO file) with CORE Generator type Hex values into Vivado and then upgrade and launch the customization GUI, I receive an error message indicating that the parameters are invalid (missing the 0x prefix.)
Example: The AXI4-Stream Interconnect v1_1 has two HEX numbers in the IP core parameters.
Import the XCO file from the CORE Generator project directory.
Right-click XCO and select Upgrade
Choose a native version of the selected IP (e.g. AXI4-Stream Interconnect v1_1 (Native)).
Observe that error messages about BASE/HIGH TDEST are produced due to hexadecimal conversion.
What is the best way to reconcile these differences?
After the upgrade, the .xci file can be opened in a text editor and the hexadecimal values can be prepended with 0x.
This issue is fixed in Vivado Design Suite 2012.3.
In Vivado Design Suite 2012.3, the conversion from non-native to native IP instance now checks all parameter values to see if they are being supplied for use in a bitString representation.
- If the converted value contains only '1' and '0' and has the same length as the number of bits in the target bitString, it is assumed to be binary value and is placed inside double quotes as per the IP-XACT standard. - If the value contains only 0-9 and A-F, then a '0x' prefix is applied if not present.