DFU support in Fast pair locator tag on nRF52833-DK

[Jignesh shingala]

Hi every one,

If any body have been succeeded  in adding DFU support in Fast pair locator tag on nRF52833-DK, if so can you guide me for it?

I am getting configuration and partition manager error every time.

regards,

Jignesh

[Vidar Berg]

Hi,

DFU should be enabled by default if you select the "release" configuration. Did you try that? 

Best regards,

Vidar

[Jignesh shingala]

Hi Vidar,

With this change it build successful, but when i tried to do dfu with generated dfu_application.zip, it is failing in eneabling bootloader. I have tested with DFU and Device manager apps in both app it is failing in bootloader enable.

Also generated merged.hex file siae is 1214KB and dfu_application.zip size is 420KB.

i have build this code for nRF52833-DK, then how merged.hex file size is possible more than 512KB?

[Jignesh shingala]

Hi Vidar,

Please find attached screenshot of DFU and Device manager app.

 

It is failing in bootloader enable in both app.

[Vidar Berg]

The dfu app shown in the second picture is only supporting legacy dfu. You need to use either the device manager or nrf connect app. Also, the first image from det device manager app is not showing any attempts to upload the fw

[Jignesh shingala]

Hi Vidar,

please find attached nRF connect and DFU app screenshot for DFU.

In both case DFU not started and device come out from DFU mode in some seconds.

[Vidar Berg]

These are not showing any error message either. I suggest you look at the log from both the app and the device.

[Jignesh shingala]

Hi Vidar,

getting connection Time out in device manager app

[Jignesh shingala]

Hi Vidar,

Can you suggest if any other configurations need to be made for DFU in Locator Tag example code for nRF52833-DK? 

[Vidar Berg]

You still haven't provided any logs as I requested. You also need to ensure you are in dfu mode https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/samples/bluetooth/fast_pair/locator_tag/README.html#dfu_mode 

[Jignesh shingala]

Hi Vidar,

this is release build so no logs from device side and for device manager app can you confirm where can we see logs?

[Vidar Berg]

Forgot that logs were disabled, but at least you can get the logs from the nrf connect app. Have you confirmed you are in dfu mode as well?

[Jignesh shingala]

please find attached nrf connect logs.

Fullscreen 0878.DFU_logs.txt Download

nRF Connect, 2026-01-21
NCS locator Tag (40:04:83:EA:03:A6)
V	15:56:13.989	Connecting to 40:04:83:EA:03:A6...
D	15:56:13.990	gatt = device.connectGatt(autoConnect = false, TRANSPORT_LE, preferred PHY = LE 1M)
D	15:56:14.753	[Callback] Connection state changed with status: 133 and new state: DISCONNECTED (0)
E	15:56:14.753	Error 133 (0x85): GATT ERROR
I	15:56:14.753	Disconnected
D	15:56:16.698	gatt.close()
D	15:56:16.706	wait(200)
V	15:56:16.907	Connecting to 40:04:83:EA:03:A6...
D	15:56:16.907	gatt = device.connectGatt(autoConnect = false, TRANSPORT_LE, preferred PHY = LE 1M)
D	15:56:17.835	[Callback] Connection state changed with status: 0 and new state: CONNECTED (2)
I	15:56:17.835	Connected to 40:04:83:EA:03:A6
V	15:56:17.837	Discovering services...
D	15:56:17.837	gatt.discoverServices()
D	15:56:17.875	[Broadcast] Action received: android.bluetooth.device.action.ACL_CONNECTED
D	15:56:17.968	[Callback] Services discovered with status: 0
I	15:56:17.968	Services discovered
V	15:56:17.989	Generic Attribute (0x1801)
- Service Changed [I] (0x2A05)
   Client Characteristic Configuration (0x2902)
- Client Supported Features [R W] (0x2B29)
- Database Hash [R] (0x2B2A)
Generic Access (0x1800)
- Device Name [R] (0x2A00)
- Appearance [R] (0x2A01)
- Peripheral Preferred Connection Parameters [R] (0x2A04)
Device Information (0x180A)
- Firmware Revision String [R] (0x2A26)
Accessory Non-Owner Service (15190001-12f4-c226-88ed-2ac5579f2a85)
- Accessory Non-Owner Characteristic [I W] (8e0c0001-1d68-fb92-bf61-48377421680e)
   Client Characteristic Configuration (0x2902)
Google Fast Pair Service (0xFE2C)
- Key-based Pairing [N W] (fe2c1234-8366-4814-8eb0-01de32100bea)
   Client Characteristic Configuration (0x2902)
- Passkey [N W] (fe2c1235-8366-4814-8eb0-01de32100bea)
   Client Characteristic Configuration (0x2902)
- Account Key [W] (fe2c1236-8366-4814-8eb0-01de32100bea)
- Beacon Actions [N R W] (fe2c1238-8366-4814-8eb0-01de32100bea)
   Client Characteristic Configuration (0x2902)
SMP Service (8d53dc1d-1db7-4cd3-868b-8a527460aa84)
- SMP Characteristic [N WNR] (da2e7828-fbce-4e01-ae9e-261174997c48)
   Client Characteristic Configuration (0x2902)
D	15:56:17.990	gatt.setCharacteristicNotification(00002a05-0000-1000-8000-00805f9b34fb, true)
D	15:56:17.995	gatt.setCharacteristicNotification(8e0c0001-1d68-fb92-bf61-48377421680e, true)
D	15:56:17.997	gatt.setCharacteristicNotification(fe2c1234-8366-4814-8eb0-01de32100bea, true)
D	15:56:18.000	gatt.setCharacteristicNotification(fe2c1235-8366-4814-8eb0-01de32100bea, true)
D	15:56:18.003	gatt.setCharacteristicNotification(fe2c1238-8366-4814-8eb0-01de32100bea, true)
I	15:56:18.452	Connection parameters updated (interval: 45.0ms, latency: 0, timeout: 1000ms)
V	15:56:26.415	[McuMgr] Connecting...
D	15:56:26.421	[McuMgr] gatt = device.connectGatt(autoConnect = false, TRANSPORT_LE, LE 1M)
D	15:56:26.514	[McuMgr] [Callback] Connection state changed with status: 0 and new state: 2 (CONNECTED)
I	15:56:26.520	[McuMgr] Connected to 40:04:83:EA:03:A6
D	15:56:26.526	[McuMgr] wait(300)
V	15:56:26.884	[McuMgr] Discovering services...
D	15:56:26.890	[McuMgr] gatt.discoverServices()
I	15:56:26.914	[McuMgr] Services discovered
V	15:56:26.919	[McuMgr] Primary service found
V	15:56:26.941	[McuMgr] Requesting new MTU...
D	15:56:26.947	[McuMgr] gatt.requestMtu(498)
I	15:56:27.113	[McuMgr] MTU changed to: 247
D	15:56:27.119	[McuMgr] gatt.setCharacteristicNotification(da2e7828-fbce-4e01-ae9e-261174997c48, true)
V	15:56:27.128	[McuMgr] Enabling notifications for da2e7828-fbce-4e01-ae9e-261174997c48
D	15:56:27.134	[McuMgr] gatt.writeDescriptor(00002902-0000-1000-8000-00805f9b34fb, value=0x01-00)
I	15:56:27.329	[McuMgr] Data written to descr. 00002902-0000-1000-8000-00805f9b34fb
V	15:56:27.339	[McuMgr] Waiting for value change...
V	15:56:27.345	[McuMgr] Writing characteristic da2e7828-fbce-4e01-ae9e-261174997c48 (WRITE COMMAND)
D	15:56:27.351	[McuMgr] gatt.writeCharacteristic(da2e7828-fbce-4e01-ae9e-261174997c48, value=0x000000010000FF06A0, WRITE COMMAND)
I	15:56:27.368	[McuMgr] Data written to da2e7828-fbce-4e01-ae9e-261174997c48
W	15:56:28.347	[McuMgr] Request timed out
V	15:56:28.356	[McuMgr] Requesting connection priority: HIGH (11.25–15ms, 0, 5s)...
D	15:56:28.516	[McuMgr] gatt.requestConnectionPriority(HIGH)
A	15:56:28.688	[McuMgr] Sending (9 bytes) Header (Version: 1, Op: 0, Flags: 0, Len: 1, Group: 0, Seq: 0, Command: 8) CBOR {}
I	15:56:28.804	Connection parameters updated (interval: 15.0ms, latency: 0, timeout: 5000ms)
V	15:56:28.860	[McuMgr] Writing characteristic da2e7828-fbce-4e01-ae9e-261174997c48 (WRITE COMMAND)
D	15:56:28.875	[McuMgr] gatt.writeCharacteristic(da2e7828-fbce-4e01-ae9e-261174997c48, value=0x0800000100000008A0, WRITE COMMAND)
I	15:56:28.881	[McuMgr] Connection parameters updated (interval: 15.0ms, latency: 0, timeout: 5000ms)
I	15:56:28.893	[McuMgr] Data written to da2e7828-fbce-4e01-ae9e-261174997c48
A	15:56:31.045	[McuMgr] Sending (9 bytes) Header (Version: 1, Op: 0, Flags: 0, Len: 1, Group: 1, Seq: 1, Command: 0) CBOR {}
V	15:56:31.052	[McuMgr] Writing characteristic da2e7828-fbce-4e01-ae9e-261174997c48 (WRITE COMMAND)
D	15:56:31.058	[McuMgr] gatt.writeCharacteristic(da2e7828-fbce-4e01-ae9e-261174997c48, value=0x0800000100010100A0, WRITE COMMAND)
I	15:56:31.068	[McuMgr] Data written to da2e7828-fbce-4e01-ae9e-261174997c48
V	15:56:36.046	[McuMgr] Disconnecting...
D	15:56:36.053	[McuMgr] gatt.disconnect()
D	15:56:36.224	[McuMgr] [Callback] Connection state changed with status: 0 and new state: 0 (DISCONNECTED)
I	15:56:36.234	[McuMgr] Disconnected
D	15:56:36.241	[McuMgr] gatt.close()