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: 
Scholar richardhead
Scholar
234 Views
Registered: ‎08-01-2012

Is there a standard format for bitfile header?

Is there any standard for the bitfile header? We see that the top level name is written to the header in cleartext, along with a few other fields and things like vivado version, part number etc. Is there a standard for this? can we specify what the top level name written to the bitfile is?

0 Kudos
2 Replies
Xilinx Employee
Xilinx Employee
165 Views
Registered: ‎05-22-2018

Re: Is there a standard format for bitfile header?

Hi @richardhead ,

Which device family are you targeting?

For example for Ultrascale device configuration data file format check page no.139:

https://www.xilinx.com/support/documentation/user_guides/ug570-ultrascale-configuration.pdf

Thanks,

Raj

0 Kudos
Moderator
Moderator
82 Views
Registered: ‎06-05-2013

Re: Is there a standard format for bitfile header?

@richardhead

You can generate the .rbt file to see the bitstream header. There are so many factors to it. Like Vivado tool version, date, design top name etc.
There is no specific size to it. Although configuration engine completely ignores that part.

It takes the design top module name as the bitstream name. I have attached the sample header information from rbt file. So you can change the name of top level and generate a new bit file with appropriate name. 

rbt.JPG

If that is not possible you can use USER_ID as the identifier which is also in the header part. Used to identify implementation revisions. You can enter up to an 8-digit hexadecimal string in the User ID register

user_id.JPG

 

If that does not work, you can define USR_ACCESS register in bitstream settings and use it as identifier. This can be read via JTAG. Refer to the following XAPP https://www.xilinx.com/support/documentation/application_notes/xapp1232-bitstream-id-with-usr_access.pdf

Hope it helps. 

Thanks

Harshit 

 
-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------
header.png