Calling sd_ble_gap_tx_power_set() errors out with 0x3004, NRF_ERROR_NO_MEM

RE: Calling sd_ble_gap_tx_power_set() errors out with 0x3004, NRF_ERROR_NO_MEM

Einar Thorsrud — Tue, 18 Jan 2022 08:01:18 GMT

Hi,

The API of sd_ble_gap_tx_power_set() changed in SoftDevice version 6.0.0. Since then, you can set TX power separately for different roles, connections, etc. See API documentation for details.

RE: Calling sd_ble_gap_tx_power_set() errors out with 0x3004, NRF_ERROR_NO_MEM

Sami — Tue, 18 Jan 2022 05:11:15 GMT

Looks like a misread interpreted the error code. Thank you for clarifying. Ok, so I can now successfully call sd_ble_gap_tx_power_set() with the following code:

BLE_ADVERTISING_DEF(m_advertising);                                                 /**< Advertising module instance. */
static uint16_t m_conn_handle = BLE_CONN_HANDLE_INVALID;                            /**< Handle of the current connection. */


//err_code = sd_ble_gap_tx_power_set(BLE_GAP_TX_POWER_ROLE_ADV, m_connHandle, calaTxPower); // this does not work!
err_code = sd_ble_gap_tx_power_set(BLE_GAP_TX_POWER_ROLE_ADV, m_advertising.adv_handle, calaTxPower); // this works

The way that doesn't work is the way we used to call sd_ble_gap_tx_power_set() from SDK 11.0.0~!

The method that you suggested, which doesn't use the connection handle but rather, the advertising instance m_advertising, does work. Is my attempt to use m_conn_handle simply deprecated?

I turned on the DEBUG preprocessor as you suggested, however, I got no further information (only the old error code 0x3004).

RE: Calling sd_ble_gap_tx_power_set() errors out with 0x3004, NRF_ERROR_NO_MEM

Einar Thorsrud — Mon, 17 Jan 2022 07:48:55 GMT

Hi,

The error code 0x3004 is BLE_ERROR_INVALID_ADV_HANDLE (not NRF_ERROR_NO_MEM). Looking at the API documentation for sd_ble_gap_tx_power_set() you see that it is returned if you provided an invalid connection handle. I do not see from your code snippet what the value of m_connHandle is, but it is clearly not valid. You get this value from when you initialize advertising (see for instance <SDK 17.x.x>\examples\ble_peripheral\ble_app_proximity\main.c).

For future reference, I highly recommend making use of the APP_ERROR_CHECK() function in combination with having DEBUG defined in your preprocessor defines, like shown in the included image:

This will make your logger output a detailed error message whenever a non-NRF_SUCCESS error code is passed to an APP_ERROR_CHECK, which makes debugging much easier. It would be very useful to see the error message output by the logger in this case, if you insert an APP_ERROR_CHECK on the error code returned by sd_ble_gap_tx_power_set.