Nrf52840 DFU Over thread uses single or dual bank update ??

RE: Nrf52840 DFU Over thread uses single or dual bank update ??

kpyush — Wed, 19 Sep 2018 07:33:34 GMT

currently I am stuck in performing dfu over thread form PC itself. I had successfully performed the DFUfew months ago..but I am not able to reproduce it. I have created new issue https://devzone.nordicsemi.com/support/214105

Any help will be appreciated..

RE: Nrf52840 DFU Over thread uses single or dual bank update ??

Edvin — Wed, 19 Sep 2018 07:20:35 GMT

It seems like the RPi can't open the serial port.

Can you try to add -f to your nrfutil command? That is:

python nordicsemi/__main__.py dfu thread -f -pkg app_dfu_package.zip -p /dev/ttyACM0

Best regards,

Edvin

RE: Nrf52840 DFU Over thread uses single or dual bank update ??

kpyush — Mon, 17 Sep 2018 11:57:51 GMT

Hi,

I tried to update the firmware of thread end devices. I have built OTBR on RPi 3B.

Also I have commented the code which flash firmware in NCP.

When I execute the python nordicsemi/__main__.py dfu thread -pkg app_dfu_package.zip -p /dev/ttyACM0 command, below are the logs:

pi@raspberrypi:~/sources/pc-nrfutil $ python nordicsemi/__main__.py dfu thread -pkg app_dfu_package.zip -p /dev/ttyACM0

Address not specified. Using ff03::1 (all Thread nodes)

Using connectivity board at serial port: /dev/ttyACM0

2018-09-17 17:12:50,133 Couldn't open /dev/ttyACM0

Traceback (most recent call last):

File "/usr/local/lib/python2.7/dist-packages/spinel/stream.py", line 57, in __init__

self.serial = serial.Serial(dev, baudrate)

File "/usr/local/lib/python2.7/dist-packages/serial/serialutil.py", line 240, in __init__

self.open()

File "/usr/local/lib/python2.7/dist-packages/serial/serialposix.py", line 268, in open

raise SerialException(msg.errno, "could not open port {}: {}".format(self._port, msg))

SerialException: [Errno 16] could not open port /dev/ttyACM0: [Errno 16] Device or resource busy: '/dev/ttyACM0'

2018-09-17 17:12:50,149 'StreamSerial' object has no attribute 'serial'

Traceback (most recent call last):

File "nordicsemi/__main__.py", line 976, in thread

transport.open()

File "/home/pi/sources/pc-nrfutil/nordicsemi/thread/tncp.py", line 219, in open

if (self._config[NCPTransport.CFG_KEY_RESET]) and not self._wpan.cmd_reset():

File "/usr/local/lib/python2.7/dist-packages/spinel/codec.py", line 1015, in cmd_reset

self.transact(SPINEL.CMD_RESET, "", SPINEL.HEADER_DEFAULT)

File "/usr/local/lib/python2.7/dist-packages/spinel/codec.py", line 891, in transact

self.stream_tx(pkt)

File "/usr/local/lib/python2.7/dist-packages/spinel/codec.py", line 929, in stream_tx

self.stream.write(pkt)

File "/usr/local/lib/python2.7/dist-packages/spinel/stream.py", line 63, in write

self.serial.write(data)

AttributeError: 'StreamSerial' object has no attribute 'serial'

Traceback (most recent call last):

File "nordicsemi/__main__.py", line 991, in <module>

cli()

File "/usr/local/lib/python2.7/dist-packages/click/core.py", line 722, in __call__

return self.main(*args, **kwargs)

Exception in thread Thread-2:

Traceback (most recent call last):

File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner

self.run()

File "/usr/lib/python2.7/threading.py", line 754, in run

self.__target(*self.__args, **self.__kwargs)

File "/usr/local/lib/python2.7/dist-packages/spinel/codec.py", line 935, in stream_rx

self.rx_pkt = self.hdlc.collect()

File "/usr/local/lib/python2.7/dist-packages/spinel/hdlc.py", line 79, in collect

byte = self.stream.read()

File "/usr/local/lib/python2.7/dist-packages/spinel/stream.py", line 68, in read

pkt = self.serial.read(size)

AttributeError: 'StreamSerial' object has no attribute 'serial'

File "/usr/local/lib/python2.7/dist-packages/click/core.py", line 697, in main

rv = self.invoke(ctx)

File "/usr/local/lib/python2.7/dist-packages/click/core.py", line 1066, in invoke

return _process_result(sub_ctx.command.invoke(sub_ctx))

File "/usr/local/lib/python2.7/dist-packages/click/core.py", line 1066, in invoke

return _process_result(sub_ctx.command.invoke(sub_ctx))

File "/usr/local/lib/python2.7/dist-packages/click/core.py", line 895, in invoke

return ctx.invoke(self.callback, **ctx.params)

File "/usr/local/lib/python2.7/dist-packages/click/core.py", line 535, in invoke

return callback(*args, **kwargs)

File "nordicsemi/__main__.py", line 988, in thread

transport.close()

File "/home/pi/sources/pc-nrfutil/nordicsemi/thread/tncp.py", line 236, in close

self._wpan.cmd_reset()

File "/usr/local/lib/python2.7/dist-packages/spinel/codec.py", line 1015, in cmd_reset

self.transact(SPINEL.CMD_RESET, "", SPINEL.HEADER_DEFAULT)

File "/usr/local/lib/python2.7/dist-packages/spinel/codec.py", line 891, in transact

self.stream_tx(pkt)

File "/usr/local/lib/python2.7/dist-packages/spinel/codec.py", line 929, in stream_tx

self.stream.write(pkt)

File "/usr/local/lib/python2.7/dist-packages/spinel/stream.py", line 63, in write

self.serial.write(data)

AttributeError: 'StreamSerial' object has no attribute 'serial'

As the wpantund service is using the serial port /dev/ttyACM0, I stop the wpantund service manually. Then I executed the python nordicsemi/__main__.py dfu thread -pkg app_dfu_package.zip -p /dev/ttyACM0 command again, below are the logs:

pi@raspberrypi:~/sources/pc-nrfutil $ python nordicsemi/__main__.py dfu thread -pkg app_dfu_package.zip -p /dev/ttyACM0

Address not specified. Using ff03::1 (all Thread nodes)

Using connectivity board at serial port: /dev/ttyACM0

2018-09-17 17:19:32,988 Failed to set property PROP_NET_STACK_UP

Traceback (most recent call last):

File "nordicsemi/__main__.py", line 976, in thread

transport.open()

File "/home/pi/sources/pc-nrfutil/nordicsemi/thread/tncp.py", line 223, in open

if (not self._attach_to_network()):

File "/home/pi/sources/pc-nrfutil/nordicsemi/thread/tncp.py", line 104, in _attach_to_network

self._set_property(*props)

File "/home/pi/sources/pc-nrfutil/nordicsemi/thread/tncp.py", line 88, in _set_property

raise Exception("Failed to set property {}".format(self.__class__._propid_to_str(propid)))

Exception: Failed to set property PROP_NET_STACK_UP

RE: Nrf52840 DFU Over thread uses single or dual bank update ??

Edvin — Mon, 17 Sep 2018 07:48:38 GMT

Hello,

What is the problem when you use nrfutil on the RPi? Are you able to run nrfutil? When you try to perform it, what error does it give, if any?

BR,

Edvin

RE: Nrf52840 DFU Over thread uses single or dual bank update ??

kpyush — Fri, 14 Sep 2018 11:34:33 GMT

I have tried on computer it works fine... in the rpi the issues comes in DFU package transfer while flashing the NCP firmware. That raises another question if I have already NCP flashed with border router then do we need flashing the NCP. I am trying to achieve DFU from Rpi...if not possible from cloud.

RE: Nrf52840 DFU Over thread uses single or dual bank update ??

Edvin — Fri, 14 Sep 2018 10:31:20 GMT

Have you tried it on a computer first? Just to figure out whether the issue is in the RPi setup or the DFU package transfer.

RE: Nrf52840 DFU Over thread uses single or dual bank update ??

kpyush — Fri, 14 Sep 2018 04:43:03 GMT

Thank you for reply .. i am using nrfutil on raspberry pi to perform the DFU over thread.. but unfortunately i am not able to achieve it on Rpi. Please let me know how can I use nrfutil to perform DFU from rpi or cloud. As you have mentioned in the documentation that DFU server can run over Mobile and cloud as well.

RE: Nrf52840 DFU Over thread uses single or dual bank update ??

Edvin — Thu, 13 Sep 2018 13:34:09 GMT

The bootloader in the Thread SDK supports dual bank updates. Look in the file:

nRF5_SDK_for_Thread_and_Zigbee_v1.0.0\examples\thread\dfu\bootloader\pca10055\blank\config\sdk_config.h

There is a define called NRF_DFU_FORCE_DUAL_BANK_APP_UPDATES, initially set to 0. If you set this to 1, then the DFU will not be accepted if there is no room for Dual Banking.

Regarding the power consumption, I am not sure. I don't see a reason why DFU will not work on SEDs (Sleepy End Devices). You have to have a way to enter the bootloader. When it is in bootloader mode, it will not be a sleepy end device, until it either receives a new application (which may be a sleepy end device application, or not), or the bootloader disconnects and times out.

Best regards,

Edvin