L
Admin
[Technical article / FAQ, rfforum Editorial Team]
An RFIC input that meets ESD on the datasheet can still burn 0.3–0.8 dB of noise figure in diodes and clamps the app note never puts in the NF cascade. The first LNA stage never gets the antenna match you simulated; the ESD network sits in series with that match and owns part of the budget.
1. What the clamp actually does at RF
- ESD diodes add shunt capacitance and lossy resistance at the pin. At a few GHz that capacitance is already a matching element; at tens of GHz it can dominate the input Q.
- A "robust" dual-diode + series resistor path that passes HBM can look like a few tenths of a dB IL plus a shifted Gamma_opt. Your discrete matching network then fights a different load than the bare die model.
- Package bond wires and the ESD cell are often one lump in the S-parameters; stripping ESD "for RF performance" without a re-qualified package is not a free lunch.
2. Freeze list before you blame the LNA core NF
- Whether the S-parameters and NF data include the ESD cell (and which package)
- De-embedded or on-wafer NF versus packaged NF on the same die revision
- Measured input match and NF with ESD enabled vs a known ESD-less evaluation path (if the vendor provides one)
- Whether your matching network was tuned to the packaged S-parameters or to an ideal Gamma_opt from a core-only model
3. Habit
Never close a "we are 0.5 dB worse than the datasheet NF" ticket without asking whether the datasheet NF includes ESD and package. Archive ESD-included vs core-only notes next to every front-end NF claim. If the package S-parameters already contain the clamp, matching to a core-only Gamma_opt invents loss that looks like a process problem.
4. Practical gate
- Ask the vendor: NF and S-parameters with ESD on, package PN named
- On the board, treat the ESD network as part of the first matching section, not as "protection after RF"
- If you need both hard ESD and best NF, budget the clamp IL explicitly; do not hide it in "implementation loss"
Discussion: on your last NF miss versus datasheet, how much landed in ESD/package versus matching — and do you require ESD-included S-parameters before freezing a front-end budget?
— rfforum 编辑部 / Editorial Team
An RFIC input that meets ESD on the datasheet can still burn 0.3–0.8 dB of noise figure in diodes and clamps the app note never puts in the NF cascade. The first LNA stage never gets the antenna match you simulated; the ESD network sits in series with that match and owns part of the budget.
1. What the clamp actually does at RF
- ESD diodes add shunt capacitance and lossy resistance at the pin. At a few GHz that capacitance is already a matching element; at tens of GHz it can dominate the input Q.
- A "robust" dual-diode + series resistor path that passes HBM can look like a few tenths of a dB IL plus a shifted Gamma_opt. Your discrete matching network then fights a different load than the bare die model.
- Package bond wires and the ESD cell are often one lump in the S-parameters; stripping ESD "for RF performance" without a re-qualified package is not a free lunch.
2. Freeze list before you blame the LNA core NF
- Whether the S-parameters and NF data include the ESD cell (and which package)
- De-embedded or on-wafer NF versus packaged NF on the same die revision
- Measured input match and NF with ESD enabled vs a known ESD-less evaluation path (if the vendor provides one)
- Whether your matching network was tuned to the packaged S-parameters or to an ideal Gamma_opt from a core-only model
3. Habit
Never close a "we are 0.5 dB worse than the datasheet NF" ticket without asking whether the datasheet NF includes ESD and package. Archive ESD-included vs core-only notes next to every front-end NF claim. If the package S-parameters already contain the clamp, matching to a core-only Gamma_opt invents loss that looks like a process problem.
4. Practical gate
- Ask the vendor: NF and S-parameters with ESD on, package PN named
- On the board, treat the ESD network as part of the first matching section, not as "protection after RF"
- If you need both hard ESD and best NF, budget the clamp IL explicitly; do not hide it in "implementation loss"
Discussion: on your last NF miss versus datasheet, how much landed in ESD/package versus matching — and do you require ESD-included S-parameters before freezing a front-end budget?
— rfforum 编辑部 / Editorial Team
