Hi Sowmya & Nantha,
If two signal or clock nets are closer enough to each other, the effect of coupling capacitance between them leads to crosstalk.
Crosstalk delay: Let's say one net is switching at faster rate (time taken for signal level to rise from 0 to 1 is less) and other net switching at slower rate (time taken for signal level to rise from 0 to 1 is less), due to coupling cap...faster switching net effects in speedingup of slower net.
Let say one net is switching at faster rate from 0 to 1 and other adjacent ramps down from 1 to 0 at slower rate. The effect of first net will delay ramping down of slower net further.
Think of these kind of situations on the chip for crosstalk delays....I will not elaborate further on this...just imagine...
Crosstalk noise: When one net is idle and its adjacent net is switching form 0 to 1, there is possiblilty of unwanted signal transition for finite time induced in idle net due to coupling cap. If this unwanted transition is within noisemargin of your technology then it will corrupt the logics.
Remedies to encounter these two effects:
1. Move interacting nets apart in layout. (if your layout is not congested)
2. Shield the nets using proper sheilding metal (Let me know what metal is usually used for shieiding purpose).
3. Re-route tge interacting nets.
You can add to this list....if you have any more remedies....
Crosstalk delay analysis: PT-SI tool does this based on timing constraints. It needs SPEF and incremental SDF to do this. I can elaborate on this...let me know if you want to...
Crosstalk noise analysis: I believe libs should have noise models to do this. Don't have much idea on this. Please let me know if you know something on this.
Inputs: PT-SI license, SPEF and inc SDF, Proper timing constraints, noise models.
Outputs: Violating timing paths.
Regards,
Eshwar.