STM32WL LORA: HW specific out of STM32WL_LoRaRadio class

[jeromecoutant]

Summary of changes

Some code in STM32WL_LoRaRadio class was specific to NUCLEO_WL55JC HW,
and not general to STM32WL

It is then now compiled in another file.
Function is weak, and can be / has to be updated in each HW application

Should fix #14714

@niondir @ludoch-stm

Impact of changes

Migration actions required

Documentation

---

Pull request type

[x] Patch update (Bug fix / Target update / Docs update / Test update / Refactor)
[] Feature update (New feature / Functionality change / New API)
[] Major update (Breaking change E.g. Return code change / API behaviour change)

---

Test results

[] No Tests required for this change (E.g docs only update)
[x] Covered by existing mbed-os tests (Greentea or Unittest)
[] Tests / results supplied as part of this PR

---

Reviewers

---

[ciarmcom]

@jeromecoutant, thank you for your changes.
@ARMmbed/mbed-os-maintainers please review.

[0xc0170]

is weak function really needed ? Seems like based on the state that is valid for everyone, just the ctrl1-3 changes its values. or is there more that can come in?

wondering if config would be sufficient for this or we need a weakly function

[jeromecoutant]

is weak function really needed ? Seems like based on the state that is valid for everyone, just the ctrl1-3 changes its values. or is there more that can come in?
wondering if config would be sufficient for this or we need a weakly function

I have discussed with some LORA experts, and I understand that our HW reference design currently supports 4 antenna switch state, which are then configurable thanks to 3 GPIOs.
But I don't know at all, beut a custom board can maybe supports only 3 states ?
So how to do the mapping between available GPIO and state ?

[0xc0170]

@niondir what your custom function look like, if you just use one pin ?

[ciarmcom]

This pull request has automatically been marked as stale because it has had no recent activity. , please complete review of the changes to move the PR forward. Thank you for your contributions.

[0xc0170]

CI started

[mbed-ci]

Jenkins CI Test : ✔️ SUCCESS

Build Number: 1 | 🔒 Jenkins CI Job | 🌐 Logs & Artifacts

CLICK for Detailed Summary

jobs	Status
jenkins-ci/mbed-os-ci_unittests	✔️
jenkins-ci/mbed-os-ci_cmake-cloud-example-ARM	✔️
jenkins-ci/mbed-os-ci_cmake-cloud-example-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_cmake-example-ARM	✔️
jenkins-ci/mbed-os-ci_build-cloud-example-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_build-example-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_build-greentea-ARM	✔️
jenkins-ci/mbed-os-ci_build-example-ARM	✔️
jenkins-ci/mbed-os-ci_build-cloud-example-ARM	✔️
jenkins-ci/mbed-os-ci_cmake-example-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_build-greentea-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_greentea-test	✔️

[niondir]

@0xc0170
Looks fine with the weak function - so I can just override it. I actually use 2 pins now. One is "RF-Switch Power on/off" and one is for the direction (RX/TX). I was able to use 2 of the existing pins, since they work as expected and set the third one to an unused PIN.

With this fix I can simply build my own method just containing my pins. That's great.

Kind regards
Tobias