Thingy GCC App goes straight to DFU

RE: Thingy GCC App goes straight to DFU

jublin — Fri, 03 Nov 2017 06:35:55 GMT

Thanks for the help. Turns out I was running something out of memory with another service and afterwards trying to load up the DFU service.

RE: Thingy GCC App goes straight to DFU

Hung Bui — Thu, 02 Nov 2017 16:10:28 GMT

You can choose to flash the softdevice or not if your application need the softdevice or not. My suggestion is to test first with blink an LED for example, make sure it works. Then you can try something else. If it doesn't work, you need to debug it and see where in the code cause the problem.

RE: Thingy GCC App goes straight to DFU

jublin — Thu, 02 Nov 2017 15:56:37 GMT

I've tried Application only, App + Softdevice, and Softdevice + my own compiled/signed bootloader, making a dfu package of the application, None of them seem to run.

Stock firmware + signed dfu application package doesn't load because of a invalid FW version.

RE: Thingy GCC App goes straight to DFU

jublin — Thu, 02 Nov 2017 15:00:57 GMT

So would I JUST have the application, or application + softdevice?

RE: Thingy GCC App goes straight to DFU

Hung Bui — Thu, 02 Nov 2017 12:20:03 GMT

No, it's not a bug. It's just the bootloader checks CRC and find that the new application you flash didn't match with the CRC it stores. I would suggest is to erase the bootloader and flash your application. You can flash the bootloader back later after you done with modifying your firmware. Then you can update your firmware using bootloader (OTA update) or writing to bootloader setting to match the CRC.