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
2,572 Views
Registered: ‎09-05-2015

Why do we need to specify reconfigurable modules beforehand? (partial reconfiguration)

Jump to solution

 

 

 

1.JPG

 

 

Hi, I don't understand why we need to specify what should be cpuEngine, usbEngine0, and usbEngine1 when we create configuration in the figure above.(It is from ug909) Intuitively, the most efficient way is implementing static part first, and all the possible reconfigurable modules separately. Then, combine pre-implemented modules with static part so that all we need to do is stitching pre-implemented parts together.

 

If we have to specify reconfigurable modules beforehand, all we save is the time spent on placing/routing static part. I don't understand why there should be a coupling among cpuEngine, usbEngine0, and usbEngine1.

 

0 Kudos
1 Solution

Accepted Solutions
Highlighted
Explorer
Explorer
4,728 Views
Registered: ‎09-05-2015

Re: Why do we need to specify reconfigurable modules beforehand? (partial reconfiguration)

Jump to solution

Sorry, never mind. Just realized that all the partial bitstreams for different physical locations are generated with the full bitstream. 

0 Kudos
1 Reply
Highlighted
Explorer
Explorer
4,729 Views
Registered: ‎09-05-2015

Re: Why do we need to specify reconfigurable modules beforehand? (partial reconfiguration)

Jump to solution

Sorry, never mind. Just realized that all the partial bitstreams for different physical locations are generated with the full bitstream. 

0 Kudos