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: 
Participant vapostolov
Participant
768 Views
Registered: ‎08-06-2013

Done pin released 920 bytes (7360 bits) before the last configuration byte (bit)

I have 7A200T device with 77,845,216 bits (9730652 bytes) configuration file size.

I am using Slave SelectMAP (8-bit bus width) configuration interface and an encrypted binary configuration image (size  9,730,652) generated by Vivado 2015.4.

 

For some reason I see the Done pin released after the 9,729,732 configuration byte instead of after the last 9,730,652 byte (920 configuration bytes earlier).

 

This is causing an issue for my design and I am wondering what could be the explanation for this.

0 Kudos
2 Replies
Xilinx Employee
Xilinx Employee
748 Views
Registered: ‎10-24-2013

Re: Done pin released 920 bytes (7360 bits) before the last configuration byte (bit)

Hi @vapostolov

What is the issue that you are seeing with your design?

Try the following command, regenerate the bitstream and let me know if this helps.

set_property BITSTREAM.STARTUP.DONE_CYCLE 6 [current_design]


Also, try using the latest version of Vivado for better results.

Thanks,Vijay
--------------------------------------------------------------------------------------------
Please mark the post as an answer "Accept as solution" in case it helped resolve your query.
Give kudos in case a post in case it guided to the solution.
0 Kudos
Participant vapostolov
Participant
742 Views
Registered: ‎08-06-2013

Re: Done pin released 920 bytes (7360 bits) before the last configuration byte (bit)

Hi Vijay,

Thank you for trying to help.

 

The issue was that by default the IO outputs were enabled before (startup phase 5) the logic flip-flops (startup phase 6).

This was causing  a CPU deadlock because of holding a wait state signal low (after phase 5) and not releasing it due to the late logic startup (phase 6).

 

Swapping the IO outputs and logic startup sequence phases fixed my issue.

 

I am still curious to know why the startup phase and Done goes high so early before the end of the configuration file.

 

Regards,

Vlad

0 Kudos