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: 
Highlighted
Observer matzik
Observer
1,197 Views
Registered: ‎10-18-2017

createhw warning in 2017.3 that was not present in 2017.2

Jump to solution

I have an hdf that is created with 2017.3.

 

The exact same xsct command sequence, taken nearly verbatim from the ref manual, produces an unpleasant warning in 2017.3. What should I do to avoid that? Or is it just noise?

 

See the following sequence:

 

bash$ source /opt/Xilinx/SDK/2017.2/settings64.sh

bash$ xsct

 

 

****** Xilinx Software Commandline Tool (XSCT) v2017.2
**** Build date : Jun 15 2017-18:45:22
** Copyright 1986-2017 Xilinx, Inc. All Rights Reserved.


xsct% setws .
xsct% createhw -name hw1 -hwspec hw1.hdf
Starting xsdk. This could take few seconds... done
xsct%

 

 

Compare that to the following sequence after removing all products from the previous sequence:

 

bash$ source /opt/Xilinx/SDK/2017.3/settings64.sh
bash$ xsct

****** Xilinx Software Commandline Tool (XSCT) v2017.3
**** Build date : Oct 4 2017-20:06:47
** Copyright 1986-2017 Xilinx, Inc. All Rights Reserved.


xsct% setws .
xsct% createhw -name hw1 -hwspec hw1.hdf
Starting xsdk. This could take few seconds... done
WARNING: [Hsi 55-1434] Error /opt/Xilinx/SDK/2017.3/data/embeddedsw/XilinxProcessorIPLib/drivers/rfdc_v2_1/data/rfdc.mdd:49 Unrecognized Option name. List of possible Option names are : DRC, DESC, COPYFILES, DEPENDS, SUPPORTED_PERIPHERALS, DRIVER_STATE, DEFAULT_OS, NAME, VERSION

INFO: [Hsi 55-1698] elapsed time for repository loading 0 seconds
hsi::open_hw_design: Time (s): cpu = 00:00:05 ; elapsed = 00:00:05 . Memory (MB): peak = 484.516 ; gain = 132.508 ; free physical = 10595 ; free virtual = 29389
xsct%

 

 

Tags (2)
0 Kudos
1 Solution

Accepted Solutions
Moderator
Moderator
1,751 Views
Registered: ‎09-12-2007

Re: createhw warning in 2017.3 that was not present in 2017.2

Jump to solution

This can be safely ignored. this is a new RFSoC driver added to 2017.3. There is a known issue in the MDD file

0 Kudos
2 Replies
Moderator
Moderator
1,752 Views
Registered: ‎09-12-2007

Re: createhw warning in 2017.3 that was not present in 2017.2

Jump to solution

This can be safely ignored. this is a new RFSoC driver added to 2017.3. There is a known issue in the MDD file

0 Kudos
Observer matzik
Observer
1,058 Views
Registered: ‎10-18-2017

Re: createhw warning in 2017.3 that was not present in 2017.2

Jump to solution

Thanks!

I still think it is strange that I get warnings from the tools while using them correctly - I can however live with that.

0 Kudos