Permanently damaged Radio RX path on STM32WB55
Hi,
we've been developing with stm32wb55 for some time and found that some combinations of STOP2 and radio usage causes permanent damage to RX path.
It looks like that: device announce stops at some point and power consumption raises(+10mA). After reset device starts announce again, but doesn't receive anything.
Flashing TransparentVCP and checking RX with CubeMonitorRF shows RSSI -108dBm
Wiping flash and re-flashing radio and firmware doesn't help.
Overall we've been following all application notes on power, radio, LSE/HSE. The only significant difference is antenna(we use IMD by Ethertronics/AVX 1001312) and software(we use STOP2 in between announces and prevent sleep only when connection arrives).
Disabling STOP2 prevents damage, but completely unacceptable in terms of UX and power consumption.
Since radio is a black box we are completely puzzled by this behavior and were unable to trace cause of damage.
Is there any way to examine radio path internals (like on st25)? As I understand AT0, AT1 exists exactly for that purpose.
Or any other ways to find what may cause RX path damage?