cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Visitor
Visitor
5,403 Views
Registered: ‎02-06-2014

driveDone does not report correctly in bitgen log for Vivado 2014.x and 2015.2

 

Hi,

 

Very minor bug to report here on the text output of bitgen for Vivado 2014.x and 2015.2 for drive done...

 

Step 1. Turn on DriveDone

 

set_property BITSTREAM.CONFIG.DRIVEDONE Yes [current_design]

 

Step 2. Run bitgen

write_bitstream $verbose_flag                -force $bitOut

Design behaves as expected

:)

 

Step 3. Log file does not

:(

+-------------------------+-------------------------+
| DONEPIN                 | PULLUP*                 |
+-------------------------+-------------------------+

-m

 

0 Kudos
5 Replies
Highlighted
Xilinx Employee
Xilinx Employee
5,393 Views
Registered: ‎08-02-2007

Re: driveDone does not report correctly in bitgen log for Vivado 2014.x and 2015.2

hi,

 

it looks DriveDone was removed from bitgen options based off this link.

http://www.xilinx.com/support/answers/44103.html

 

can you confirm if it was seen in the bitgen report earlier?

 

--hs

----------------------------------------------------------------------------------------------
Kindly note- Please mark the Answer as "Accept as solution" if information provided is helpful.

Give Kudos to a post which you think is helpful and reply oriented.
----------------------------------------------------------------------------------------------
0 Kudos
Highlighted
Scholar
Scholar
5,385 Views
Registered: ‎06-05-2013

Re: driveDone does not report correctly in bitgen log for Vivado 2014.x and 2015.2

@maxbaker 

set_property BITSTREAM.CONFIG.DRIVEDONE Yes [current_design]

This property shouldnt be used with 7 series devices. This property is not visiable to customers hence shouldnt be reported in reports tools is doing correct job.

 

report_property [current_design ]
Property Type Read-only Visible Value
BITSTREAM.CONFIG.DRIVEDONE enum false false Yes

-Pratham

----------------------------------------------------------------------------------------------
Kindly note- Please mark the Answer as "Accept as solution" if information provided is helpful.

Give Kudos to a post which you think is helpful and reply oriented.
----------------------------------------------------------------------------------------------
0 Kudos
Visitor
Visitor
5,372 Views
Registered: ‎02-06-2014

Re: driveDone does not report correctly in bitgen log for Vivado 2014.x and 2015.2

Is there any reliability issue that would lead it to not be used?  It saved me from a PCB bug.  It works fine for me.

 

-m

 

0 Kudos
Highlighted
Visitor
Visitor
5,367 Views
Registered: ‎02-06-2014

Re: driveDone does not report correctly in bitgen log for Vivado 2014.x and 2015.2

I also wanted to add that the configuration user guide (UG470) for the 7-series says,

"The DriveDONE option is not supported for stacked silicon interconnect technology devices. External 330Ω resistor circuits work in the 7 series FPGAs as they have on previous generations."

This implies that it IS supported when using non-stacked parts.

-m
0 Kudos
Highlighted
Scholar
Scholar
5,355 Views
Registered: ‎06-05-2013

Re: driveDone does not report correctly in bitgen log for Vivado 2014.x and 2015.2

@maxbaker Like i told that is supported but you need not use it.

 

Same does UG says

-Pratham

----------------------------------------------------------------------------------------------
Kindly note- Please mark the Answer as "Accept as solution" if information provided is helpful.

Give Kudos to a post which you think is helpful and reply oriented.
----------------------------------------------------------------------------------------------
forum.jpg
0 Kudos