Hi,
Currently, I know that OTA updates for the nRF5340 can be performed using Device Manager and the nRF Connect mobile application. However, if using a PC, is it possible to achieve the same functionality via the command line?
Thanks!!
Mike
Hi,
Currently, I know that OTA updates for the nRF5340 can be performed using Device Manager and the nRF Connect mobile application. However, if using a PC, is it possible to achieve the same functionality via the command line?
Thanks!!
Mike
Hi Mike,
Is it a Windows PC? There has not been BLE support for this OS in the past, but it looks like that may have changed with the introduction of the smpmgr tool added here: https://github.com/zephyrproject-rtos/zephyr/issues/70871
- https://github.com/intercreate/smpmgr/releases
Best regards,
Vidar
Hi Vidar,
Yes, that’s correct. I am trying to run this on a Windows PC.
I have already installed the smpmgr tool (version 0.17.0) on my Windows PC and attempted to perform FOTA on my nRF5340 device.
However, I encountered the following issue. The error logs are shown below.
C:\Users\user>smpmgr --ble E8:B8:C3:0E:CC:23 image upload C:\Users\user\Desktop\Mike\p1_v1.1.2_32M_12pF_dfu_application.zip
[08:48:32] ERROR Inspection of FW image failed - image_management:187 image_management.py:187
╭─────────────────── Traceback (most recent call last) ────────────────────╮
│ C:\Users\user\AppData\Local\Programs\Python\Python312\Lib\site-pack │
│ ages\smpmgr\image_management.py:184 in upload │
│ │
│ 181 │ """Upload a FW image.""" │
│ 182 │ │
│ 183 │ try: │
│ ❱ 184 │ │ image_info = ImageInfo.load_file(str(file)) │
│ 185 │ │ logger.info(str(image_info)) │
│ 186 │ except Exception: │
│ 187 │ │ logger.exception("Inspection of FW image failed") │
│ │
│ C:\Users\user\AppData\Local\Programs\Python\Python312\Lib\site-pack │
│ ages\smpclient\mcuboot.py:326 in load_file │
│ │
│ 323 │ │ │ │ raise MCUBootImageError(f"hex2bin() ret: {ret}") │
│ 324 │ │ │
│ 325 │ │ f.seek(0) # move to the start of the image │
│ ❱ 326 │ │ image_header = ImageHeader.load_from(f) │
│ 327 │ │ │
│ 328 │ │ tlv_offset = image_header.hdr_size + image_header.img_size │
│ 329 │
│ │
│ C:\Users\user\AppData\Local\Programs\Python\Python312\Lib\site-pack │
│ ages\smpclient\mcuboot.py:223 in load_from │
│ │
│ 220 │ @staticmethod │
│ 221 │ def load_from(file: BytesIO | BufferedReader) -> 'ImageHeader' │
│ 222 │ │ """Load an `ImageHeader` from an open file.""" │
│ ❱ 223 │ │ return ImageHeader.loads(file.read(IMAGE_HEADER_STRUCT.siz │
│ 224 │ │
│ 225 │ @staticmethod │
│ 226 │ def load_file(path: str) -> 'ImageHeader': │
│ │
│ C:\Users\user\AppData\Local\Programs\Python\Python312\Lib\site-pack │
│ ages\smpclient\mcuboot.py:205 in loads │
│ │
│ 202 │ │ │ flags, │
│ 203 │ │ │ *ver, │
│ 204 │ │ ) = IMAGE_HEADER_STRUCT.unpack(data) │
│ ❱ 205 │ │ return ImageHeader( │
│ 206 │ │ │ magic=magic, │
│ 207 │ │ │ load_addr=load_addr, │
│ 208 │ │ │ hdr_size=hdr_size, │
│ │
│ C:\Users\user\AppData\Local\Programs\Python\Python312\Lib\site-pack │
│ ages\pydantic\_internal\_dataclasses.py:121 in __init__ │
│ │
│ 118 │ def __init__(__dataclass_self__: PydanticDataclass, *args: Any │
│ None: │
│ 119 │ │ __tracebackhide__ = True │
│ 120 │ │ s = __dataclass_self__ │
│ ❱ 121 │ │ s.__pydantic_validator__.validate_python(ArgsKwargs(args, │
│ self_instance=s) │
│ 122 │ │
│ 123 │ __init__.__qualname__ = f'{cls.__qualname__}.__init__' │
│ 124 │
│ │
│ C:\Users\user\AppData\Local\Programs\Python\Python312\Lib\site-pack │
│ ages\smpclient\mcuboot.py:218 in __post_init__ │
│ │
│ 215 │ def __post_init__(self) -> None: │
│ 216 │ │ """Do initial validation of the header.""" │
│ 217 │ │ if self.magic != IMAGE_MAGIC: │
│ ❱ 218 │ │ │ raise MCUBootImageError(f"Magic is {hex(self.magic)}, │
│ {hex(IMAGE_MAGIC)}") │
│ 219 │ │
│ 220 │ @staticmethod │
│ 221 │ def load_from(file: BytesIO | BufferedReader) -> 'ImageHeader' │
╰──────────────────────────────────────────────────────────────────────────╯
MCUBootImageError: Magic is 0x4034b50, expected 0x96f3b83d
C:\Users\user>
I am not sure whether I am using the smpmgr tool correctly.
Thanks!!
Mike
Hi Vidar,
So on a Linux PC, your team has tested that using mcumgr to update the nRF5340 works reliably. However, mcumgr cannot be used on a Windows PC. Is my understanding correct?
Thanks!!
Mike
Hi Mike,
Yes, mcumgr BLE transport is not supported on Windows. On linux it works ok, but it does have some reliability issues and we are looking to replace it.
Hi Vidar,
For the Windows PC side, there is currently no command-line tool that you have tested and can recommend for use. Also, unlike the nRF52 series, Nordic does not provide a tool such as "nrfutil" for performing OTA updates, correct?
If we exclude command-line tools, does Nordic provide any tools that can be used to update the nRF5340?
Thanks!!
Mike
Hi Mike,
Correct, we currently do not offer a command line tool for BLE dfu on Windows.
If you know a bit of python, you can code a command line tool with the smpclient python lib in very little time. BTDT. Supports BTLE transpport in windows (via bleak).
Python code can be compiled into an exe file for distribution - target PC does not need a python install. The only snag here is a hidden import in bleak, which makes the command line for pyinstaller a bit more difficult.
If you know a bit of python, you can code a command line tool with the smpclient python lib in very little time. BTDT. Supports BTLE transpport in windows (via bleak).
Python code can be compiled into an exe file for distribution - target PC does not need a python install. The only snag here is a hidden import in bleak, which makes the command line for pyinstaller a bit more difficult.
Hi Turbo,
would you mind sharing some sample code examples? Thank you very much.
Ｍike
smpmgr which was suggested initially in this thread is using the smpclient library, but it failed to parse the image trailer when it included protected TLVs so it seems like this library may have some limitations still?
Hi Vidar,
may I ask which type of image file (application.signed.bin or dfu_application.zip) I should use when using the mcumgr tool?
Thanks!!
Mike
Hi Mike,
The zip package format is only recognised by Nordic tools. For mcumgr you have to pass the binary file. application.signed.bin in this case.
Best regards,
Vidar
Hi Vidar,
I am currently using Ubuntu 24.04.3 to perform nRF5340 DFU testing with mcumgr, but I have encountered an issue at the very beginning.
$ mcumgr --conntype ble --name 'Test 3116' echo hello Error: Failed to connect to peer after 10s
It seems that I am unable to establish a connection with my device using mcumgr.
However, I can successfully discover the device using bluetoothctl, and DFU works normally when using nRF Device Manager.
Could you please provide some suggestions or guidance on what might be causing this issue?
Thanks!!
Mike
