FUOTA(Firmware update over the air) of Nordic controller NRF52840 using Azure as host.

RE: FUOTA(Firmware update over the air) of Nordic controller NRF52840 using Azure as host.

Einar Thorsrud — Thu, 24 Sep 2020 14:22:19 GMT

Hi,

Nordic does not provide a ready made example, nor do I have any. There are several threads discussing this before so you could look on this forum, for instance at this post, which has an unofficial example.

RE: FUOTA(Firmware update over the air) of Nordic controller NRF52840 using Azure as host.

Abhishek8585 — Thu, 24 Sep 2020 11:19:09 GMT

Hi ,

I went through the links above but they don't look of much help , can you please give some more details on how to proceed after writing the FW on flash.

We are using SDK v17 and chip nrf52840 .

Any help would be nice.

thanks .

RE: FUOTA(Firmware update over the air) of Nordic controller NRF52840 using Azure as host.

Einar Thorsrud — Wed, 23 Sep 2020 11:59:56 GMT

I see. There could be another issue. Referring to dfu_transport_serial.py and this code:

    def __ensure_bootloader(self):
        lister = DeviceLister()

        device = None
        start = datetime.now()
        while not device and datetime.now() - start < timedelta(seconds=self.timeout):
            time.sleep(0.5)
            device = lister.get_device(com=self.com_port)

        if device:
            device_serial_number = device.serial_number

            if not self.__is_device_in_bootloader_mode(device):
                retry_count = 10
                wait_time_ms = 500

                trigger = DFUTrigger()
                try:
                    trigger.enter_bootloader_mode(device)
                    logger.info("Serial: DFU bootloader was triggered")
                except NordicSemiException as err:
                    logger.error(err)


                for checks in range(retry_count):
                    logger.info("Serial: Waiting {} ms for device to enter bootloader {}/{} time"\
                    .format(500, checks + 1, retry_count))

                    time.sleep(wait_time_ms / 1000.0)

                    device = lister.get_device(serial_number=device_serial_number)
                    if self.__is_device_in_bootloader_mode(device):
                        self.com_port = device.get_first_available_com_port()
                        break

                trigger.clean()
            if not self.__is_device_in_bootloader_mode(device):
                logger.info("Serial: Device is either not in bootloader mode, or using an unsupported bootloader.")

    def __is_device_in_bootloader_mode(self, device):
        if not device:
            return False

        #  Return true if nrf bootloader or Jlink interface detected.
        return ((device.vendor_id.lower() == '1915' and device.product_id.lower() == '521f') # nRF52 SDFU USB
             or (device.vendor_id.lower() == '1366' and device.product_id.lower() == '0105') # JLink CDC UART Port
             or (device.vendor_id.lower() == '1366' and device.product_id.lower() == '1015'))# JLink CDC UART Port (MSD)

You can see that nrfutil looks at the USB vendor ID to check if the device is in DFU mode, and if not it attempts to trigger DFU mode (that only works via the nRF52840's USB interface though). If you are not using a J-Link debugger as USB-UART bridge nrfutil will assume the device is not in DFU mode. So you either need to use a different debug probe, or (probably more relevant), modify __is_device_in_bootloader_mode.

RE: FUOTA(Firmware update over the air) of Nordic controller NRF52840 using Azure as host.

rajAsthana — Tue, 22 Sep 2020 16:49:36 GMT

Hi Einar,

>> I am uploading installSDKdirectory\examples\dfu\secure_bootloader\pca10056_uart this code to my nrf52 device, After uploading this code led 4 is continuously on.

>>UART communication is working well in normal condition without bootloader.

>>yes i configured the bootloader UART in the same way as the application.

RE: FUOTA(Firmware update over the air) of Nordic controller NRF52840 using Azure as host.

Einar Thorsrud — Tue, 22 Sep 2020 13:16:25 GMT

Hi,

There may be an issue with nrfutil, as you should not normally get "No trigger interface found" for serial DFU, as that is USB specific (where there is a USB DFU trigger mechanism). I do not believe that is the root cause of the problem, though. It looks like there is communication issues, so I wonder if the nRF device is in bootloader/DFU mode?

Can you confirm that the nRF is in bootloader mode, for instance using some leds in the bootloader or also using the debug bootloader with RTT logging?
Can you confirm that the UART communication is working normally, when not in the bootloader, so that we know that the HW configuration and USB-UART bridge etc. is working?
Have you configured the bootloader UART in the same way as the application where you have (hopefully) verified that the setup works? (specifically the pin assignments and baud rate in sdk_config.h, which should be the same in the bootloader and application).

RE: FUOTA(Firmware update over the air) of Nordic controller NRF52840 using Azure as host.

rajAsthana — Tue, 22 Sep 2020 11:04:40 GMT

Hi Einar ,

As suggested in the link I disabled the fc(flowcontrol), But still I am facing the same issue, Below is the command & log I am getting atfer issuing command for serial DFU:

Command issued:

nrfutil dfu serial -pkg hrs_application_s140.zip -p COM19 -b 9600 -fc 0

-----------------------------LOG_START--------------------------------

2020-09-22 03:33:13,686 No trigger interface found for device with serial number: 6&2d471516&0&4, Product ID: 0x7523 and Vendor ID: 0x1A86

Traceback (most recent call last):
File "c:\users\raj\appdata\local\programs\python\python38-32\lib\runpy.py", line 194, in _run_module_as_main
return _run_code(code, main_globals, None,
File "c:\users\raj\appdata\local\programs\python\python38-32\lib\runpy.py", line 87, in _run_code
exec(code, run_globals)
File "C:\Users\raj\AppData\Local\Programs\Python\Python38-32\Scripts\nrfutil.exe\__main__.py", line 7, in <module>
File "c:\users\raj\appdata\local\programs\python\python38-32\lib\site-packages\click\core.py", line 829, in __call__
return self.main(*args, **kwargs)
File "c:\users\raj\appdata\local\programs\python\python38-32\lib\site-packages\click\core.py", line 782, in main
rv = self.invoke(ctx)
File "c:\users\raj\appdata\local\programs\python\python38-32\lib\site-packages\click\core.py", line 1259, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "c:\users\raj\appdata\local\programs\python\python38-32\lib\site-packages\click\core.py", line 1259, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "c:\users\raj\appdata\local\programs\python\python38-32\lib\site-packages\click\core.py", line 1066, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "c:\users\raj\appdata\local\programs\python\python38-32\lib\site-packages\click\core.py", line 610, in invoke
return callback(*args, **kwargs)
File "c:\users\raj\appdata\local\programs\python\python38-32\lib\site-packages\nordicsemi\__main__.py", line 1055, in serial
do_serial(package, port, connect_delay, flow_control, packet_receipt_notification, baud_rate, serial_number, True,
File "c:\users\raj\appdata\local\programs\python\python38-32\lib\site-packages\nordicsemi\__main__.py", line 970, in do_serial
dfu.dfu_send_images()
File "c:\users\raj\appdata\local\programs\python\python38-32\lib\site-packages\nordicsemi\dfu\dfu.py", line 127, in dfu_send_images
self._dfu_send_image(self.manifest.application)
File "c:\users\raj\appdata\local\programs\python\python38-32\lib\site-packages\nordicsemi\dfu\dfu.py", line 88, in _dfu_send_image
self.dfu_transport.open()
File "c:\users\raj\appdata\local\programs\python\python38-32\lib\site-packages\nordicsemi\dfu\dfu_transport_serial.py", line 214, in open
raise NordicSemiException("No ping response after opening COM port")
pc_ble_driver_py.exceptions.NordicSemiException: No ping response after opening COM port

-------------------------- LOG_END --------------------------------

For reference I have attached my hardware connections diagram & snapshot of Device Manager on my pc.

I am using USB to TTL convertor to connect my board to my PC & the com generated is COM19,Connection details are listed below

Board (GND) <---> USB to TTL convertor (GND) Brown wire

Board(Tx(pin no 6)) <---> USB to TTL convertor (RX) Red wire

Board(Rx(pin no 8)) <---> USB to TTL convertor (TX) Blue wire

RE: FUOTA(Firmware update over the air) of Nordic controller NRF52840 using Azure as host.

Einar Thorsrud — Tue, 22 Sep 2020 09:00:22 GMT

Hi Raj,

There is some communication error, though it could be several things. You could try to change the flow control configuration and see if that helps, as suggested here. If that does not work, could you try to verify that the device is in DFU mode? One good way to check this (and other DFU problems) is to use a debug bootlaoder build with RTT logging, and observe the RTT log.

RE: FUOTA(Firmware update over the air) of Nordic controller NRF52840 using Azure as host.

rajAsthana — Tue, 22 Sep 2020 05:46:39 GMT

Hi Einar

I am trying to perform DFU over serial UART of my board NRF52840.

whenever I am giving the command to perform serial DFU using nrfutil, I got the error given below:

2020-09-21 22:39:52,824 No trigger interface found for device with serial number: 6&2d471516&0&4, Product ID: 0x7523 and Vendor ID: 0x1A86

The command I isuued to for serial DFU is mentioned below:

nrfutil dfu serial -pkg hrs_application_s140.zip --port COM19 -b 115200

Thanks

Raj

RE: FUOTA(Firmware update over the air) of Nordic controller NRF52840 using Azure as host.

Einar Thorsrud — Fri, 18 Sep 2020 11:08:55 GMT

Hi,

[quote user="Abhishek8585"]But can i write a file in flash at a particular address?[/quote]

Yes, as long as you have unused flash space you can write to it as you like.

[quote user="Abhishek8585"]If possible after that i can instruct DFU module to start FW update using it?[/quote]

Yes. This is what is often referred to as background DFU in this forum. There are no official examples for it though, but the IoT documentation in older SDKs (up to SDK 16) describes one possible way to do it, and you can find several threads about it on DevZone.

RE: FUOTA(Firmware update over the air) of Nordic controller NRF52840 using Azure as host.

Abhishek8585 — Thu, 17 Sep 2020 14:04:47 GMT

Hi,

But can i write a file in flash at a particular address?

If possible after that i can instruct DFU module to start FW update using it?

ty ..

RE: FUOTA(Firmware update over the air) of Nordic controller NRF52840 using Azure as host.

Einar Thorsrud — Thu, 17 Sep 2020 13:18:52 GMT

Nordic does not provide anything like that, unfortunately. I suggest you refer to what is there in the SDK and accompanying tools and see how that can be implemented for your needs.

RE: FUOTA(Firmware update over the air) of Nordic controller NRF52840 using Azure as host.

Abhishek8585 — Thu, 17 Sep 2020 13:15:51 GMT

Hi Einar ,

If i have some REST API through which i can download the firmware file on nordic52840 , can i perform update after that ?

Thanks

RE: FUOTA(Firmware update over the air) of Nordic controller NRF52840 using Azure as host.

Einar Thorsrud — Thu, 17 Sep 2020 12:43:00 GMT

Hi,

Nordic provides DFU solutions for the nRF52 devices, but not all the way up to the cloud. If you are using the nRF5 SDK, then you should look at the bootloader example and related DFU documentation. This and accompanying tools handles the upgrade on the nRF side, as well as image generation and upgrades from mobile phones or PC. But it is up to you to integrate this in your own system. Typically by having a mobile app which acts as DFU master (based on Nordic DFU libraries) and which is also integrated with your cloud service.