Set debug.tx_power to ant.ch.ref_frame.tx_power_index to meet regulations

[edwa_casntr]

Hello,

I’m trying to understand the relationship between the debug.tx_power parameter and the ant1.ch9.ref_frame0.tx_power_index settings in the calibration file of the QM35825 SoC.
From my understanding, debug.tx_power is the value used to ensure UWB regulations compliance when operating in Continuous Wave mode with a BW of 1 MHz.

Is the debug.tx_power value directly equivalent to the value that should be configured in antX.ch9.ref_frame0.tx_power_index (and others)?
Or is there some conversion, scaling, or other relationship between these two parameters?
So that, if I determine a compliant TX power using debug.tx_power, I can use the same numeric value for the tx_power_index fields - or are they mapped differently internally?

Thanks in advance for any clarification.

[Matthias]

The debug.tx_power value is not equivalent to the ant1.ch9.ref_frame0.tx_power_index.

In normal mode, ant1.ch9.ref_frame0.tx_power_index adjusts tx power by 0.25dB per unit with 0 being the maximum.

In debug mode, you have control of debug.tx_power, debug.pa_enabled and debug.pll_bias_trim. In this case there is no linear relationship.