PA LNA in a serialized application

[Romain]

Hi,

I am currently working with two nrf52 boards in a serialized configuration. I wanted to add the PA and LNA pin toogle on the connectivity chip. As the gpio can't be configured from the application chip, I did a little work around to allow the application to ask the connectivity to enable PA and LNA pins : I added the following code in the connectity application (in conn_mw_ble.c, in the function conn_mw_ble_opt_set()):

if(opt_id == BLE_COMMON_OPT_PA_LNA){
    sd_err_code = pa_lna_init(19,20);
}else{
    sd_err_code = sd_ble_opt_set(opt_id, p_opt);
}

With pa_lna_init(), the function you gave in an other forum post.

And I used it as follow on the application chip :

gap_params_init();
advertising_init();
services_init();
sensor_simulator_init();
conn_params_init();

// Start execution.
NRF_LOG_INFO("Heart Rate Sensor Start!\r\n");
sd_ble_opt_set(BLE_COMMON_OPT_PA_LNA, NULL);

This configuration works perfectly with the SPI 5W serialization, but stop after the call to sd_ble_opt_set(BLE_COMMON_OPT_PA_LNA, &opt) in the standart SPI serialization (6 wires).

Does anybody have an idea of the differences between the normal SPI and the 5W SPI which could lead to this behavior ?

Regards,

Romain

[Romain]

Thank you for your answer. I forgot to tell you that I already made the change for the return value of pa_lna_init. The 5W spi implementation works perfectly with it. In the standart spi implementation, the call to sd_ble_opt_set(BLE_COMMON_OPT_PA_LNA, &opt);, in the function pa_lna_init(..) makes the connectivity chip to stop and the call never returns. I don't see why the differences between the 5W spi and the standart spi could lead to this problem. Do you have any example with PA and LNA pin activated on the connectivity chip in a serialized application using the standart spi transport ?

Regards,

Romain