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: 
Explorer
Explorer
777 Views
Registered: ‎11-01-2015

How to determine the size of bitstream

Jump to solution

Hi,

 

When I use the IP of partial reconfiguration controller, there is an option about the size of bitstream. My question is how to decide the value of it?

03.JPG

 

Thanks,

 

0 Kudos
1 Solution

Accepted Solutions
Xilinx Employee
Xilinx Employee
717 Views
Registered: ‎11-17-2008

Re: How to determine the size of bitstream

Jump to solution

Let me add a few more comments to @kvasantr's statement:

 

The size of a partial bitstream will depend on a few factors, most notably the size and shape of the pblock(s) used to define the Reconfigurable Partition (RP) area.  Other factors include bitstream options such as compression and per-frame CRC checking.  If the floorplan and bitstream options remain the same, the bitstream size will remain the same, with one exception:  compression depends on the implementation result, so each partial bitstream for a given RP will vary.  If you are not using compression, determine the bitstream size from an initial result and then update the IP customization for all subsequent runs with that floorplan.

 

If you are using compression, or you are simply looking for different options, there are two ways to add/change this value post-route.  The first is through a Tcl API call, e.g.

prc_v1_2::netlist::set_rm_bs_size dscr vs_shift rm_shift_right 375300

This is documented in the Customizing the Core Post Implementation section of PG193, and is shown in labs 5 and 6 of the PR Tutorial document, UG947.

 

The other option, also documented in PG193 and shown in UG947, is to update the partial bitstream details while the design is running, via AXI-Lite.  Slots and triggers must be predefined to use this approach, but fine-tuning of bitstream size and address can be done as in-system updates.

 

thanks,

david.

2 Replies
Moderator
Moderator
746 Views
Registered: ‎04-12-2017

Re: How to determine the size of bitstream

Jump to solution

Hello @araongao2015,

 

It is basically the size of the bit-stream you are going to use for partial reconfiguration after full configuring the full size bit-stream programming.

 

You can figure out the size of the bit-stream by checking it's properties post generation of the bit-stream.

While in the address section you mention where you are supposed to put the bit-stream.

 

Thank you.

-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------
Xilinx Employee
Xilinx Employee
718 Views
Registered: ‎11-17-2008

Re: How to determine the size of bitstream

Jump to solution

Let me add a few more comments to @kvasantr's statement:

 

The size of a partial bitstream will depend on a few factors, most notably the size and shape of the pblock(s) used to define the Reconfigurable Partition (RP) area.  Other factors include bitstream options such as compression and per-frame CRC checking.  If the floorplan and bitstream options remain the same, the bitstream size will remain the same, with one exception:  compression depends on the implementation result, so each partial bitstream for a given RP will vary.  If you are not using compression, determine the bitstream size from an initial result and then update the IP customization for all subsequent runs with that floorplan.

 

If you are using compression, or you are simply looking for different options, there are two ways to add/change this value post-route.  The first is through a Tcl API call, e.g.

prc_v1_2::netlist::set_rm_bs_size dscr vs_shift rm_shift_right 375300

This is documented in the Customizing the Core Post Implementation section of PG193, and is shown in labs 5 and 6 of the PR Tutorial document, UG947.

 

The other option, also documented in PG193 and shown in UG947, is to update the partial bitstream details while the design is running, via AXI-Lite.  Slots and triggers must be predefined to use this approach, but fine-tuning of bitstream size and address can be done as in-system updates.

 

thanks,

david.