[Bug]: high-power mode broken in v1.5.0 release

[nicolas-juteau]

Bug Summary

High-power mode can not be used in v1.5.0 release (examples and sx126x driver)

Detailed Description

Steps to reproduce on a NUCLEO-WL55JC board

1. Open the LoRaWAN_End_Node_LBM application example from STM32CubeWL v1.5.0 release
2. Explicitely modify the BSP driver so that high-power mode is used by default (make function BSP_RADIO_GetTxConfig return RADIO_CONF_RFO_HP rather than RADIO_CONF_RFO_LP_HP)
3. Hook an oscilloscope or logic probe on PC4 (RF_SW_CTRL1). The signal shall go LOW when high-power mode is selected:

4. Debug the example and confirm that in ral_sx126x_bsp_get_tx_cfg function paSelect is set to RFO_HP and that configured output_params power are indeed the highest (high-power mode)
5. PC4 never goes LOW during TX

Cause

No surprise PC4 never goes LOW: in sx126x.c file, function sx126x_set_ant_switch, paSelect is hardcoded to RFO_LP. If changed to RFO_HP, PC4 will go LOW during TX as it should.

Side note

How come in the LoRaWAN v1.5.0 examples, one cannot explicitely configure the TX power level?

Expected Behavior

PC4 should go LOW during TX phase when high-power mode is used

Actual Behavior

PC4 never goes LOW during TX phase (no high-power mode achieved)

Environment

NUCLEO-WL55JC1, STM32CubeWL v1.5.0, STM32CubeIDE v2.1.1

Severity

Major

[MKISTM]

Hello @nicolas-juteau,

Thank you for your intervention, this point will be tracked internally.
I'll keep you informed by our decision about this point.

BR,
Mohamed Chaker.

[MKISTM]

ST Internal Reference: CDM0061259