mesh models dfu metadata encode

RE: mesh models dfu metadata encode

Hung Bui — Fri, 04 Aug 2023 12:03:49 GMT

Hi Serhii

A dash is needed between metadata and encode, so it should be

mesh models dfu metadata-encode 2 0 0 0 241236 1 0x71f3267c 1

RE: mesh models dfu metadata encode

Sergnrf — Fri, 04 Aug 2023 11:16:40 GMT

What is wrong with this command?

mesh models dfu metadata encode 2 0 0 0 241236 1 0x71f3267c 1

RE: mesh models dfu metadata encode

Sergnrf — Tue, 01 Aug 2023 14:17:43 GMT

Please add a broader description of all parameters.

RE: mesh models dfu metadata encode

Hung Bui — Tue, 01 Aug 2023 13:55:45 GMT

Hi Serhii,
Could you try:

mesh models dfu metadata-encode <Major> <Minor> <Rev> <BuildNum> <Size> <CoreType> <Hash> <Elems> [<UserData>]

I think it's mistake in the documentation.

RE: mesh models dfu metadata encode

Sergnrf — Mon, 31 Jul 2023 16:24:31 GMT

19:17:03.339 -> mesh models dfu metadata comp-add 0x59 0 0 10 7
19:17:03.339 -> [1;32muart:~$ [mmesh models dfu metadata comp-elem-add 1 4 0 0x0000 0x0002 0xBF42 0xBF44
19:17:20.972 -> [1;32muart:~$ [mmesh models dfu metadata comp-hash-get
19:17:46.469 -> Composition data to be hashed:
19:17:46.469 -> CID: 0x0059
19:17:46.469 -> PID: 0x0000
19:17:46.469 -> VID: 0x0000
19:17:46.469 -> CPRL: 10
19:17:46.469 -> Features: 0x7
19:17:46.469 -> Elem: 1
19:17:46.469 -> NumS: 4
19:17:46.469 -> NumV: 0
19:17:46.469 -> SIG Model ID: 0x0000
19:17:46.469 -> SIG Model ID: 0x0002
19:17:46.469 -> SIG Model ID: 0xbf42
19:17:46.469 -> SIG Model ID: 0xbf44
19:17:46.469 -> Composition data hash: 0x71f3267c
19:17:46.469 -> [1;32muart:~$ [mmesh models dfu metadata encode 2 0 0 0 241236 1 0x71f3267c 1
19:18:04.609 ->
19:18:04.642 -> For a detailed description of the commands and arguments in this shell module,
19:18:04.642 -> please refer to the Zephyr Project documentation online.
19:18:04.642 ->
19:18:04.642 -> [1;31mmetadata unknown command: encode

RE: mesh models dfu metadata encode

Hung Bui — Mon, 31 Jul 2023 12:59:34 GMT

Hi Serhii,

The mesh DFU in nRF Connect SDK is relatively new and it follows the new DFU protocol in the new Mesh specification. So it's quite different from the mesh DFU we had in the nRF5 SDK.

Could you send the whole log when you compose the firmware data ?