Problems with the "bt_gatt_dm_start" function

[SerhiiR]

Hi,

I'm just learning the nRF Connect SDK and don't know all the ins and outs of it.

I have the following problem:
When calling the function bt_gatt_dm_start, I get the following log:

<err> bt_gatt_dm: attr_store: No space for new attribute.
<err> bt_gatt_dm: discovery_process_attribute: Not enough memory for next attribute descriptor at handle 68.

The discovery procedure failed with -12

The service I want to connect to has 14 attributes, I think this is the problem.

How can I fix this problem?

When trying to call bt_gatt_dm_start for BT_UUID_BAS (Battery Service) there is no problem.

TRANSLATE with x

English

Arabic	Hebrew	Polish
Bulgarian	Hindi	Portuguese
Catalan	Hmong Daw	Romanian
Chinese Simplified	Hungarian	Russian
Chinese Traditional	Indonesian	Slovak
Czech	Italian	Slovenian
Danish	Japanese	Spanish
Dutch	Klingon	Swedish
English	Korean	Thai
Estonian	Latvian	Turkish
Finnish	Lithuanian	Ukrainian
French	Malay	Urdu
German	Maltese	Vietnamese
Greek	Norwegian	Welsh
Haitian Creole	Persian

TRANSLATE with

COPY THE URL BELOW

Back

EMBED THE SNIPPET BELOW IN YOUR SITE

Enable collaborative features and customize widget: Bing Webmaster Portal

Back

[Edvin]

Hello,

Looks like the default discovery module attribute table size is set to 35. Try increasing this in your prj.conf:

CONFIG_BT_GATT_DM_MAX_ATTRS=50

Best regards,

Edvin

[SerhiiR]

Hi,

Thanks for all your help.

That solved my problem.

Please clarify, is there a list of all available СONFIG_.... to understand when to use them?

[Edvin]

There used to be on our documentation page, but it was removed. But it was a very (!!!!) long list, so it doesn't really make sense to read it from start to finish. Most of them are not relevant for you project (it contained all CONFIGs for Zephyr as well as our custom). Unfortunately, I don't have any good advice to familiarize yourself with the ones that you would need. To find the one that you were looking for, I was searching through the source code, and found the struct that held the array that was too small in your case, and I saw that it's size was set by that config:

struct bt_gatt_dm {
	/* Connection object */
	struct bt_conn *conn;
	/* The user context */
	void *context;

	/* The discovery parameters used */
	struct bt_gatt_discover_params discover_params;
	/* Currently parsed attributes */
	struct bt_gatt_dm_attr attrs[CONFIG_BT_GATT_DM_MAX_ATTRS];
	/* Currently accessed attribute */
	size_t cur_attr_id;
	/* Flags with the status of the attributes */
	ATOMIC_DEFINE(state_flags, STATE_NUM);

	/* The UUID of the service to discover. */
	union {
		struct bt_uuid uuid;
		struct bt_uuid_16 u16;
		struct bt_uuid_32 u32;
		struct bt_uuid_128 u128;
	} svc_uuid;

    ...

Also, if you know approximately what config you are looking for, you can search either in the link at the start of this reply, or you can start typing into prj.conf if you are using nRF Connect for VS Code, and it should give you a list of possible matches. 

Best regards,

Edvin

[SerhiiR]

Thanks Edvin , you helped me a lot!

TRANSLATE with x

English

Arabic	Hebrew	Polish
Bulgarian	Hindi	Portuguese
Catalan	Hmong Daw	Romanian
Chinese Simplified	Hungarian	Russian
Chinese Traditional	Indonesian	Slovak
Czech	Italian	Slovenian
Danish	Japanese	Spanish
Dutch	Klingon	Swedish
English	Korean	Thai
Estonian	Latvian	Turkish
Finnish	Lithuanian	Ukrainian
French	Malay	Urdu
German	Maltese	Vietnamese
Greek	Norwegian	Welsh
Haitian Creole	Persian

TRANSLATE with

COPY THE URL BELOW

Back

EMBED THE SNIPPET BELOW IN YOUR SITE

Enable collaborative features and customize widget: Bing Webmaster Portal

Back