This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Reset in Nordic Connect versus DFU Library (iOS)

I have a weird situation with uploads of firmware:

- pushing a firmware via Nordic Connect works fine

- pushing a firmware via the library, interrupting it by killing the app or letting it go to sleep, and restarting the push on the currently-in-dfu-mode device works fine (*)

- pushing a firmware via the library, letting run properly to completion, systematically blocks the device until I reset it (on my device, via a electrical short-circuit of a component, which I suppose activates a given set of pins on the nRF52832... I'm not the electrical engineer, only the iOS dev)

What this set of data makes me wonder is: is there a command that might be sent by the Nordic Connect application and the library when proceeding with a previously interrupted firmware upload that forces a reset of the chip, which does not by default happen with a "problem-less" upload? If so, how do I ask the system to do this reset?

Since the boards are already in preproduction, a "reset" physical button is not an option for us...



_____________

(*) (apart from the fact I need to do it manually or via some hand-written code storing the DFU-mode name, which looks like DFUxxxxxx, x in [0-9], but I asked a question specifically about that)