So, open up the log file and see: 09:25:58,594 ERROR Failed to RESET a dongle Looking at file, I see mention of a log file:
Docker leanote upgrade#
In the upgrade folder (C:\Program Files (x86)\Bluetooth SIG\PTS Firmware Upgrade Software) I went searching for the real firmware, not just the bootloader. I also tried with connectivity_4.1.4_usb_with_s132_5.1.0.hex from: I originally had the standard firmware on the nrf52840 dongle that runs with nrf connect app.
Docker leanote update#
If I put the dongle into this same update mode and tried their gui tool, it actually failed at the same place, same message. If you unpack the zip it's got a manifest file that shows this is just a bootloader anyway, not the actual PTS code. Failed to execute script _main_This fails with the helpful message:Īpparently this InvalidObject typically means signature mismatch? EIther way, it continued to fail. This fails with the helpful message: Traceback (most recent call last):įile "nordicsemi\_main_.py", line 1537, in įile "site-packages\click\core.py", line 764, in _call_įile "site-packages\click\core.py", line 717, in mainįile "site-packages\click\core.py", line 1137, in invokeįile "site-packages\click\core.py", line 956, in invokeįile "site-packages\click\core.py", line 555, in invokeįile "nordicsemi\_main_.py", line 1056, in serialįile "nordicsemi\_main_.py", line 970, in do_serialįile "nordicsemi\dfu\dfu.py", line 123, in dfu_send_imagesįile "nordicsemi\dfu\dfu.py", line 95, in _dfu_send_imageįile "nordicsemi\dfu\dfu_transport_serial.py", line 250, in send_init_packetįile "nordicsemi\dfu\dfu_transport_serial.py", line 244, in try_to_recoverįile "nordicsemi\dfu\dfu_transport_serial.py", line 421, in _executeįile "nordicsemi\dfu\dfu_transport_serial.py", line 505, in _get_response The firmware update tool has a folder in it with a DFU file in it, which you would normally flash by pressing the side-button on the dongle to put it into update mode - it then has it's led pulse red and it comes up as a COM port, you then run: C:\Program Files (x86)\Bluetooth SIG\PTS Firmware Upgrade Software\tools>nrfutil.exe dfu serial -p COM6 -pkg nrf52840_xxaa_default_v5.zip
This private key change blocks the DFU from allowing the standard PTS firmware upgrade tool from just being able to flash straight onto it. It turns out this is basically just a normal nrf52840 dongle in a plastic case with a copy of the nordic bootloader with their own private key in it. Normally you need to buy this dongle then flash the PTS firmware onto it:
Unfortunately it was out of stock on all of them, for about 4 months. This is normally stocked by all the online electronics distributers element14, digikey, mouser, arrow etc. So we need a new BLE Dongle - they now only support the Laird Connectivity | 451-00004
Docker leanote Bluetooth#
We had the legacy PTS dongle provided by Bluetooth SIG, however I found it only supports testing devices up the BLE 4.2 At work we needed to certify a BLE device recently.
0 kommentar(er)
