OTA update in mesh

RE: OTA update in mesh

Amanda Hsieh — Fri, 26 Nov 2021 12:40:31 GMT

Hi,

[quote user="Mohsin khan"]Nothing is changed in RTT log [/quote]

Please try to test again without the signing keys.

Please make sure UART is working between your computer and the board, you can test using a UART example.

Here is a similar case that might help.

[quote user="Mohsin khan"]In fact now its empty with i run hex file of blink then erase it after that i try to do all steps but i didn't see anything in RTT logs .[/quote]

Follow this Configuring and performing DFU over Mesh document to program the bootloader again.

[quote user="Mohsin khan"]Is there any issue if this warning comes after connection . [/quote]

It detects that your probe is a J-Link clone, and cannot guarantee the operation correctly. Please contact your provider for the issue.

-Amanda

RE: OTA update in mesh

Mohsin khan — Fri, 26 Nov 2021 11:19:54 GMT

Nothing is changed in RTT log

In fact now its empty with i run hex file of blink then erase it after that i try to do all steps but i didn't see anything in RTT logs .

Is there any issue if this warning comes after connection .

RE: OTA update in mesh

Amanda Hsieh — Fri, 26 Nov 2021 11:12:09 GMT

Good, but I need the RTT log until you get the error (Error is: Failed to establish the connection).

-Amanda

RE: OTA update in mesh

Mohsin khan — Fri, 26 Nov 2021 10:16:55 GMT

00> <t:          3>, main.c,  227, ----- Bluetooth Mesh DFU Example -----
00> <t:       8811>, nrf_mesh_dfu.c,  753, Version info: BL(ver, id): 0x01 0x01 SD: 0x0100
00> <t:       8815>, nrf_mesh_dfu.c,  755, Version info: APP company: 0x20210304 id: 0x0001 version: 0x00000001
00> <t:       8827>, serial_handler_prov.c,  267, Generating encryption keypair...
00> <t:      13608>, main.c,  233, Initialization complete!
00> <t:      18278>, main.c,  254, Enabling serial interface...
00> <t:      18281>, mesh_app_utils.c,   66, Device UUID (raw): 0F2EAF580D3F439FBB24D199F320A8BE
00> <t:      18284>, mesh_app_utils.c,   67, Device UUID : 0F2EAF58-0D3F-439F-BB24-D199F320A8BE
00> <t:      18296>, nrf_mesh_dfu.c,  554,   RADIO TX! SLOT 0, count 15, interval: periodic, handle: FFFE
00> <t:      18300>, nrf_mesh_dfu.c,  593,   SERIAL TX (type: 65534)
00> <t:      18308>, main.c,  262, DFU example started!

These are logs of RTT viewer .

LOG: Connecting to J-Link via USB...
LOG: Device "NRF52840_XXAA" selected.
LOG: InitTarget() start
LOG: InitTarget() end
LOG: Found SW-DP with ID 0x2BA01477
LOG: DPIDR: 0x2BA01477
LOG: CoreSight SoC-400 or earlier
LOG: Scanning AP map to find all available APs
LOG: AP[2]: Stopped AP scan as end of AP map has been reached
LOG: AP[0]: AHB-AP (IDR: 0x24770011)
LOG: AP[1]: JTAG-AP (IDR: 0x02880000)
LOG: Iterating through AP map to find AHB-AP to use
LOG: AP[0]: Core found
LOG: AP[0]: AHB-AP ROM base: 0xE00FF000
LOG: CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)
LOG: Found Cortex-M4 r0p1, Little endian.
LOG: FPUnit: 6 code (BP) slots and 2 literal slots
LOG: CoreSight components:
LOG: ROMTbl[0] @ E00FF000
LOG: [0][0]: E000E000 CID B105E00D PID 000BB00C SCS-M7
LOG: [0][1]: E0001000 CID B105E00D PID 003BB002 DWT
LOG: [0][2]: E0002000 CID B105E00D PID 002BB003 FPB
LOG: [0][3]: E0000000 CID B105E00D PID 003BB001 ITM
LOG: [0][4]: E0040000 CID B105900D PID 000BB9A1 TPIU
LOG: [0][5]: E0041000 CID B105900D PID 000BB925 ETM
LOG: RTT Viewer connected.
LOG: Terminal 0 added.

RE: OTA update in mesh

Amanda Hsieh — Fri, 26 Nov 2021 10:08:04 GMT

Hi,

Those are not the RTT log I'm asking. See Using SEGGER's J-Link RTT viewer to connect via RTT documentation.

-Amanda

RE: OTA update in mesh

Mohsin khan — Fri, 26 Nov 2021 09:59:21 GMT

These are logs from my cmd and rtt

D:\nrf mesh>nrfjprog --program s140_nrf52_7.2.0_softdevice.hex --chiperase
Parsing image file.
Applying system reset.
Verified OK.

D:\nrf mesh>nrfjprog --program mesh_bootloader_serial_gccarmemb_nrf52840_xxAA.hex
Parsing image file.
Applying system reset.
Verified OK.

D:\nrf mesh>nrfjprog --program device_page_nrf52840_xxAA_s140_7.2.0.hex
Parsing image file.
Applying system reset.
Verified OK.

D:\nrf mesh>nrfjprog --program dfu_nrf52840_xxAA_s140_7.2.0.hex
Parsing image file.
Applying system reset.
Verified OK.

D:\nrf mesh>nrfjprog -r
Applying system reset.
Run.

D:\nrf mesh>nrfutil --verbose dfu serial -pkg dfu_test.zip -p COM6 -b 115200 -fc --mesh
Upgrading target on COM6 with DFU package D:\nrf mesh\dfu_test.zip. Flow control is enabled.
Flushing com-port...
Opened com-port
Starting DFU upgrade of type 4, SoftDevice size: 0, bootloader size: 0, application size: 130832
Sending DFU start packet, afterwards we wait for the flash on target to be initialized before continuing.
1: PC -> target: 0502aabbccdd
2: PC -> target: 0502aabbccdd
3: PC -> target: 0502aabbccdd
4: PC -> target: 0502aabbccdd
5: PC -> target: 0502aabbccdd
6: PC -> target: 0502aabbccdd
7: PC -> target: 0502aabbccdd
8: PC -> target: 0502aabbccdd
9: PC -> target: 0502aabbccdd
10: PC -> target: 0502aabbccdd


Failed to upgrade target. Error is: Failed to establish connection

Possible causes:
- bootloader, SoftDevice or application on target does not match the requirements in the DFU package.
- baud rate or flow control is not the same as in the target bootloader.
- target is not in DFU mode. If using the SDK examples, press Button 4 and RESET and release both to enter DFU mode.
- if the error is ERROR_BUSY at the beginning of the DFU process,increase the value of PAGE_ERASE_TIME_MAX by few milliseconds.
Closing serial port...

###RTT Client: Connecting to J-Link RTT Server via localhost:19021 ....................................................................................................................................................
###RTT Client: Connected.

SEGGER J-Link V7.58c - Real time terminal output
SEGGER J-Link ARM V9.7, SN=59768885
Process: jlinkarm_nrf_worker.exe

###RTT Client: Connection lost. Going to reconnect.
###RTT Client: Connecting to J-Link RTT Server via localhost:19021 ...............................................
###RTT Client: Connected.

SEGGER J-Link V7.58c - Real time terminal output
SEGGER J-Link ARM V9.7, SN=59768885
Process: jlinkarm_nrf_worker.exe

###RTT Client: Connection lost. Going to reconnect.
###RTT Client: Connecting to J-Link RTT Server via localhost:19021 ................................
###RTT Client: Connected.

SEGGER J-Link V7.58c - Real time terminal output
SEGGER J-Link ARM V9.7, SN=59768885
Process: jlinkarm_nrf_worker.exe

###RTT Client: Connection lost. Going to reconnect.
###RTT Client: Connecting to J-Link RTT Server via localhost:19021 ..............................
###RTT Client: Connected.

SEGGER J-Link V7.58c - Real time terminal output
SEGGER J-Link ARM V9.7, SN=59768885
Process: jlinkarm_nrf_worker.exe

###RTT Client: Connection lost. Going to reconnect.
###RTT Client: Connecting to J-Link RTT Server via localhost:19021 ....................
###RTT Client: Connected.

SEGGER J-Link V7.58c - Real time terminal output
SEGGER J-Link ARM V9.7, SN=59768885
Process: jlinkarm_nrf_worker.exe

###RTT Client: Connection lost. Going to reconnect.
###RTT Client: Connecting to J-Link RTT Server via localhost:19021 .............................................................................................................................................................................................................................................

RE: OTA update in mesh

Amanda Hsieh — Fri, 26 Nov 2021 09:43:17 GMT

You would need to connect with Jlink and get RTT log via Jlink Viewer. Also, see my previous reply.

Please try testing without using any key. Just to simplify the testing.
Please make sure COM7 is the correct comport and in your code NRF_MESH_SERIAL_ENABLE is set to 1. 
Please print out RTT log from the DFU firmware, and check if mesh_evt_handler() is called for any DFU event.

-Amanda

RE: OTA update in mesh

Mohsin khan — Fri, 26 Nov 2021 09:16:58 GMT

It takes too much time to respond to new questions i want to solve problem immediately .

[quote userid="77782" url="~/f/nordic-q-a/81676/ota-update-in-mesh/340842#340842"]The RTT log from the DFU firmware might help provide clues[/quote]

How to check RTT log from DFU firmware .

RE: OTA update in mesh

Amanda Hsieh — Fri, 26 Nov 2021 08:59:43 GMT

Hi,

[quote user="Mohsin khan"]Can you please tell me steps to follow to do DFU on waveshare eval kit of NRF52840 .[/quote]

The waveshare eval kit of NRF52840 is not developed by Nordic, and I don't have their board to reproduce it. The RTT log from the DFU firmware might help provide clues. Please create a new support case. The latest issue is away from the original scope.

[quote user="Mohsin khan"]tell me one more thing when we are trying to do on eval board so we have to program from jlink or USB board . [/quote]

Not sure the waveshare eval kit has the onboard debugger or not, but I guess not. On the NRF52840 Eval Kit User Manual page.6, there is a 4PIN SWD debugging interface: for connecting ARM Debugger to program/debug. Seems you need an ARM Debugger (Jlink) to program.

-Amanda

RE: OTA update in mesh

Mohsin khan — Fri, 26 Nov 2021 05:56:10 GMT

Hello

I want to clear one thing i have successfully done DFU with development kit but i want to do this with nrf52840 eval kit waveshare but when i try to do on that its giving me same error which i have showed you . Can you please tell me steps to follow to do DFU on waveshare eval kit of NRF52840 . I am attaching some pictures to show you my board . And tell me one more thing when we are trying to do on eval board so we have to program from jlink or USB board .

RE: OTA update in mesh

Amanda Hsieh — Wed, 24 Nov 2021 14:17:19 GMT

Hi,

Please try testing without using any key. Just to simplify the testing.

Please make sure COM7 is the correct comport and in your code NRF_MESH_SERIAL_ENABLE is set to 1.

Please print out RTT log from the DFU firmware, and check if mesh_evt_handler() is called for any DFU event.

-Amanda

RE: OTA update in mesh

Mohsin khan — Wed, 24 Nov 2021 06:33:18 GMT

Hello Amanda,

sorry for being late i am getting error using the file in the link please tell me where the issue is

D:\nrf mesh>nrfutilmesh --verbose dfu serial -pkg dfu_test.zip -p COM7 -b 115200 -fc --mesh
Upgrading target on COM7 with DFU package D:\nrf mesh\dfu_test.zip. Flow control is enabled.
Flushing com-port...
Opened com-port
Starting DFU upgrade of type 4, SoftDevice size: 0, bootloader size: 0, application size: 130832
Sending DFU start packet, afterwards we wait for the flash on target to be initialized before continuing.
1: PC -> target: 0502aabbccdd
2: PC -> target: 0502aabbccdd
3: PC -> target: 0502aabbccdd
4: PC -> target: 0502aabbccdd
5: PC -> target: 0502aabbccdd
6: PC -> target: 0502aabbccdd
7: PC -> target: 0502aabbccdd
8: PC -> target: 0502aabbccdd
9: PC -> target: 0502aabbccdd
10: PC -> target: 0502aabbccdd


Failed to upgrade target. Error is: Failed to establish connection

Possible causes:
- bootloader, SoftDevice or application on target does not match the requirements in the DFU package.
- baud rate or flow control is not the same as in the target bootloader.
- target is not in DFU mode. If using the SDK examples, press Button 4 and RESET and release both to enter DFU mode.
- if the error is ERROR_BUSY at the beginning of the DFU process,increase the value of PAGE_ERASE_TIME_MAX by few milliseconds.
Closing serial port...

D:\nrf mesh>nrfutilmesh --verbose dfu serial -pkg dfu_test.zip -p COM7 -b 115200 -fc --mesh
Upgrading target on COM7 with DFU package D:\nrf mesh\dfu_test.zip. Flow control is enabled.
Flushing com-port...
Opened com-port
Starting DFU upgrade of type 4, SoftDevice size: 0, bootloader size: 0, application size: 130832
Sending DFU start packet, afterwards we wait for the flash on target to be initialized before continuing.
1: PC -> target: 0502aabbccdd


Failed to upgrade target. Error is: WriteFile failed (WindowsError(22, 'The device does not recognize the command.'))

Possible causes:
- bootloader, SoftDevice or application on target does not match the requirements in the DFU package.
- baud rate or flow control is not the same as in the target bootloader.
- target is not in DFU mode. If using the SDK examples, press Button 4 and RESET and release both to enter DFU mode.
- if the error is ERROR_BUSY at the beginning of the DFU process,increase the value of PAGE_ERASE_TIME_MAX by few milliseconds.
Closing serial port...

D:\nrf mesh>nrfutilmesh --verbose dfu serial -pkg dfu_test.zip -p COM7 -b 115200 -fc --mesh
Upgrading target on COM7 with DFU package D:\nrf mesh\dfu_test.zip. Flow control is enabled.
Flushing com-port...
Opened com-port
Starting DFU upgrade of type 4, SoftDevice size: 0, bootloader size: 0, application size: 130832
Sending DFU start packet, afterwards we wait for the flash on target to be initialized before continuing.
1: PC -> target: 0502aabbccdd
2: PC -> target: 0502aabbccdd
3: PC -> target: 0502aabbccdd
4: PC -> target: 0502aabbccdd
5: PC -> target: 0502aabbccdd
6: PC -> target: 0502aabbccdd
7: PC -> target: 0502aabbccdd
8: PC -> target: 0502aabbccdd
9: PC -> target: 0502aabbccdd
10: PC -> target: 0502aabbccdd


Failed to upgrade target. Error is: Failed to establish connection

Possible causes:
- bootloader, SoftDevice or application on target does not match the requirements in the DFU package.
- baud rate or flow control is not the same as in the target bootloader.
- target is not in DFU mode. If using the SDK examples, press Button 4 and RESET and release both to enter DFU mode.
- if the error is ERROR_BUSY at the beginning of the DFU process,increase the value of PAGE_ERASE_TIME_MAX by few milliseconds.
Closing serial port...

RE: OTA update in mesh

Amanda Hsieh — Tue, 16 Nov 2021 08:25:45 GMT

Hi,

Have a look at this post https://devzone.nordicsemi.com/f/nordic-q-a/72479/configuring-and-performing-dfu-over-mesh , and test the file provided by my colleague.

-Amanda

RE: OTA update in mesh

Mohsin khan — Mon, 15 Nov 2021 13:05:02 GMT

Microsoft Windows [Version 10.0.19042.1288]
(c) Microsoft Corporation. All rights reserved.

C:\Users\Mohsin khan>cd ..

C:\Users>d:

D:\>cd nrf mesh]
The system cannot find the path specified.

D:\>cd nrf mesh

D:\nrf mesh>nrfutilmesh dfu serial -pkg dfu_test.zip -p COM7 -b 115200 -fc --mesh
Upgrading target on COM7 with DFU package D:\nrf mesh\dfu_test.zip. Flow control is enabled.


Failed to upgrade target. Error is: Failed to establish connection

Possible causes:
- bootloader, SoftDevice or application on target does not match the requirements in the DFU package.
- baud rate or flow control is not the same as in the target bootloader.
- target is not in DFU mode. If using the SDK examples, press Button 4 and RESET and release both to enter DFU mode.
- if the error is ERROR_BUSY at the beginning of the DFU process,increase the value of PAGE_ERASE_TIME_MAX by few milliseconds.

D:\nrf mesh>nrfutilmesh keys --gen-key private.key
Generated key at: private.key

D:\nrf mesh>nrfutilmesh keys --show-vk hex private.key
Verification key Qx: 714f113b75c0c50891da361d1f1968d5fe2a5bec49dbebce139791c2a8fa7f09
Verification key Qy: beb8a06b430a2c1ab0f6d5caef9dbdc31b1480aec0035ee075f1f95e0ab39848

D:\nrf mesh>nrfutilmesh dfu --help
Usage: nrfutilmesh dfu [OPTIONS] COMMAND [ARGS]...

  This set of commands support Nordic DFU OTA package generation for
  distribution to applications and serial DFU.

Options:
  --help  Show this message and exit.

Commands:
  genpkg  Generate a package for distribution to Apps supporting Nordic DFU
          OTA

  serial  Program a device with bootloader that support serial DFU

D:\nrf mesh>nrfutilmesh dfu genpkg --help
Usage: nrfutilmesh dfu genpkg [OPTIONS] ZIPFILE

  Generate a zipfile package for distribution to Apps supporting Nordic DFU
  OTA. The application, bootloader and softdevice files are converted to
  .bin if it is a .hex file. For more information on the generated init
  packet see:
  http://developer.nordicsemi.com/nRF51_SDK/doc/7.2.0/s110/html/a00065.html

Options:
  --application TEXT              The application firmware file
  --company-id INT OR NONE        Company ID for mesh-application. Must either
                                  be a Bluetooth SIG assigned company ID (see
                                  https://www.bluetooth.com/specifications
                                  /assigned-numbers/company-identifiers for
                                  more information), or a random number
                                  between 65535 and 4294967295. If a random
                                  number is chosen, it is recommended to not
                                  use the "lazy" approach of selecting an easy
                                  number, as this increases the risk of
                                  namespace collisions for the app-IDs. It is
                                  also recommended to use the same company-ID
                                  for all your applications.

  --application-id INT OR NONE    Mesh application ID, default: 0x0000
  --application-version INT OR NONE
                                  Application version, default: 0xFFFFFFFF
  --bootloader-id INT OR NONE     Mesh bootloader id, default: 0xFF00
  --bootloader TEXT               The bootloader firmware file
  --dev-revision INT OR NONE      Device revision, default: 0xFFFF
  --dev-type INT OR NONE          Device type, default: 0xFFFF
  --dfu-ver FLOAT                 DFU packet version to use, default: 0.5
  --sd-req TEXT OR NONE           SoftDevice requirement. A list of SoftDevice
                                  versions (1 or more)of which one is required
                                  to be present on the target device.Example:
                                  --sd-req 0x4F,0x5A. Default: 0xFFFE.

  --softdevice TEXT               The SoftDevice firmware file
  --key-file FILE                 Signing key (pem fomat)
  --mesh                          Generate a package targeting Mesh-DFU
  --help                          Show this message and exit.

D:\nrf mesh>nrfutilmesh dfu genpkg --application bin/blinky/blinky_nrf52840_xxAA_s140_7.2.0.hex --company-id 0x00000059 --application-id 1 --application-version 1 --key-file private.key --sd-req 0x0101 --mesh dfu_test.zip
Key file was given, setting DFU version to 0.8
Traceback (most recent call last):
  File "C:\Python27\Scripts\nrfutilmesh-script.py", line 11, in <module>
    load_entry_point('nrfutil==0.3.0.0', 'console_scripts', 'nrfutil')()
  File "C:\Python27\lib\site-packages\click\core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "C:\Python27\lib\site-packages\click\core.py", line 782, in main
    rv = self.invoke(ctx)
  File "C:\Python27\lib\site-packages\click\core.py", line 1259, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "C:\Python27\lib\site-packages\click\core.py", line 1259, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "C:\Python27\lib\site-packages\click\core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "C:\Python27\lib\site-packages\click\core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "c:\python27\lib\site-packages\nrfutil-0.3.0.0-py2.7.egg\nordicsemi\__main__.py", line 276, in genpkg
    package.generate_package(zipfile_path)
  File "c:\python27\lib\site-packages\nrfutil-0.3.0.0-py2.7.egg\nordicsemi\dfu\package.py", line 212, in generate_package
    Package.normalize_firmware_to_bin(work_directory, firmware[FirmwareKeys.FIRMWARE_FILENAME])
  File "c:\python27\lib\site-packages\nrfutil-0.3.0.0-py2.7.egg\nordicsemi\dfu\package.py", line 366, in normalize_firmware_to_bin
    temp.tobinfile(new_filepath)
  File "c:\python27\lib\site-packages\nrfutil-0.3.0.0-py2.7.egg\nordicsemi\dfu\nrfhex.py", line 162, in tobinfile
    super(nRFHex, self).tobinfile(fobj, start=start_address, size=size)
  File "c:\python27\lib\site-packages\nrfutil-0.3.0.0-py2.7.egg\nordicsemi\dfu\intelhex\__init__.py", line 401, in tobinfile
    fobj.write(self._tobinstr_really(start, end, pad, size))
  File "c:\python27\lib\site-packages\nrfutil-0.3.0.0-py2.7.egg\nordicsemi\dfu\intelhex\__init__.py", line 373, in _tobinstr_really
    return asstr(self._tobinarray_really(start, end, pad, size).tostring())
  File "c:\python27\lib\site-packages\nrfutil-0.3.0.0-py2.7.egg\nordicsemi\dfu\intelhex\__init__.py", line 342, in _tobinarray_really
    raise ValueError("tobinarray: wrong value for size")
ValueError: tobinarray: wrong value for size

So these are all code which i try to run with nrfutilmesh its version is

nrfutil version 0.3.0.0

Right now its not making the packge

I am new to nrf mesh please help me out of this

my nrf52 version is 17.0.2

RE: OTA update in mesh

Amanda Hsieh — Mon, 15 Nov 2021 12:03:20 GMT

Hi,

What does the update package include SD+BL+APP?

Please post the command you are using and provide the log from the device.

-Amanda