0% found this document useful (0 votes)
47 views3 pages

Routing Inside Pblock - Odt

Routing signals within a module's pblock (intra-module routing) can reduce the chances of a design remaining unrouted by keeping modules close together without needing to re-route them. However, it increases the resource overhead for modules and may reduce their relocatability. While intra-pblock routing worked well for simple modules with low congestion, more complex modules with higher congestion saw incomplete routing when placed close together.

Uploaded by

Srijeet Guha
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as ODT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
47 views3 pages

Routing Inside Pblock - Odt

Routing signals within a module's pblock (intra-module routing) can reduce the chances of a design remaining unrouted by keeping modules close together without needing to re-route them. However, it increases the resource overhead for modules and may reduce their relocatability. While intra-pblock routing worked well for simple modules with low congestion, more complex modules with higher congestion saw incomplete routing when placed close together.

Uploaded by

Srijeet Guha
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as ODT, PDF, TXT or read online on Scribd
You are on page 1/ 3

Routing Inside Pblock

Pros:
• Intra-module routing will not be disturbed and different modules can be brought close to each other without the
need to route the modules again. Reduces the chances of the design remaining unrouted. (see diagrams)

Case 1: Fork + Multiplier module.

Fork module with routing outside pblock Multiplier module outside pblock

Complete routing
in Fork + multiplier
module placed
close to each other.

Routing outside
pblock did not
cause routing
problems.

[Ignore the red


routing, they are
because clock pins
are not connected]

However, this was apparently due to less congestion in the modules. We tried some modules with higher congestion.
Case 2: Fifo + Multiplier module
Fifo module with routing outside pblock Multiplier module outside pblock

Incomplete routing on a design merged between Fifo and


multiplier module.

The yellow lines indicate unrouted paths.

[Ignore the red routing, they are because clock pins


are not connected]

Cons:
• Reduces the number of shapes available for each component.
Eg. The multiplier component will then have only one shape.

• Increases overhead for the modules. (ie. requires more sites than would have required if the routing was
outside the pblock)
Eg. In the Fifo module, minimum site requirement rises to 8 SITES when only 5 were required if routing
was not inside the pblock. This implies a 37.5% increase in the resources consumed by components.
• Relocatibility reduces in some cases.
Eg: The fifo module (without routing inside the pblock) requires a minimum of 5 sites. The number of
valid placement positions in the device is : 91920
However, the same module (with routing inside the pblock) requires a minimum of 8 sites and the
number of valid placement positions in the device is: 56376

This is a reduction by 38.6%

You might also like