You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
it is located at drivers/radio/lr1120mb1dxs_pa_pwr_cfg/lr1120mb1dxs_pa_pwr_cfg.c in our codebase.
There are other options for lr1120 and lr1110 in the SWD003 repository.
Since we are currently unsure what this power configuration actually entails, we will keep using this one.
A way for the user to specify which configuration should be used might be required in the future.
Is the configuration based on how the lr1xx is placed on the board (and the board's passive elements), or is it based on something else?
This must be investigated and a decision made accordingly.
The text was updated successfully, but these errors were encountered:
We have also recently made the following observation:
The power table uses both the LP and HP paths (via LR11XX_RADIO_PA_SEL_LP and LR11XX_RADIO_PA_SEL_HP). But not both of those paths are placed on all of our PCBs.
This issue has been addressed in the SLW2001 "layer" - see here, where we use a DTS binding to configure the available paths.
The correct way to do a similar thing on the SWDR layer is unknown to us.
We are currently using
lr1120mb1dxs_pa_pwr_cfg.c
, which was taken directly from Semtechs SWD003 here: https://github.com/Lora-net/SWSD003/tree/master/shields/LR1120/LR1120MB1DxSit is located at
drivers/radio/lr1120mb1dxs_pa_pwr_cfg/lr1120mb1dxs_pa_pwr_cfg.c
in our codebase.There are other options for lr1120 and lr1110 in the SWD003 repository.
Since we are currently unsure what this power configuration actually entails, we will keep using this one.
A way for the user to specify which configuration should be used might be required in the future.
Is the configuration based on how the lr1xx is placed on the board (and the board's passive elements), or is it based on something else?
This must be investigated and a decision made accordingly.
The text was updated successfully, but these errors were encountered: