Secure Bootloader fails to start its application on SDK 15

RE: Secure Bootloader fails to start its application on SDK 15

Einar Thorsrud — Fri, 08 Jun 2018 06:24:59 GMT

The sensible way to understand what is going on is to use a debugger to understand what happens in the bootloader. Do you use the debug version of the bootloader also in the case there the bootloader does not start the application? If no, can you switch to the debug version? Then, please upload the log to this case (same as can be seen in the non-relevant screenshot that you uploaded in the original question). Also, can you halt the application and see what state the application is in when it should have started the application? Is it in an error handler? What is the value of the stack pointer?

RE: Secure Bootloader fails to start its application on SDK 15

Prakash Rajiah — Thu, 07 Jun 2018 12:48:59 GMT

Oh sorry.!!! The bootloader program stops and freeze there and doesnt advertise nor starting application. the example was just a blinky example in the SDK 15. It was expected to blink its LEDs. The example works when i debug it in normal via debugger.

RE: Secure Bootloader fails to start its application on SDK 15

Einar Thorsrud — Thu, 07 Jun 2018 12:18:56 GMT

Hi,

Everything looks fine from the log in the screenshot, indicating that the application should have been started.

How have you verified that the device advertises as "DfuTarg"? Is the device really in bootloader DFU mode? The reason I ask is that for example iOS tends to cache the device name of peer devices and use the old name for some time even if it has changed. Have you verified with a debugger that the application is not started?