nRFConnect DFU upload fails, Thingy 52 new 2.0 version of firmware

[Rando]

Howdy!

Before I break out the Segger JTAG, I thought I would try nRF Connect DFU upload. As I had a failure on OTA update there was not issue about being in DFU mode. However when I attempt upload the *.zip file for 2.0 I get this error...

See log below.

nRF Connect, 2017-10-05 ThingyDfu (E7:7C:E3:9E:C0:D4) V 14:37:32.913 [DFU] DFU service started V 14:37:32.914 [DFU] Opening file... I 14:37:32.950 [DFU] Image file opened (307776 bytes in total) D 14:37:32.950 [DFU] wait(1000) D 14:37:33.951 [DFU] wait(1000) V 14:37:34.966 [DFU] Connecting to DFU target... D 14:37:34.967 [DFU] gatt = device.connectGatt(autoConnect = false) I 14:37:34.967 [DFU] Connected to E7:7C:E3:9E:C0:D4 V 14:37:34.967 [DFU] Discovering services... D 14:37:34.967 [DFU] gatt.discoverServices() I 14:37:34.967 [DFU] Services discovered W 14:37:34.967 [DFU] Sending system components D 14:37:35.001 [DFU] wait(1000) V 14:37:35.999 [DFU] Requesting new MTU... D 14:37:35.999 [DFU] gatt.requestMtu(517) V 14:37:36.067 [DFU] Enabling notifications for 8ec90001-f315-4f60-9fb8-838830daea50 D 14:37:36.067 [DFU] gatt.setCharacteristicNotification(8ec90001-f315-4f60-9fb8-838830daea50, true) D 14:37:36.067 [DFU] gatt.writeDescriptor(00002902-0000-1000-8000-00805f9b34fb, value=0x01-00) I 14:37:36.104 [DFU] Data written to descr.8ec90001-f315-4f60-9fb8-838830daea50, value (0x): 01-00 V 14:37:36.104 [DFU] Notifications enabled for 8ec90001-f315-4f60-9fb8-838830daea50 A 14:37:36.104 [DFU] Notifications enabled D 14:37:36.107 [DFU] wait(1000) V 14:37:37.124 [DFU] Writing to characteristic 8ec90001-f315-4f60-9fb8-838830daea50 D 14:37:37.124 [DFU] gatt.writeCharacteristic(8ec90001-f315-4f60-9fb8-838830daea50) I 14:37:37.143 [DFU] Data written to 8ec90001-f315-4f60-9fb8-838830daea50, value (0x): 06-01 I 14:37:37.177 [DFU] Notification received from 8ec90001-f315-4f60-9fb8-838830daea50, value (0x): 60-06-01-00-01-00-00-8B-00-00-00-DB-3C-45-EA A 14:37:37.177 [DFU] Command object info received (Max size = 256, Offset = 139, CRC = EA453CDB) A 14:37:37.177 [DFU] Received CRC match Init packet V 14:37:37.177 [DFU] Writing to characteristic 8ec90001-f315-4f60-9fb8-838830daea50 D 14:37:37.177 [DFU] gatt.writeCharacteristic(8ec90001-f315-4f60-9fb8-838830daea50) I 14:37:37.242 [DFU] Data written to 8ec90001-f315-4f60-9fb8-838830daea50, value (0x): 04 I 14:37:37.242 [DFU] Notification received from 8ec90001-f315-4f60-9fb8-838830daea50, value (0x): 60-04-0B-05 E 14:37:37.242 [DFU] Remote DFU error: REMOTE DFU EXTENDED ERROR E 14:37:37.242 [DFU] Details: FW version failure (Code = 5) V 14:37:37.242 [DFU] Disconnecting... D 14:37:37.246 [DFU] gatt.disconnect() I 14:37:37.295 [DFU] Disconnected D 14:37:37.295 [DFU] gatt.refresh() (hidden) D 14:37:37.295 [DFU] gatt.close() D 14:37:37.295 [DFU] wait(600)

As you can see, the error, "Remote DFU error: etc." about the FW version is seen.

I realize 2.0 is new, wondering if the upload facility can't handle the 1.1 to 2.0 version upgrade information???

R.

[Bjørn Kvaale]

Have you tried using an Over The Air DFU using the Nordic Thingy app for iOS and Android? Could you see if that works? What is the reason you want to use nRFConnect instead of the Thingy app to do the DFU? This link might be helpful too.

[Rando]

I lost patience, and just used the Segger JTAG to flash the 2.0 software to the Thingy.

I've been transmitting temperature from my fridge for a couple of days, however the cold finally got to it this morning. I'm, delighted to say, been very happy with the performance so far!

I was using the nRFConnect (I think) because I was following an on-line tutorial on how to update the code using OTA, my thoughts were I might want to spin my own nRF dev-board, and would want my users to be able to update via OTA. My thought was to test the most generalizable solution possible.

Thanks so much for the consideration of your response!

R.