CONFIG_CHIP_DFU_OVER_BT_SMP not work

[Denghongyan]

Hello, 

We use NCS2.9.0 and NRF54L15-DK do the matter development, and we use template demo, just enable CONFIG_CHIP_DFU_OVER_BT_SMP in root prj.conf, then we do the ota test: 

Matter over thread ota is ok, but smp ota cannot work, here is my andriod nrfconnect app log:

Should I config any other params?

[Sigurd Hellesvik]

Hi,

Can you check if the following is set for your project? (For example by checking build/template/zephyr/.config):

CONFIG_MCUMGR_GRP_OS

Regards,
Sigurd Hellesvik

[Denghongyan]

Thanks for your reply, I checked, CONFIG_MCUMGR_GRP_OS=y is ok in  build/template/zephyr/.config

[Sigurd Hellesvik]

Error 8 is "not supported", you see, so I just wanted to rule out that the management group was enabled.

From sample.yaml of the template, I see that they set both these for DFU:

"
- CONFIG_CHIP_DFU_OVER_BT_SMP=y
-CONFIG_NCS_SAMPLE_MATTER_OPERATIONAL_KEYS_MIGRATION_TO_ITS=y

"

Try to use both.

Also, do you get any logs from the nRF when DFU does not work?

[Denghongyan]

I tried, but same error, and I cannot change the version in VERSION file now, I don't know what's wrong, and tomorrow I will try to use cmd to build the project.

And I try to turn on the log in prj.conf:
CONFIG_BT_LOG_LEVEL_INF=y

CONFIG_DFU_TARGET_LOG_LEVEL_INF=y
But got no logs any more during OTA:
...

[Sigurd Hellesvik]

Denghongyan said:

cannot change the version in VERSION file now

What do you mean "cannot change" here?

[Denghongyan]

This is ok, but cmd build get the same error, I use an older nrf connect for mobile app, and this is the log:

nRF Connect, 2025-04-03
No name (CF:FD:17:C2:42:0D)
V16:54:43.608Connecting to CF:FD:17:C2:42:0D...
D16:54:43.608gatt = device.connectGatt(autoConnect = false, TRANSPORT_LE, preferred PHY = LE 1M)
D16:54:43.906[Callback] Connection state changed with status: 0 and new state: CONNECTED (2)
I16:54:43.906Connected to CF:FD:17:C2:42:0D
V16:54:43.908Discovering services...
D16:54:43.908gatt.discoverServices()
D16:54:43.918[Broadcast] Action received: android.bluetooth.device.action.ACL_CONNECTED
I16:54:44.239Connection parameters updated (interval: 7.5ms, latency: 0, timeout: 5000ms)
D16:54:44.495[Callback] Services discovered with status: 0
I16:54:44.496Services discovered
V16:54:44.500Generic Attribute (0x1801)
- Service Changed [I] (0x2A05)
   Client Characteristic Configuration (0x2902)
Generic Access (0x1800)
- Device Name [R] (0x2A00)
- Appearance [R] (0x2A01)
- Peripheral Preferred Connection Parameters [R] (0x2A04)
SMP Service (8d53dc1d-1db7-4cd3-868b-8a527460aa84)
- SMP Characteristic [N WNR] (da2e7828-fbce-4e01-ae9e-261174997c48)
   Client Characteristic Configuration (0x2902)
Unknown Service (0000fff6-0000-1000-8000-00805f9b34fb)
- Unknown Characteristic [W WNR] (18ee2ef5-263d-4559-959f-4f9c429f9d11)
- Unknown Characteristic [I] (18ee2ef5-263d-4559-959f-4f9c429f9d12)
   Client Characteristic Configuration (0x2902)
D16:54:44.500gatt.setCharacteristicNotification(00002a05-0000-1000-8000-00805f9b34fb, true)
D16:54:44.503gatt.setCharacteristicNotification(18ee2ef5-263d-4559-959f-4f9c429f9d12, true)
I16:54:44.569Connection parameters updated (interval: 30.0ms, latency: 0, timeout: 5000ms)
I16:54:45.006Connection parameters updated (interval: 45.0ms, latency: 0, timeout: 5000ms)
V16:54:52.945[McuMgr] Connecting...
D16:54:52.949[McuMgr] gatt = device.connectGatt(autoConnect = false, TRANSPORT_LE, LE 1M)
D16:54:52.969[McuMgr] [Callback] Connection state changed with status: 0 and new state: 2 (CONNECTED)
I16:54:52.972[McuMgr] Connected to CF:FD:17:C2:42:0D
D16:54:52.974[McuMgr] wait(300)
V16:54:53.276[McuMgr] Discovering services...
D16:54:53.285[McuMgr] gatt.discoverServices()
I16:54:53.298[McuMgr] Services discovered
V16:54:53.302[McuMgr] Primary service found
V16:54:53.306[McuMgr] Requesting new MTU...
D16:54:53.308[McuMgr] gatt.requestMtu(515)
I16:54:53.383[McuMgr] MTU changed to: 498
D16:54:53.390[McuMgr] gatt.setCharacteristicNotification(da2e7828-fbce-4e01-ae9e-261174997c48, true)
V16:54:53.394[McuMgr] Enabling notifications for da2e7828-fbce-4e01-ae9e-261174997c48
D16:54:53.397[McuMgr] gatt.writeDescriptor(00002902-0000-1000-8000-00805f9b34fb, value=0x01-00)
I16:54:53.556[McuMgr] Data written to descr. 00002902-0000-1000-8000-00805f9b34fb, value: (0x) 01-00
I16:54:53.564[McuMgr] Notifications enabled
V16:54:53.570[McuMgr] Writing characteristic da2e7828-fbce-4e01-ae9e-261174997c48 (WRITE COMMAND)
D16:54:53.572[McuMgr] gatt.writeCharacteristic(da2e7828-fbce-4e01-ae9e-261174997c48)
I16:54:53.579[McuMgr] Data written to da2e7828-fbce-4e01-ae9e-261174997c48, value: (0x) 00-00-00-02-00-01-00-00-BF-FF
A16:54:53.585[McuMgr] "Operation: READ
Flags: 0
Length: 2
Group Id: 1 (IMAGE)
Sequence Num: 0
Command Id: 0 (STATE)
Message: {}" sent
I16:54:53.653[McuMgr] Notification received from da2e7828-fbce-4e01-ae9e-261174997c48, value: (0x) 01-00-00-F0-00-01-00-00-A2-66-69-6D-61-67-65-73-82-A8-64-73-6C-6F-74-00-67-76-65-72-73-69-6F-6E-65-31-2E-39-2E-30-64-68-61-73-68-58-20-A5-94-EF-0F-44-56-D8-57-A4-04-5D-66-00-F5-B2-BA-AA-FC-76-89-1D-9C-51-3B-A3-A5-4A-39-6C-06-F0-68-68-62-6F-6F-74-61-62-6C-65-F5-67-70-65-6E-64-69-6E-67-F4-69-63-6F-6E-66-69-72-6D-65-64-F5-66-61-63-74-69-76-65-F5-69-70-65-72-6D-61-6E-65-6E-74-F4-A8-64-73-6C-6F-74-01-67-76-65-72-73-69-6F-6E-65-31-2E-30-2E-30-64-68-61-73-68-58-20-50-84-65-C3-81-0A-47-B4-C8-40-B6-78-9C-98-14-1A-C1-81-8F-BE-B4-B1-67-0B-F8-7A-8D-FD-E5-F1-9F-27-68-62-6F-6F-74-61-62-6C-65-F5-67-70-65-6E-64-69-6E-67-F4-69-63-6F-6E-66-69-72-6D-65-64-F4-66-61-63-74-69-76-65-F4-69-70-65-72-6D-61-6E-65-6E-74-F4-6B-73-70-6C-69-74-53-74-61-74-75-73-00
A16:54:53.664[McuMgr] "{"images":[{"slot":0,"version":"1.9.0","hash":"pZTvD0RW2FekBF1mAPWyuqr8dokdnFE7o6VKOWwG8Gg=","bootable":true,"pending":false,"confirmed":true,"active":true,"permanent":false},{"slot":1,"version":"1.0.0","hash":"UIRlw4EKR7TIQLZ4nJgUGsGBj760sWcL+HqN/eXxnyc=","bootable":true,"pending":false,"confirmed":false,"active":false,"permanent":false}],"splitStatus":0}" received
V16:54:53.671[McuMgr] Uploading firmware...