SMP OTA using dev board

RE: SMP OTA using dev board

AHaug — Thu, 17 Oct 2024 07:26:04 GMT

Hi,

Yes, I understand what you want to do. There are quite a few changes in configurations that have occured in between v1.8.0 and v2.4.0.

You might be better of using the unofficial sample here instead https://github.com/simon-iversen/ncs_samples/tree/master/central_smp_client_dfu which is based on NCS v2.0.0 instead of NCS v2.4.0 which the first sample I sent you uses.

Kind regards,
Andreas

RE: SMP OTA using dev board

Usama Shafiq — Tue, 15 Oct 2024 04:54:20 GMT

On my server side the OTA process is implemented through App (acts as a client). We have developed an App (client) that uses the SDK and does the OTA of the server. Now we want to mimic the exact same thing through another controller(nrf52840dk as client) instead of App.
My server side is fixed that can't be changed. All I can do is to play around the client side and exactly replicate the process of App into firmware.
Do you get what I exactly want to do?

RE: SMP OTA using dev board

AHaug — Mon, 14 Oct 2024 13:23:54 GMT

Yeah, that will cause issues. The sample works out of box for 2.4.0 for both side of the demo, but it hasn't been tested for v2.4.0 and a server that is v1.8.0.

The best I can suggest is to either migrate the server side (if you're not talking about devices in the field) to a newer version of NCS by following the migration guides here and try again: https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/releases_and_maturity.html

Kind regards,
Andreas

RE: SMP OTA using dev board

Usama Shafiq — Mon, 14 Oct 2024 12:30:13 GMT

One thing worth mentioning is my client side is NCS v2.4.2 and my server side is NCS 1.8.0

RE: SMP OTA using dev board

AHaug — Mon, 14 Oct 2024 12:19:44 GMT

Thank you, I'll see if I can recreate it.

Kind regards;
Andreas

RE: SMP OTA using dev board

Usama Shafiq — Mon, 14 Oct 2024 12:12:47 GMT

Here are the logs (NCS v2.4.2)
Bluetooth initialized
Scanning successfully started
Filters matched. Address: C4:22:CD:xx:xx:xx (random) connectable: no
Connected: C4:22:CD:xx:xx:xx(random)
MTU exchange pending
E: pairing failed (peer reason 0x5)
Security failed: C4:22:CD:xx:xx:xx (random) level 1 err 5
MTU exchange successful
Current MTU: 65
The discovery procedure succeeded
Echo test: 1
Echo response part received, size: 28.
Total response received - decoding
{_"r": "Echo message: 1"}
Echo test: 2
Echo response part received, size: 28.
Total response received - decoding
{_"r": "Echo message: 2"}
Sending DFU Image List command
Sending DFU Image List command
DFU Image List command send error (err: -16)

RE: SMP OTA using dev board

Usama Shafiq — Mon, 14 Oct 2024 12:09:02 GMT

I am using NCS v2.4.2. Will it work?

RE: SMP OTA using dev board

AHaug — Mon, 14 Oct 2024 11:57:55 GMT

The sample is only tested in NCS v2.4.0. Please try again using 2.4.0 and update me if you still see the issue with full device logs and complete steps to recreate.

Kind regards,
Andreas

RE: SMP OTA using dev board

Usama Shafiq — Mon, 14 Oct 2024 11:55:54 GMT

According to the 1st link when I am trying to execute that code I am not getting any response for command image list. but when I send the command again it gives -16 error code which is -EBUSY.

RE: SMP OTA using dev board

AHaug — Mon, 14 Oct 2024 11:51:08 GMT

Hi,

You can have a look at these unofficial samples created by a colleague of mine: https://github.com/hellesvik-nordic/samples_for_nrf_connect_sdk/tree/main/bootloader_samples/client_smp/smp_client_ble

In addition I recommend you have a look at https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-8-bootloaders-and-dfu-fota/

Kind regards,
Andreas