Is this all still valid, or are there any changes required for the latest stack(s). Thanks?
@edpgc - Yes, this is still valid in the EmberZNet 5.10 stack, but beginning in 6.0 we will have a new "LNA" plugin that can be enabled to manage all this automatically for MGM12P.
Is this valid for Bluetooth Mesh SDK 1.2?
I used the soc_btmesh_empty project from the AppBuilder and migrated my custom code into it. I was having trouble getting packet to transmit. When I set HAL_FEM_TX_ACTIVE to 1 and HAL_FEM_RX_ACTIVE to 0 in hal-config-board.h, I was able to get packets to transmit. This is contrary to what was mentioned above, but seems to work for my project. Note that I am using the fem-control plugin.
Are there other FEM related or any other configurations that need to be implemented in order for TX and RX optimization?
I'm using MGM12P32F1024GA however these comments probably applies to other modules with internal FEMs.
For anyone who stumbles across this now, the FEM setup should be handled automatically by the latest Simplicity Studio and radio stacks. You will see within the Hardware Configurator that "External FEM" is set by default and that if you enable the FEM driver within the Plugins tab that you cannot reconfigure the driver as its setup for the module automatically. Apparently whether you enable the driver or not in the plugins tab it is always loaded as this is necessary for the module to work correctly.