Connect to Generic Access Service with SDK 17.1.0

RE: Connect to Generic Access Service with SDK 17.1.0

Sigurd — Fri, 20 Jun 2025 11:11:49 GMT

Hi!

You should not remove the APP_ERROR_CHECK(), they are there to catch errors. By default a APP_ERROR_CHECK() error will enter app_error_fault_handler(), where the default behavior is to reset the device. So try placing a breakpoint in app_error_fault_handler(). If you are having issues with this, please open a new case for that.

RE: Connect to Generic Access Service with SDK 17.1.0

ricardo.oliveira — Thu, 19 Jun 2025 22:20:29 GMT

I was able to read the device name as I wanted, but now, when the beacon shuts off the connection or when I try to disconnect by code, my device reboots. I have removed all APP_ERROR_CHECK but it still reboots.
Any idea of what can be happening?

RE: Connect to Generic Access Service with SDK 17.1.0

Sigurd — Fri, 06 Jun 2025 14:11:42 GMT

That's after you have connected, and done service discovery.

You can view the advertisement data in the "Scanner" tab (make sure you disconnect from the device)

RE: Connect to Generic Access Service with SDK 17.1.0

ricardo.oliveira — Fri, 06 Jun 2025 11:39:54 GMT

Sure. This image is from nRF Connect:

RE: Connect to Generic Access Service with SDK 17.1.0

Sigurd — Fri, 06 Jun 2025 07:46:11 GMT

Could you post a screenshot on how the advertising data looks like for the beacon, e.g. using nRF Connect for mobile ?
Maybe there is some information apart from the MAC address that you can use to trigger a connect on.

RE: Connect to Generic Access Service with SDK 17.1.0

ricardo.oliveira — Thu, 05 Jun 2025 13:50:24 GMT

What I mean is, since I know my beacon is connectable, and suppose it has only the Generic Access Service, how can I connect to it and then read the device name in the UUID characteristic 0x2A00?

I saw the link you attached, but since I'm new to Ble and nordic, it still lacks informations for me.

What I did here was to set "init_scan.connect_if_match = false", and then in the BLE_GAP_EVT_ADV_REPORT case inside the callback of the event handler, I could see my beacon MAC and other informations, but I don't know how to proceed to connect to it and read that characteristic.

RE: Connect to Generic Access Service with SDK 17.1.0

Sigurd — Wed, 04 Jun 2025 14:48:35 GMT

From the screenshot, the beacon seem to only have the Generic Access Service, and don't have e.g. the NUS service.

A BLE advertiser, can advertise different kind of data. e.g. Incomplete/Complete UUID list of available services, Shortened/Complete Local Name, Tx Power Level, Manufacturer Specific Data, etc. If you want to find "your beacon" you need to advertise something that is unique for your beacons.

RE: Connect to Generic Access Service with SDK 17.1.0

ricardo.oliveira — Wed, 04 Jun 2025 14:30:04 GMT

[quote userid="15146" url="~/f/nordic-q-a/121958/connect-to-generic-access-service-with-sdk-17-1-0/537864"]You are filtering on NUS UUID, but the beacon does not have the NUS UUID.[/quote]

My beacon do not have an connectable UUID? Sorry I didn't get it.

I was able to connect to the beacon via it's MAC address, but for my development that is not useful. I should try to connect to any beacon of this type that is around, so I would not know all MAC address to connect to. After I connect to any nearby beacon, than I'd read it's name and so my program logic would start.

RE: Connect to Generic Access Service with SDK 17.1.0

Sigurd — Tue, 03 Jun 2025 12:03:05 GMT

Hi!

[quote user=""]But I'm not able to even connect to it yet.[/quote]

    err_code = nrf_ble_scan_filter_set(&m_scan, SCAN_UUID_FILTER, &m_nus_uuid);
    APP_ERROR_CHECK(err_code);

    err_code = nrf_ble_scan_filters_enable(&m_scan, NRF_BLE_SCAN_UUID_FILTER, false);
    APP_ERROR_CHECK(err_code);

You are filtering on NUS UUID, but the beacon does not have the NUS UUID.

[quote user=""] so I can read the characteristic 0x2A00 and then read it's name. [/quote]

See this post on how to do that: RE: Reading the central device name (smart phone) in nRF52DK(Peripheral) and printing on the terminal