device could not be found due to changes in m_adv_uuids[]

[Andhika]

Hi expert,

I'm working for my project that make a controller for drone, and that i need nus for as my service so i can exchange the data (send order via rx from smartphone) so i'm using ble_app_templat as my basis for esthablishing a connection, and it works and then i want to implement my NUS, theoritically I just should  change uuid and the service so the nus could be implemented

but as i change m_adv_uuids[] my device could not be found anymore.

I change it from

static ble_uuid_t m_adv_uuids[] =                                               /**< Universally unique service identifiers. */
{
    {BLE_UUID_DEVICE_INFORMATION_SERVICE, BLE_UUID_TYPE_BLE}
};

to

static ble_uuid_t m_adv_uuids[] =                                               /**< Universally unique service identifiers. */
{
		{BLE_UUID_NUS_SERVICE, NUS_SERVICE_UUID_TYPE }
};

I also try these

static ble_uuid_t m_adv_uuids[] =                                               /**< Universally unique service identifiers. */
{
		{BLE_UUID_NUS_SERVICE, BLE_UUID_TYPE_BLE}
};

it works, my device could be found but i got another problem it shows an error "the handle is invalid" in nrf toolbox app as i want to check the uart.

could anyone help me?

thanks in advance

Andhika

[Marjeris Romero]

Hi,

How have you defined BLE_UUID_NUS_SERVICE? Did you include ble_nus.h in your project? Please take a look at the ble_app_uart example. This example runs the Nordic UART Service (NUS) and can be found under 'examples/ble_peripheral/ble_app_uart' folder.

The Nordic UART service is a custom service, so we use a 128-bit vendor specific UUID and you need to use UUID type BLE_UUID_TYPE_VENDOR_BEGIN.

You can change the base of the 128-bit vendor-specific UUID by changing NUS_BASE_UUID in ble_nus.c if you want (for example if you want to create a custom UART service for your application), please take a look a this tutorial for more information about custom services and UUIDs.

Best regards,

Marjeris

[Andhika]

Hi,

Marjeris Romero said:

How have you defined BLE_UUID_NUS_SERVICE? Did you include ble_nus.h in your project? Please take a look at the ble_app_uart example. This example runs the Nordic UART Service (NUS) and can be found under 'examples/ble_peripheral/ble_app_uart' folder.

yes I defined it through ble_nus.h i already included it in makefile and yes i took the example for my project from ble_app_uart.

Marjeris Romero said:

The Nordic UART service is a custom service, so we use a 128-bit vendor specific UUID and you need to use UUID type BLE_UUID_TYPE_VENDOR_BEGIN.

yeah i also aready defined BLE_UUID_TYPE_VENDOR_BEGIN in nus_service_uuid_type this one that cause the problem i think.

best regard,

Andhika

[Andhika]

Hi,

thanks for your reply, and yes NRF_LOG_ENABLED is set to 1. bu as I debug the program my code stop at service_init the program didn't go through this and go to  NRF_BREAKPOINT_COND instead.

i did exactlc like tutorial.

best regards,

Andhika

[Marjeris Romero]

Hi,

Sorry for the late reply. Have you increased NRF_SDH_BLE_VS_UUID_COUNT from 0 to 1 in sdk_config.h?

[Andhika]

yes I have

[Marjeris Romero]

Hi,

Do you call ble_nus_init() in service_init()? If yes, place a breakpoint in the code line right under it, so for example if you have:

err_code = ble_nus_init(&m_nus, &nus_init);
APP_ERROR_CHECK(err-code);

Try sending a breakpoint at the APP_ERROR_CHECK line. Then check the value you get in err_code.

BR,

Marjeris

[Andhika]

Hi,

sorry for the late reply, i placed the breakpoint in ble_nus_init() but the LED error show nothing

void services_init(void)
{
    uint32_t       err_code;
    ble_nus_init_t nus_init;

    memset(&nus_init, 0, sizeof(nus_init));

    nus_init.data_handler = nus_data_handler;


    err_code = ble_nus_init(&m_nus, &nus_init);
	Err::signalWithCode(err_code,6);
}

problem is if i debug it the device can be found but the code goes direct to NRF_BREAKPOINT_COND;

but if i only flash and run the device could not be found at all.

best regards,

Andhika

[Marjeris Romero]

Hi,

You will need to look at the call stack to find where the error is coming from. In the debugger, open the p_error_info and find the value of err_code...

BR,

Marjeris