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: 
Adventurer
Adventurer
302 Views
Registered: ‎08-16-2017

hls 2018.2: Why does the standalone driver append _V to axilite variables?

Hi folks,

I have synthesized an IP core through HLS 2018.2. Perhaps things have changed in this version, but I noticed that all the APIs generated for the standalone driver seem to append (_V) to the name of each variable. I do not recall this was the case in previous versions and having rechecked UG902 (v2018.2) July 2, 2018 Table 1-10: C Driver API Functions, the API should have the form :

- XDUT_Set_ARG

vs what I am getting:

- XDUT_Set_ARG_V

This doesn't seem to affect the functionality of the IP core.

 

Any idea why _V is appended to variable names?

0 Kudos
1 Reply
Visitor tsaga
Visitor
93 Views
Registered: ‎06-25-2018

Re: hls 2018.2: Why does the standalone driver append _V to axilite variables?

+1 to this question.

 

I noticed that my ap_uint ports get the _V but my bool does not.

what gives?

0 Kudos