DFU Update of NRF52840

[Andreas48752]

Hello,

I need some help updating NRF52840.
This is my first project and I have a working application which uses Softdevice 140. I would like to update it with usb-serial in the field.

4. I generated my update file with following command:

nrfutil pkg generate --hw-version 52 --key-file C:\vault\priv.pem --sd-id 0xb6 --softdevice files\s140_nrf52_6.1.1_softdevice.hex --sd-req 0x00 --application-version 0xFF --application App_s140.hex files\dfu_update.zip

5. Using this command line in order to update: 

nrfutil dfu usb-serial -pkg files\dfu_update.zip -p COM20

If I erease the chip and only upload the bootloader and try to update it succeeds. If i try the update again I get following error:

Extended Error 0x07: The array of supported SoftDevices for the update does not contain the FWID of the current SoftDevice.

I think this is because SD 6.1.1 is already on the target on seconds update. How do I configure the update.zip to accept none softdevice or 6.1.1 on the target?

Can anyone help me point in the right direction?

Thanks, Andreas

[Simon]

Try setting --sd-req to 0xB6 (s140_nrf52_6.1.0).

Best regards,

Simon

[Andreas48752]

Thanks for the reply.
If I do this the update succeeds if softdevice is already on the target but fails if if the target is blank. I want an update file where both ways (blank target and target with SD 6.1.1) is working. 

[Simon]

Try defining both sd-req: --sd-req 0x00, 0xB6

[Andreas48752]

As you suggested, I made the update file with following command:

nrfutil pkg generate --hw-version 52 --key-file C:\vault\priv.pem --sd-id 0xb6 --softdevice files\s140_nrf52_6.1.1_softdevice.hex --application-version 0xFF --application \s140\ses\Output\Debug\Exe\App_s140.hex --sd-req "0x00,0xb6" files\dfu_update_s140.zip

But it does still not work:

Traceback (most recent call last):
  File "C:\Users\Andreas\AppData\Roaming\Python\Scripts\nrfutil-script.py", line 11, in <module>
    load_entry_point('nrfutil==5.2.0', 'console_scripts', 'nrfutil')()
  File "C:\Users\Andreas\AppData\Roaming\Python\Python27\site-packages\click\core.py", line 764, in __call__
    return self.main(*args, **kwargs)
  File "C:\Users\Andreas\AppData\Roaming\Python\Python27\site-packages\click\core.py", line 717, in main
    rv = self.invoke(ctx)
  File "C:\Users\Andreas\AppData\Roaming\Python\Python27\site-packages\click\core.py", line 1137, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "C:\Users\Andreas\AppData\Roaming\Python\Python27\site-packages\click\core.py", line 1137, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "C:\Users\Andreas\AppData\Roaming\Python\Python27\site-packages\click\core.py", line 956, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "C:\Users\Andreas\AppData\Roaming\Python\Python27\site-packages\click\core.py", line 555, in invoke
    return callback(*args, **kwargs)
  File "C:\Users\Andreas\AppData\Roaming\Python\Python27\site-packages\nordicsemi\__main__.py", line 1001, in usb_serial
    timeout)
  File "C:\Users\Andreas\AppData\Roaming\Python\Python27\site-packages\nordicsemi\__main__.py", line 956, in do_serial
    dfu.dfu_send_images()
  File "C:\Users\Andreas\AppData\Roaming\Python\Python27\site-packages\nordicsemi\dfu\dfu.py", line 121, in dfu_send_images
    self._dfu_send_image(self.manifest.softdevice)
  File "C:\Users\Andreas\AppData\Roaming\Python\Python27\site-packages\nordicsemi\dfu\dfu.py", line 97, in _dfu_send_image
    self.dfu_transport.send_init_packet(data)
  File "C:\Users\Andreas\AppData\Roaming\Python\Python27\site-packages\nordicsemi\dfu\dfu_transport_serial.py", line 256, in send_init_packet
    self.__execute()
  File "C:\Users\Andreas\AppData\Roaming\Python\Python27\site-packages\nordicsemi\dfu\dfu_transport_serial.py", line 421, in __execute
    self.__get_response(DfuTransportSerial.OP_CODE['Execute'])
  File "C:\Users\Andreas\AppData\Roaming\Python\Python27\site-packages\nordicsemi\dfu\dfu_transport_serial.py", line 502, in __get_response
    raise NordicSemiException('Extended Error 0x{:02X}: {}'.format(resp[3], data))
pc_ble_driver_py.exceptions.NordicSemiException: Extended Error 0x07: The array of supported SoftDevices for the update does not contain the FWID of the current SoftDevice.

I first made an update with ereased target, that worked. After that I entered bootloader (with pin at startup) and tried a second update that failed.

[Simon]

I tested this myself, and I couldn't figure out how to do it using the same command.

Is there a reason you have to use the same packet (generated with the same command) two times in a row? 

Couldn't you just use the following command on the first update:

nrfutil pkg generate --hw-version 52 --key-file priv.pem --sd-id 0xb6 --softdevice s140_nrf52_6.1.1_softdevice.hex --sd-req 0x00 --application-version 0xFF --application ble_application1.hex dfu_update1.zip

Then, on the second update, you use this command:

nrfutil pkg generate --hw-version 52 --key-file priv.pem --sd-req 0xB6 --application-version 0xFF --application BLE_application2.hex dfu_update2.zip

Could you tell me your end goal? Then it is easier to find a solution to your problem. 

However, if you need to use the same command (dfu packet) for both updates, I can look into it. I can ask the developers how to go about this.

Best regards,

Simon

[Andreas48752]

Thanks for the verification that this is not possible.

Well the goal was to use one update file in production and field update. I could make two different files but that would at least require a little bit more administrative effort which I would have liked to avoid if possible. If it cannot be done, I can live with it...

[Simon]

A workaround for this is to modify the bootloader itself, where the validation happens. Take a look at the file nrf_dfu_ver_validation.c.

Best regards,

Simon