I have uploaded the 256K efr32bg14p732f256gm48-brd4105a  bootloader-storage-internal-ble    bootloader to the board

Please make sure that you've programmed the device with the correct bootloader. For BGM121, the Bluetooth in-place OTA DFU Bootloader should be used in your case. KBA_BT_0603 provides more information about how to add bootloader to your project.

hi Gabriele,

There is no extra setup needed if you are using the BGM121 radio board and the demo examples. Please just try to program the BGM121 with demo image SoC-Empty, and then check if you can capture the network log correctly.

Thanks

I'm afraid that I didn't understand the question.

Is this a Bluetooth Mesh application? Please help to elaborate a bit more about your question.

You should able to get the documentations from Zephyrproject.

hi Szabolcs,

As you might know that the communication between the NCP Host and NCP Target is defined in the Silicon Labs Proprietary Protocol called BGAPI, and the Bluetooth SDK delivers a ready-made BGAPI serial protocol ANSI C parser implementation, called BGLIB. You can just take the NcpHost example comes with the SDK as example, and it's easy to port it to the 3rd MCU.

Please see the KBA_BT_1602 for NCP host code walkthrough.

This GPIO activation provides functionality to enter firmware upgrade mode automatically after reset if a GPIO pin is active during boot. So you should reset your NCP target while keeping the GPIO is active to make the NCP target entering bootloader.

And the pin mode on the host side should be gpioModePushPull
GPIO_PinModeSet(gpioPortF, 3, gpioModePushPull, x);

hi Thomas,

Thanks for bringing us attention about it, I'm looking into it and will get back to you soon.

Please see the comparison below.

EFR32BG21 SoC, Radio current consumption at 3.0V

BGM210P module, Radio Current Consumption at 3.0V

If you are using the EFR32BG13 starter kit, the VCOM_TX is connected to PA0, and the macro "USART_ROUTELOC0_TXLOC_DEFAULT" defines the location information for how to route the US0_Tx to PA0, and the location information is documented in the datasheet.

 

If BlueGecko device is the master, you can use the command "cmd_le_gap_set_data_channel_classification" to block certain BLE data channels manually. And there is another method AFH (Adaptive Frequency Hopping) which can detects high interference and block low-quality channels dynamically. See more information in KBA_BT_0406.
And also the Bluetooth SDK supports the most common Wi-Fi/PTA implementations to improve Bluetooth coexistence with Wi-Fi. More information can be found in AN1128.