nrfutil v6.1.0 dfu ble fail with connectivity firmware v4.1.2

RE: nrfutil v6.1.0 dfu ble fail with connectivity firmware v4.1.2

Edvin — Wed, 13 Jan 2021 15:08:58 GMT

You did use the bootloader from the nrf52840 dongle programming tutorial? If not, try to use it (attached here: devzone.nordicsemi.com/.../0045.pca10059_5F00_bootloader.zip)

If you can confirm that this is the bootloader you programmed on the dongle, looking into your log:

Is the dongle and the target device properly powered? And are they well within range?

And do you restart the DFU process manually after the error code 12290? And is there something missing in the log at the line saying "..."? Or did nrfutil print this?

BR,

Edvin

RE: nrfutil v6.1.0 dfu ble fail with connectivity firmware v4.1.2

jacksong — Tue, 12 Jan 2021 12:12:35 GMT

Unfortunately, it did not resolve.

step1, via jlink erase dongle

step2, via jlink program dongle with bootloader

step3, PC plug in dongle, Enumerate into nRF52 SDFU USB(COM4)

step4, open nRF Connect for Desktop->Programmer, select COM3, and upload connectivity_4.1.2_usb_with_s132_5.1.0.hex. hit "Write"

COM port become nRF Connect USB CDC ACM (COM3)

It seems that the programmer operation is ok , but still FAIL when use nrfutil dfu ble

RE: nrfutil v6.1.0 dfu ble fail with connectivity firmware v4.1.2

Edvin — Mon, 11 Jan 2021 11:19:56 GMT

So did you remove the pre-flashed bootloader from the Dongle?

If so, please read the section "Adapting firmware to set REGOUT0 properly" and from the nRF52840 dongle programming tutorial.

This is usually done in the pre-flashed bootloader. Perhaps you can try to add the bootloader back in, to see if that is the issue you are encountering.

I tested (without an external programmer, but programming via nRF Connect for Desktop -> Programmer), and I didn't see the issues that you are seeing. Perhaps they are caused by resets due to incorrect voltage supply.

Best regards,

Edvin

RE: nrfutil v6.1.0 dfu ble fail with connectivity firmware v4.1.2

jacksong — Mon, 11 Jan 2021 07:51:05 GMT

Sorry i didn't make it clear, the log I uploaded was generated by manually inputting instructions, not a batch. I program it via a external jlink swd first, then, plug in dongle which seen as COM3.

No need to doubt operation, as I have repeatedly confirmed that it is okay many times.

RE: nrfutil v6.1.0 dfu ble fail with connectivity firmware v4.1.2

Edvin — Mon, 11 Jan 2021 07:34:30 GMT

I am a bit confused about your setup. Are you using the nRF52 Dongle as your connecitivity device? The reason I ask is because the dongle doesn't have a programmer, so you can't run this command:

PS C:\Users\Administrator> nrfjprog -f NRF52 --program "C:\Python38\Lib\site-packages\pc_ble_driver_py\hex\sd_api_v5\connectivity_4.1.2_usb_with_s132_5.1.0.hex" --chiperase

If so, then the dongle is not the device that will be programmed. What device is your COM3? What is it programmed with, and how did you program it?

Unless you have soldered on a programming header, and used an external programmer on your nRF52 Dongle, then the dongle is not programmed with "C:\Python38\Lib\site-packages\pc_ble_driver_py\hex\sd_api_v5\connectivity_4.1.2_usb_with_s132_5.1.0.hex".

Best regards,

Edvin

RE: nrfutil v6.1.0 dfu ble fail with connectivity firmware v4.1.2

jacksong — Sat, 09 Jan 2021 07:59:07 GMT

Hi,

Thanks for your reply

I tested it today. as you mentioned above, I use nrfjprog flash connectivity_4.1.2 firmware, all other test environment remain the same.

The result is barely succeeded, many errors be reported in the process. then, I tried again several times , all of result are like first one, or wrose!

btw guys, ble connect failure originally mentioned in this post may be due to target board is run in "Nordic_Buttonless" instead of "DfuTarg"

post some useful logs and attachment

PS C:\Users\Administrator> nrfjprog -f NRF52 --program "C:\Python38\Lib\site-packages\pc_ble_driver_py\hex\sd_api_v5\connectivity_4.1.2_usb_with_s132_5.1.0.hex"  --chiperase
Parsing image file.
Erasing user available code and UICR flash areas.
Applying system reset.
Checking that the area to write is not protected.
Programming device.
PS C:\Users\Administrator> nrfjprog -f NRF52 --verify "C:\Python38\Lib\site-packages\pc_ble_driver_py\hex\sd_api_v5\connectivity_4.1.2_usb_with_s132_5.1.0.hex"
Parsing image file.
Verifying programming.
Verified OK.
PS C:\Users\Administrator> nrfutil dfu ble -pkg "E:\nrfutil_DFU_test\ble_app_buttonless_dfu_without_bonds_s132.zip" -ic NRF52 -n "Nordic_Buttonless" -p COM3
...
PS C:\Users\Administrator> nrfutil dfu ble -pkg "E:\nrfutil_DFU_test\ble_app_buttonless_dfu_without_bonds_s132.zip" -ic NRF52  -p COM3
No target selected. Default device name: DfuTarg is used.
  [########----------------------------]   23%  00:00:53
...
  File "c:\python38\lib\site-packages\pc_ble_driver_py\ble_driver.py", line 103, in wrapper
    raise NordicSemiException(
pc_ble_driver_py.exceptions.NordicSemiException: Failed to ble_gattc_write. Error code: 12290
PS C:\Users\Administrator> nrfutil dfu ble -pkg "E:\nrfutil_DFU_test\ble_app_buttonless_dfu_without_bonds_s132.zip" -ic NRF52  -p COM3
No target selected. Default device name: DfuTarg is used.
  [###############################-----]   87%  00:00:02
...
  File "c:\python38\lib\site-packages\pc_ble_driver_py\ble_driver.py", line 103, in wrapper
    raise NordicSemiException(
pc_ble_driver_py.exceptions.NordicSemiException: Failed to ble_gattc_write. Error code: 12290
PS C:\Users\Administrator> nrfutil dfu ble -pkg "E:\nrfutil_DFU_test\ble_app_buttonless_dfu_without_bonds_s132.zip" -ic NRF52  -p COM3
No target selected. Default device name: DfuTarg is used.
...
  File "c:\python38\lib\site-packages\pc_ble_driver_py\ble_adapter.py", line 222, in att_mtu_exchange
    raise NordicSemiException(
pc_ble_driver_py.exceptions.NordicSemiException: MTU exchange request failed. Common causes are: missing att_mtu setting in ble_cfg_set, different config tags used in ble_cfg_set and connect.
PS C:\Users\Administrator> nrfutil dfu ble -pkg "E:\nrfutil_DFU_test\ble_app_buttonless_dfu_without_bonds_s132.zip" -ic NRF52  -p COM3
No target selected. Default device name: DfuTarg is used.
  [##################################--]   95%  00:00:00

    File "c:\python38\lib\site-packages\pc_ble_driver_py\ble_driver.py", line 103, in wrapper
    raise NordicSemiException(
pc_ble_driver_py.exceptions.NordicSemiException: Failed to ble_gattc_write. Error code: 12290
PS C:\Users\Administrator> nrfutil dfu ble -pkg "E:\nrfutil_DFU_test\ble_app_buttonless_dfu_without_bonds_s132.zip" -ic NRF52  -p COM3
No target selected. Default device name: DfuTarg is used.
...
  File "c:\python38\lib\site-packages\pc_ble_driver_py\ble_adapter.py", line 222, in att_mtu_exchange
    raise NordicSemiException(
pc_ble_driver_py.exceptions.NordicSemiException: MTU exchange request failed. Common causes are: missing att_mtu setting in ble_cfg_set, different config tags used in ble_cfg_set and connect.
PS C:\Users\Administrator> nrfutil dfu ble -pkg "E:\nrfutil_DFU_test\ble_app_buttonless_dfu_without_bonds_s132.zip" -ic NRF52  -p COM3
No target selected. Default device name: DfuTarg is used.
...
  File "c:\python38\lib\site-packages\pc_ble_driver_py\ble_adapter.py", line 489, in write_req
    return result["status"]
TypeError: 'NoneType' object is not subscriptable
PS C:\Users\Administrator> nrfutil dfu ble -pkg "E:\nrfutil_DFU_test\ble_app_buttonless_dfu_without_bonds_s132.zip" -ic NRF52  -p COM3
No target selected. Default device name: DfuTarg is used.
  [####################################]  100%
Device programmed.

devzone.nordicsemi.com/.../nrfutil_5F00_program_5F00_4.1.2usb_5F00_FW_5F00_hex-dfu-success-after-Several_5F00_times-fail-TEST2.log

There must be something wrong, maybe compatibility as issue can't reproduce in your side, i tried my best to solve it(tried to set win10 system time resolution as 1ms, etc), but all in vain.

Please let me know if there is research progress on this issue, I am glad to test the fix

RE: nrfutil v6.1.0 dfu ble fail with connectivity firmware v4.1.2

Edvin — Fri, 08 Jan 2021 15:22:55 GMT

Hello,

Thank you for reporting. I see that nrfutil is missing the connectivity FW for the dongle. I will report this to our developers, and also make them aware of the github issue.

I see that I answered in the other thread that you link to as well, but nothing has happened from our side as far as I can tell. I will notify them about this as well.

There are some ways to work around this bug.

The simplest one is to open the folder:

C:\Users\<User>\AppData\Local\Programs\Python\Python38-32\Lib\site-packages\pc_ble_driver_py\hex\sd_api_v5 (or where you have installed pc_ble_driver_py, probably through Python pip).

Then copy the file connectivity_4.1.2_usb_with_s132_5.1.0_dfu_pkg.zip, and rename your copy:

connectivity_4.1.1_usb_with_s132_5.1.0_dfu_pkg.zip

After that you should be able to use the -f command in nrfutil towards the dongle. Please note that you may need to do it two times, as some times the nRF52 Dongle changes COM port when a new FW is received.

Alternatively, you can flash the file connectivity_4.1.2_usb_with_s132_5.1.0.hex from the same folder to the nRF52 Dongle using the nRF Connect for Desktop -> Programmer app.

After that you can perform the nrfutil command without the -f flag. I tested this now, and it works, as long as the softdevice version is the same as nrfutil expects it to be.

Again, thank you for reporting. I will take it forward to our R&D team.

Best regards,

Edvin