RE: nRF52840 Dongle + nRF Connect v.3.3.0 [Programmer] + SEGGER Embedded Studio v.4.30C

teslabox — Wed, 08 Jan 2020 10:08:34 GMT

Hello Einar,

Thank you for your reply and advice.

Finally it turned out that the errors occurred after programming in nRF Connect Programmer exists because the SDFU is not visible/does not exist after programming but nRF Connect Programmer is still looking for SDFU which in fact is not needed after programming.

Everything work OK for now. The occurred errors are ignored by me.

Best regards,

Jakub

RE: nRF52840 Dongle + nRF Connect v.3.3.0 [Programmer] + SEGGER Embedded Studio v.4.30C

Einar Thorsrud — Mon, 06 Jan 2020 11:32:31 GMT

Hi Jakub,

The error message you posted is expected and is not caused by a failure during programming. The failure is after programming when nRF Connect Programmer attempts to read the device again. Since the new firmware you programmed does not contain the DFU trigger library, nRF Connect Programmer cannot put it in DFU mode. Thus giving you the error. However, if you look a bit earlier in the log I suspect you would get a log similar to this, including a line stating "DFU for SoftDevice completed successfully!".

2020-01-06T10:33:10.219Z INFO Parsing HEX file: C:\Users\eith\SDK\nRF5_SDK_16.0.0_98a08e2\examples\ble_peripheral\ble_app_blinky\hex\ble_app_blinky_pca10059_s140.hex
2020-01-06T10:33:10.243Z INFO File was last modified at 10/18/2019, 7:06:05 PM
2020-01-06T10:33:10.343Z INFO Data block: 0x00000000-0x00000B00 (0x00000B00 bytes long)
2020-01-06T10:33:10.343Z INFO Data block: 0x00001000-0x00026598 (0x00025598 bytes long)
2020-01-06T10:33:10.344Z INFO Data block: 0x00027000-0x0002CC8C (0x00005C8C bytes long)
2020-01-06T10:33:10.346Z INFO SoftDevice detected, id 0xCA (S140 v7.0.1)
2020-01-06T10:33:15.619Z INFO Does not need to be reloaded: C:\Users\eith\SDK\nRF5_SDK_16.0.0_98a08e2\examples\ble_peripheral\ble_app_blinky\hex\ble_app_blinky_pca10059_s140.hex
2020-01-06T10:33:15.624Z INFO SdReq for SoftDevice is set as 0x00.
2020-01-06T10:33:15.625Z INFO Hash is generated by SHA256
2020-01-06T10:33:15.625Z INFO Hash is generated by SHA256
2020-01-06T10:33:15.628Z INFO Performing DFU. This may take a few seconds
2020-01-06T10:33:15.648Z INFO DFU procedure starts. This may take a few seconds.
2020-01-06T10:33:24.046Z INFO DFU for SoftDevice completed successfully!
2020-01-06T10:33:24.046Z INFO 1 dfu package(s) left.
2020-01-06T10:33:24.046Z INFO Waiting for device
2020-01-06T10:33:24.060Z INFO DFU procedure starts. This may take a few seconds.
2020-01-06T10:33:27.228Z INFO DFU for Application completed successfully!
2020-01-06T10:33:27.229Z INFO 0 dfu package(s) left.
2020-01-06T10:33:27.229Z INFO Waiting for device
2020-01-06T10:33:32.230Z ERROR Reopen device failed: Timeout while waiting for device C6A33869C345 to be attached and enumerated
2020-01-06T10:33:32.230Z INFO Nordic DFU Trigger Interface was not found.Please physically reset device.
2020-01-06T10:33:32.234Z ERROR Device not found due to failure during DFU
2020-01-06T10:33:32.243Z INFO Target device closed.

The error message tells you to push the sideways reset button, which is how you put the dongle in DFU mode again so that it can be used with the nRF Connect programmer.

I suspect you will see that the dongle does work after programming if you try to connect to it via BLE. Please note that despite the name, the ble_app_blinky example does not blink by itself. You need to connect via BLE to control it in order to change the LED state.

Einar