The state status is Unknown(147) after FOTA DFU on 54L15

RE: The state status is Unknown(147) after FOTA DFU on 54L15

Menon — Thu, 06 Mar 2025 15:51:37 GMT

Hello,

Sorry for getting back to you a bit late. I received the update from the mobile Apps developers earlier, but I got a bit busy and missed updating it here. I'm glad you found the right thread where the same issue was discussed.

Kind regards,

Abhijith

RE: The state status is Unknown(147) after FOTA DFU on 54L15

LHZ — Thu, 06 Mar 2025 14:18:05 GMT

The problem was due to the app's default time-out setting. This question has been answered by another thread.

Android based FOTA doesn't work with nRF54L15 (2.9.0)

RE: The state status is Unknown(147) after FOTA DFU on 54L15

LHZ — Mon, 03 Mar 2025 16:54:44 GMT

Thank you very much for the reply!

After you saw the DFU sucess, did you reset the board and double check the build?

My situation is that the DFU does work before the resetting. Once resetting, it rolled back to the old build.

Thank you very much!,

Haizhou

RE: The state status is Unknown(147) after FOTA DFU on 54L15

Menon — Mon, 03 Mar 2025 14:54:39 GMT

Hello,

I just tried the sample from the exercise, and I observed a similar behavior, like an unknown state in the Device Manager app. Though the app threw this error, my DFU process still worked.

I also tried the nRF Connect app using a Google Pixel 7 (Android 15) and didn't encounter any issues.

Yes, that is the correct method to collect logs from the nRF Connect app, but the logs I mentioned refer to the nRF device (nRF54L15 in this case) to check if anything is going wrong there.

I will inquire internally about the error message from the Device Manager app.

Kind Regards,

Abhijith

RE: The state status is Unknown(147) after FOTA DFU on 54L15

LHZ — Thu, 27 Feb 2025 16:47:20 GMT

More testing results:

The nRF54L15 FOTA doesn't work on three Android phones, two of them are Google Pixel; but an iPhone works with the same setting and builds.

All Android works on nRF52840.

RE: The state status is Unknown(147) after FOTA DFU on 54L15

LHZ — Wed, 26 Feb 2025 19:28:53 GMT

Hello Abhijith,

Thank you for the reply!

As your suggestion, I reload a fresh LBS example, followed the course exactly, and verified the LBS functioned. It still doesn't work.

I tried a different cell phone just in case. This time, the phone shows "Connection timed out".

Then I tried a brand new nRF54L15 DK board hoping the old hardware is not perfect. No luck.

Then I tried a nRF54840DK board. It works, yes, the different board works. Only difference was to set a new config. In the config, everything is kept the default for both board types.

I used "nRF Connect" app and slide the side to get the log. Is this the right way to collect the logs?

The log is as follow:

nRF Connect, 2025-02-26
Nordic_LBSm (E3:A3:EA:52:01:F2)
V 13:22:38.374 Connecting to E3:A3:EA:52:01:F2...
D 13:22:38.374 gatt = device.connectGatt(autoConnect = false, TRANSPORT_LE, preferred PHY = LE 1M)
D 13:22:38.651 [Callback] Connection state changed with status: 0 and new state: CONNECTED (2)
I 13:22:38.651 Connected to E3:A3:EA:52:01:F2
V 13:22:38.652 Discovering services...
D 13:22:38.652 gatt.discoverServices()
D 13:22:38.662 [Broadcast] Action received: android.bluetooth.device.action.ACL_CONNECTED
D 13:22:38.769 [Callback] Services discovered with status: 0
I 13:22:38.769 Services discovered
V 13:22:38.774 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)
Nordic LED Button Service (00001523-1212-efde-1523-785feabcd123)
- Button [N R] (00001524-1212-efde-1523-785feabcd123)
   Client Characteristic Configuration (0x2902)
- LED [W] (00001525-1212-efde-1523-785feabcd123)
SMP Service (8d53dc1d-1db7-4cd3-868b-8a527460aa84)
- SMP Characteristic [N WNR] (da2e7828-fbce-4e01-ae9e-261174997c48)
   Client Characteristic Configuration (0x2902)
D 13:22:38.774 gatt.setCharacteristicNotification(00002a05-0000-1000-8000-00805f9b34fb, true)
D 13:22:38.776 gatt.setCharacteristicNotification(00001524-1212-efde-1523-785feabcd123, true)
I 13:22:39.311 PHY updated (TX: LE 2M, RX: LE 2M)
I 13:22:43.899 Connection parameters updated (interval: 45.0ms, latency: 0, timeout: 420ms)
V 13:22:44.693 [McuMgr] Connecting...
D 13:22:44.697 [McuMgr] gatt = device.connectGatt(autoConnect = false, TRANSPORT_LE, LE 1M)
D 13:22:44.723 [McuMgr] [Callback] Connection state changed with status: 0 and new state: 2 (CONNECTED)
I 13:22:44.726 [McuMgr] Connected to E3:A3:EA:52:01:F2
D 13:22:44.728 [McuMgr] wait(300)
V 13:22:45.033 [McuMgr] Discovering services...
D 13:22:45.045 [McuMgr] gatt.discoverServices()
I 13:22:45.058 [McuMgr] Services discovered
V 13:22:45.064 [McuMgr] Primary service found
V 13:22:45.070 [McuMgr] Requesting new MTU...
D 13:22:45.075 [McuMgr] gatt.requestMtu(498)
I 13:22:45.160 [McuMgr] MTU changed to: 498
D 13:22:45.168 [McuMgr] gatt.setCharacteristicNotification(da2e7828-fbce-4e01-ae9e-261174997c48, true)
V 13:22:45.179 [McuMgr] Enabling notifications for da2e7828-fbce-4e01-ae9e-261174997c48
D 13:22:45.185 [McuMgr] gatt.writeDescriptor(00002902-0000-1000-8000-00805f9b34fb, value=0x01-00)
I 13:22:45.341 [McuMgr] Data written to descr. 00002902-0000-1000-8000-00805f9b34fb
V 13:22:45.350 [McuMgr] Waiting for value change...
V 13:22:45.357 [McuMgr] Writing characteristic da2e7828-fbce-4e01-ae9e-261174997c48 (WRITE COMMAND)
D 13:22:45.362 [McuMgr] gatt.writeCharacteristic(da2e7828-fbce-4e01-ae9e-261174997c48, value=0x000000010000FF06A0, WRITE COMMAND)
I 13:22:45.372 [McuMgr] Data written to da2e7828-fbce-4e01-ae9e-261174997c48
I 13:22:45.433 [McuMgr] Notification received from da2e7828-fbce-4e01-ae9e-261174997c48, value: (0x) 01-00-00-19-00-00-FF-06-BF-68-62-75-66-5F-73-69-7A-65-19-09-AB-69-62-75-66-5F-63-6F-75-6E-74-04-FF
I 13:22:45.441 [McuMgr] Wait for value changed complete
A 13:22:45.450 [McuMgr] Received Header (Version: 0, Op: 1, Flags: 0, Len: 25, Group: 0, Seq: 255, Command: 6) CBOR {"buf_size":2475,"buf_count":4}
I 13:22:45.467 [McuMgr] SMP reassembly supported with buffer size: 2475 bytes and count: 4
V 13:22:45.473 [McuMgr] Requesting connection priority: HIGH (11.25–15ms, 0, 5s)...
D 13:22:45.478 [McuMgr] gatt.requestConnectionPriority(HIGH)
A 13:22:45.495 [McuMgr] Sending (9 bytes) Header (Version: 1, Op: 0, Flags: 0, Len: 1, Group: 0, Seq: 0, Command: 8) CBOR {}
V 13:22:45.690 [McuMgr] Writing characteristic da2e7828-fbce-4e01-ae9e-261174997c48 (WRITE COMMAND)
D 13:22:45.701 [McuMgr] gatt.writeCharacteristic(da2e7828-fbce-4e01-ae9e-261174997c48, value=0x0800000100000008A0, WRITE COMMAND)
I 13:22:45.716 [McuMgr] Data written to da2e7828-fbce-4e01-ae9e-261174997c48
I 13:22:45.800 Connection parameters updated (interval: 11.25ms, latency: 0, timeout: 420ms)
I 13:22:45.807 [McuMgr] Notification received from da2e7828-fbce-4e01-ae9e-261174997c48, value: (0x) 09-00-00-15-00-00-00-08-BF-6A-62-6F-6F-74-6C-6F-61-64-65-72-67-4D-43-55-62-6F-6F-74-FF
I 13:22:45.811 [McuMgr] Connection parameters updated (interval: 11.25ms, latency: 0, timeout: 420ms)
A 13:22:45.819 [McuMgr] Received Header (Version: 1, Op: 1, Flags: 0, Len: 21, Group: 0, Seq: 0, Command: 8) CBOR {"bootloader":"MCUboot"}
A 13:22:45.865 [McuMgr] Sending (20 bytes) Header (Version: 1, Op: 0, Flags: 0, Len: 12, Group: 0, Seq: 1, Command: 8) CBOR {"query":"mode"}
V 13:22:45.872 [McuMgr] Writing characteristic da2e7828-fbce-4e01-ae9e-261174997c48 (WRITE COMMAND)
D 13:22:45.876 [McuMgr] gatt.writeCharacteristic(da2e7828-fbce-4e01-ae9e-261174997c48, value=0x0800000C00000108A1657175657279646D6F6465, WRITE COMMAND)
I 13:22:45.893 [McuMgr] Data written to da2e7828-fbce-4e01-ae9e-261174997c48
I 13:22:45.893 Connection parameters updated (interval: 15.0ms, latency: 0, timeout: 5000ms)
I 13:22:45.902 [McuMgr] Connection parameters updated (interval: 15.0ms, latency: 0, timeout: 5000ms)
I 13:22:45.911 [McuMgr] Notification received from da2e7828-fbce-4e01-ae9e-261174997c48, value: (0x) 09-00-00-08-00-00-01-08-BF-64-6D-6F-64-65-03-FF
A 13:22:45.920 [McuMgr] Received Header (Version: 1, Op: 1, Flags: 0, Len: 8, Group: 0, Seq: 1, Command: 8) CBOR {"mode":3}
A 13:22:45.935 [McuMgr] Sending (9 bytes) Header (Version: 1, Op: 0, Flags: 0, Len: 1, Group: 1, Seq: 2, Command: 0) CBOR {}
V 13:22:45.940 [McuMgr] Writing characteristic da2e7828-fbce-4e01-ae9e-261174997c48 (WRITE COMMAND)
D 13:22:45.942 [McuMgr] gatt.writeCharacteristic(da2e7828-fbce-4e01-ae9e-261174997c48, value=0x0800000100010200A0, WRITE COMMAND)
I 13:22:45.962 [McuMgr] Data written to da2e7828-fbce-4e01-ae9e-261174997c48
I 13:22:45.970 [McuMgr] Notification received from da2e7828-fbce-4e01-ae9e-261174997c48, value: (0x) 09-00-00-86-00-01-02-00-BF-66-69-6D-61-67-65-73-9F-BF-64-73-6C-6F-74-00-67-76-65-72-73-69-6F-6E-65-33-2E-30-2E-30-64-68-61-73-68-58-20-A2-38-BF-7E-02-5E-44-EE-4A-D4-37-1A-65-A0-D8-56-75-45-FA-6F-76-08-4B-EC-DC-2F-E6-63-12-E9-73-19-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-FF-FF-6B-73-70-6C-69-74-53-74-61-74-75-73-00-FF
A 13:22:45.974 [McuMgr] Received Header (Version: 1, Op: 1, Flags: 0, Len: 134, Group: 1, Seq: 2, Command: 0) CBOR {"images":[{"slot":0,"version":"3.0.0","hash":"oji/fgJeRO5K1DcaZaDYVnVF+m92CEvs3C/mYxLpcxk=","bootable":true,"pending":false,"confirmed":true,"active":true,"permanent":false}],"splitStatus":0}
V 13:22:45.987 [McuMgr] Uploading firmware...
A 13:22:49.496 [McuMgr] 223448 bytes sent in 3417 ms (65.39 kB/s)
V 13:22:49.546 [McuMgr] New state: TEST
A 13:22:49.551 [McuMgr] Sending (57 bytes) Header (Version: 1, Op: 2, Flags: 0, Len: 49, Group: 1, Seq: 97, Command: 0) CBOR {"confirm":false,"hash":"l+/yJI3ZNSjN49qhsLCpe+P/1SzeC3vUtZnUCIs0b90="}
V 13:22:49.554 [McuMgr] Writing characteristic da2e7828-fbce-4e01-ae9e-261174997c48 (WRITE COMMAND)
D 13:22:49.557 [McuMgr] gatt.writeCharacteristic(da2e7828-fbce-4e01-ae9e-261174997c48, value=0x0A00003100016100A267636F6E6669726DF46468617368582097EFF2248DD93528CDE3DAA1B0B0A97BE3FFD52CDE0B7BD4B599D4088B346FDD, WRITE COMMAND)
I 13:22:49.566 [McuMgr] Data written to da2e7828-fbce-4e01-ae9e-261174997c48
I 13:22:49.597 [McuMgr] Notification received from da2e7828-fbce-4e01-ae9e-261174997c48, value: (0x) 0B-00-00-F4-00-01-61-00-BF-66-69-6D-61-67-65-73-9F-BF-64-73-6C-6F-74-00-67-76-65-72-73-69-6F-6E-65-33-2E-30-2E-30-64-68-61-73-68-58-20-A2-38-BF-7E-02-5E-44-EE-4A-D4-37-1A-65-A0-D8-56-75-45-FA-6F-76-08-4B-EC-DC-2F-E6-63-12-E9-73-19-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-FF-BF-64-73-6C-6F-74-01-67-76-65-72-73-69-6F-6E-65-33-2E-30-2E-30-64-68-61-73-68-58-20-97-EF-F2-24-8D-D9-35-28-CD-E3-DA-A1-B0-B0-A9-7B-E3-FF-D5-2C-DE-0B-7B-D4-B5-99-D4-08-8B-34-6F-DD-68-62-6F-6F-74-61-62-6C-65-F5-67-70-65-6E-64-69-6E-67-F5-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-FF-FF-6B-73-70-6C-69-74-53-74-61-74-75-73-00-FF
A 13:22:49.603 [McuMgr] Received Header (Version: 1, Op: 3, Flags: 0, Len: 244, Group: 1, Seq: 97, Command: 0) CBOR {"images":[{"slot":0,"version":"3.0.0","hash":"oji/fgJeRO5K1DcaZaDYVnVF+m92CEvs3C/mYxLpcxk=","bootable":true,"pending":false,"confirmed":true,"active":true,"permanent":false},{"slot":1,"version":"3.0.0","hash":"l+/yJI3ZNSjN49qhsLCpe+P/1SzeC3vUtZnUCIs0b90=","bootable":true,"pending":true,"confirmed":false,"active":false,"permanent":false}],"splitStatus":0}
V 13:22:49.615 [McuMgr] New state: RESET
A 13:22:49.627 [McuMgr] Sending (9 bytes) Header (Version: 1, Op: 2, Flags: 0, Len: 1, Group: 0, Seq: 98, Command: 5) CBOR {}
V 13:22:49.632 [McuMgr] Writing characteristic da2e7828-fbce-4e01-ae9e-261174997c48 (WRITE COMMAND)
D 13:22:49.635 [McuMgr] gatt.writeCharacteristic(da2e7828-fbce-4e01-ae9e-261174997c48, value=0x0A00000100006205A0, WRITE COMMAND)
I 13:22:49.643 [McuMgr] Data written to da2e7828-fbce-4e01-ae9e-261174997c48
I 13:22:49.675 [McuMgr] Notification received from da2e7828-fbce-4e01-ae9e-261174997c48, value: (0x) 0B-00-00-02-00-00-62-05-BF-FF
A 13:22:49.687 [McuMgr] Received Header (Version: 1, Op: 3, Flags: 0, Len: 2, Group: 0, Seq: 98, Command: 5) CBOR {}
D 13:22:54.915 [Callback] Connection state changed with status: 8 and new state: DISCONNECTED (0)
E 13:22:54.915 Error 8 (0x8): GATT CONN TIMEOUT
I 13:22:54.916 Disconnected
D 13:22:54.917 [McuMgr] [Callback] Connection state changed with status: 8 and new state: 0 (DISCONNECTED)
W 13:22:54.935 [McuMgr] Error: (0x8): GATT CONN TIMEOUT
I 13:22:54.941 [McuMgr] Disconnected
D 13:22:54.956 [McuMgr] gatt.close()
D 13:22:54.968 [Broadcast] Action received: android.bluetooth.device.action.ACL_DISCONNECTED
V 13:22:59.716 [McuMgr] Connecting...
D 13:22:59.727 [McuMgr] gatt = device.connectGatt(autoConnect = false, TRANSPORT_LE, LE 1M)
V 13:22:59.742 [McuMgr] New state: CONFIRM

RE: The state status is Unknown(147) after FOTA DFU on 54L15

Menon — Fri, 21 Feb 2025 15:48:56 GMT

Hello,

Have you tried the solution provided in the Developer Academy course? Does the same issue occur with that application as well? To rule out the possibility that the issue is not coming from the application, I recommend testing the solution and observing the results. Additionally, I suggest collecting logs from the nRF side to get a better understanding of the issue.

Kind Regards,
Abhijith

RE: The state status is Unknown(147) after FOTA DFU on 54L15

LHZ — Thu, 20 Feb 2025 22:48:57 GMT

I don't know if I need open a new thead. Since it has not been replied, I just attched it to my last question.

So, my statement about "The build has been uploaded successfully" was not completely true in my previous question.

Yes, the blinking speed changed and the new build has been uploaded. I also changed the device name each time as a secondary verification. HOWEVER, once i reset or power cycle the DK board, the LED does NOT blink for a short peiord (30-60 seconds ish), then the build was rolled back. Both the device name and blinking speed changed back.

I followed the Nordic Hand-on video tutorial on youtube. Then I verified my setup by with Exercise 5 (FOTA over BLuetooth LOW Energy) from the Nordic Academy. I am using the nRF64L15-DK, and the SDK is 2.9.0.

What could I miss?

Thank you very much