How to Choose Between GaN and GaAs Microwave SSPAs?

Choosing between GaN and GaAs SSPAs is tricky. GaN's smaller size is appealing, but its non-linearity can secretly tank your system performance¹. Let’s find the right solution.

Choose GaN for higher power density and a smaller footprint, but be prepared for its non-linearity. To maintain signal integrity, you must implement Digital Pre-Distortion (DPD) and a 3-5 dB power back-off. For applications demanding high linearity without DPD, GaAs remains a solid choice.²

On the surface, the choice seems simple. You either pick GaN for power or GaAs for linearity. But the real engineering challenge lies in the details. The consequences of picking the wrong one, or using one incorrectly, can be costly. We need to look closer at what these differences really mean for your system's performance. Let's break down the critical factors you must consider.

Why Does GaN's Size Advantage Come with a Linearity Cost?

Everyone loves GaN's smaller footprint. But the fear of non-linear effects causing signal distortion is real. Understanding the source of this problem is the first step to solving it.

GaN's superior thermal conductivity³ and high power density allow for smaller heat sinks. However, this same material property contributes to stronger trapping effects, which create non-linear memory effects. This causes AM-AM and AM-PM distortion⁴, negatively impacting your signal quality if not properly managed.

The Trade-Off: Power Density vs. Memory Effects

Gallium Nitride (GaN) has a wider bandgap than Gallium Arsenide (GaAs). This lets it handle higher voltages and temperatures. The result is much higher power density. You can get more watts out of a smaller chip, which means your heat sink can be smaller and your overall SSPA is more compact. I remember a project where switching to a GaN SSPA, like one of our high-power models, cut our heat sink volume by nearly half.

But this advantage has a catch. The high-density operation in GaN creates "trapping effects." Charge carriers get temporarily trapped and released within the semiconductor material. This process is not instant, so the amplifier's response at any given moment depends on the signals that came just before. This is what we call a "memory effect." It leads directly to AM-AM and AM-PM distortions, where amplitude and phase variations are no longer linear.

Here's a simple comparison:

cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits⁵, cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits.

How Can You Use GaN SSPAs Without Sacrificing Signal Integrity?

cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits.

cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits.

cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits

cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits.

cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits

cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits⁶. cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits.

Konklusion

cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits.