Change bt device id on THINGY:91

RE: Change bt device id on THINGY:91

Karl Ylvisaker — Tue, 23 Jan 2024 13:18:00 GMT

Hello 0x35c and Izpons,

I am terribly sorry for the delay in getting back to you here - I have unfortunately been out of office since new year due to illness, and this case have somehow fallen through the cracks and not been picked up in the meantime, for which I am terribly sorry!

I am glad to read that you reached out to Matt Heins and get the assistance you needed!

Best regards,
Karl

RE: Change bt device id on THINGY:91

0x35c — Thu, 18 Jan 2024 09:05:09 GMT

[quote userid="77062" url="~/f/nordic-q-a/106758/change-bt-device-id-on-thingy-91/461732"]Øyvind[/quote]

Hello Øyvind Karl Ylvisaker ,
The problem is fixed, thanks to Matt Heins, our field rep in the US.
Here is the solution for anyone bumping into the same issue
Adding these lines to prj.conf worked:

CONFIG_SETTINGS_FCB=y
CONFIG_FCB=y

# Flash - Used in FOTA, settings and storage for P-GPS.
CONFIG_FLASH=y
CONFIG_FLASH_PAGE_LAYOUT=y
CONFIG_FLASH_MAP=y
CONFIG_STREAM_FLASH=y
CONFIG_MPU_ALLOW_FLASH_WRITE=y

Thanks for your time, you can now close this ticket !

Kind regards,

0x35c

RE: Change bt device id on THINGY:91

lzpons — Mon, 15 Jan 2024 11:29:31 GMT

Dear Support team,

This issue is holding us from releasing our product update. We are locked with it since 24 days and do not have any other way to move ahead than you, Nordic Support, helping us find the solution.

We checked all we could check, read all documentation available, tested all we could test...

This is an important issue for us. We cannot deliver devices with the very same ID!

Please help us move ahead.

Lorenzo

RE: Change bt device id on THINGY:91

0x35c — Thu, 11 Jan 2024 11:56:06 GMT

If you want, here is the app_config.c file modified (I changed it to match as much as possible the settings sample)

devzone.nordicsemi.com/.../1586.app_5F00_config.c

RE: Change bt device id on THINGY:91

0x35c — Mon, 08 Jan 2024 10:45:29 GMT

Hi, any updates ? Karl Ylvisaker Øyvind

RE: Change bt device id on THINGY:91

Øyvind — Wed, 27 Dec 2023 09:25:45 GMT

Hello,

We are severely understaffed this week because of the Christmas holidays, and Karl will have to get back to you on this next week. Sorry for the inconvenience.

Kind regards,
Øyvind

RE: Change bt device id on THINGY:91

0x35c — Fri, 22 Dec 2023 12:27:02 GMT

[quote userid="87869" url="~/f/nordic-q-a/106758/change-bt-device-id-on-thingy-91/461561"]Could you share the full log for this scenario as well?[/quote]

Here is the full log at boot (there are a few log/print statements for debugging purposes).

[00:00:00.267,486] <err> ADXL372: failed to read id (0xFF:0xFF)
*** Booting nRF Connect SDK v2.5.0 ***
[00:00:00.267,669] <inf> main: ***** XXXXXXXXXX T91 app started, Version 261 ***********
device id: 54:0:0
[00:00:00.568,023] <inf> app_ble: Id created: C6:09:16:54:00:00
[00:00:00.568,023] <inf> app_ble: Initializing Bluetooth..
[00:00:00.578,308] <wrn> lpuart: req pin low when expected high
[00:00:00.578,430] <err> lpuart: Empty receiver state:4
[00:00:01.078,796] <inf> app_ble: Dev: 54:00:00
[00:00:01.687,316] <wrn> bt_hci_core: opcode 0x0000 pool id 3 pool 0x2000d4f0 != &hci_cmd_pool 0x2000d558
[00:00:01.727,691] <inf> bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)
[00:00:01.727,722] <inf> bt_hci_core: HW Variant: nRF52x (0x0002)
[00:00:01.727,752] <inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 197.47763 Build 2370639017
[00:00:01.730,407] <inf> bt_hci_core: Identity: C6:09:16:54:00:00 (random)
[00:00:01.730,468] <inf> bt_hci_core: HCI: version 5.4 (0x0d) revision 0x1102, manufacturer 0x0059
[00:00:01.730,499] <inf> bt_hci_core: LMP: version 5.4 (0x0d) subver 0x1102
[00:00:01.730,499] <inf> app_ble: Bluetooth ready
[00:00:01.740,325] <inf> app_ble: Advertising successfully started

The log where the id fails to set is here

[00:01:00.058,349] <inf> app_ble: Connected 64:3D:C8:51:4B:77 (random)
[00:01:00.610,626] <inf> app_ble: MTU: 23
[00:01:00.640,594] <wrn> bt_l2cap: Ignoring data for unknown channel ID 0x003a
[00:01:01.540,710] <inf> xxxxxxxxx_service: Writing device id.
Device id: 54:16:9
[00:01:01.540,954] <inf> main: Evt: APP_EVENT_DEVICE_ID_UPDATE
[00:01:01.540,985] <inf> main: ------------------- POST status 42
base device_id: 54:0:0
path app/device_id, id: 54:16:9
[00:01:01.541,076] <wrn> main: Unable to set device id. -2
[00:01:01.603,515] <inf> app_ble: Disconnected from 64:3D:C8:51:4B:77 (random) (reason 0x13)

I move the definition outside of the scope and removed static but it doesn't seem to change anything...

Enjoy your holidays and I really hope we will be able to figure out what's going wrong !

Best regards,

0x35c

RE: Change bt device id on THINGY:91

Karl Ylvisaker — Fri, 22 Dec 2023 12:03:59 GMT

Hello,

[quote user="0x35c"]Sorry for the delay[/quote]

No need to apologize - we'll continue this whenever you have a chance! :)
That being said, please also note that the national christmas holiday starts in Norway today, and lasts until new years. In this time we will have significantly reduced capacity here on DevZone, just so you know! :)

[quote user="0x35c"]here is the whole code related to setting the device_id:[/quote]

Could you move the definition of the settings_handler outside of the scope of the init function, and make it non-static?

[quote user="0x35c"]I just found this error message at boot:[/quote]

This looks like there is an error in your communication with the ADXL372 sensor, rather than an issue with setting the device ID. Could you share the full log for this scenario as well?

Best regards,
Karl

RE: Change bt device id on THINGY:91

0x35c — Thu, 21 Dec 2023 11:09:21 GMT

Sorry for the delay, here is the whole code related to setting the device_id:
devzone.nordicsemi.com/.../app_5F00_config.c

It is quite similar to the documentation you sent me but it does not work...
I just found this error message at boot:

[00:00:00.267,517] <err> ADXL372: failed to read id (0xFF:0xFF)

I guess it could be related but I don't know why does this happen.
Thanks in advance :)
Regards,

0x35c

RE: Change bt device id on THINGY:91

Karl Ylvisaker — Tue, 19 Dec 2023 16:00:57 GMT

Hello 0x35c,

Thank you for the elaboration and clarification.

[quote user="0x35c"]I can see that my id has the right value, but settings_save_one() returns -2 which is -ENOENT in the code below:[/quote]

The -2 / -ENOENT error code means 'no such file or directory', which points in the direction of the key used for the write being incorrect or missing.
However, looking at the source code for settings_save_one it looks like the reason for the return code specifically is that settings_save_dst has not been populated prior to the call.

Could you share the rest of your relevant code as well, specifically your initalization and registration of the settings module? This should look similar to example in the settings documentation.

Best regards,
Karl

RE: Change bt device id on THINGY:91

0x35c — Tue, 19 Dec 2023 08:21:48 GMT

Also, here is my prj.conf file if you want to check everything is ok
[ EDIT ] prj.conf removed to keep informations away

RE: Change bt device id on THINGY:91

0x35c — Mon, 18 Dec 2023 15:13:52 GMT

int app_config_set_device_id(struct app_ble_device_id *id)
{
    /* Save into settings only if we're configured as a default */
    if (m_device_id.lower == APP_CONFIG_DEVICE_ID_LOWER_DEFAULT &&
        m_device_id.upper == APP_CONFIG_DEVICE_ID_UPPER_DEFAULT)
    {
        printk("path %s, id: 54:%d:%d\n", APP_CONFIG_DEVICE_ID_PATH, id->upper, id->lower);
        return settings_save_one(APP_CONFIG_DEVICE_ID_PATH, id, sizeof(struct app_ble_device_id));
    }
    else
    {
        /* Cannot set again.. */
        return -EALREADY;
    }
}

This is my piece of code that used to write the device id to the memory, I didn't change anything except the printk() I added for debugging purposes. I can see that my id has the right value, but settings_save_one() returns -2 which is -ENOENT in the code below:

/*
 * Append a single value to persisted config. Don't store duplicate value.
 */
int settings_save_one(const char *name, const void *value, size_t val_len)
{
	int rc;
	struct settings_store *cs;

	cs = settings_save_dst;
	if (!cs) {
		return -ENOENT;
	}

	k_mutex_lock(&settings_lock, K_FOREVER);

	rc = cs->cs_itf->csi_save(cs, name, (char *)value, val_len);

	k_mutex_unlock(&settings_lock);

	return rc;
}

Note that this code is the SDK source and that I didn't change it in any way.

My guess is that it has something to do with the first parameter of settings_save_one (APP_CONFIG_DEVICE_ID_PATH) which is set to app/device_id:

#define APP_CONFIG_DEVICE_ID_KEY "device_id"
#define APP_CONFIG_DEVICE_ID_PATH APP_CONFIG_SETTINGS_KEY "/" APP_CONFIG_DEVICE_ID_KEY

I don't know why is it set to this, I wasn't in charge of the code when this was written and I can't find any element in the documentation about what this path should be set to.

Thanks for your help and feel free to ask anything if you need precisions.

0x35c

RE: Change bt device id on THINGY:91

Karl Ylvisaker — Mon, 18 Dec 2023 15:02:23 GMT

Hello,

[quote user=""]

we have an app running on T91s and we recently upgraded it to sdk 2.5.0, from sdk 1.9.1. We used to change the device id after flashing our app on the thingy by connecting to the thingy and sending data, which was then processed and written to the thingy as its device id.

This solution does not seem to work anymore with the newer sdk... I would like to know if there is any way to change the device id¹ after flashing the thingy91 with our app.

[/quote]

Which changes did you make to the application in your upgrade from v1.9.1 to v2.5.0?
How did you configure this when it was working, and how are you configuring it now?
By device ID are you here referring to the advertised BLE name, or another ID?
It would be great if you could share the relevant code using the Insert -> Code option here on DevZone, so that I can know exactly what you are referring to here.

Best regards,
Karl