sd_ble_gap_device_name_set returning 0x7 with any parameters

RE: sd_ble_gap_device_name_set returning 0x7 with any parameters

NewtoM — Sat, 11 Jun 2022 10:53:14 GMT

Hey All,

I've found a different solution that appeals to me. In the file nrf_svc.h you will find following wrapper:

#define SVCALL(number, return_type, signature)          \
  _Pragma("GCC diagnostic push")                        \
  _Pragma("GCC diagnostic ignored \"-Wreturn-type\"")   \
  __attribute__((naked))                                \
  __attribute__((unused))                               \
  static return_type signature                          \
  {                                                     \
    __asm(                                              \
        "svc %0\n"                                      \
        "bx r14" : : "I" (GCC_CAST_CPP number) : "r0"   \
    );                                                  \
  }                                                     \
  _Pragma("GCC diagnostic pop")

The functions of the softdevice (SD) seem to always be called over SVCALL. So, since I want my own code to be optimized in release mode, but the calls to the SD doesn't seem to work when the code is optimized, I hacked in a single line of code __attribute__((optimize("O0"))), see:

#define SVCALL(number, return_type, signature)          \
  _Pragma("GCC diagnostic push")                        \
  _Pragma("GCC diagnostic ignored \"-Wreturn-type\"")   \
  __attribute__((naked))                                \
  __attribute__((unused))                               \
  __attribute__((optimize("O0")))                       \
  static return_type signature                          \
  {                                                     \
    __asm(                                              \
        "svc %0\n"                                      \
        "bx r14" : : "I" (GCC_CAST_CPP number) : "r0"   \
    );                                                  \
  }                                                     \
  _Pragma("GCC diagnostic pop")

That way, the calls to the SD work and my parts of the code remain optimized.

That works well with SEGGER Embedded Studio v6.30 along with nRF5 SDK 17.1 on an nRF52840 DK.

Best,
Tamas

RE: sd_ble_gap_device_name_set returning 0x7 with any parameters

matheus almeida — Fri, 10 Jun 2022 23:50:56 GMT

Heys NewtoM, i managed to "solve" the issue here:

https://devzone.nordicsemi.com/f/nordic-q-a/88778/wierd-error-7-happening-in-init

TLDR: Rollback to Segger studio 5.70a

Thougt the issue might be something deeper because if i swap the compiler from GGC (deffault), to SEGGER it got the code partially working (it crashes during the connection).

RE: sd_ble_gap_device_name_set returning 0x7 with any parameters

NewtoM — Fri, 10 Jun 2022 23:19:36 GMT

I see similar behavior with Segger Embedded Studio v6.30 on Windows 11 with SDK 17.1 when trying to run a program based on the ble_peripheral\ble_app_uart example. Interestingly, sd_ble_gap_device_name_set() only returns 0x7 if the code was compiled in release mode. If compiled in debug mode, the return value is 0.

When trying around with RTT viewer, I can see following messages:

<error> nrf_sdh_ble: sd_ble_cfg_set() returned NRF_ERROR_INVALID_PARAM when attempting to set BLE_CONN_CFG_GAP.
<error> nrf_sdh_ble: sd_ble_cfg_set() returned NRF_ERROR_INVALID_PARAM when attempting to set BLE_GAP_CFG_ROLE_COUNT.
<error> nrf_sdh_ble: sd_ble_cfg_set() returned NRF_ERROR_INVALID_LENGTH when attempting to set BLE_GATTS_CFG_ATTR_TAB_SIZE.
<error> nrf_sdh_ble: sd_ble_enable() returned NRF_ERROR_NO_MEM.
<error> app: Fatal error

But again, this only happens if built in release mode (optimization being above level 0). Other settings are the same for debug and release modes.

I am using the nRF52840 DK.

RE: sd_ble_gap_device_name_set returning 0x7 with any parameters

Simonr — Thu, 09 Jun 2022 08:02:01 GMT

Okay, from seeing the error I assumed you might have changed the device name to an invalid value, but I guess not. I'm not able to reproduce this error on the nRF52 DK I have here on my end, so it must be related to moving to the nRF52810 HW. If you're running the PCA10040e version of the example the only change necessary should be to remove the DEVELOP_IN_NRF52832 and NRFX_COREDEP_DELAY_US_LOOP_CYCLES defines from the compile flags in your IDE. Here is the user guide for transferring projects to nRF52810 HW.

Are you certain the INVALID_PARAM error is coming from the sd_ble_gap_device_name_set() function? Because the only parameters are the security mode (should be BLE_GAP_CONN_SEC_MODE_SET_OPEN by default), DEVICE_NAME, and the length for the DEVICE_NAME.

Best regards,

Simon

RE: sd_ble_gap_device_name_set returning 0x7 with any parameters

matheus almeida — Wed, 08 Jun 2022 14:17:51 GMT

Hello Simon,

So, as i mentioned before, that was the example that came with the SDK version 17.1.0, at first i havent changed anything. Just after debugging i tried to change values. The name is:

#define LEDBUTTON_BUTTON                BSP_BUTTON_0                            /**< Button that will trigger the notification event with the LED Button Service */

#define DEVICE_NAME                     "Nordic_Blinky"                         /**< Name of device. Will be included in the advertising data. */

#define APP_BLE_OBSERVER_PRIO           3                                       /**< Application's BLE observer priority. You shouldn't need to modify this value. */

Which is the default value declared on line 77 on the main.c

RE: sd_ble_gap_device_name_set returning 0x7 with any parameters

Simonr — Wed, 08 Jun 2022 12:37:56 GMT

If sd_ble_gap_device_name_set() returns an "INVALID PARAM" error, that does indeed point to one of the parameters in the function not being vaild. What have you set your DEVICE_NAME as exactly? This should be set somewhere in the top of your application as a define.

Best regards,

Simon