BLE_UUID_OUR_BASE_UUID not correct, flags not correct

[Geoffroy]

Hi,

I'm using nRF52840 with SDK15.0.0 wit code from : https://devzone.nordicsemi.com/tutorials/b/bluetooth-low-energy/posts/ble-services-a-beginners-tutorial

I could make the tutorial advertising works i can see my device on nRF connect application... but i have troubles with definitions :

my problem is defining 128-bit base UUIDs :

ADVERTISING :

#define BLE_UUID_OUR_BASE_UUID              {{0xAA, 0xBB, 0xCC, 0xDD, 0xEE, 0xFF, 0x11, 0x22, 033, 0x44, 0xAB, 0x00, 0x00, 0x00, 0x00, 0x00}}

NOT ADVERTISNG :

#define BLE_UUID_OUR_BASE_UUID              {{0xAA, 0xBB, 0xCC, 0xDD, 0xEE, 0xFF, 0x11, 0x22, 033, 0x44, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00}}

so the problem seems to be a sequence of 6 0x00, but that's the sequence requested by my protocol...

I have another problem similar with flags :

 ADVERTSING
 init.advdata.flags                   = BLE_GAP_ADV_FLAGS_LE_ONLY_GENERAL_DISC_MODE;
 NOT ADVERTISING
 init.advdata.flags                   = BLE_GAP_ADV_FLAGS_NEW_MODE;

i defined : #define BLE_GAP_ADV_FLAGS_NEW_MODE    (0x1A), requested by my protocol :

bit 0 (OFF) : LE Limited Discoverable Mode
bit 1 (ON)  : LE General Discoverable Mode
bit 2 (OFF) : BR/EDR not Supported
bit 3 (ON)  : Simultaneous LE and BR/EDR to Same Device Capable (controller)
bit 4 (ON)  : Simultaneous LE and BR/EDR to Same Device Capable (Host)

thank your for your help

Geoffroy

[Hakon]

Hello,

have you debugged the application? Do you receive an error code when you try advertising or any other place in the application?

[Geoffroy]

yes i debugged the application for BLE_UUID_OUR_BASE_UUID.

in ble_advertising.c a test is done in ble_advertising_init :

    if (!config_is_valid(&p_init->config))
    {
        return NRF_ERROR_INVALID_PARAM;
    }

and i get NRF_ERROR_INVALID_PARAM (0x07)

i tryed to further, but i didn't fnd a solution yet.

I'm try trying right now to debug and add trace with SEGGER_RTT_printf

[Hakon]

I noticed it says "0BB" and not "0xBB". Maybe that has something to do with it. It shouldn't even compile though.

[Geoffroy]

I edited, in code it's 0xBB

[Hakon]

Well, the project files on github are supposed to work with nrf52832, so if you want it to work for nrf52840 you probably need to make some changes to the project options, like preprocessor symbols and perhaps also memory layout.

[Geoffroy]

yes i adapted the project, it's working and advertising with nRF58240

my problem is with a special definition for my BLE_UUID_OUR_BASE_UUID  with a sequence of 6 consecutive 0x00

and other problem with definition of flag

[Geoffroy]

I would like to know where is  verification for 6 consecutives 0x00 to remove this verification of BASE_UUID

and to remove verifiaction for flags ...

[Geoffroy]

for flags, in ble_advertising.c, ble_advertising_start calls sd_ble_gap_adv_set_configure and it returns :  0x0A for NRF_ERROR_INVALID_FLAGS.

call of sd_ble_gap_adv_set_configure send  me in ble-gap.h to :

SVCALL(SD_BLE_GAP_ADV_SET_CONFIGURE, uint32_t, sd_ble_gap_adv_set_configure(uint8_t *p_adv_handle, ble_gap_adv_data_t const *p_adv_data, ble_gap_adv_params_t const *p_adv_params));

it's supervisor call interface but i don't know how to proceed to desactivate this control...