RE: Serial DFU and Application with SoftDevice Issues

figsys100 — Fri, 03 Jan 2020 16:44:57 GMT

Hi Hung,

That did it! Added the SoftDevice hex file to my SES project file (and removed the mbr) as in the BLE DFU examples. I was under the impression that you did not need a SD pre-update but can work around this. Also had to set sd-req and sd-id to 0xCA.

Thanks for the quick response!

Gary

RE: Serial DFU and Application with SoftDevice Issues

Hung Bui — Fri, 03 Jan 2020 09:29:15 GMT

Hi Gary,

I think I know what's wrong here. The serial DFU bootloader doesn't contain a softdevice. It's made to work with just the MBR.

If you want to update an application that requires the softdevice, you would need to flash the softdevice in addition, when you flash the bootloader.

RE: Serial DFU and Application with SoftDevice Issues

figsys100 — Thu, 02 Jan 2020 22:21:14 GMT

Hi Hung,

1. I can DFU a simple application (blinky SES w/mbr) onto my hardware with no issues.

2. I get same results with a simple application with SD (ble_app_blinky_pca10056_s140). sd-req and sd-id set to 0x00 Image loads with no errors but does not run.

3. When I change sd-req and sd-id to 0xCA (one or both) I get the following error : Extended Error 0x07: The array of supported SoftDevices for the update does not contain the FWID of the current SoftDevice.

C:\junk\test>nrfutil -v dfu serial -pkg testB.zip -p COM22 -b 115200 -fc 0

Traceback (most recent call last):
  File "C:\Python38-32\Scripts\nrfutil-script.py", line 11, in <module>
    load_entry_point('nrfutil==6.0.1', 'console_scripts', 'nrfutil')()
  File "c:\python38-32\lib\site-packages\click\core.py", line 764, in __call__
    return self.main(*args, **kwargs)
  File "c:\python38-32\lib\site-packages\click\core.py", line 717, in main
    rv = self.invoke(ctx)
  File "c:\python38-32\lib\site-packages\click\core.py", line 1137, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "c:\python38-32\lib\site-packages\click\core.py", line 1137, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "c:\python38-32\lib\site-packages\click\core.py", line 956, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "c:\python38-32\lib\site-packages\click\core.py", line 555, in invoke
    return callback(*args, **kwargs)
  File "c:\python38-32\lib\site-packages\nordicsemi\__main__.py", line 1034, in serial
    do_serial(package, port, connect_delay, flow_control, packet_receipt_notification, baud_rate, serial_number, True,
  File "c:\python38-32\lib\site-packages\nordicsemi\__main__.py", line 949, in do_serial
    dfu.dfu_send_images()
  File "c:\python38-32\lib\site-packages\nordicsemi\dfu\dfu.py", line 119, in dfu_send_images
    self._dfu_send_image(self.manifest.softdevice)
  File "c:\python38-32\lib\site-packages\nordicsemi\dfu\dfu.py", line 95, in _dfu_send_image
    self.dfu_transport.send_init_packet(data)
  File "c:\python38-32\lib\site-packages\nordicsemi\dfu\dfu_transport_serial.py", line 256, in send_init_packet
    self.__execute()
  File "c:\python38-32\lib\site-packages\nordicsemi\dfu\dfu_transport_serial.py", line 421, in __execute
    self.__get_response(DfuTransportSerial.OP_CODE['Execute'])
  File "c:\python38-32\lib\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.

4. Looking at the hex dump or using nRF Connect GUI tool the memory map looks as expected.

Can anyone provide an actual script to generate DFU image for an example using SoftDevice (e.g., ble_app_blinky_pca10056_s140 )

Thanks!

RE: Serial DFU and Application with SoftDevice Issues

Hung Bui — Thu, 02 Jan 2020 16:24:13 GMT

Hi Gary,

Have you modified the bootloader ?

I don't think you can call nrfutil settings display with a hex dump from the chip. The function only works with the generated bootloader setting hex (or the hex that cover the exact part of bootloader setting).

Have you tried to test DFU only the application, not with the softdevice ?
I'm not sure why you set the sd-req and sd-id to 0x00. You would need to use the correct id of the softdevice as shown by nrfutil pkg generate --help

When you take the hex dump, do you see the application copied to the correct location ?