t()` and DPD tracking enabled but **no** `adi_adrv9025_DpdReset()` issued, the actuator is never programmed: its MMR block holds no model program, bit1 of the word at 0xA0820000 is set (our reading: actuator bypass, output = input, since `dpdMeanTxPower` ≈ `dpdMeanTuPower`), and tracking reports 0x340A (AM-AM outliers) on every iteration with `dpdUpdateCount = 0`.
2. Any `adi_adrv9025_DpdReset(TX1, ADI_ADRV9025_DPD_LUT_RESTORE)` or `ADI_ADRV9025_DPD_RESET_FULL` (tracking disabled ≥1 s beforehand, per the release-note workaround) programs the actuator from the loaded model **but the actuator LUT RAM reads all zero afterwards**. Tx output disappears (`dpdMeanTxPower` reads null/INT32_MIN, ORx −56 dBFS, error 0x3405 ORx signal too small). Tx attenuation stays at 10000 mdB, PA protection is disabled on this board and shows no flags, and CLGC-on/off ordering made no difference.
3. The condition is permanent at runtime (re-enabling tracking, reloading the model, repeating the reset in any mode/order, CLGC off, recovery-action changes — none recovered). The only recovery we found is writing bit1 of 0xA0820000 back by host DMA; Tx returns within 3 s and tracking resumes in the state of item 1.
We would like to understand what makes the firmware program the actuator with an empty LUT, and what the intended way is to obtain a non-bypass, non-zero actuator on this device.
## 2. Evidence
Register values were read with the private `adrv9025_CpuDmaMemRead()` at the addresses in `adrv9025_reg_addr_macros.h` (`ADRV9025_ADDR_DPD_ACT_MMR_DPD_CFG_TX1 = 0xA0820000`, `…_DPD_MOD_TX1 = 0xA0820004`, `…_LUT_OFF_TX1 = 0xA0820088`, `…_STAT_TX1 = 0xA08200F0`, `ADRV9025_EXT_DPD_ACTUATOR_TX1_LUT_BASEADDR = 0xA0800000`). We have no register description for these; interpretations below are ours.
### 2.1 Status (`adi_adrv9025_DpdStatusGet`, `adi_adrv9025_ClgcStatusGet`, `adi_adrv9025_TxAttenGet`)
| state | dpdErrorCode | meanTu | meanTx | meanORx | CLGC TxRms / OrxRms | Tx atten |
|---|---|---|---|---|---|---|
| tracking, no DpdReset ("healthy") | 0x340A, iterCount climbs, updateCount 0 | −18.9 dBFS | −19.0 dBFS | −16.5 dBFS | ~7300 / ~9500–10100 | 10000 mdB |
| 2 s after DpdReset(LUT_RESTORE) | 0 | −18.9 dBFS | null (INT32_MIN) | null | ~7070 / **83** | 10000 mdB |
| +20 s, tracking re-enabled | 0x3405 | −18.9 dBFS | null (INT32_MIN) | −56 dBFS | — / ~83 | 10000 mdB |
Pre-actuator level (meanTu) is unchanged; post-actuator level (meanTx) collapses. PA protection is disabled and no error flags are set; `TxAttenGet` and CLGC `activeTxAttenIndex` are unchanged.
### 2.2 Actuator MMR and LUT RAM (TX1)
| state | DPD_CFG (0xA0820000) | DPD_MOD (+0x04) | LUT_OFF (+0x88) | +0x08 | LUT RAM 0xA0800000… |
|---|---|---|---|---|---|
| fresh bring-up, before any reset | 0x00C00003 | 0 | 0 | 0 | non-zero (31663 of 32768 words over 128 KiB), contents change between two reads 10 s apart |
| right after LUT_RESTORE | 0x00C00001 | 0x0010001F | 0x9F8020E0 | 0x003FCF0F | **0 non-zero words of 8192 (first 32 KiB)** |
| +20 s, tracking on (muted) | 0x00C00001 | 0x0010001F | 0x9F8020E0 | 0x003FCF0F | **all zero across the full 128 KiB (0xA0800000–0xA081FFFF)** |
| never-enabled TX2 | 0 | 0 | 0xFFFFFFFF | — | first 32 KiB zero |
- `0x003FCF0F` at +0x08 (repeated at +0x28, +0x48) is exactly the LUT set used by our model (LUTs 0–3, 8–11, 14–21), so the reset does consult the loaded model when it programs the actuator.
- DPD_CFG bit1 is cleared by the reset. Writing `0x00C00003` back by host DMA restores Tx within 3 s (CLGC OrxRms 83 → 9857); in a second run the LUT RAM read all zero immediately before the write-back and Tx still returned. This is why we read bit1 as an actuator bypass/passthrough bit.
- No GPIO-based actuator bypass is configured: the stream image is the vendor-package one (`stream_options.txt`: `Gpio0..15Selection = 255`, `ExternalDpdEnabled = false`, no Tx Ant Cal GPIO) and `streamGpioCfg.streamGpInput0..15 = ADI_ADRV9025_GPIO_INVALID` in the post-MCS init structure. Tx/Rx use PIN enable mode, ORx SPI mode. So the state of bit1 is set by the firmware alone.
- Host DMA writes into the LUT RAM window return success but read back 0 (single word and 1 KiB fill on engaged TX1; single words on idle TX2). MMR writes do take effect.
### 2.3 Variations tried
| variation | result |
|---|---|
| RESET_FULL instead of LUT_RESTORE; LUT_RESTORE then FULL; GUI order (ModelConfigSet → LUT_RESTORE) | mutes |
| LUT_RESTORE on TX1→TX2→TX3→TX4 back to back (SDUG single-band sequence) | mutes |
| ADI firmware default model (63 features, read with `DpdModelConfigGet` before any load) instead of ours (95 features) | mutes |
| CLGC tracking disabled before the reset | mutes |
| `DpdRecoveryActionSet`: REVERT_LUTS_TO_UNITY + RESET_ADAPTATION_STATE on mean Tx/ORx power-low persistent metrics | did not fire within 43 iterations; cause not established |
| `minAvgSignalLevel = 8000` (≈ −12 dBFS, above meanTu) to force the U table | firmware reports 0x3407 (Tx signal too small), `dpdModelTable` stays M, DPD_CFG stays 0x00C00003 |
| `DpdModelConfigGet` | FW-default readback shows `txChannelMask = 0x0` (reserved field) |
| DPD init cal (`ADI_ADRV9025_DPD` = 0x00100000 in the init-cal mask) at runtime | "DPD hardware is being used by other cals" |
| DPD init cal in the boot init-cal mask | init cals pass, but `TrackingCalsEnableSet(DPD)` then returns rc=0 without the DPD bit sticking |
| External path delay cal (TX1) | passes every bring-up (fifoDelay 159–160) |
| ORx level sweep −16 … −36 dBFS, ORx saturation check, TxQEC off, direct-learning, staggered cals | no change to the 0x340A state |
| **FDD** 20 MHz 2T2R profile (`Adrv902X-44NLS-4.9GLR-20MHz-FDD-2T2R`), same carrier, PA continuously on | identical: 0x340A (with intermittent 0x3421 capture timeouts) and updateCount 0 while bypassed; LUT_RESTORE mutes with the same MMR signature and all-zero LUT RAM; bit1 write-back restores Tx. So TDD Tx-enable gating is not the cause. |
## 3. Questions
1. What is the expected content of the actuator LUT RAM after `DpdReset(LUT_RESTORE)` with a model that contains a single non-zero coefficient (ours: i=1, j=1, k=0, LUT 9, 1.0+0j; the other 94 features 0)? Is an all-zero LUT a legal outcome, and under what conditions does the firmware produce it?
2. Which M-table does LUT_RESTORE restore — the model most recently written with `DpdModelConfigSet`, or a coefficient set that only exists after a successful adaptation / DPD init cal? The comment on the reserved `txChannelMask` field in `adi_adrv9025_dfe_types.h` reads: "Reserved Param. Currently Tx channel mask is not supported. Settings are applied to the channel for which DPD init cal was run." Is the DPD init cal a prerequisite for LUT_RESTORE/FULL to produce a non-zero actuator? On our board it cannot run at runtime ("DPD hardware is being used by other cals") and when placed in the boot init-cal mask DPD tracking does not enable afterwards — what is the intended ordering with CFR and the other init cals?
3. Is bit1 of 0xA0820000 the actuator bypass / unity-model mux? Is it expected that tracking runs with bit1 = 1 for the whole run (20 s to several minutes in our tests) and never programs the actuator, reporting 0x340A on every iteration with `dpdUpdateCount = 0`? What does the adaptation compare in that state, given pre- and post-actuator are identical?
4. What do `0x0010001F` at +0x04 and `0x9F8020E0` at +0x88 encode? Is a register description of the actuator MMR block (0xA0820000–0xA0820140) available for support purposes?
5. Is host access to the actuator LUT RAM (0xA0800000, 128 KiB) intended to be read-only? Reads return data, but DMA writes read back 0.
6. Does the firmware zero-fill the LUT RAM on `DpdReset` by design before loading the model, so that an empty LUT means the model-expansion step failed silently? If so, is there any status/error we should see (`dpdErrorCode` reads 0 right after the reset)?
7. In this firmware's GMP convention, is i=1,j=1,k=0 (our unity seed) the identity term, or should the identity be i=0,j=0,k=0 (c·|u(n−i)|^k·u(n−j) form)? Could a model without an identity term be treated as a zero actuator?
8. Is there any sequence that leaves the bypass state with a non-zero actuator before an adaptation has succeeded (e.g. is `ADI_ADRV9025_DPD_MODEL_TABLE_U` selectable on demand)?