Using RapidWright with F2 for "Reuse Timing-closed Logic As A Shell"

[jkjkim]

Hi RapidWright team,

We're trying to use RapidWright to speed up specific module swaps on AWS F2 (xcvu47p, Vivado 2024.2) using the Reuse Timing-closed logic flow.

I'm having trouble loading the design into RapidWright at the CL level because there are some IPs within the CL that RapidWright cannot read (such as sh_ddr given by AWS). However, I think it also doesn't work when I give rapidwright a cell dcp at lower context to create as the "shell". This Do you have some guidance on how I can use this flow? Our ultimate goal is to minimize the compilation time for iterating on a specific module (with everything else staying constant).

Thanks!

[eddieh-xlnx]

Hi @jkjkim. Thanks for posting this discussion! Your ultimate goal is a very valid and feasible one that we'd be happy to help you with.

To be clear, RapidWright has no visibility into the logical netlist of encrypted IPs (which I assume sh_ddr would be) and requires some special handling to ensure such encrypted IPs are emitted again when RapidWright writes out new DCPs. This FAQ entry covers AWS F1, and something similar could apply to F2 too.

Would you be able to share your RapidWright code, and ideally, your input DCP too so that we're on the same page?

Thanks!