Thingy52 DFU fails with message "FW version failure (Code = 5)", using nrfutil and nRF Connect

RE: Thingy52 DFU fails with message "FW version failure (Code = 5)", using nrfutil and nRF Connect

Bjørn Kvaale — Wed, 31 Jan 2018 14:20:55 GMT

Hi Till, there's a makefile located under project\bootloader_secure\pca20020\armgcc in the Thingy FW. Is this fine or did you want to use the debug bootloader? I don't think you will need to modify the bootloader. This link explains what steps you need to take to make OTA-DFU work on the Thingy:52. In other words, this might be the reason you are getting the error.

RE: Thingy52 DFU fails with message "FW version failure (Code = 5)", using nrfutil and nRF Connect

Till — Tue, 30 Jan 2018 09:18:58 GMT

Hi Bjørn, thanks for your comment! Yes, that's correct. I've been flashing the device through the nRF52 DK without any problems. (It's great that the DK automatically switches to "passthrough" as soon as you connect an external device via SWD). If I find the time I'll compile the bootloader_secure - do you have a Makefile for armgcc, for compiling it on Linux? And secondly, I was going to investigate whether modifying the Bootloader to accept custom FW (as mentioned in my update above) makes a difference... could that be the culprit?

RE: Thingy52 DFU fails with message "FW version failure (Code = 5)", using nrfutil and nRF Connect

Bjørn Kvaale — Mon, 29 Jan 2018 12:26:20 GMT

So basically everything works fine when you do dfu via the nrf52 and swd cable, but not via OTA-DFU, right? You could try to use the pca20020_debug version of the bootloader_secure (see step B: Build the bootloader). This should avoid version checking. For more information on version checking, this link could be helpful.